4be9b2ca3eb18bfbe00be853721ee804105cd247 |
|
15-May-2017 |
TreeHugger Robot <treehugger-gerrit@google.com> |
Merge "Keyguard shouldn't listen to FP if bouncer showing and keyguard dismissing" into oc-dev
|
6db7d5fc84ae67cc0d11b0cd376b5cf21a1fafd3 |
|
04-May-2017 |
Kevin Chyn <kchyn@google.com> |
Keyguard shouldn't listen to FP if bouncer showing and keyguard dismissing There's a race condition if user unlocks from bouncer and an app underneath uses FP does onResume() If a user has an application that's authenticating via FP underneath keyguard and the user dismisses keyguard via bouncer, the app underneath will get kicked out since onKeyguardVisibilityChanged(false) calls shouldListenForFingerprint() during this race. Keyguard shouldn't listen to FP if bouncer is showing but keyguard is dismissing Fixes: 37967985 Test: 1) open FP settings 2) enter keyguard and go to bouncer 3) unlock keyguard via pin/pattern/password (NON FP method) 4) tap any finger on sensor (should vibrate) Merged-In: Ie38d55e6a1ec9b49f9df0c7520d0bc451315c161 Change-Id: Ie38d55e6a1ec9b49f9df0c7520d0bc451315c161
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|
df9d33e9039d8567ea82f67a76d95a7ae7ab8df8 |
|
04-May-2017 |
Kevin Chyn <kchyn@google.com> |
strong fp lockout after 20 failed attempts Fingerprint currently locks out for 30s after every 5 failed attempts. This change makes it so that in addition to the above, PIN/pattern/password will be required after 20 failed attempts. Fixes: 35954316 Test: manual Change-Id: I3aeb0e5b5b4d5011555f60fbe6cc2c1ce702a670
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|
0c45b07fe238b3e88f30c67219440669818aa1ee |
|
25-Apr-2017 |
Kevin Chyn <kchyn@google.com> |
FP won't wake device if daemon dies Keyguard should retry FP auth if HW unavailable occurs Fixes: 37483809 Test: enroll FP, turn off screen (enter keyguard) pid biometrics | xargs adb shell kill -9 after 3 seconds, FP should be able to auth again Change-Id: Ied3a4c07de655f3145ad40e3b73078fe9b161291
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|
625a014006d63ddb59c4b3b7520f0b14afbc18a3 |
|
10-Apr-2017 |
Kevin Chyn <kchyn@google.com> |
Keyguard should authenticate with FP even after getting valid FP There may be strange states where the user is already authenticated but still on the lockscreen. The user should be able to dismiss keyguard in that state. Fixes: 29306222 Test: unlock phone go back to keyguard swipe up screen half way touch fingerprint sensor (icon should change to unlocked) then touch fingerprint sensor again (keyguard should be dismissed) Test: unlock phone and go to settings -> Pixel Imprint lock phone, unlock phone with fingerprint touch sensor again and make sure Pixel Imprint page also responds to FP do this test at least 10 times Change-Id: I86acd520a06a68fab3548dd4cf6153a7833114fe
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|
7e4602519977b6bb9c41afc91a44ca782e716e40 |
|
11-Mar-2017 |
Sanket Padawe <sanketpadawe@google.com> |
Change 'idx' to 'index' in SubscriptionManager & TelephonyManager apis. Bug: 35767068 Test: No build failure. Change-Id: I3b15901ff18742b5e99f03e74a6412d352461458
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|
91ba307d9bbd1b9c62feb1bea1d8035d11572d72 |
|
14-Feb-2017 |
Adrian Roos <roosa@google.com> |
AOD: Show fingerprint error messages Change-Id: I6570bffed1632b5e42ad5f82f7e0ab6192e04e1d Fixes: 34902351 Test: Enable fingerprint, get notification on Ambient Display, try to unlock with wrong finger. Verify that the fingerprint not recognized message shows
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|
23f85ec14dab49b2c525dc266d2a1f74f7f9d07c |
|
31-Jan-2017 |
Jason Monk <jmonk@google.com> |
Move Keyguard to SystemUI Test: make Change-Id: I3abb67e2b022737d2aa0226bb07f3966ad68fff7
/frameworks/base/packages/SystemUI/src/com/android/keyguard/KeyguardUpdateMonitor.java
|