| 21a0d1eee17d708eae926df8b719eda7f847c1ac |
|
27-Apr-2018 |
Ilya Matyukhin <ilyamaty@google.com> |
Updated haptic effect for success
Fixes: 78596832
Test: tested on a device
Change-Id: I5953bdb367867b001bc85a2bf799c77b65b3b9d4
/frameworks/base/services/core/java/com/android/server/fingerprint/ClientMonitor.java
|
| d9ec6df38cf97d5a8931da5110daed2268cfa43c |
|
20-Mar-2018 |
Beverly <beverlyt@google.com> |
Fingerprint vibrate doesn't change based on DND
Add sonification audio attributes to fingerprint vibration,
so it doesn't get 'muted' by DND.
Bug: 76016723
Test: manual
Change-Id: Ib0ccab2003853ced01d3be97032d261bdc1b6430
/frameworks/base/services/core/java/com/android/server/fingerprint/ClientMonitor.java
|
| 6726fd5cc66e43d54b2988a1b107888f343c5d74 |
|
27-Jun-2017 |
Michael Wright <michaelwr@google.com> |
Update fingerprint haptic patterns
Have fingerprint take advantage of the haptics capabilities of new
devices. In particular, use prebaked DOUBLE_CLICK effect for failure
since we tune that to feel good for a specific piece of hardware, and
use the equivalent of the long press effect since we tune that to be the
strongest feeling single click effect that doesn't cause the device to
feel "buzzy" or annoying.
Bug: 62392467
Test: manual
Change-Id: I9331718b1d515959a4b5f8bd0f17243b28a6f788
/frameworks/base/services/core/java/com/android/server/fingerprint/ClientMonitor.java
|
| 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/ClientMonitor.java
|
| 80e40ccf49bca22a6eb1846a582574092f3e0c1a |
|
14-Mar-2017 |
Kevin Chyn <kchyn@google.com> |
fixed typos in log
fixed bug 34845702
Test: manual
Change-Id: I6bb87d4a99b7af3c186c647cc1450c1d11e85f52
Signed-off-by: Kevin Chyn <kchyn@google.com>
/frameworks/base/services/core/java/com/android/server/fingerprint/ClientMonitor.java
|
| 7e1cb55230055b04e5c6c86deae5412dfe0799a7 |
|
28-Feb-2017 |
Jim Miller <jaggies@google.com> |
Don't crash if client token is null.
Test: verify that fingerprint clients still work and that
null client no longer crashes systemui.
Fixes bug 35806157
Change-Id: Icda7fb538caf50ba44297fe8e47c35aed1275280
/frameworks/base/services/core/java/com/android/server/fingerprint/ClientMonitor.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/ClientMonitor.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/ClientMonitor.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/ClientMonitor.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/ClientMonitor.java
|