diff options
| author | 2022-11-02 18:42:27 +0000 | |
|---|---|---|
| committer | 2022-11-05 17:14:21 +0000 | |
| commit | af57f130e948e4d9399c428c042e7b87ea42df06 (patch) | |
| tree | 13f825806641766fbf70d9e23302b233d0025a94 /libs/input/PointerController.cpp | |
| parent | 7fcef9e6d45cc1bf615031f8d7a0c8b47671a31a (diff) | |
Always trigger face auth even when it is locked out.
1. This is the only way to show a message on keyguard that face unlock is not available in response to all face unlock triggers.
2. This was the behavior of face auth until recently (b/244402839#comment11)
Other options:
- Add a new callback method to a KeyguardUpateMonitorCallback to indicate that face auth trigger occurred.
- Adding a new method to a long list of methods in KeyguardUpateMonitorCallback is not a good idea
- This would be a very specific API that no one else might even need.
Indication message shown on keyguard:
1. first time face lockout.
- Shows "Too many attempts. Face Unlock disabled." followed by "Use fingerprint instead" or "Swipe up to open"
2. while the face is already locked out
- when the device wakes up
- "Face Unlock unavailable." followed by "Use fingerprint instead" or "Swipe up to open"
3. Coex when both face and fingerprint are locked out
- when the device wakes up
- Existing behavior is retained, nothing is shown.
No difference in behavior between bypass vs non-bypass
Bug: 247688462
Test: atest KeyguardUpdateMonitorTest
Change-Id: I3c7e15818eedfef9b5af9dd0b0fc29b7fda231e1
Diffstat (limited to 'libs/input/PointerController.cpp')
0 files changed, 0 insertions, 0 deletions