Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

Commit

Permalink
Merge "Don't reset the keyguard on occlusion if it's going away." int…
Browse files Browse the repository at this point in the history
…o tm-d1-dev am: f50462e

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/19509200

Change-Id: I0dd7d5ab7921d84bae5db791954db5d695441568
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
  • Loading branch information
TreeHugger Robot authored and android-build-merge-worker-robot committed Aug 4, 2022
2 parents 799cb3f + f50462e commit 9f8a5c0
Showing 1 changed file with 4 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -739,8 +739,10 @@ public void run() {
}
mNotificationShadeWindowController.setKeyguardOccluded(mOccluded);

// setDozing(false) will call reset once we stop dozing.
if (!mDozing) {
// setDozing(false) will call reset once we stop dozing. Also, if we're going away, there's
// no need to reset the keyguard views as we'll be gone shortly. Resetting now could cause
// unexpected visible behavior if the keyguard is still visible as we're animating unlocked.
if (!mDozing && !mKeyguardStateController.isKeyguardGoingAway()) {
// If Keyguard is reshown, don't hide the bouncer as it might just have been requested
// by a FLAG_DISMISS_KEYGUARD_ACTIVITY.
reset(isOccluding /* hideBouncerWhenShowing*/);
Expand Down

0 comments on commit 9f8a5c0

Please sign in to comment.