From 583912613251cf2429912f7a6abae599c57ce5bf Mon Sep 17 00:00:00 2001 From: Suprabh Shukla Date: Tue, 3 Nov 2020 14:58:31 -0800 Subject: [PATCH] Switching to lazily batching alarms by default Test: atest CtsAlarmManagerTestCases atest CtsAppTestCases:android.app.cts.AlarmManagerTest Bug: 161497385 Change-Id: I56773ced10f5bce5ba31b4f52368e015fc9add35 --- .../java/com/android/server/alarm/AlarmManagerService.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apex/jobscheduler/service/java/com/android/server/alarm/AlarmManagerService.java b/apex/jobscheduler/service/java/com/android/server/alarm/AlarmManagerService.java index ba2a8a34a92be..d4ea7af06ed1c 100644 --- a/apex/jobscheduler/service/java/com/android/server/alarm/AlarmManagerService.java +++ b/apex/jobscheduler/service/java/com/android/server/alarm/AlarmManagerService.java @@ -439,7 +439,7 @@ public class AlarmManagerService extends SystemService { private static final int DEFAULT_APP_STANDBY_RESTRICTED_QUOTA = 1; private static final long DEFAULT_APP_STANDBY_RESTRICTED_WINDOW = MILLIS_IN_DAY; - private static final boolean DEFAULT_LAZY_BATCHING = false; + private static final boolean DEFAULT_LAZY_BATCHING = true; // Minimum futurity of a new alarm public long MIN_FUTURITY = DEFAULT_MIN_FUTURITY;