Can't delete fingerprints and scanner not working

  • Thread starter Thread starter Android Central Question
  • Start date Start date
A

Android Central Question

Hello all,

I have an HTC 10, Android v 7.0 . Recently, my fingerprint scanner stopped working, so I went into settings to try to reset the fingerprints. However, when I click "delete" on an individual fingerprint, or "Reset all fingerprints", nothing happens. Some apps seem to believe that my fingerprints are deleted, since they no longer give me the option to unlock with my fingerprint. But the fingerprint manager still shows all the originals and even after a few days and phone restarts I still can't delete any of them or use the fingerprint scanner to even unlock my phone. Can anyone help with this?

Thank you
 
Hi! Same issue. Tried safe mode and wiping cache. And in addition, bottom speaker just have a crackling sound. I just have this phone for 7 months. Is this a hardware issue? Or will this be fixed by an OTA update? Thanks.
 
We've had no feedback in this thread from either of the posters with this problem, so there's no way of knowing whether a fix has been found. It may be worth contacting HTC customer support in case they know anything about it.
 
I've been having this same problem for a week now. I've rebooted and restarted. I've done the soft reboot and wiped the cache partition. I've cleared the cache and the data in the Fingerprint app. I can't clear the credentials and I can't get in to delete fingerprints.

Samsung Galaxy S7
 
This worked for me (Android 8/LineageOS15.1):
I allowed root access to my file explorer app.
I went to /data/system/user/0/fpdata/ and deleted user.db
I went to /data/system/user/0/ and deleted settings_fingerprint.xml.
I rebooted phone.. all fingerprints were gone.. ready to add some more.

(optional: rename the files instead if you are concerned)
 
That's a good fix to know, but there is a major bug in the fingerprint system in Android since, probably, around June, and an Android team at Google is looking into it. A fix should be coming out in a few months if they find the cause (which is probably a typo somewhere).
 

Forum statistics

Threads
955,932
Messages
6,966,123
Members
3,163,430
Latest member
SHALARD