tree 8b5b0ec461c8989da7db7e04cf467c36d4fef6fa
parent 09cb5879a1feaf43d673e966914b674391dd0453
author Suprabh Shukla <suprabh@google.com> 1626119582 -0700
committer Suprabh Shukla <suprabh@google.com> 1626218363 -0700

Separating alarm history for lower quota

Using a separate container for lower allow-while-idle quota to avoid out
of quota issues. Using the same container means that the lower quota is
out whenever higher quota is used for alarms from the same app.
Lower quota - currently once per 9 minutes - is used in the
following cases:
 - Inexact allow-while-idle alarms. This means the same app can use
 alarms using high quota and low quota simultaneously.
 - When the caller is targeting < S.
 - When the caller is in the power save allowlist, but does not have the
 permission - for exact alarms.

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

Bug: 190788800
Change-Id: Iba46fdd36dc04843e9256827b0754d21cfff89c9