This change adds onBubbleOrderChanged to BubbleStackView
to try to keep the order synchronized. There are some known
issues with the animation and visual state, which will be
addressed in a follow up CL.
Bug: 123542488
Test: BubbleControllerTest BubbleDataTest
Change-Id: Ie5a679df2f3069236f4d67a3fce4189b39b9eb28
Make sure to read the opportunistic carrier display property
Bug: 131849855
Test: verified that carrier text is displayed correctly
Change-Id: I93f9da8d0a9a8dae276370a0cca2df889229d4c3
- Add back arrow for QS customizer
- Update work profile status bar / QS / corp badge icon to GM2
- Add Settings and Launcher overlay icons
Bug: 131346125
Test: visual
Change-Id: I61b56b04993ef19b5e66c9ad3d78eddcfce3aeb1
This is a refactor. It touches a lot of files, but zero functionality.
The primary change is changing FalsingManager.getInstance() into
FalsingManagerFactory.getInstance(); chaning FalsingManager into an
interface, and then turning the existing FalsingManager into
FalsingManagerImpl, an implementation of that interface. Other changes
are merely references to those classes.
Bug: 130256776
Test: atest SystemUITests
Change-Id: I5d64a7673e4efc554105dd841b27807361ed3828
Bubbles has some particular notification behaviour needs:
1) Whenever there is a bubble, the notif is kept around but may be hidden
from the shade
2) When the bubble is dismissed, if the notif is no longer in the
shade => really remove the notification
3) When the bubble is dismissed, if there is still a notification in the
shade => notif stays around and is normal
4) Clear all should only hide the bubble notification, not remove the
bubble
5) Apps canceling a notification that has a bubble will cancel the bubble
This CL does this by:
* Including the removal reason removeNotification path
* Adding a NotificationRemoveInterceptor that gets the option of overriding
the removal
* BubbleController has this new interceptor and uses the removal reason
to determine what should happen to the bubble & if the notification
should be allowed to be removed
* When the bubble is dismissed, if the notif is no longer in the shade,
then actually remove that notification
Test: atest BubbleControllerTest NotificationEntryManagerTest
Bug: 130347307
Bug: 130687293
Change-Id: I4459864a2ee5522076117f84ae37022bdfe4ee5d
Because we are freeing the AOD view, the view was not attached
to the window anymore and therefore we would not trigger the
remote input. Additionally if the expanded view was already showing
on AOD, we also wouldn't wait on it to become visible, also leading
to an issue where the user couldn't reply.
This also fixes an issue where the notificaiton would be invisible
if it was replied to in a group.
Fixes: 118365629
Fixes: 110072505
Change-Id: Ied33ed19eacc115006f5457f427acd4fefe0494b
Don't try to get it from the notification because the notification
is inflated in an async task.
Fixes: 130775480
Test: visual -- played music with GPM and checked background updated
Change-Id: I891f06b05b4ca4ba570a3b405fefa7b049f05cca
Otherwise the notification shade would be expanded behind the
the pin pad.
Test: manual
Test: atest StatusBarKeyguardViewManagerTest
Fixes: 120767257
Change-Id: Ic8f5e4477e75dddbefc5e2c5decd0f5a74289591
This will make the association with smart actions closer. This changes
the transition when opening an action from a two step close shade - open app
to a direct animation into the app from the notification.
Fixes: 123591046
Test: atest SystemUiTests
Change-Id: I3c92aa20437ca7c37ef27ae6618df1959ef63137
