GrapheneOS isn't going to be including Google services in the base OS: grapheneos.org/#never-google-….
This doesn't mean it won't be possible to use apps depending on Play services on GrapheneOS. It means it shouldn't be deeply integrated into the OS as a cross-user, privileged app.
This doesn't mean it won't be possible to use apps depending on Play services on GrapheneOS. It means it shouldn't be deeply integrated into the OS as a cross-user, privileged app.
We're going to support installing a Google compatibility layer within a user profile as a regular app. The OS will include minimal support for this in a way that does not compromise the security model. It won't have special privileges other than masquerading as Play services.
We plan to add support for using a GrapheneOS release of microG this way. In the longer term, we also plan to offer a more minimal compatibility layer implemented by pretending that Google services are offline. Both will be options you can choose to install in a specific profile.
Our releases of the apps signed with specific keys will be able to pretend to be a specific app (Play services). microG is capable of functioning this way rather than as a cross-user, privileged system app since this is not how we'll be providing neutral AOSP APIs like geocoding.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
