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

Allow system processes to set near-future alarms

Browse Source 
Bug: 151689784
Test: atest CtsAlarmManagerTestCases
Test: atest FrameworksMockingServicesTests:AlarmManagerServiceTest
Test: observe DHCP +2 sec alarm

Merged-In: Ic987eb168fb632d77e841f33518c2d0ea650693e
Change-Id: Ic987eb168fb632d77e841f33518c2d0ea650693e
This commit is contained in:
Christopher Tate
2020-04-01 10:09:07 -07:00
parent 565160c302
commit 7e701dbe8c
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
services/core/java/com/android/server/AlarmManagerService.java
View File

@@ -1735,8 +1735,9 @@ class AlarmManagerService extends SystemService {
final long nowElapsed = mInjector.getElapsedRealtime();
final long nominalTrigger = convertToElapsed(triggerAtTime, type);
// Try to prevent spamming by making sure we aren't firing alarms in the immediate future
final long minTrigger = nowElapsed + mConstants.MIN_FUTURITY;
// Try to prevent spamming by making sure apps aren't firing alarms in the immediate future
final long minTrigger = nowElapsed
+ (UserHandle.isCore(callingUid) ? 0L : mConstants.MIN_FUTURITY);
final long triggerElapsed = (nominalTrigger > minTrigger) ? nominalTrigger : minTrigger;
final long maxElapsed;