Google is the next Apple and you know it.

Google released Android on September 23, 2008. They promised a freedom from the Apple walled-garden for all users- developers and users alike. Sure, it was coming from humble beginnings and was nowhere near Apple's offerings, but it was maturing.

Fast forward to 2026. Android today has matured to a point where it beats Apple in certain statistics. But the freedom they promised... it has long since been taken away.

The shiny new features, Gemini EVERYWHERE. Wanna cook? Gemini! Do you want to do a simple search about spline reticulation? GEMINI! Some people love it, many hate it. But behind all the new AI integrations, they have been brewing the biggest anti-consumer scandal ever. And a massive disgrace to Open-Source, ever.

Common terminology to familiarize before continuing:

• Play Protect/Integrity: An API based hardware-backed attestation used by apps to detect device certification.


• Custom ROMs: Forks/Distributions of AOSP (Android Open Source Project) created by developers because Android is open source.


• Bootloader: Piece of software below the OS which locates the OS on your flash memory OR allows access to various low-level components written into the flash memory (vbmeta, dtbo, etc.)

ACT ONE:

OEM Unlocking (skip this if you are not interested in below OS level trust chains, but recommended to read to understand Google's practices)

In the past, there was no 'aggressive' attestation for apps when custom ROMs were mainstream. So bootloader unlocking was safe and no one would judge you for doing so.

Android 4.4, 2013. Verified Boot. Not a big problem because bootloader unlocking was incredibly sparse and Android was still gaining traction. However, this introduced the 'signed images only' measure. However, it was incredibly easy to circumvent.

2014, Google adds an option for OEM Unlocking. Fair enough, unlocking the bootloader. Incredibly hackenstein option, no one is doing that.

2015, FRP (Factory Reset Protection). Malicious groups cannot Factory Reset for security, however Factory Reset from user-side also became impossible without inputting Gmail credentials. Left compromised devices unusable. Circumvented by low level security tools used by repair shops.

2016, Verified Boot became MAJOR. Unlocking bootloader means tripping security and losing the 'certification' of security from your device. Enforced a chain of 'trust' between Google and the user. Circumventable only by developers only on certain Android devices.

2017, Android Verified Boot (Verified Boot 2.0). The most powerful strike. Introduced Anti-rollback protection, permanently removing your ability to downgrade your system without a certain, unusual method and trying to do so would result in a brick.

2017-18 (bridge to Play Protect), Introduction of SafetyNet Attestation. Unlocked Bootloaders or unsigned Android images will not be able to pass this proprietary 'safety' check, hence, multiple apps with DRMs (Digital Rights Management) and Banking apps won't work.

Circumvented by root and root modules, highly dangerous stuff.

2021, Beginning of Deprecation of SafetyNet and introduction of Play Integrity API. So much more tougher than SafetyNet and relies on Hardware checks and so many tough checks. Was easy to circumvent but has been tightening ever since. Unlocked bootloaders WON'T pass Play Integrity at all, and will require a library of root modules and stuff beyond basic modules.

2024, End of Life for SafetyNet. Migration to Play Integrity required.

ACT TWO

PLAY PROTECT (the thing plaguing the general public)

2017, Install Unknown Apps permissions. You must have seen this once in your life if you have used Android for quite a while. This was common when you were installing say an app from GitHub or from a 'sketchy place' either way, it was just a toggle and you didn't need to mess with it again.

2017-18, Google flags uncertified devices (which do not come under the GMS and Google MADA agreement, or devices that have unlocked bootloaders)

2021, Announcement of Play Integrity. Slowly beginning to replace SafetyNet on newer devices, however older devices still used SafetyNet Attestation and was easy to circumvent.

2024, SafetyNet deprecated (End of Life in January 2025.), Play Integrity now MANDATORY for device attestation.

2026, Starting from September of this year (or September of 2026 if you are from the dystopian future), Google will now requite GOVERNMENT IDs for developer verification. You CANNOT install .apk files normally like toggling developer level permissions (the older permission is now locked behind developer options). Dismiss scare screens, WAIT 24 HOURS, dismiss MORE scare screens then toggle the install unknown apps option and THEN install the app.

(read more about this on https://keepandroidopen.org)

There it is. A once open-source platform now a 95% walled garden.

Worst of all, this runs through Google Play Services, which is literally REQUIRED on every Android device (replacements include microG which is Play Services implementation at it's bare minimum, without Google's suspicious stuff). Google can tighten it or kill .apks off at any time. Breaking their old promise on being open ground for developers and users.

Is the shiny new AI feature really necessary if your autonomy with your device is being crippled? Ponder. Rally. Write to Google. Reject. Lead an uprising. Boycott. Write to your Government. Do whatever to take an action against this nightmare.

Or have your autonomy and ownership with your hardware traded for more AI.

cover page thumbnail by Techlore on this video, "The End of Android Freedom".