| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Context is no longer passed in as a constructor arg.
Bug: 229228871
Test: manual
Change-Id: I3dd5e593f209d120eb36faf33ba629a2066ad3f5
Merged-In: I3dd5e593f209d120eb36faf33ba629a2066ad3f5
|
| |
|
|
|
|
|
|
|
|
|
|
| |
'General' was too undescriptive. Since the channel's importance
is fixed, and these notifications already break through DND,
I don't think it's worth migrating user settings from the old channel
to the new channel.
Test: NotificationChannelsTest
Test: run an instant app, verify channel
Fixes: 225171990
Change-Id: I79b8fe015db1bd177b998752ddee8c037dbf3e1b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove's config_systemUIServiceComponents from SystemUI's config.xml
and replaces it with a list of Dagger providers that can easily be
defined and customized in code.
This is a step to removing our reliance on reflection and hopefully
lets SystemUI clients better tailor their binary to their needs.
Various other small code tweaks are included to address startup-order
dependent issues that were discovered while writing this CL.
Some startup customization still occurs via XML - one form factor
in particular has an overlay that relies on this. It is my intent
to find a way to move off of that in the future.
Bug: 205725937
Test: manual
Change-Id: I4c207bc9487718eddc21f364e81ec760f286bf30
|
| |
|
|
|
|
| |
Bug: 205725937
Test: manual
Change-Id: I045a8b4b21cae0f4a6e61502384e2b1a607bc1c6
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This saves hundreds of ms of binder calls when SystemUI
starts up (to INotificationManager.getNotificationChannel
and INotificationManager.deleteNotificationChannel).
Fixes: 201541113
Test: (boot device)
Test: (test secondary users, user switching)
Test: atest SystemUITests
Change-Id: Ie1d011581c49878911e8ddb46121fa95c24339ba
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Make TvPipNotificationController (formerly PipNotification) responsible
for handling broadcasts sent from the Pip StatusBarNotification.
Previouslt TV PipContoller was in charge of that.
Also, as mentioned above, rename PipNotification to
TvPipNotificationController.
Bug: 153784643
Test: atest WMShellFlickerTests:TvPipNotificationTests
Change-Id: Iabdf5ee9d464653e233aee9044ac8cbb26478dea
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: 161118569
Test: make SystemUI
Test: make ArcSystemUI
Test: make WMShellUnitTests
Test: lunch cf_x86_tv-userdebug & make
Test: atest CtsSystemUiTestCases:BasicPipTests
Test: atest CtsSystemUiTestCases:CustomPipActionsTests
Test: atest CtsSystemUiTestCases:FlickerPipTests
Test: atest CtsSystemUiTestCases:PipNotificationTests
Test: atest SystemUITests
Test: atest WMShellUnitTests
Test: manual test PIP demo AP
Test: manual test TV PIP function
Test: manual test disabled PIP
Test: adb shell input keyevent 171(KEYCODE_WINDOW)
Test: adb shell am start -n android.systemui.cts.tv.pip/.PipTestActivity
-a android.systemui.cts.tv.pip.PipTestActivity.enter_pip
Test: adb root;adb shell am start \
-n com.android.systemui/com.android.wm.shell.pip.tv.PipMenuActivity
Test: adb shell dumpsys activity service com.android.systemui
Change-Id: I0ec0e9b9bfc4795a10483acd225f14bde9c72407
|
| |
|
|
|
|
|
|
|
| |
Rename the method to setBlockable. Also rename isBlockableSystem in the
same way.
Fixes: 151311073
Test: atest NotificationChannelTest
Change-Id: Ie25f8aed3c22b74d9ad2329863c4ffebbace03f7
|
| |
|
|
|
|
|
|
|
| |
The next step is to remove `components` from the SystemUI objects
and replace them with Dagger injection.
Bug: 138786270
Test: atest SystemUITests
Change-Id: I27415a8fa8ba0378599356426d849c9cfb9879d2
|
| |
|
|
|
| |
Test: n/a
Change-Id: I432e11b52deb7974e50f62076af3b7aa07e364b6
|
| |
|
|
|
|
| |
Test: runtest systemui-notification
Change-Id: Iab2eebb0da8163f520af95c2ad5fd8f35333a9d5
Fixes: 109777940
|
| |
|
|
|
|
|
|
| |
But silence them by saying them cannot bypass DND.
Test: atest SystemUITests
Bug: 77656914
Change-Id: I044696cfdcef0e4a14be21173949612480722236
|
| |
|
|
|
|
|
|
|
| |
- both System and SystemUi notification channels' names
change on locale update
Change-Id: I0d23fe9b008c608c54ac178a97c2f682aa46d954
Fixes: 64887866
Test: manual
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Spec: go/ebs-low-battery-mode-flow
- Basically when the user manually enables battery saver 4 times,
we show this notification to suggest turning on "scheduled"
(i.e. auto) battery saver.
- We show it through 8th time. If the user hits "no thanks",
or if auto-saver is enabled already, we will not show it.
- Introduced a new notification channel "HINTS" with
IMPORTANCE_DEFAULT.
Bug: 74120126
Test: Manual test with ll development/scripts/battery_simulator.py
Change-Id: I713abc59dc7caee6882ba848c3e3aabaf778c2bd
|
| |
|
|
|
|
|
|
|
| |
Allow some channels to be blocked, and most to
bypass DND.
Test: make
Change-Id: I135ef6f32a15bb2fc9c859ab087b2dc7477d67e1
Fixes: 75429403
|
| |
|
|
|
|
| |
Test: updated ChannelsTest; manually verified heads up ss posted and old channel deleted.
Change-Id: Iafc1c65d3e8a5929ba922a2814848ce5bc036747
|
| |
|
|
|
|
| |
Change-Id: I51c8e099da04d4bf1a55d081c9fce7fc8fb90bd1
Fixes: 63853037
Test: runtest systemui
|
| |
|
|
|
|
|
|
| |
Bug: 37249867
Test: Manual test (checked that the notification UI is shown when the
PIP starts, and dismissed when the PIP is closed. The 'DETAILS' and
the 'DISMISS' button in the notification also worked.)
Change-Id: I12e385b51f834991a0115ce5ba7dd98180577adb
|
| |
|
|
|
|
|
|
|
| |
Apps can listen for the LOCALE_CHANGED broadcast to
change names if needed.
Fixes: 35336590
Test: runtest systemui-notification, cts, manual
Change-Id: I62d2778f61e99200692755a6f268828a374837e6
|
| |
|
|
|
|
| |
Bug: 35164265
Test: Using the Sabrent 120Gb external drive and manually going through all flows
Change-Id: If856cfd3b67bb97b60998d805f9ebb3d459cf28f
|
| |
|
|
|
|
| |
Bug: 35336590
Test: runtest sytemui runtest systemui-notification, manual
Change-Id: I1e6ebbcc36cab22ab9b2dfde505a68513544ef52
|
| |
|
|
|
|
|
| |
Some changes to channels based on UX feedback.
Test: runtest systemui
Change-Id: I1b2f661ba145d6926035f992231dc3c2f8cbf844
|
|
|
There are five channels at present:
ALERTS - low battery etc.
SCREENSHOTS - progress & result
SECURITY - notifications hidden due to policy
STORAGE - disk low
STATUS - basically everything else
The importance for each channel should match the legacy
priority of the notifications it carries.
Bug: 34250937
Test: runtest systemui
Change-Id: I5915ca453258caea63b0d9bd756893db05e8d600
|