- Without this screen would light up for just a few seconds, matching would be unreliable and often error out with GF_ERROR_ACQUIRED_IMAGER_DIRTY or GF_ERROR_TOO_FAST
Change-Id: Ibc02d111224dc0921bf91c7b69330dcda2c7dc8f
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>
These methods can be used to handle vendor acquired messages and disable
fod listening on cancelled and successful unlocks.
Change-Id: Ie6a8d24840b0b6c34527f863a6052f789200a79f
This is more like a hack, also observed in the stock HAL, for pre-P shipped devices
because those have fpdata store path set to /data/system/users/ by the FingerprintService.
Force treble compliant path and thus avoid using data_between_core_and_vendor_violators
attribute:
> typeattribute hal_fingerprint_default data_between_core_and_vendor_violators;
> # access to /data/system/users/[0-9]+/fpdata
> allow hal_fingerprint_default fingerprintd_data_file:dir rw_dir_perms;
> allow hal_fingerprint_default fingerprintd_data_file:file create_file_perms;
Change-Id: I388f993de7f95fc68007d945f5a9cc975afde120
While Google found that fingerprint HAL is insensitive to
increased CPU throughput, we have not found that to be the
case. Allowing more CPUs makes fingerprint unlock up to
2x faster in some tests.
SM8250 device with fingerprint on display:
- Before: 3128ms
- After: 944ms
SDM845 device with fingerprint on the power button:
- Before: 1146ms
- After: 688ms
This reverts commit d0fdb4431d26e4f257b8867f67ffd9b4a9818d9e.
Change-Id: I7a28d82caee2b8503b974a8226b29240eb072ceb
