But one example: https://news.ycombinator.com/item?id=43518866
AFAIK Graphene is oriented towards strong device security with privacy as more of a side effect.
Which I believe is GrapheneOS' argument when people praise microG: microG being open source does not fundamentally add privacy: apps using microG will phone to Google's servers (that's the whole point of microG). What microG solves is that it removes the Play Services that are root on your device, and it turns out that sandboxed Play Services do that as well.
> The idea for more privacy is you run open source apps instead that just don't collect data.
Yep exactly, I just wanted to add about the sandboxed Play Services, because it was not obvious to me at first :)
Hmm... the sandboxing is a security feature, it's not there to prevent tracking (not sure what "fingerprinting" includes here). The sandboxing of Android is actually pretty good (a lot better than, say, desktop OSes).
There is pretty much nothing you can do against an app requesting e.g. your location data and sending it to their servers. Fundamentally, the whole goal of apps is that they can technically do that. Then you have to choose apps you trust, and it's easier to trust open source apps.
What GrapheneOS brings in terms of sandboxing is that the Play Services run sandboxed like normal apps. Whereas on Android, the Play Services run with system permissions.
Grapheneos doesn't prevent the installed apps fingerprinting you linked either.
Honestly the state of anti-fingerprinting (app, browser, and otherwise) is fairly abysmal but that's hardly limited to android or even mobile as a whole.
But there's no evidence that stock android leaks apps installed across profiles? The link you provided doesn't discuss profiles at all, and stock android also has private space and work profile just like grapheneos.