diff options
| author | 2023-12-11 17:58:49 +0100 | |
|---|---|---|
| committer | 2023-12-15 12:28:33 +0100 | |
| commit | 16d90af8a54f087f7b048b4a1336113f2520ca18 (patch) | |
| tree | 3baf1d7b53ad10751a82dad483ff0538b7c8c9ed /libs/androidfw/ResourceTimer.cpp | |
| parent | 918378f0b236dfa46d1f9c9f90b9e0da331068ac (diff) | |
Properly distinguish origin of Zen Changes
Add entry points to NotificationManager and INotificationManager so that Settings and SystemUI can tag Zen operations as "fromUser" (apps cannot do this, except for setAutomaticZenRulke via the Condition.source field). Also update SystemUI callers to provide "fromUser == true" where it makes sense (which is almost everywhere).
This effectively separates the "System" and "User" origins (the former being reserved to changes that are not originated from the user, such as schedule-based rules starting or ending).
Bug: 308670715
Flag: ACONFIG android.app.modes_api DEVELOPMENT
Test: atest NotificationManagerServiceTest ZenModeHelperTest DefaultDeviceEffectsApplierTest
Change-Id: If1e74e7989697c3126fd50636347488bfe3cda51
Diffstat (limited to 'libs/androidfw/ResourceTimer.cpp')
0 files changed, 0 insertions, 0 deletions