commit c312eeaa5a60420671aa6429537320bff889ee50
author Suprabh Shukla <suprabh@google.com> Wed Mar 10 23:59:15 2021 -0800
committer Suprabh Shukla <suprabh@google.com> Mon Mar 15 15:26:32 2021 -0700
tree 0453f4b72e2e8fd904d776771ad7be2782281428
parent 9ce91b84e90a8789ec89203cf503b9fd29d86cb8

All exact alarms now require SCHEDULE_EXACT_ALARM

Even exact alarms outside of idle require this permission. This is to
draw a clear boundary of the permission. If the app needs exact timing,
it should request this permission and then choose the most appropriate
API for its needs. Otherwise, it has to work with inexact alarms, which
now cannot have a window smaller than a set minimum, currently, ten
seconds.

Test: atest FrameworksMockingServicesTests:com.android.server.alarm
atest CtsAlarmManagerTestCases

Bug: 182226633
Change-Id: Iec953dbe8570f1ea6aaf81d864468ef1eb690de6