Add an trigger to start the fingerprint HAL immediately after /data is mounted. Keeps to avoid race conditions, but ensures the HAL is available early enough for first-boot SetupWizard enrollment. This fixes the issue where fingerprint setup fails during initial device setup but works after skipping and opening Settings. Signed-off-by: aminfauzi <aremean0107@gmail.com>
12 lines
459 B
Plaintext
12 lines
459 B
Plaintext
service vendor.fps_hal.realme_sm7125 /vendor/bin/hw/android.hardware.biometrics.fingerprint@2.3-service.realme_sm7125
|
|
# "class hal" causes a race condition on some devices due to files created
|
|
# in /data. As a workaround, postpone startup until later in boot once
|
|
# /data is mounted.
|
|
class hal
|
|
user system
|
|
group system input uhid
|
|
writepid /dev/cpuset/system-background/tasks
|
|
|
|
on post-fs-data
|
|
start vendor.fps_hal.realme_sm7125
|