diff options
| author | Christopher Tate <ctate@google.com> | 2019-09-20 17:30:12 -0700 |
|---|---|---|
| committer | Luca Stefani <luca.stefani.ge1@gmail.com> | 2019-11-30 12:35:49 +0100 |
| commit | ee9739cd7ef7971221782938f1066f6720af32d7 (patch) | |
| tree | 194a250f2102c6b4ea938aae4bf34721c5fb0d77 /core/xsd | |
| parent | a41c9222264bed1bd21b9df30ab6c05ef7f93b41 (diff) | |
| download | android_frameworks_base-ee9739cd7ef7971221782938f1066f6720af32d7.tar.gz android_frameworks_base-ee9739cd7ef7971221782938f1066f6720af32d7.tar.bz2 android_frameworks_base-ee9739cd7ef7971221782938f1066f6720af32d7.zip | |
Services exit fg when bg-restricted app leaves top
Apps under bg restrictions can still start foreground services while
they are the top/frontmost UI. However, this was not being reexamined
when the app was no longer the top UI. This is now fixed: when an app
under bg restrictions exits the top state, any foreground services it is
hosting are demoted out of the foreground state. At this point the
service lifecycle is just like any other ordinary service that an app
has left running after it is no longer the active UI: the service is
stopped by the OS after the standard grace period.
Bug: 139436349
Test: repro app supplied with the bug
Test: foreground use of GPM under bg restrictions
Test: atest CtsAppTestCases:android.app.cts.ActivityManagerProcessStateTest\#testBgRestrictedForegroundService
Change-Id: I6d0e954c961f7c547c1f5d98e3926586f3071bca
Merged-In: I6d0e954c961f7c547c1f5d98e3926586f3071bca
Diffstat (limited to 'core/xsd')
0 files changed, 0 insertions, 0 deletions