Fingerprint Sensor stopped working again

Help Fairphone 5
1

Hi! I downloaded a system update yesterday (Build Number: FP5-UTP2.B.122.20250422, I rechecked, there is no newer update available) and now my fingerprint sensor stopped working again!

I had this before in July of 2024 and ultimately sent my phone in for repair, as all the common fixes werent working. Getting it back, they replaced the outer shell and everything worked again.

I also had this before where the common fixes DID work (like disabling find my device).
Now, its the third time the sensor stopped working …

Calling ##2886## now and doing the finger print tests just crashes the test utilitity. Booting in safe mode and removing SD and SIM card also didnt yield any results.

I need my phone right now and really can’t send it to repair currently, I dont feel like I have a lot of options. Since it was replaced so recently, I think it must be a software error, how could the sensor even break? This rather annoys me. I even tried connecting with adb and checking what the error is, but to not luck either.

2 Likes
2

On the lock screen, the fingerprint hardware not available text just keeps flashing
Here is a sample of the ADB output when I fetch the logs through adb logcat and look for “fingerprint”

05-14 10:19:49.634  1552  1552 D BiometricScheduler/Fingerprint21: [Polled] {[699] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, State: 0
05-14 10:19:49.634  1552  1552 D Fingerprint21: Daemon was null, reconnecting, current operation: {[699] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}
05-14 10:19:49.638  1552  1552 I android_os_HwBinder: HwBinder: Starting thread pool for getting: android.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint/default
05-14 10:19:49.639  1552  1552 D Fingerprint21: Fingerprint HAL ready, HAL ID: 0
05-14 10:19:49.639  1552  1552 E Fingerprint21: Unable to set callback
05-14 10:19:49.639  1552  1552 V BiometricSchedulerOperation: unable to start: {[699] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, State: 0
05-14 10:19:49.639  1552  1552 W Fingerprint21: Failed to change user, still: -10000
05-14 10:19:49.639  1552  1552 D BiometricSchedulerOperation: [Finished / destroy]: {[699] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}
05-14 10:19:49.639  1552  1552 E BiometricScheduler/Fingerprint21: [Unable To Start] {[699] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, State: 5. Last pending operation: null
05-14 10:19:49.639  1552  1552 D BiometricScheduler/Fingerprint21: No operations, returning to idle
05-14 10:19:49.641  1552  1552 D BiometricScheduler/Fingerprint21: [Added] {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}, new queue size: 1
05-14 10:19:49.641  1552  1552 D BiometricScheduler/Fingerprint21: [Polled] {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}, State: 0
05-14 10:19:49.642  1552  1552 D Fingerprint21: Daemon was null, reconnecting, current operation: {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}
05-14 10:19:49.645  1552  1552 I android_os_HwBinder: HwBinder: Starting thread pool for getting: android.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint/default
05-14 10:19:49.646  1552  1552 D Fingerprint21: Fingerprint HAL ready, HAL ID: 0
05-14 10:19:49.646  1552  1552 E Fingerprint21: Unable to set callback
05-14 10:19:49.646  1552  1552 V BiometricSchedulerOperation: unable to start: {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}, State: 0
05-14 10:19:49.646  1552  1552 D BiometricStateCallback: Client finished, state updated to 0, client {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}
05-14 10:19:49.646  1552  1552 D BiometricSchedulerOperation: [Finished / destroy]: {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}
05-14 10:19:49.647  1552  1552 E BiometricScheduler/Fingerprint21: [Unable To Start] {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0}, State: 5. Last pending operation: null
05-14 10:19:49.647  1552  1552 D BiometricScheduler/Fingerprint21: No operations, returning to idle
05-14 10:19:49.647  1552  1552 E BiometricScheduler/Fingerprint21: [Finishing] {[699] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0} but current operation is null, success: false, possible lifecycle bug in clientMonitor implementation?
05-14 10:19:49.647  1552  1552 E BiometricScheduler/Fingerprint21: [Finishing] {[700] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintAuthenticationClient, proto=3, owner=com.android.systemui, cookie=0, requestId=349, userId=0} but current operation is null, success: false, possible lifecycle bug in clientMonitor implementation?
3

For me it is the first time that unlock using fingerprint stopped working.

It happened right after the same upgrade to FP5.UT2P.B.122.20250422 .

As a workaround I enabled face recognition, which I find rather unreliable with changing light conditions.

A fix would be very welcome.

4

I found some time to diagnose this issue:

I typed *#*#2886#*#* in the phone app, got an encouraging green PASS.
Then I used MANU and selected “FINGERPRINT RAWDATA” and I got the result:
Electric test is OK
Sensorpix test is OK

I found this thread about a previous update https://forum.fairphone.com/t/fp5-fingerprint-sensor-unresponsive-after-update-098-not-0-88/115560 . There someone suggested a workaround “Disabled and enabled back Find My Device toggle. Now fingerprint unlock works.”.

Unfortunately “Find My Device” is active, but I can not deactivate it! Not sure if I ever changed it.

1 Like
5

I requested repair for my phone, even reinstalling Android completly didnt fix the issue. I guess its really the hardware again thats broken, for me. Just fyi

Not a big fan of facial recognition either, its not a fix
seems good when your tests work at least

6

Same problem! Super annoying

1 Like
7

Same problem here. Just stopped working. Don’t remember if it was directly after the last update.

2 Likes
8

Same here, Fairphone 5.

I just opened a support ticket.

I tried everything I’ve found here, but nothing helps.
Don’t want to reset my phone, because I don’t expect it to be working.

Does anyone already had contacted the support with a helpful response?

1 Like
9

Yeah, tough luck :confused:
Support took a while longer this time… They told me yesterday the return voucher will be send in the next 24h. I remember they used to have a phone number, now its just email and an online chat on thursdays/fridays for “urgent” matters.

If you send it in to repair, you wont get around factory resetting it. They ask you to do it when you send it in. Cause of GDPR regulations, they will perform a factory reset themselves too.

I suggest you back up all your important stuff, two factor auth etc etc and see if you have an spare phone around (or can borrow one for friends and family)

10

But is it a hardware issue or something that can be fixed via an update?
I would love to see an official statement from FP.

11

As you confirmed in the other topic your fingerprint setting is gone. @katcos was this the same for you or did it “just” not work? A setting gone and a tool not working are different in my eyes?

12

Both the setting was gone and the fingerprint didnt work. The testing tool crashed when I tried using the fingerprint test. Even after factory resetting AND after flashing the entire operating system anew (something I definitely would not recommend trying) it didnt work. It must have been a hardware issue again

1 Like
13

Thanks as it was solved for you I will close here, all others foe those the setting is gone, please follow-up here

1 Like