Android: Difference between revisions

(One intermediate revision by one other user not shown)

Line 39:

===Blocking third-party programs===

Starting at September 2026, third-party apps will no longer be able to install on a unmodified Android in Brazil, Indonesia, Singapore and Thailand without "verified identities"<ref>{{Cite web |last=Whitwam |first=Ryan |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |url-status=live |archive-url=https://web.archive.org/web/20250826032858/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=26 Aug 2025 |access-date=26 Aug 2025 |website=ArsTechnica}}</ref><ref>{{Cite web |date=26 Aug 2025 |title=Google's plan to end sideloading on Android |url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ |url-status=live |archive-url=https://web.archive.org/web/20250826161809/https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ |archive-date=26 Aug 2025 |access-date=26 Aug 2025 |website=XdaForums}}</ref>. The affected regions will expand globally in 2027. Devices without Google Mobile Service (GMS) or running a third-party ROM won't be affected. However it's hard for users to bypass/spoof [[Google Play Integrity API|Google Play Integrity]] to hide their ROM or root status to use utility apps such as most of banking apps<ref>{{Cite web |date=3 Apr 2022 |title=[Discussion] The root-and-mod-hiding/fingerprint-spoofing/keybox-stealing cat-and-mouse game |url=https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |url-status=live |archive-url=https://web.archive.org/web/20250823095950/https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |archive-date=23 Aug 2025 |access-date=26 Aug 2025 |website=XdaForums}}</ref>.

A [https://www.change.org/p/stop-google-from-limiting-apk-file-usage petition] has been started on change.org to try and stop this from happening. If you wish to keep the control of your mobile device, please sign it.

===Android Cast restricted to Google -signed receivers===

Line 47:

Line 45:

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 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>

==References==

[[Category:{{PAGENAME}}]]

@@ Line 39: / Line 39: @@
 ===Blocking third-party programs===
 {{Main|Google blocking sideloading of unverified Android apps}}
 Starting at September 2026, third-party apps will no longer be able to install on a unmodified Android in Brazil, Indonesia, Singapore and Thailand without "verified identities"<ref>{{Cite web |last=Whitwam |first=Ryan |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |url-status=live |archive-url=https://web.archive.org/web/20250826032858/https://arstechnica.com/gadgets/2025/08/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=26 Aug 2025 |access-date=26 Aug 2025 |website=ArsTechnica}}</ref><ref>{{Cite web |date=26 Aug 2025 |title=Google's plan to end sideloading on Android |url=https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ |url-status=live |archive-url=https://web.archive.org/web/20250826161809/https://xdaforums.com/t/googles-plan-to-end-sideloading-on-android.4756353/ |archive-date=26 Aug 2025 |access-date=26 Aug 2025 |website=XdaForums}}</ref>. The affected regions will expand globally in 2027. Devices without Google Mobile Service (GMS) or running a third-party ROM won't be affected. However it's hard for users to bypass/spoof [[Google Play Integrity API|Google Play Integrity]] to hide their ROM or root status to use utility apps such as most of banking apps<ref>{{Cite web |date=3 Apr 2022 |title=[Discussion] The root-and-mod-hiding/fingerprint-spoofing/keybox-stealing cat-and-mouse game |url=https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |url-status=live |archive-url=https://web.archive.org/web/20250823095950/https://xdaforums.com/t/discussion-the-root-and-mod-hiding-fingerprint-spoofing-keybox-stealing-cat-and-mouse-game.4425939/ |archive-date=23 Aug 2025 |access-date=26 Aug 2025 |website=XdaForums}}</ref>.
-A [https://www.change.org/p/stop-google-from-limiting-apk-file-usage petition] has been started on change.org to try and stop this from happening. If you wish to keep the control of your mobile device, please sign it.
 ===Android Cast restricted to Google -signed receivers===
@@ Line 47: / Line 45: @@
 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 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>
 ==References==
 <references />
 [[Category:{{PAGENAME}}]]