| 373685817cb5ee094c64c3358995ca50656b3dbe |
|
20-May-2017 |
Kevin Chyn <kchyn@google.com> |
ClientMonitor should only send cancel() once to fp daemon
This is already done for AuthenticationClient.
This should be done for all ClientMonitor subclasses which override
stop(), otherwise hardware and framework will be in inconsistent states.
Fixes: 38463417
Test: 1) Open fp settings in background, enter keyguard, dismiss
keyguard with fp and make sure settings can "authenticate"/highlight
fp when touched
2) Enroll fp and go back/forth between FingerprintEnrollFindSensor
and FingerprintEnrollEnrolling. Make sure touching fp sensor
will always bring you to FingerprintEnrollEnrolling
Change-Id: Iee3d03c8a8b3445073740fbfbe411f12172afe23
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| ee17d352d641cdcfc955f0e37b0ca042427f2879 |
|
16-May-2017 |
Charles He <qiurui@google.com> |
Fingerprint: call onRemovalSucceeded with # of remaining templates.
The onRemoved() callback from fingerprint daemon provides a "remaining"
parameter which contains the number of fingerprint templates yet to be
removed in the current removal operation. This is especially useful when
a group is removed, as remaining == 0 indicates the end of the group
removal.
In this CL, we wire up FingerprintManager so that the "remaining"
parameter gets passed to RemovalCallback#onRemovalSucceeded(). This
would allow clients like Settings to make use of the information.
Bug: 37938345
Test: manual, both with and without work profile
Change-Id: Idf46ef42e1d178cd3dc267aaf4219f03e27be766
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| ac521ec3f59b1d6e7c313a3c2e4b7afb372e01e9 |
|
04-May-2017 |
Kevin Chyn <kchyn@google.com> |
RemovalClient sendRemoved should check remaining instead of fingerId
Test: for each of the following, make sure code goes into
if (client != null && client.onRemoved(fingerId, groupId, remaining)) {
removeClient(client);
}
1) remove single fingerprint
2) remove all fingerprint by removing password
Change-Id: I6f1ebd42c05fd57225dd4808766791ff1922b09e
Fixes: 37992170
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| d1f1a0b60a660cbff9efdf77c2aed11e1f7061f2 |
|
03-Apr-2017 |
Kevin Chyn <kchyn@google.com> |
Implement enumerate in FingerprintService
Enumeration will happen only for the current active user.
Fixes 35358801
Test: manual
Change-Id: I4c935626edba6eceb1aec4f79a7b3a39313943a5
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| 40e4645e6e564b962bb73c85c5325ec54ad34cc1 |
|
17-Dec-2016 |
Jim Miller <jaggies@google.com> |
Rewrite FingerprintService to use HIDL 2.1
Bug: 33199080
Test: Fingerprint enroll, remove, unlock, fingerprint arbitration.
Change-Id: I8b98236ba81f053527ee74c8a189af1adfd17d55
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| c57c8d934cf77673154bc81d767365b4d6cda33f |
|
01-Oct-2016 |
Jim Miller <jaggies@google.com> |
Add metrics logging for critical fingerprintd errors
This adds logging when fingerprintd dies or invoked functions
fail so we can track driver breakage:
- failure to start fingerprintd (fingerprintd_openhal_error)
- fingerprintd dies (fingerprintd_died)
- call to authenticate/enroll/enumerate/remove fails
Fixes bug 30896409
Change-Id: Ic53fcd551ba909ef141893796b33b52cd5e56395
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| 8f2aca0ee4ff0eff6226df05d1531d2f2fa2f3c1 |
|
20-Apr-2016 |
Jim Miller <jaggies@google.com> |
Fix bug where fingerprint for wrong userId was attempted to be removed.
- cleaned up private API to ensure userId is distinct from groupId.
- fixed bug where we were sending the wrong userId when attempting to
- fix warning about wrong fingerId when receiving final id of 0.
Fixes bug 28268635
Change-Id: I9507723c1a763152775f2feff76c16762f23cf2d
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| ff715ac551fcb09640acdf28278384ca2d5f85c0 |
|
19-Apr-2016 |
Tony Mak <tonymak@google.com> |
Fix the misuse of calling user id as group id
1. The userId stored in different clients are actually calling user id.
groupId should be used to do all the operations. Also, renamed the variable
to avoid further confusion.
2. Fix the bug null is always returned in getFingerprintDaemon
in RemovalClient.
3. Fix the misuse of calling uid as calling user id in startAuthentication.
Fix: 28268635
Fix: 28264725
Change-Id: I618ac3c6d913ae5c86e7b04cb3f9ead39828f216
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|
| cb2ce6f1f0deef80943ece093ae40bacc1f57c44 |
|
14-Apr-2016 |
Jim Miller <jaggies@google.com> |
Fix bug where fingerprint events can be delivered to the wrong client
- Make FingerprintService more closely track the expected state of fingerprintd.
- Don't switch to a new operation until fingerprintd completes previous operation.
- Refactor clients into separate classes and add tracking logic.
- Add missing enumerate()/cancelEnumeration() methods to IFingerprintDaemon
- Make late-binding decision of "foregroundness" of activity so that it's
decided in the order the events are actually handled.
- Add more logging so we can determine FingerprintService state when errors occur.
- Cache a copy of authenticator_id from the last time it was set so we don't
interrupt the driver during actual authentication.
- Don't allow clients to access authenticator_id unless they're current.
Fixes: 27902478, 26273819
Change-Id: Ic1f9e30bd89bcdbb8fe7f69e0545e68339317721
/frameworks/base/services/core/java/com/android/server/fingerprint/RemovalClient.java
|