Android: Difference between revisions

Line 35:

===OEM Locked Bootloaders===

In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found.

In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found. Some OEMs like Samsung are now completely blocking bootloader unlocking on their phones regardless of region.

===Blocking third-party programs===

Line 46:

In Android 9, Miracast was fully replaced with proprietrary Chromecast -protocol. Chromecast protocol includes signing key verification of both the Cast source and receiver device, meaning that since Android 9 it is no longer possible to cast high quality content to receivers which aren't signed by Google. This means that unlike AirPlay on Apple devices, there's no way to stream multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web |last=Weiske |first=Christian |date=2025-08-31 |title=Android/Lineage OS and Screen mirroring ("Cast") |url=https://p.cweiske.de/669 |url-status=live |archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 |archive-date=2025-08-31 |access-date=2025-08-31}}</ref>

=== '''Google delaying AOSP 16 QPR1 update without proper explanation''' ===

==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===

Google is releasing Android 16 QPR1 update for Pixel devices on September 3, 2025, normally AOSP will get QPR1 update in 24-48 hours after Pixel devices. But until now, there still no QPR1 update for AOSP. Google later told Android Authority said they will release the source code “in the coming weeks.” But they doesn't explain why they delaying QPR1 update for AOSP 16<ref>{{Cite news |last=Rahman |first=Mishaal |date=September 10, 2025 |title=Android 16 QPR1’s source code is nowhere to be found, but Google swears it’s coming |url=https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |url-status=live |archive-url=https://web.archive.org/web/20250911142548/https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |archive-date=September 11, 2025 |access-date=October 18, 2025 |work=Android Authority}}</ref>

@@ Line 35: / Line 35: @@
 ===OEM Locked Bootloaders===
 {{Main|Motorola}}
-In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found.
+In North America, many Android devices like phones or tablets will not allow consumers to unlock and do what they want to modify the software. Therefore, it has been incredibly difficult and nearly impossible to root and install custom ROMs on the device unless an exploit has been found. Some OEMs like Samsung are now completely blocking bootloader unlocking on their phones regardless of region.
 ===Blocking third-party programs===
@@ Line 46: / Line 46: @@
 In Android 9, Miracast was fully replaced with proprietrary Chromecast -protocol. Chromecast protocol includes signing key verification of both the Cast source and receiver device, meaning that since Android 9 it is no longer possible to cast high quality content to receivers which aren't signed by Google. This means that unlike AirPlay on Apple devices, there's no way to stream multichannel Hi-Fi audio on Android unless the receiver has a valid vendor signature.<ref>{{Cite web |last=Weiske |first=Christian |date=2025-08-31 |title=Android/Lineage OS and Screen mirroring ("Cast") |url=https://p.cweiske.de/669 |url-status=live |archive-url=https://web.archive.org/web/20250831142415/https://p.cweiske.de/669 |archive-date=2025-08-31 |access-date=2025-08-31}}</ref>
-=== '''Google delaying AOSP 16 QPR1 update without proper explanation''' ===
+==='''Google delaying AOSP 16 QPR1 update without proper explanation'''===
 Google is releasing Android 16 QPR1 update for Pixel devices on September 3, 2025, normally AOSP will get QPR1 update in 24-48 hours after Pixel devices. But until now, there still no QPR1 update for AOSP. Google later told Android Authority said they will release the source code “in the coming weeks.” But they doesn't explain why they delaying QPR1 update for AOSP 16<ref>{{Cite news |last=Rahman |first=Mishaal |date=September 10, 2025 |title=Android 16 QPR1’s source code is nowhere to be found, but Google swears it’s coming |url=https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |url-status=live |archive-url=https://web.archive.org/web/20250911142548/https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/ |archive-date=September 11, 2025 |access-date=October 18, 2025 |work=Android Authority}}</ref>