more details on dedicated profiles for Play
This commit is contained in:
parent
23cd7d97a6
commit
76609a07fa
@ -691,9 +691,12 @@
|
||||
doesn't use them for anything. They run as unprivileged, sandboxed apps like any
|
||||
others. GrapheneOS simply provides fallback code teaching them how to run without
|
||||
any of the special privileged permissions and SELinux policy they depend on
|
||||
having. Even within the same profile, apps not explicitly choosing to use Google
|
||||
services won't use them because the OS doesn't integrate support for it or use it
|
||||
as the backend for APIs in the OS like the stock OS.</p>
|
||||
having. You can choose which apps will use them by using dedicated a dedicated
|
||||
user profile since apps can't share data or communicate across users. A work
|
||||
profile also works, although without as much isolation. Even within the same
|
||||
profile, apps not explicitly choosing to use Google services won't use them
|
||||
because the OS doesn't integrate support for it or use it as the backend for APIs
|
||||
in the OS like the stock OS.</p>
|
||||
|
||||
<p>The core functionality and APIs are almost entirely supported already since
|
||||
GrapheneOS largely only has to coerce these apps into continuing to run without
|
||||
|
Loading…
x
Reference in New Issue
Block a user