@Androidauth

On the topic, #GrapheneOS allows to install the official PlayServices, Playstore and ServicesFramework.

These run with a compatibility tool called #GMSCompat and if this tool grants them the required privileged permissions.

So GCam should work fine, it just got a ton more invasive. #Enshittification

Apps run fine without elevated permissions, but #Google doesnt care to build their apps following the #Android security model. So they require crazy deep access to things, as they are too lazy to make a permission for that.

Meanwhile Google is locking down user app permissions further and further (breaking things like #Syncthing), while leaving out essential permissions like the ones GrapheneOS adds (network permission, storage scopes, contact scopes, sensors) to fuel their tracking business.

And systems without basically backdoors (proprietary system apps that bypass the Android app sandboxing model... by not using it) are not Play Certified and apps using #PlayIntegrity will refuse to run on them. FOR SECURITY!

They refuse to run on systems without backdoors!

(Little side tangent but this just strengthens how ironic Google is)

@ilumium @GrapheneOS @article19 When I asked #Google a follow-up question using Google's own terminology, like #PlayIntegrity #GMS etc. their team of three competition lawyers brushed it aside saying they didn't understand the acronyms. They did not let me clarify. This is a classic example of the Google lawyers being conveniently #ignorant of the key details of things the Google Play team does that nicely props up their monopoly.

#DMA #DMAWorkshop #DigitalMarketsAct #GooglePlay #EC #policy