Make the condition of DISABLE_RECENT more robust in launch GCA CUJ
There's race on below CUJs 1. Keyguard Fingerprint Unlock + Double tap power key to launch camera 2. Keyguard Face Unlock + Double tap power key to launch camera Latency info a. Fingerprint unlock latency : 120ms ~ 180ms b. Face unlock latency : 800ms ~ 1000ms c. Double tap power key launch camera gesture(b/195788686#comment12) : 170ms ~ 190ms The 100% repro CUJs on both gesture nav & 3-button nav modes 1. UDFPS + double tap launch GCA gesture t0 : User finger down, UDFPS request auth t1 : Double tap power key to launch camera t2 : UDFPS auth passed, keyguard is going away t3 : Camera launched occluded keyguard(mPowerGestureIntercepted=true), `flags |= StatusBarManager.DISABLE_RECENT;` t4 : Keyguard hide, launcher on top 2. Face + double tap launch GCA gesture t0 : User lift to wake, Face auth t1 : Double tap power key to launch camera t2 : Face auth passed, keyguard is going away t3 : Camera launched occluded keyguard(mPowerGestureIntercepted=true), `flags |= StatusBarManager.DISABLE_RECENT;` t4 : Keyguard hide, launcher on top Bug: 268593702 Fixes: 284669723 Test: Concurrently unlock by UDFPS + double tap power key launch GCA Make sure the recents keys and overview works good in launcher Test: forest v2/aep-ironwood/suite/test-mapping-ironwood-p0-cujs Test: atest BiometricsWakeAndUnlockLaunchCamera Test: atest LaunchCameraFromHomeIn3ButtonMode Test: atest LaunchCameraFromLockScreenIn3ButtonMode Change-Id: Ia9243d3d3569747afa9ef8d8a27c59f30573a6ad
Loading
Please register or sign in to comment