diff options
| author | 2024-08-01 11:10:57 +0000 | |
|---|---|---|
| committer | 2024-08-01 11:10:57 +0000 | |
| commit | 89ed5491a549efc5fe2f76f3e94a2901ff884a99 (patch) | |
| tree | 4e347437dcb009282d1b17e4014b5eb7934a4970 /libs/androidfw/StringPool.cpp | |
| parent | 65672c908669a0e2036253c4b92fe1aa00b6f555 (diff) | |
Check user type before adding user wakeup
Not all user types should have their wakeups persisted.
Guest users should not run in the background. And since they are meant to be used temporarily, their activity like alarms should not disrupt other users. Therefore their alarms do not get persisted and thet are not started prior to their alarms.
System users are always running on the device, so there is no need to start them.
Profiles are not full users and have special applications. For private profile or work profile, users might want to keep them stopped so starting them in the background can be unexpected to users. So this feature at this time should only be applied to full users.
Bug: 353736798
Test: atest UserWakeupStoreTest && atest AlarmManagerServiceTest
Flag: com.android.server.alarm.start_user_before_scheduled_alarms
Change-Id: I8657342fb48b177455352ad8ec207afa5a7e0dd0
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions