Google has been trying to make Android proprietary for a few years now, and that’s not news, as many AOSP default apps have been abandoned over time in favor of proprietary Google ones. This was never a huge problem for me, as you can still use those apps without network access or use open source alternatives like Fossify on a custom ROM.
However, the situation is quickly getting worse, now that Google is actively trying to prevent the development of custom ROMs and taking a page from Apple’s book by forcing developers to beg them for permission to release apps on the Android platform, even outside of the Play Store - giving Google full control.
Is there still any hope left for privacy respecting Android ROMs? What do you think will happen next? And what would be your suggestions for those looking for a phone in 2025?
If you have a different perspective on the situation, also please comment below!
What do you think will happen next?
Development of Linux on mobile will ramp up.
EU or similar wrecking Google over being monopolistic would be nice but unlikely.
Same but targeting phone manufacturers.We need the EU to regulate Banking and Payment apps to not rely on Google apis first and mandate that they have to be available in open app stores or as apk.
Right now the EU regulation is pushing banks to require more of Google or Apple because it’s unclear and banks won’t take a chance of getting fined.
Among the requirements are: ensure the device and the OS were not “altered”. What does that mean exactly? Answer: [crickets].
But that’s why many banks just go with the Google Play Integrity API.
They don’t even do that with their own apps.
Maybe they can regulate themselves first as a start then. They already use Matrix, so it’s not like they are completely lost regarding IT Security and FOSS.
As of right now, it’s looking like GrapheneOS will be unaffected, and Google has yet to lock down the bootloader. So this should remain a valid option for at least 2 years.
Other than that:
- Any smartphones with an unlocked bootloader + any ROMs without gapps
- Chinese smartphones with non-Google Android builds
- Linux smartphones
- Bonus: Huawei is about to release their own non-Android OS, but I wouldn’t expect it to be privacy-friendly
Honestly there probably isn’t any good, long-term solution. Personally I’m somewhat shocked we’ve gone this many years with reasonably open smartphones. Next step is probably closing bootloaders in new laptops, as part of the switch to ARM (which is already undergoing).
Until substantially more people join the fight for privacy or something else fundamentally changes, I think there is a very real possibility of Google completely clamping down on Android while governments and workplaces mandate apps that only run on phones with all of Google or Apple’s bells and whistles.
But the folks at GrapheneOS, Calyx, and Murena seem to be a devoted and resourceful bunch, so I am hopeful that they can give something for us to work with, even if Google pulls the plug, whether it’s a fork of Android or rebasing to mobile Linux.
If that all falls through, I’ll look for whichever phone supports Linux best and eventually move everything over. The vast majority of the apps I use regularly on my GrapheneOS phone aren’t very demanding and have a decent alternative on Linux. And whatever apps are forced on me by other people will reside on a dedicated Android phone, ideally with a removable battery.
For this year, I’d still recommend a secondhand or reseller Pixel with GrapheneOS. Everything just works on it.
Yes, absolutely there is hope.
Phones that don’t support Google play services (AKA any hardcore privacy phone) will not be directly effected by Google restricting sideloading. The restriction is only for phones that use the Google suite. (source: https://9to5google.com/2025/08/25/android-apps-developer-verification/ “This requirement applies to ‘certified Android devices’ that have Play Protect and are preloaded with Google apps.”) Graphene OS isn’t going anywhere, AOSP is open source, even if Google tried to make that change in the OS, the community would hard-fork AOSP instantly and continue like nothing ever happened.
Realistically this is going to squeeze people “in the middle” towards fully-google controlled Android (one exteme) and towards fully-de-googled Android (the other extreme). Its just elminating the middle. Which is bad for people trying to gradually de-google their life, but not as dire as it might seem.
On the bright side, this is an opportunity for play-services spoofing to become commonplace and easy, and could cause more apps to avoid google play services. The EU also has a shot at forcing google to allow sideloading, since they’ve recently been forcing Apple to move in that direction.
So, while not a bright future, its far from hopeless for privacy respecting Android phones.
This is the point, isn’t it?
Lock down their own ecosystem because they’re jealous of how Apple does it, so they can herd all users into their walled garden. Then close the gates behind them. There’s no easy way out, you can’t just wander back and forth anymore. You have to scale a wall in the dead of night and shed a tear as you look back and see everyone else having a lovely life, then set off into the dark forest of privacy on your own.
People hate friction in the first place. This is as much friction as they can realistically make on their own without triggering anti-trust cases and EU fines.
