From 16e0f280a8d9b0c334359b8539e88d38d49c96c7 Mon Sep 17 00:00:00 2001 From: Suprabh Shukla Date: Thu, 7 Apr 2022 18:54:39 -0700 Subject: [PATCH] Toggle schedule_exact_alarm to be denied by default Flipping the flag to on. This will mean apps targeting T will need to request permission from the user before they can schedule exact alarms. Test: atest CtsAlarmManagerTestCases Bug: 226439802 Change-Id: I69dacf6dfb4871ed3597dff805eaec27df831205 --- .../java/com/android/server/alarm/AlarmManagerService.java | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) 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 881453fe237d7..0e4887d27b535 100644 --- a/apex/jobscheduler/service/java/com/android/server/alarm/AlarmManagerService.java +++ b/apex/jobscheduler/service/java/com/android/server/alarm/AlarmManagerService.java @@ -612,8 +612,7 @@ public class AlarmManagerService extends SystemService { private static final boolean DEFAULT_KILL_ON_SCHEDULE_EXACT_ALARM_REVOKED = true; - // TODO(b/226439802): Flip to true. - private static final boolean DEFAULT_SCHEDULE_EXACT_ALARM_DENIED_BY_DEFAULT = false; + private static final boolean DEFAULT_SCHEDULE_EXACT_ALARM_DENIED_BY_DEFAULT = true; // Minimum futurity of a new alarm public long MIN_FUTURITY = DEFAULT_MIN_FUTURITY;