Somehow one of the tiles doesn't have a view yet. Assume that this
is a transient part of the tiles getting recreated and that the skipped
tile will get picked up in the next layout.
Change-Id: Ia1370d66119bfcfa7b00bd087bcb0d72a072666a
Fixes: 31394359
- Prevent third party apps from inadvertently changing internal SystemUI
flags through a call to setSystemUiVisibility(). These flags are only
set in the individual SystemUI components and can be updated in WMS
directly.
Bug: 29875297
Change-Id: I5ea238c8fb16a0eccd6e993d95a912acb359cee6
If a notification is updated to be non-dismissable it gets "snapped back"
into place, if the notification was slid over to show the gear when this
happens it'll snap back to the gear. If the screen is turned off during
this time, the notification tries to reset itself back over the gear.
The translation animator was not cancelled in the reset method, so the gear
visibility would get reset, but the translation animation to snap back
into position would continue. This results in the notification being slid
over but the gear being invisible.
The fix is to simply cancel the animator when the translation is reset.
Bug: 31437688
Change-Id: Icb9d777e30ee3a5578c49475b89f6d46c1096053
Work profile challenge is shown by intercepting normal activity launching and
replacing it with the confirm credential activity. For direct boot aware
activities, they should be able to be displayed when the work profile is
still locked, so add a conditional in the activity intercepting logic to bypass
work challenge in this case.
Also launching work profile activities from notification is handled specially
in order to avoid dismissing the notification if the work challenge is canceled,
so add similar logic there to allow direct boot aware activity to go through.
Bug: 30296144
Change-Id: Ib6395271cee2d4781009bb08d50351d73824de0c
1. When dreaming starts before locking, notifications can remain
pinned. This is because the device is locked without
screen off, and HeadsUp are not escalated.
As a result is the pinned heads up shown behind the bouncer
when unlocking.
In this case touchable bound is limited to headsup bounds,
so the user can't unlock at all.
2. Escalate HeadsUp when bar state changes to KEYGUARD
3. This also fixed a bug where the bouncer isn't touchable
When device is occluded and locked, HeadsUp can appear.
If the user then clicks on the HeadsUp and try to send
pending intent, Bouncer can be shown without expanding
panel.
Bug:30820511
Change-Id: I8604c9d00d839d773b32d8b913dfdcd2ed72f1dd
It was using DeviceDefault which is black in AOSP. It should be using
the blue grey primary color instead used by DeviceDefault.Settings.
Bug: 30748928
Change-Id: I7e7ed87f74f654f412c106a44906d7fba4e992dc
Swiping to show the gear for ongoing notifications can be difficult, this
CL adds an additional check for the duration of the gesture, if the
gesture takes long enough on an non dismissable notification then it
considers it a gear reveal.
Bug: 30908400
Change-Id: Iec769bae2a70ef79acb43c69063cc9e2b6b1f56f
Fix overlapping issue of overflow number view in RTL layout.
And also, fit the width of overflow Single-line view to match_parent.
Change-Id: I436a3770c8a0001b7a577e3f726bb52cd978298e
Fixes: 31181327
When the locale changes, update not only text
but also contentDescription of the DismissView.
Test: switch language and observe dismiss view description
Fixes: 31320721
Change-Id: If89fd6d2f3c3819927a181ff69849b66855ae451
Fixes a bug where the icon area and user switcher
could overlap if the animation was canceled at a
bad time.
Change-Id: I21713512fb5c70c45439258609b87a585675304a
Fixes: 30865084
Fixes a bug where the RemoteInputView would issue an
utterance upon resetting the view because it was not
hidden at that point.
Change-Id: I3f80b903c0b3e55c308bda8d4f18aa0b586aa328
Fixes: 30103313
Some top level Settings menus launch activities from other packages.
In that case, they should be considered as a part of the Settings
if they follow the Leanback's side panel style.
Add such activities to the whitelist to keep the PIP position.
Bug: 31142005
Change-Id: I12cab611b346154048cbd61f6a678f23b5a10c00
If a user doesn't have credentials, we start the unlock process
automatically, but that races with the UI binding process. Fix by
rebinding the UI once we hear the user is unlocked.
Change-Id: Id678b97aa6120ba78088fb6cf4c2a65d129e98a3
Test: none
Bug: 30840626
(cherry picked from commit 181001379f)
