summaryrefslogtreecommitdiff
path: root/static
diff options
context:
space:
mode:
authorDaniel Micay <danielmicay@gmail.com>2021-11-22 09:14:34 -0500
committerDaniel Micay <danielmicay@gmail.com>2021-11-22 09:14:34 -0500
commita79a41bb77006050649775e9b039c3a0b5163dc8 (patch)
tree214a02d87f3cc3a92c78baa6d83830d0b38c5e5c /static
parent682aac38bcdf5ab8aad296c474bd711e3783a9cd (diff)
sandboxed Play Store compatibility layer improved
Diffstat (limited to 'static')
-rw-r--r--static/usage.html22
1 files changed, 13 insertions, 9 deletions
diff --git a/static/usage.html b/static/usage.html
index c1c031e9..3c0408c7 100644
--- a/static/usage.html
+++ b/static/usage.html
@@ -808,6 +808,16 @@
modules). The compatibility layer will be gradually expanded and improved in order
to get more of the Play services functionality working.</p>
+ <p>The Play Store app is designed to use privileged permissions for unattended app
+ installation, updates and removal which isn't possible on GrapheneOS since it's
+ not a privileged app. GrapheneOS provides a dedicated compatibility layer for Play
+ Store app installation/updates/removal teaching it to use the standard
+ unprivileged approach. It prompts the user to permit it as an app source and then
+ prompts for the initial app install/update or removal. It will use Android 12's
+ support for unattended updates when possible which means it can do unattended
+ updates of modern (API 29+) apps where it was the installer for the currently
+ installed version already.</p>
+
<section id="sandboxed-play-services-installation">
<h3><a href="#sandboxed-play-services-installation">Installation</a></h3>
@@ -874,15 +884,9 @@
depending on having highly invasive privileged access beyond what would be
realistic to get working with an expanded compatibility layer.</p>
- <p>The Play Store app is designed to use privileged permissions for unattended
- app installation, updates and removal which isn't possible on GrapheneOS since
- it's not a privileged app. GrapheneOS provides a dedicated compatibility layer
- for Play Store app installation teaching it to use the standard unprivileged
- approach. It prompts the user to permit it as an app source and then prompts
- for each app install/update. The Play Store currently doesn't get the result
- for the install succeeding or failing so it will think the installation is
- still in progress. You can work around this by force stopping the Play Store
- after installing an app and then opening it again to install other apps.</p>
+ <p>Play Store assumes that uninstallation always succeeds so it will stall if
+ it tries to uninstall an app and you reject it. You can work around this by
+ force stopping and then reopening it.</p>
<p>Play Store feature delivery isn't currently supported, but this isn't
broadly used by current generation apps aside from large games.</p>