deGoogle

833 readers

2 users here now

founded 3 years ago

MODERATORS

lincoln@discuss.tchncs.de

Why I moved from GrapheneOS to iodéOS on my Google Pixel (the.unknown-universe.co.uk)

submitted 2 weeks ago by cm0002@libretechni.ca to c/degoogle@discuss.tchncs.de

10 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] lokalhorst@feddit.org 5 points 2 weeks ago (1 children)

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?

[–] lemmysmash@piefed.social 5 points 2 weeks ago

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:

either the author hasn't disabled additional GOS protections (e.g. native code debugging) which ~shitty~ banking apps tend not to like
or the apps rely on the Play Services (mocked by microG on iodeOS out of the box), and the author hasn't installed them