diff options
author | Pavel Grafov <pgrafov@google.com> | 2020-06-02 13:45:19 +0100 |
---|---|---|
committer | Pavel Grafov <pgrafov@google.com> | 2020-06-10 23:11:01 +0100 |
commit | 80b763830e277e9d4f44b82cbb793f06930dbcb2 (patch) | |
tree | 8d9de92842f66ae845ff9e699260bfaca0c24e18 /tools/aapt2/java/JavaClassGenerator.cpp | |
parent | 2ad21ed9ddc6b9bcc4f8acfc4560195cf2c83e3d (diff) |
Convert personal app suspension on COMP->COPE migration
* if no apps are suspended by the DO prior to migration, nothing
changes
* if some apps were suspended by the DO and the DPC targets R+
via DPM.setPackagesSuspended(), this will result in personal
apps suspended explicitly by the PO DPC as if it called
DPM.setPersonalAppsSuspended(). The apps will stay suspended.
* if the DPC target SDK is below R, the apps will be unsuspended
because the DPC won't have a way to unsuspend them. And the
user will be stuck with suspended apps.
+ when unsuspending apps, don't collect the list of apps subject
to suspension, but rather unsuspend all that is suspended. It
is more robust, e.g. when some app stops meeting the
conditions, e.g. not SMS app anymore.
Bug: 157270093
Test: com.android.server.devicepolicy.DevicePolicyManagerServiceMigrationTest
Test: Manual, with TestDPC, also patching it to target R
Change-Id: I1eba7216dd557c94bef822b77d25b484dfcd6f63
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions