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

Skip to content
Commit 0d9eccf8 authored by Kevin Chyn's avatar Kevin Chyn
Browse files

Don't cache lockout state in KeyguardUpdateMonitor

Partial revert of ag/5369172 - caching the state makes it too complicated
in SystemUI. Issues are as follows

1) SystemUI did not track lockout per-user
2) SystemUI would not show lockout after the initial error

The bug (b/118235602) is already fixed by calling update*ListeningState
instead of startListening.

Test: 1) Enroll multiple users and set up FP
      2) Lockout one user
      3) Switch to second user
      4) Switch back to first user - lockout message is shown

Test: 1) Lockout user
      2) Unlock with pin/pattern/pass
      3) Look at FingerprintService logs - SysUI does not authenticate
         when the user is already unlocked

Bug: 118235602
Fixes: 126926000



Change-Id: Ia8dd44b0dda4246bd94e5f72bf3b0a72ff20eb13
parent 8c7968a8
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment