🚨 Google is killing Android freedom.
Starting 2027, unverified apps can’t be side-loaded.

➡️ F-Droid harder to install
➡️ Custom APKs blocked
➡️ Google decides what runs on YOUR phone

Google’s Android is becoming Apple: Your device, their rules.

It’s time to switch to open alternatives: Graphene, Calyx, Lineage. ✊

https://tuta.com/blog/android-side-load-apps-google

Sign the petition to stop Google from limiting APK file usage: https://www.change.org/p/stop-google-from-limiting-apk-file-usage

@Tutanota I have tried several alternative phone OSes and de-Googled Androids, and written about some.

I do not know of anywhere that I can go and see a list of all of them.

Here is a nice easy non-coding project for anyone who is interested in this area.

* A list of FOSS phone OSes

* Better still, with strengths/weaknesses comparisons: what each one is good for

* Better still, some tool where you can enter your phone model and it tells you you could run.

@Tutanota Apple has always been morally more in the right side than Google ever has been. Apple's ecosystem is *honestly proprietary* i.e. you need to pay for everything, nothing is free, and that is fully transparent.

Google's ecosystem on the other hand is *dishonestly proprietary" where the real payment comes from your privacy, your data etc., and to fully understad what you actually end up paying is hard or impossible to understand in detail, unless you hire an IT specialized legal firm for you to decipher that from Google's legal and contractual documents.

For these reason I don't agree with this comparison :-)

@Tutanota I think the next step have to be a new device that support @GrapheneOS
or their own device

@SeanGeil @Tutanota We're working with a major OEM already towards a subset of their future devices providing official GrapheneOS support.

@GrapheneOS

Great to hear you’re working with a major OEM! Is there an estimated timeline for when end users can expect the first devices with official GrapheneOS support? Thanks for your work!

@SeanGeil @Tutanota

@lazou @SeanGeil @Tutanota Likely in 2026 or 2027 but we can't give any firm timeline.

@GrapheneOS @SeanGeil @Tutanota this is good news, it's always seemed a bit odd to me to step away from using google using a goigle device... is it going to be budget/mud friendly, or are we talking premium costs?

@luxet @SeanGeil @Tutanota The purpose of GrapheneOS is providing a high level of privacy and security, not specifically avoiding Google. Other large tech companies aren't really any more privacy friendly. In fact, they do not make devices meeting reasonable security requirements yet and nearly entirely don't provide proper alternate OS support. The reason we need to work with an OEM towards their devices meeting our requirements is because none of the non-Pixel options currently do.

@luxet @SeanGeil @Tutanota The initial devices will be Snapdragon flagships since that's going to be needed for providing the required security features and updates. The current Snapdragon flagship does not have hardware memory tagging but the upcoming one should provide what we need. Therefore, the earliest possible time other devices can meet our requirements is around early 2026. However, there's significantly more to do than having an SoC meeting our requirements including update support.