security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

update status of sandboxed Google Play

Browse Source
This commit is contained in:
Daniel Micay 2022-05-24 15:59:07 -04:00
parent d6aacdeab1
commit 616069e4e1
2 changed files with 46 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
static/features.html
View File

@ -414,20 +414,30 @@
permissions. Apps within the same profile can communicate with mutual consent and permissions. Apps within the same profile can communicate with mutual consent and
it's no different for sandboxed Google Play.</p> it's no different for sandboxed Google Play.</p>
<p>The core functionality and APIs are almost entirely supported already since <p>Sandboxed Google Play is close to being fully functional and provides near
GrapheneOS largely only has to coerce these apps into continuing to run without complete compatibility with the app ecosystem depending on Google Play. Only a
being able to use any of the usual invasive OS integration. A compatibility layer small subset of privileged functionality which we haven't yet ported to
is also provided to support dynamically downloaded/loaded modules (dynamite different approaches with our compatibility layer is unavailable. Some
modules). The compatibility layer will be gradually expanded and improved in order functionality is inherently privileged and can't be provided as part of the
to get more of the Google Play functionality working.</p> compatibility layer.</p>
<p>GrapheneOS provides a dedicated compatibility layer for Play Store app <p>The vast majority of Play services functionality works perfectly including
installation/updates/removal teaching it to use the standard unprivileged approach dynamically downloaded / updated modules (dynamite modules) and functionality
available to sandboxed apps. It prompts the user to permit it as an app source and provided by modular app components such as Google Play Games. By default,
then prompts for the initial app install/update or removal. It will use Android location requests are rerouted to a partial implementation of the Play
12's support for unattended updates when possible which means it can do unattended geolocation service provided by GrapheneOS. You can disable rerouting and use
updates of modern (API 29+) apps where it was the installer for the currently the full Play services geolocation service instead.</p>
installed version already.</p>
<p>Our compatibility layer includes full support for the Play Store. Play
Store services are fully available including in-app purchases, Play Asset
Delivery, Play Feature Delivery and app / content license checks. It can
install, update and uninstall apps with the standard approach requiring that
the user authorizes it as an app source and consents to each action. It will
use the standard Android 12+ unattended update feature to do automatic updates
for apps where it was the last installer. Unattended updates by sandboxed apps
are throttled and it can hit the limit when installing batches of updates and
request consent. We plan to improve this in the future by teaching it to try
an unattended update again after a short wait.</p>
<p>See the <a href="/usage#sandboxed-google-play-installation">usage guide <p>See the <a href="/usage#sandboxed-google-play-installation">usage guide
section on sandboxed Google Play</a> for instructions.</p> section on sandboxed Google Play</a> for instructions.</p>

36
static/usage.html
View File

@ -833,20 +833,30 @@
permissions. Apps within the same profile can communicate with mutual consent and permissions. Apps within the same profile can communicate with mutual consent and
it's no different for sandboxed Google Play.</p> it's no different for sandboxed Google Play.</p>
<p>The core functionality and APIs are almost entirely supported already since <p>Sandboxed Google Play is close to being fully functional and provides near
GrapheneOS largely only has to coerce these apps into continuing to run without complete compatibility with the app ecosystem depending on Google Play. Only a
being able to use any of the usual invasive OS integration. A compatibility layer small subset of privileged functionality which we haven't yet ported to different
is also provided to support dynamically downloaded/loaded modules (dynamite approaches with our compatibility layer is unavailable. Some functionality is
modules). The compatibility layer will be gradually expanded and improved in order inherently privileged and can't be provided as part of the compatibility
to get more of the Google Play functionality working.</p> layer.</p>
<p>GrapheneOS provides a dedicated compatibility layer for Play Store app <p>The vast majority of Play services functionality works perfectly including
installation/updates/removal teaching it to use the standard unprivileged approach dynamically downloaded / updated modules (dynamite modules) and functionality
available to sandboxed apps. It prompts the user to permit it as an app source and provided by modular app components such as Google Play Games. By default, location
then prompts for the initial app install/update or removal. It will use Android requests are rerouted to a partial implementation of the Play geolocation service
12's support for unattended updates when possible which means it can do unattended provided by GrapheneOS. You can disable rerouting and use the full Play services
updates of modern (API 29+) apps where it was the installer for the currently geolocation service instead.</p>
installed version already.</p>
<p>Our compatibility layer includes full support for the Play Store. Play Store
services are fully available including in-app purchases, Play Asset Delivery, Play
Feature Delivery and app / content license checks. It can install, update and
uninstall apps with the standard approach requiring that the user authorizes it as
an app source and consents to each action. It will use the standard Android 12+
unattended update feature to do automatic updates for apps where it was the last
installer. Unattended updates by sandboxed apps are throttled and it can hit the
limit when installing batches of updates and request consent. We plan to improve
this in the future by teaching it to try an unattended update again after a short
wait.</p>
<section id="sandboxed-google-play-installation"> <section id="sandboxed-google-play-installation">
<h3><a href="#sandboxed-google-play-installation">Installation</a></h3> <h3><a href="#sandboxed-google-play-installation">Installation</a></h3>