Related
Any way to reset it (trying to see how long I can keep the phone on without restarting it)? It says 'Initializing etc. etc.' and the only way I can unlock the phone is by inputing my 4-digit security code. Thanks!
Turn off, turn back on. Motorola recognized that this might be a problem from week one of the device being out. I would assume they are working on a fix. Happened to me a couple times.
EDIT: Didn't see the part about you keeping it on as long as you can. I have not found another way around it as of yet. I didn't try too hard though, I just unlocked with my password to get whatever I needed and then rebooted when I had a chance.
I had the same thing happen once.
I went in to settings and the fingerprint reader off, then back on. Of course I had to rescan my fingers, but its the only way I could find to fix it.
Fingerprint Reader Issues
My fingerprint reader won't load. I have a feeling I restored something that I shouldn't have in Titanium Backup, but I have no idea what I need to remove to get it working again.
My Atrix has the OTA update and is rooted.
I can only get into my Atrix using the unlock code, which I guess I also restored. I'm sure this is a simple fix, but I'm still learning Titanium.
My reader crashed at one point. Restarting didn't work, and erasing my finger prints didn't work either. I wasn't able to input new fingerprints. The only way I could get it working was to remove the battery for a few seconds and the restart the phone.
My fingerprint scanner stopped working randomly. Did a reboot it worked one more time then stopped again. Now not working what so ever. Im running 2.3.4 unlocked. Anyone know of a fix?
From unlocked/rooted GB Atrix
I CANT EVEN SET MINE UP IT WONT DO ANYTHING! MY MOMS EITHER THEY ARE NEW
Ok i just read some stuff about rebooting your phone i tried it set it up without any issues now it is working perfect
drock212 said:
My fingerprint scanner stopped working randomly. Did a reboot it worked one more time then stopped again. Now not working what so ever. Im running 2.3.4 unlocked. Anyone know of a fix?
From unlocked/rooted GB Atrix
Click to expand...
Click to collapse
This Link is in the IHOP sticky in the dev section though flashing pudding or titanium is reported 50/50 chance of messing your finger print even if you re-flashed/rebooted or asked it nicely you might wana try this out
Most likely an issue of not enough free RAM for the scanner to initiate the recognition task.
Reboot the phone and it ll be fine. Real saviour is the alternate security code, which is your kickstand in case the fingerprint scanner gets jammed again.
Its not the same issue of that when you use TiBu and it confuses the scanner. My scanner isn't recognizing my finger swipes period. I think the scanner might be dead :-/
From unlocked/rooted GB Atrix
Op,
I had the same issue. The fingerprint sensor wasn't detecting any of my swipes. This is what i used to fix the issue. Shouldn't make a difference but i tried this on custom rom/kernel.
Turn off the phone, pull out the battery for 2 mins. Put it in and power on. Go to settings / security / change screen lock / fingerprint
Set up your pin and restart the phone.
Once the phone is restarted, go and identify your fingerprint, it will register the fingers and work as usual.
When my fingerprint thing wasn't working I rebooted and it was fine.
Check that you don't have some task killer killing the fingerprint sensor task maybe?
They don't seem to understand its not responding at all. Mine even does ghost swipes. I haven't found any useful info for this problem either. I don't know what it is because I've flashed back to nandroids that it did work with but now doesn't. It may have changed software that is not touched by backups or its hardware... couldn't tell you which.
Sent from my MB860 using XDA App
Mine wasn't working at all,too. I guess it was effected from all of these roming madness. I just did like i posted #7 and it started to work again. Do you remember if you ever tried to use the fingerprint scanner with wet hands or something else ?
No wet hands. But it did go from working one swipe to not working at all. Ill try the battery trick when I get home as well as reflashing 2.34 if none work I'll assume he scanner died.
From unlocked/rooted GB Atrix
drock212 said:
No wet hands. But it did go from working one swipe to not working at all. Ill try the battery trick when I get home as well as reflashing 2.34 if none work I'll assume he scanner died.
From unlocked/rooted GB Atrix
Click to expand...
Click to collapse
Just try the fix I posted above >,> not like it'll kill your not working scanner even more
Rebooting works usually
Iphone > galaxy s 2.
Semseddin said:
Op,
I had the same issue. The fingerprint sensor wasn't detecting any of my swipes. This is what i used to fix the issue. Shouldn't make a difference but i tried this on custom rom/kernel.
Turn off the phone, pull out the battery for 2 mins. Put it in and power on. Go to settings / security / change screen lock / fingerprint
Set up your pin and restart the phone.
Once the phone is restarted, go and identify your fingerprint, it will register the fingers and work as usual.
Click to expand...
Click to collapse
Awesome top, mine is now working again.
Semseddin said:
Op,
I had the same issue. The fingerprint sensor wasn't detecting any of my swipes. This is what i used to fix the issue. Shouldn't make a difference but i tried this on custom rom/kernel.
Turn off the phone, pull out the battery for 2 mins. Put it in and power on. Go to settings / security / change screen lock / fingerprint
Set up your pin and restart the phone.
Once the phone is restarted, go and identify your fingerprint, it will register the fingers and work as usual.
Click to expand...
Click to collapse
Thank goodness for someone reviving an old thread. Just unlocked my bootloader (with ltdanno360 help) and scanner stopped working. Doing this worked. Thanks!
Sent from my MB860 using XDA App
Great!!
My sensor wasnt working also, great Tip
omg, this thread just saved my life. I've been with a not working fingerprint scanner for 1 month now. And a simple reboot fixed it.
Just a tip: I had no need for the pulling off battery thing. Just rebooted and worked like a charm.
Thank you very much!
Hi, does anyone had issues with fingerprint scanner not working? I updated my software to the latest on A2017U with the October update. After half a day my fingerprint scanner stoped working completely. I tried to reregister it didn't work . I did a Factory reset still nothing its dead .
So its working now by itself, maybe moisture gets in there somehow thats the only thing i can think of. Thanks everyone.
I have issues with mine too, in the past to fix it I have gone into the finger prints settings and deleted all the ones that are there and then rebooted, then you have to setup your prints again. That seemed to do the trick for me.
http://www.androidauthority.com/problems-zte-axon-7-fix-716895/
I couldn't access the device with the fingerprint reader on the first start up after the update, and I also can't access it using the pattern, even though I'm sure I'm entering the right one. So it loos like I have to do a factory reset now
Ratedzelaya said:
I have issues with mine too, in the past to fix it I have gone into the finger prints settings and deleted all the ones that are there and then rebooted, then you have to setup your prints again. That seemed to do the trick for me.
http://www.androidauthority.com/problems-zte-axon-7-fix-716895/
Click to expand...
Click to collapse
This fixed my problem.
Recently, my fingerprint reader has been acting up, and I've been unable to figure out why.
It either works as when it was new, or it doesn't register at all when I put my finger on it or move it around. It's not the same error as when the lockscreen gives an error message about fingerprint reader not responding either. It just... doesn't read the fingerprints. It does respond to me depressing the button, but it still doesn't read the print.
Apps using fingerprints have the same issue. Nothing happens.
I've tried reboots and clearing cache, neither work.
A colleague of mine has an S6, and recently he has had the exact same issue.
What's going on?
Hi, first of all I apologise if this question has been asked but I don't know how to search just this place.
I'm using everything stock, no root, stock launcher.
I have my phone set up to ask for the password on reboot. I have my fingerprint reader set up to unlock my phone. I also have the fingerprint reader set up to wake the screen.
However under certain circumstances the fingerprint reader does not unlock the phone. The most reliable way to trigger this behavior is to plug the phone in to charge.
I exclusively lock the screen with the power button.
The fingerprint reader is still responsive and it still wakes the screen but there's no vibration feedback and it does not unlock. After I unlocked the phone with my password and lock it again the reader works again.
So what's going on here? How should I debug this?
After reboot it is normal to ask for password first time. Sometimes i have also seen this but when i unlock with pattern (my backup way) and lock again it works fine. I can not trace this to be related with charging or something else and it happens rarely but i have seen it also. Maybe a software bug.
Looking back to the days when i have LG V10 i remember that i had the same problem with fingerprint sensor not working sometimes. It was more frequently related to heat buildup as it was hot phone anyway.
I had the same problem these days, I think the fingerprint reader won't work if your hands are really cold.
Hmm I don't think my U Ultra is getting particularly hot and, no, my hands are certainly not very cold either. This behavior happens indoors.
It's just extra security plan and simple
Sometimes, not very often though, my fingerprint reader refuses to respond. Not even a misread where you get haptic feedback and not a lot else.
Just using the power button and entering my back up security (pattern in my case) and it comes back to life.
I don't particularly worry about it, but I suppose it's nice to see that it's not just me
Will see if the upgrade to 8.0 fixes it.
I met this problem.The solution was very interesting.I use Yandex.disk app.This problem did occur after the Yandex.disk app is update.I hard reset my phone.The problem was not in my phone.But I setup Yandex.Disk app the problem repeat occur.İf you installed Yandex.Disk, uninstall the application.if you don't use Yandex.Disk,The last apps update uninstall to try.
Good Lord I have so many apps installed though...
Then go to a full factory reset and see if it helps, thats the 1st thing you do when you have problem.
After a bit of experimentation this behavior seems to have stopped after I disabled/removed all Smart Lock Trusted Places -- a feature that is already known to be buggy.
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Garkan said:
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Click to expand...
Click to collapse
8 fixed this bug for me but i found more bugs in oreo so i am thinking to roll back to 7.0 and meet fingerprint sensor bug again because oreo problems are disgusting - car bluetooth does not works as it should - i can't read addressbook in my car head unit - it shows error. i found that is some bluetooth software parts was not included in 8.0 but successfully fixed in 8.1. and i'am pretty sure we will never receive 8.1 for u ultra.
in russian 4pda forum i found some reports (unconfirmed yet) that fingerprint bug disappeared. maybe somebody here can confirmed it?
No i have android 8 and issue still occurs sadly did not found a fix.
I've suddenly had this issue a couple of days ago a couple of times. I didn't do anything (except a couple of reboots) and it was fixed again.
Now after updating to Oreo and again using leedroids ROM, i didn't experience theissue again..
I talked to a htc representative and said to clear credentials from security/encryption and credentials seems to be a conflict in security certificates. For the moment it works.