sandboxed Play services isn't experimental anymore
This commit is contained in:
parent
11100d59b2
commit
b8d0111493
@ -1184,13 +1184,14 @@
|
||||
<h2><a href="#google-services">Will GrapheneOS include support for Google services?</a></h2>
|
||||
|
||||
<p>Like the Android Open Source Project, GrapheneOS doesn't include Google apps
|
||||
and services. They won't ever be bundled with the OS. GrapheneOS includes an
|
||||
experimental sandboxed Play services compatibility layer to make user installed
|
||||
Play services apps able to run as fully sandboxed, unprivileged apps. This is
|
||||
<a href="https://grapheneos.org/usage#sandboxed-play-services">documented as part
|
||||
of the usage guide</a>. 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.</p>
|
||||
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 <a
|
||||
href="https://grapheneos.org/usage#sandboxed-play-services">documented as
|
||||
part of the usage guide</a>. 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.</p>
|
||||
|
||||
<p>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
|
||||
|
Loading…
x
Reference in New Issue
Block a user