diff options
| author | 2024-06-11 17:05:25 -0700 | |
|---|---|---|
| committer | 2024-06-12 13:08:28 -0700 | |
| commit | 1795db0c4ac3d99fd7c6f982873bc39602abaa4d (patch) | |
| tree | f066957b3ffa3988e0d2b813056fe7f14b2035f9 /libs/androidfw/ZipFileRO.cpp | |
| parent | 0c1aab59338f3f97f55aa87ac370b7c4fac04990 (diff) | |
Fix UMO missing on lock screen when starting from hub
If the glanceable hub claims that the UMO should show on the hub, this
always overrides the UMO on the lock screen. After UMO transitions to
and from the hub were implemented, the hub's claim to the UMO changed
to be purely based on transitions instead of scene state.
However, this meant that if you started on the hub and made it to the
lock screen through any method other than a direct keyguard transition,
the UMO would be missing from the lock screen. For example, if you
unlock on the hub then press power button twice to return to the lock
screen, or if you press power on the hub, wait 5 seconds, then press
power again to show the lock screen, the UMO will be missing.
This change adds a failsafe to ensure the hub only claims the UMO if
the hub is visible at all.
Bug: 343270202
Fix: 343270202
Test: atest CommunalTransitionViewModelTest
Flag: com.android.systemui.communal_hub
Change-Id: I52fb213d9cb9188272702f1c2e6765ba065e4105
Diffstat (limited to 'libs/androidfw/ZipFileRO.cpp')
0 files changed, 0 insertions, 0 deletions