summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorAmith Yamasani <yamasani@google.com>2019-03-20 22:49:43 -0700
committerAmith Yamasani <yamasani@google.com>2019-04-02 10:27:03 -0700
commitf235d0b53a0e33828ea23fe5aa7e668eaba3ce8b (patch)
treec4a93cdf243f6875717734f8eeab34a0ff15cd1e /tools/aapt2/java/JavaClassGenerator_test.cpp
parent825c933351dd4512fe9f8db849dfc1eac4738412 (diff)
Avoid elevating apps to high proc states on binding
For service and provider bindings from TOP and FOREGROUND_SERVICE apps, don't elevate bound apps to above BOUND_FOREGROUND_SERVICE. For service bindings, it is possible to explicitly request the binding to match the foreground app such that the bound app can get similar privileges of foreground permissions. For instance, when a foreground service has a location type, providers it binds to don't automatically get the location privilege. On the other hand, sometimes apps showing UI want to treat their dependencies also as if they are showing UI. This change does not affect the oom_adj calculation, only the proc state calculation for bound processes. New BIND_INCLUDE_CAPABILITIES flag can be used to restore old behavior for bound services. Introduces a new state PROCESS_STATE_BOUND_TOP Bug: 128337543 Test: atest CtsAppTestCases:ActivityManagerProcessStateTest Change-Id: I13733e7f43a78903299254bc110cd8f7a8db4c40
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions