From 76609a07faf1d5fdb7085b17df3f82824730b47c Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Tue, 31 Aug 2021 21:35:49 -0400 Subject: [PATCH] more details on dedicated profiles for Play --- static/usage.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/static/usage.html b/static/usage.html index 5fc6d623..3734b68a 100644 --- a/static/usage.html +++ b/static/usage.html @@ -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.

+ 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.

The core functionality and APIs are almost entirely supported already since GrapheneOS largely only has to coerce these apps into continuing to run without