diff options
| author | Josh Tsuji <tsuji@google.com> | 2022-01-11 14:06:05 -0500 |
|---|---|---|
| committer | Josh Tsuji <tsuji@google.com> | 2022-01-11 20:23:04 +0000 |
| commit | 9d5f970c7638d9951bf95d9aed6a0f627fb20da0 (patch) | |
| tree | 355bad130400479868558c7b3fd54f63b7c1286a /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 091aba9717f189ed6d99379079b6c3c339c3ac91 (diff) | |
Check if the SIM is secure before dispatching swipe to unlock.
Due to an existing bug, KeyguardStateController#canDismissLockScreen
returns true even if the device is SIM-locked, if there is no device
lock set. This caused the new sc-v2 unlock code to believe we could
dismiss the lock screen via swiping. Since the panel expansion is used
to drive swipe to unlock on the lock screen, this meant that swiping
the notification panel over the emergency dialer was interpreted as a
swipe to unlock, so we unlocked.
We'll fix the underlying issue with canDismissLockScreen in T:
b/214057466. This method is used 25+ times all over the code, and it
would be extremely risky to add the SIM-lock check there at this point.
Fixes: 214057466
Test: insert locked SIM, emergency dialer, pull down shade, try to go back/home
Change-Id: Iee86cadc8c4903c703d4fab515dc4f6f73953467
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions