Why I moved from GrapheneOS to iodéOS on my Google Pixel
I’ve been using a de-Googled Android setup and found myself running into the same issue a lot of people probably do: the privacy-first option is great right up until the everyday stuff stops working properly.
In my case, banking apps and Android Auto were the sticking points. GrapheneOS was excellent in principle, but iodéOS ended up being the more practical fit for my actual use case.
I’d be interested to hear where other people draw that line between privacy, convenience, and reliability.
https://the.unknown-universe.co.uk/tech-stories/grapheneos-to-iodeos/Open linkView original on libretechni.ca
5 replies
That's the tradeoff almost everyone eventually makes.
How does iodé/os differ from e/os? Seems they are both able to run android apps?
I really miss a technical comparison between GrapheneOS and iodéOS in this blog post. Does that mean iodé passes integrity attestation? If yes, how do they do it? How is it degoogled if it relies on Google services?
No, it doesn't pass the "strong" integrity attestation. None of "custom" ROMs does.
It's degoogled in the sense that it doesn't run original Play Services, but runs open source microG implementation instead. It still talks to the Google services and it still maintains the connection to Firebase Cloud Messaging for push notifications. MicroG sends out less sensitive infromation, but still does talk to Google.
The reason why banking apps didn't run on GrapheneOS but ran on iodeOS is probably one of two:
shittybanking apps tend not to likeSounds like the author did not try with google play services or microg. On GOS they could have made a separate profile just for auto, banks and google play services.