From 1cd708bb0b156f8946dd20ae6ad22b0e263917ca Mon Sep 17 00:00:00 2001
From: Makoto Onuki <omakoto@google.com>
Date: Wed, 12 May 2021 09:53:15 -0700
Subject: [PATCH] Clarify the semantics of
 ACTION_SCHEDULE_EXACT_ALARM_PERMISSION_STATE_CHANGED

Bug: 187206399
Test: build
Change-Id: Ibe450f0d7c29ada5848508b6ac6a585bfabad72b
---
 apex/jobscheduler/framework/java/android/app/AlarmManager.java | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/apex/jobscheduler/framework/java/android/app/AlarmManager.java b/apex/jobscheduler/framework/java/android/app/AlarmManager.java
index b096537821caa..8b824e8a9a72c 100644
--- a/apex/jobscheduler/framework/java/android/app/AlarmManager.java
+++ b/apex/jobscheduler/framework/java/android/app/AlarmManager.java
@@ -152,6 +152,8 @@ public class AlarmManager {
      * this broadcast will be sent. Applications can reschedule all the necessary alarms when
      * receiving it.
      *
+     * <p>This broadcast will <em>not</em> be sent when the user revokes the permission.
+     *
      * <p><em>Note:</em>
      * Applications are still required to check {@link #canScheduleExactAlarms()}
      * before using the above APIs after receiving this broadcast,