Google: Difference between revisions

Line 61:

On 25 August 2025, '''[[Google]]''' announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.<ref name=":0">{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260128013331/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=28 Jan 2026}}</ref><ref name=":1">{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20260119211509/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=19 Jan 2026}}</ref> This marks a significant change to Android's long-standing support for sideloading apps.

Devices without [[Google Mobile Services]] or running custom ROMs are exempt.<ref name=":22">{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}</ref> Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.<ref name=":2">{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}</ref><ref name=":3">{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}</ref>

Devices without [[Google Mobile Services]] or running [[wikipedia:List_of_custom_Android_distributions|custom ROMs]] are exempt.<ref name=":22">{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}</ref> Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.<ref name=":2">{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}</ref><ref name=":3">{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}</ref>

===Banning domain-blockers from Play Store===

Line 69:

===Pixel devices bricked due to confusing reasons===

Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or Fastboot, making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.

Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs, or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or [[wikipedia:Fastboot|Fastboot]], making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.

This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special "USB boot" bit flag set to 1. <ref>{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref>

@@ Line 61: / Line 61: @@
 On 25 August 2025, '''[[Google]]''' announced that starting in 2026 it will block the installation of Android apps from outside the Play Store unless the developer has verified their identity with Google. The policy will first roll out in Brazil, Indonesia, Singapore, and Thailand in September 2026, with global enforcement targeted for 2027.<ref name=":0">{{Cite web |last=Frey |first=Suzanne |date=25 Aug 2025 |title=A new layer of security for certified Android devices |url=https://android-developers.googleblog.com/2025/08/elevating-android-security.html |url-status=live |access-date=25 Aug 2025 |website=Android Developers Blog |archive-url=http://web.archive.org/web/20260128013331/https://android-developers.googleblog.com/2025/08/elevating-android-security.html |archive-date=28 Jan 2026}}</ref><ref name=":1">{{Cite web |last=Perez |first=Sarah |date=25 Aug 2025 |title=Google will require developer verification for Android apps outside the Play Store |url=https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |url-status=live |access-date=25 Aug 2025 |website=TechCrunch |archive-url=http://web.archive.org/web/20260119211509/https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store/ |archive-date=19 Jan 2026}}</ref> This marks a significant change to Android's long-standing support for sideloading apps.
-Devices without [[Google Mobile Services]] or running custom ROMs are exempt.<ref name=":22">{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}</ref> Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.<ref name=":2">{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}</ref><ref name=":3">{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}</ref>
+Devices without [[Google Mobile Services]] or running [[wikipedia:List_of_custom_Android_distributions|custom ROMs]] are exempt.<ref name=":22">{{Cite web |last=Anderson |first=Tim |date=2025-08-26 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |archive-url=https://web.archive.org/web/20250829170329/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |archive-date=2025-08-29 |access-date=2025-08-26 |website=The Register}}</ref> Critics argue this restricts user freedom, impacts independent developers, and may enable Google to block apps it disapproves of, such as ad-blockers, raising concerns about privacy and control over personal devices.<ref name=":2">{{Cite web |last=Anderson |first=Tim |date=26 Aug 2025 |title=Google kneecaps indie Android devs, forces them to register |url=https://www.theregister.com/2025/08/26/android_developer_verification_sideloading |url-status=live |access-date=26 Aug 2025 |website=The Register |archive-url=http://web.archive.org/web/20260119211440/https://www.theregister.com/2025/08/26/android_developer_verification_sideloading/ |archive-date=19 Jan 2026}}</ref><ref name=":3">{{Cite web |first= |date=26 Aug 2025 |title=Google will block sideloading of unverified Android apps starting next year |url=https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year |url-status=live |access-date=26 Aug 2025 |website=BleepingComputer |archive-url=http://web.archive.org/web/20250829215120/https://www.bleepingcomputer.com/forums/t/810335/google-will-block-sideloading-of-unverified-android-apps-starting-next-year/ |archive-date=29 Aug 2025}}</ref>
 ===Banning domain-blockers from Play Store===
@@ Line 69: / Line 69: @@
 ===Pixel devices bricked due to confusing reasons===
-Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or Fastboot, making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.
+Numerous Google Pixel phones have gotten bricked as a result of different use cases, such as accidentally switched slots, flashing custom ROMs, or downgrading the bootloader version of the device after an [[Anti-rollback/ARB for device firmware|Anti-Rollback (ARB)]] increment (accidentally or otherwise), or installing the June 2025 update.<ref>{{Cite web |last=Simons |first=Hadlee |date=2025-08-26 |title=Some Pixels are bricked and Google apparently won't help revive them |url=https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |url-status=live |archive-url=http://web.archive.org/web/20260108045933/https://www.androidauthority.com/google-pixel-phones-bricked-3591218/ |archive-date=8 Jan 2026 |access-date=2025-09-11 |website=Android Authority}}</ref> The device enters an emergency download state called Pixel ROM Recovery, which is a Google modification of Samsung's EUB mode on Exynos chipsets. In this mode, it refuses to enter Android recovery or [[wikipedia:Fastboot|Fastboot]], making it near impossible to restore the operating system on the device. The only way to fix it is to use Pixel ROM Recovery to boot a special, Google-signed recovery bootloader into RAM and flash a working version of Android from there.
 This recovery bootloader is just a regular bootloader as it appears in Google factory images, but with a special "USB boot" bit flag set to 1. <ref>{{Cite web |date=2025-08-11 |title=Pixel devices getting bricked / stuck in Pixel ROM Recovery after flashing AOSP-based builds with Android 15 QPR2 (BP1A.250305.019) |url=https://issuetracker.google.com/issues/402455330#comment19 |archive-url=http://web.archive.org/web/20260205112358/https://issuetracker.google.com/issues/402455330 |archive-date=5 Feb 2026}}</ref>