diff --git a/static/faq.html b/static/faq.html index a459bf61..e7f9ddc5 100644 --- a/static/faq.html +++ b/static/faq.html @@ -1210,11 +1210,10 @@ and services. They won't ever be bundled with the OS. GrapheneOS includes compatibility layer for sandboxed Play services to make user installed Play services apps able to run as fully sandboxed, unprivileged apps. This is documented as - part of the usage guide. Many apps work perfectly without Play services and - many others only depend on it for a subset of their functionality. Users can - choose to install Play services in specific profile(s) to control which apps can - use it.
+ href="/usage#sandboxed-google-play">documented as part of the usage guide. + Many apps work perfectly without Play services and many others only depend on it + for a subset of their functionality. Users can choose to install Play services in + specific profile(s) to control which apps can use it.AOSP APIs not tied to Google but that are typically provided via Play services will continue to be implemented using open source providers like the Seedvault diff --git a/static/features.html b/static/features.html index 5fb5980b..93f2a1be 100644 --- a/static/features.html +++ b/static/features.html @@ -310,7 +310,7 @@ they avoid requiring invasive OS integration. Building privileged support for Google services into the OS isn't something we're going to be doing, even if that's partially open source like microG. -
GrapheneOS will never include either Google Play services or another implementation of Google services like microG. It's possible to install Play services as a set of fully sandboxed apps without special privileges via our - sandboxed Play services compatibility + sandboxed Google Play compatibility layer. See the FAQ section for more details on our plans for filling in the gaps from not shipping Play services and Google apps.