Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 76ab55e4 authored by Josh Tsuji's avatar Josh Tsuji
Browse files

Always start dismiss transition when the going away animation starts. 

Flag: com.android.systemui.keyguard_wm_state_refactor
Bug: 278086361
Test: atest SystemUITests
Change-Id: Ie538dbc49fab99e1883f72792608ec56f3c8184f
parent bd18856d

packages/SystemUI/src/com/android/systemui/keyguard/WindowManagerLockscreenVisibilityManager.kt

+10 −8
Original line number Diff line number Diff line
@@ -142,15 +142,17 @@ constructor( 
        nonApps: Array<RemoteAnimationTarget>,

        finishedCallback: IRemoteAnimationFinishedCallback

    ) {

        if (apps.isNotEmpty()) {

        // Ensure that we've started a dismiss keyguard transition. WindowManager can start the

            // going away animation on its own, if an activity launches and then requests dismissing

            // the keyguard. In this case, this is the first and only signal we'll receive to start

            // a transition to GONE.

        // going away animation on its own, if an activity launches and then requests dismissing the

        // keyguard. In this case, this is the first and only signal we'll receive to start

        // a transition to GONE. This transition needs to start even if we're not provided an app

        // animation target - it's possible the app is destroyed on creation, etc. but we'll still

        // be unlocking.

        keyguardTransitionInteractor.startDismissKeyguardTransition(

            reason = "Going away remote animation started"

        )



        if (apps.isNotEmpty()) {

            goingAwayRemoteAnimationFinishedCallback = finishedCallback

            keyguardSurfaceBehindAnimator.applyParamsToSurface(apps[0])

        } else {