+45
−0
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
If there are many timing delays set within a few milliseconds of each other, TimeController can end up spamming and overwhelming AlarmManager. Since a job doesn't need to have its delay constraint updated immediately and we therefore don't need to have exact timing of every single delay alarm, we should be alright limiting how often a delay alarm can be set to go off. Bug: 167681468 Test: atest com.android.server.job.controllers.TimeControllerTest Test: atest CtsJobSchedulerTestCases Change-Id: I5d2eba00d1c47ddf81bb440dd00dae0239c91eb0