Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Expedited jobs to use IMP_FG proc_state.

Browse Source 
Removing BIND_FOREGROUND_SERVICE while binding to the job service
which would otherwise elevate it to BFGS proc_state.

Bug: 177641226
Test: atest CtsJobSchedulerTestCases
Test: atest CtsHostsideNetworkTests:HostsideRestrictBackgroundNetworkTests
Change-Id: I51756d0c22e141b8d6f0bd91784da6fd87a69168
This commit is contained in:
Sudheer Shanka
2021-01-15 03:13:50 -08:00
parent 200967d138
commit 5d101264ec
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
apex/jobscheduler/service/java/com/android/server/job/JobServiceContext.java
View File

@@ -260,11 +260,9 @@ public final class JobServiceContext implements ServiceConnection {
try {
final int bindFlags;
if (job.shouldTreatAsExpeditedJob()) {
// Add BIND_FOREGROUND_SERVICE to make it BFGS. Without it, it'll be
// PROCESS_STATE_IMPORTANT_FOREGROUND. Unclear which is better here.
// TODO(171305774): The job should run on the little cores. We'll probably need
// another binding flag for that.
bindFlags = Context.BIND_AUTO_CREATE | Context.BIND_FOREGROUND_SERVICE;
bindFlags = Context.BIND_AUTO_CREATE;
} else {
bindFlags = Context.BIND_AUTO_CREATE | Context.BIND_NOT_FOREGROUND
| Context.BIND_NOT_PERCEPTIBLE;