From 619ede48542ed43f73d119d03fb939b3b300e351 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Wed, 11 Aug 2021 10:33:45 -0400 Subject: [PATCH] update usage guide for dynamite module support --- static/usage.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/static/usage.html b/static/usage.html index 8be115f0..05827563 100644 --- a/static/usage.html +++ b/static/usage.html @@ -726,14 +726,14 @@ stalling and needing to be force stopped. For the time being, it's easier to use the alternative Aurora Store frontend to the Play Store.

+

Play Store feature delivery isn't currently supported, but this isn't broadly + used by current generation apps, at least aside from large games.

+

The core functionality and APIs are almost entirely supported already since GrapheneOS largely only has to coerce these apps into continuing to run without - being able to use any of the usual invasive OS integration. Certain functionality - is not yet supported. Play Store feature delivery and Play services functionality - delivered via dynamite modules are not supported yet. Fallback code will be - required to make this work without depending on weakening SELinux MAC and MLS - policies to permit it like the stock OS. The current generation Maps API is a - common example of functionality depending on a dynamite module.

+ being able to use any of the usual invasive OS integration. A compatibility layer + is also provided to support dynamically downloaded/loaded modules (dynamite + modules).

Since there's no OS integration beyond fallback code to make it function without any special privileges, there isn't a way to launch the settings activity.