Do we know if Google is operating on the frontier of the trade-off curve? What do we lose from Pixel Android when GrapheneOS security changes are made?

▲

drnick1 4 days ago | parent | next [-]

Google's spyware (Play Services) ceases to work normally and Graphene had to patch it to run as an unprivileged app. So that's one "loss."

I personally don't bother with Google dependencies at all. If an app requires them to work, I will do without it.

▲

izacus 4 days ago | parent | prev [-]

Actually functionality, stability of apps and features people use.

▲

ysnp 4 days ago | parent | next [-]

What functionality and features are lost in the base Pixel OS (not apps) as a direct result of GrapheneOS's changes to AOSP?

▲

gradeless 3 days ago | parent | next [-]

Very little if anything at all. Depends a bit how you draw the line between an app and the base OS. Contactless payments dont work with Google Pay - but that is due to Google using attestatiom to check if the OS is GMS lincesed (GrapheneOS is not). There are alternative contactless payment options that work fine.

	▲	izacus 2 days ago \| parent [-]
		Moving the goalposts to "it's not their fault that it doesn't work" doesn't really change it doesn't work.

▲

izacus 2 days ago | parent | prev [-]

There's quite a list you can get even from GrapheneOS's posts - among other things, there's a rather large set of apps that will outright crash when MTE is enabled.

	▲	ysnp 2 days ago \| parent [-]
		Could you list a couple of the biggest functionality losses from AOSP due to GrapheneOS changes? I might be misunderstanding what you mean.

▲

4 days ago | parent | prev [-]

[deleted]