This has been fixed in the kernel.
Also remove its sepolicy.
This reverts commit 96d068a98debbd934a6f264f8befedc9f31f0277.
Change-Id: Ic54d8a76ac66a090966de60e4ed904be578d5655
* onFingerUp() would also be called during unlocking with Pin/Password/etc, always resetting the brightness to the previous value
Change-Id: I5319a8a50a4ad3308e787322c6c2a417b9169b23
*Optical fingerprint sensors don't like NightDisplay and ExtraDim since those decrease overall sensor accuracy
*Turn ExtraDim off and set NightDisplay's color temperature to AOSP's default white balance value if the fingerprint sensor is touched
Change-Id: I6651cd5c8c066102feebfb764184b099c6ad741d
The way the fingerprint service handles FINGERPRINT_ERROR messages
allows for situations where the user can end up with HBM enabled even though enrolling threw an error.
Fix this by calling `onFingerUp()` when handling FINGERPRINT_ERROR
messages.
Change-Id: I7bb7d9054eb1eac412a05f63b3feb621ca21fe24
*We can now use kernel HBM instead of lighting up the whole screen
*Disable HBM when enrolling finishes and when authenticated to make sure HBM doesn't get stuck in enabled state
*Add a 35ms delay to make sure the screen dims before enabling HBM, preventing flickering
*Depends on d4e9440553
Signed-off-by: Simon1511 <simon2002.schoenmackers@gmail.com>
Change-Id: I330eb33a619e89a6744bca05edfe18fd30215e4a
*Drop lineage FOD hal
*Uprev fingerprint hal to 2.3
*Update overlays for UDFPS
*Only light up the screen for 100ms when pressed since onHideFODView is in framework now
*Switch to TARGET_SURFACEFLINGER_UDFPS_LIB
Change-Id: Id7e0d9680a5b308d16e0e91ea6678089874e7d9c
pjgowtham