Tie KeyguardStateCallbackInteractor state to WmLockscreenVisibility + add...
Tie KeyguardStateCallbackInteractor state to WmLockscreenVisibility + add dismiss callback notifications. Using KTF state resulted in some showing-state updates coming in just before the WM setLockScreenShown call, which causes issues in tests and also logically doesn't make sense. Also, whenever we setLockScreenShown(false), notify the dismiss callback registry. Bug: 278086361 Test: atest KeyguardLockedTests Flag: com.android.systemui.keyguard_wm_state_refactor Change-Id: I86b5edfe614a12a84e2722ae73b5d1dd9208cc43
Loading
Please register or sign in to comment