diff options
| author | Beverly <beverlyt@google.com> | 2020-08-20 08:32:07 -0400 |
|---|---|---|
| committer | Beverly <beverlyt@google.com> | 2020-08-21 16:11:27 -0400 |
| commit | 41580e69ef5b0bbe747c6b8799602694a38be0ec (patch) | |
| tree | 50d8f0b0d0aad888ef437a19fa93d5ed4b51f9ac /tools/aapt2/java/JavaClassGenerator.cpp | |
| parent | 89ecbea1eb4620ffe09596f7ba98f5d016085e5a (diff) | |
Update max # notifs in NotifPanelViewController
Instead of updating in NotificationViewHierarchyManager. Now both the
old and new pipeline will show the correct # max notifications in
the shade. This fixes the bug where only a max 3 notifications was
showing in the notification shade when the new notification rendering
pipeline was enabled. (onKeyguard wasn't being updated and the max # of
notifications on the keyguard is 3.)
This fix includes:
- Update ExpandableNotificationRow's keyguard state via status bar state
controller listener instead of relying on a direct call to update from NVHM/StatusBar
- Removing NotificationPresenter getMaxNotificationsWhileLocked method.
Instead, if a package wants to override this value, it should override the config
value keyguard_max_notification_count
- This also fixes regular notification expansion when enabling the
new notification pipeline because now onKeyguard is being updated
appropriately, so the expansion states can evaluate correctly
Test: atest SystemUITests
Change-Id: I07593ef5d95674911f6f96a5c03cf4128a885a99
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions
