People should be able to write software for Android, and distribute it outside Google’s Play store, without having to:
- pay Google
- give government ID to Google
- agree to Google terms and conditions
People should be able to install the software they want on their phone, from sources other than Google’s Play store, without having to jump through Google-imposed hoops.
e.g. via F-Droid.
We’ve got until September this year to stop Google squeezing the open Android ecosystem.



Google has been systematically moving stuff out of the open-source part of Android and into proprietary areas for some time now. They’re making it harder and harder for anyone to make a working Android OS that isn’t full of closed-source Google spyware. For now these projects survive, but Google is clearly hostile to them.
What would it take to start from a clean slate? I mean, a mad lad said about 35 years ago “UNIX expensive. I’m gonna make my own OS”
What are the obstacles for something like this to happen for phones? I assume device drivers, but probably it is much more complicated than that
Yes, device drivers are an issue. Reverse engineering them is a bitch and slows you down, particularly if you want to support a wide range of models and those models keep getting hardware updates.
But that’s not all, software ecosystem is another big one. Android and iOS have seen two decades of people developing software for them. In order for them to want to port their software over to your cleanSlateOS, it would have to have a significant user base. And in order for cleanSlateOS to draw that significant user base, it would have to have an attractive suite of apps to run on it. It’s a catch-22.
You could, in theory, try to develop emulators or compatibility layers so that Android apps will also run on cleanSlateOS. But that, again, is time-consuming, will never be free of friction, and require you to make compromises with regard to security and privacy (many apps simply don’t run properly without Google’s main piece of spyware, the Play Services). It will also kind of tie you to Google again - and that was the thing you were trying to get away from in the first place…
FSF has a project called LibrePhone
Broken link?
librephone.fsf.org
I have a GNU/Linux phone I carry in my other pocket. Here are the biggest issues I can see:
I carry a Linux phone in my normal pocket, not my other one.
The camera doesn’t work, I don’t have any problem with apps but I am probably not a typical user in that regard, but my 5000mAh battery lasts me a day and ends on 30-40%, which is reasonable but not nearly as good as Android. My family members complain I sound like I’m underwater when I call them and the phone crashes every morning when I take it off the charger.
Linux phones are a wonderful promise but require a lot of comprimises. I hope they improve soon
Aren’t there also issues with Banking Apps and their requirements around security and signing?
access the bank website in the browser?
Not all have websites sadly. Virgin for example got rid of their web app and now direct you to download them mobile app as the only way to manage your accounts outside of the brick and mortar branches. Obviously I now rarely use that credit card, if ever. But others may have their main bank accounts and mortgages etc with such a bank and that would suck.
oof, yeah, that sounds like a good reason not to do business with them
I see a lot of people responded with a true clean slate, but really, a fork is a clean slate.
It’s not like Graphene, or Lineage, or any others would stop working. More maintainers would be needed for security issues, but way less than to get (non-Android) Linux phones up to speed.
Many graphene users, myself included, use all FOSS software from outside Google’s store.
My last straw was when I had location services permission denied to chrome, and then one day discovered that it had turned them back on without notifying me…
Also, every time my apps updated they gave themselves back permissions that I had disabled.