Before this change alarms in multiuser environment were not consistent. If the user was stopped, their alarm did not go off. Since user stops happen without user's explicit interaction and their status is not available to regular users, if the alarm was set on background user, there was no certainty that the alarm would ring.

After the change a list of users with alarms scheduled is stored to start them in background shortly before their alarm. This ensures consistency in alarms going off even if the user gets stopped. Persistence of this list was added to save this list even after device reboots.

Bug: 314907186
Test: atest AlarmManagerServiceTest && atest UserWakeupStoreTest
Change-Id: I5a75813d76f505383909ac6a281902c54784a1ed