summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Robin Lee <rgl@google.com> 2024-02-29 15:14:34 +0100
committer Cherrypicker Worker <android-build-cherrypicker-worker@google.com> 2024-03-12 13:38:41 +0000
commit6f24f35fceecf90b15031e6fff87d00f404af523 (patch)
treeca56bf856c46fdfb1d2fce78e29b79f48113eee2 /libs/androidfw/StringPool.cpp
parent64ea99b48ca647440bdabfebbfee18ae4f5a28f1 (diff)
When wallpaper target is under keyguard, use keyguard
The case this is specifically aimed at is recent apps over the lockscreen, where the wallpaper target isn't visible during the transition or at its end but is replaced by NotificationShade when it reports finished. The problem this solves is that the wallpaper visibility cleanup in Transition.onFinish was run before the NotificationShade had a chance to make itself wallpaper target, as this was not necessarily recalculated yet. For normal app <-> app transitions, wallpaper target is calculated much earlier during collection. Since keyguard is just a mode of the notification shade there is no collection to be done for it and so the wallpaper target change is not knowable upfront. We don't use the wallpaper as its own target in this case because the keyguard does not necessarily want a wallpaper - it may become an opaque window on some form factors / skins. Bug: 315698413 Test: atest WallpaperControllerTests Test: atest PlatformScenarioTests:android.platform.test.scenario.sysui.lockscreen.LaunchCameraFromLockScreen (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:719144b3a596a9ca0b7161dfe972eb8843939732) Merged-In: Iaa631b75d5bc24444bd7c808e0aa056620edcc4b Change-Id: Iaa631b75d5bc24444bd7c808e0aa056620edcc4b
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions