Hello, I use a A2017G and have a problem with the finger print reader and DT2W features. When the phone is awake the finger print reader is pretty fast. Just tap and unlock the phone almost immediately. DT2W works fine then too.
But if the phone is in deep sleep (I suppose?) after around a minute the finger print reader takes almost 2 sec to unlock. It works only faster if I press the home button to wake the phone before tapping the fp sensor or if I tap twice (with a little break between). It's like I always miss the first touch and DT2W is slow as well (most of the time doesn't even recognize). I ve read on the zte forum about that problem but it couldn't be solved.
Anyone with the same problem? I think this is a very annoying issue knowing that the fp sensor is pretty fast.
I tried several firmwares including full reset... Nothing worked out. Some people said it could be a hardware issue but why does it work perfectly fine when the phone is awake?
vavida said:
Hello, I use a A2017G and have a problem with the finger print reader and DT2W features. When the phone is awake the finger print reader is pretty fast. Just tap and unlock the phone almost immediately. DT2W works fine then too.
But if the phone is in deep sleep (I suppose?) after around a minute the finger print reader takes almost 2 sec to unlock. It works only faster if I press the home button to wake the phone before tapping the fp sensor or if I tap twice (with a little break between). It's like I always miss the first touch and DT2W is slow as well (most of the time doesn't even recognize). I ve read on the zte forum about that problem but it couldn't be solved.
Anyone with the same problem? I think this is a very annoying issue knowing that the fp sensor is pretty fast.
I tried several firmwares including full reset... Nothing worked out. Some people said it could be a hardware issue but why does it work perfectly fine when the phone is awake?
Click to expand...
Click to collapse
Just found this post from a long time ago. My a2017g is only a few days old and I have the exact same issue. I'm on a fresh flash of B10.
Are others experiencing this as well? Only happens when the phone has been sleeping for a few minutes.
It is very annoying.
Try to hard reset
danct2005 said:
Try to hard reset
Click to expand...
Click to collapse
This is after a clean flash of b10 and a reset after that.
Are you not having that problem at all? Are you on a a2017g?
I'll try another reset tomorrow.
joaste said:
This is after a clean flash of b10 and a reset after that.
Are you not having that problem at all? Are you on a a2017g?
I'll try another reset tomorrow.
Click to expand...
Click to collapse
Well just to confirm, I have tried a full reset, and even went back to B08, and then applied the OTA to B10 (instead of flashing the whole B10 rom).
In all cases, the issue remains. The phone is very slow to unlock via the fingerprint scanner when it has been sleeping.
I do wonder if all phones suffer from this or if only some units do.
Any feedback would be appreciated.
Related
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!
my fingerprint sensor is barely working, 4/5 times it fails to recognize my finger print. I factory reset my phone twice already. Does anyone else have this problem or knows how to fix it?
On my sister's Samsung, she gave up. Just uses a number code. The fingerprint sensor was too glitchy and then she had to use the number code as "back-up" verification anyway to get into her phone. So, saved time to just make it the primary and forget the non-reliable fingerprint sensor.
Sounds like you got a lemon. My wife's fingerprint sensor works very well, 90%+ success rate on the first tap.
No issue here, if I put my finger correctly (sometimes I hit the sensor with only 50 or 75% of the width of my finger) it works every time.
Some are reporting improvement with latest B03 update here:
> Fingerprint seems better than B02 update.
Click to expand...
Click to collapse
Something to try: Cut your finger up into two halves (not literally!), register one half as one fingerprint, register the other half as another fingerprint.
Thanks for your input, maybe I did get a lemon. The weird thing is it was working fine like 2 days ago when I got it. It could be software related. Maybe I'll wait till the next update. I am on B20 is this the latest update?
Ratedzelaya said:
Thanks for your input, maybe I did get a lemon. The weird thing is it was working fine like 2 days ago when I got it. It could be software related. Maybe I'll wait till the next update. I am on B20 is this the latest update?
Click to expand...
Click to collapse
B20 is the latest for the US model, but a new update is due out next week.
Try registering the same finger at least twice, maybe even three times...yes the same finger each time. And move it all around as you register it each time. Mine works every time...unless I hit it wrong.
jaseman said:
Try registering the same finger at least twice, maybe even three times...yes the same finger each time. And move it all around as you register it each time. Mine works every time...unless I hit it wrong.
Click to expand...
Click to collapse
I tried that and my sensor still fails to read my finger, I erased and registered my finger countless times but no luck.
How do you guys register mutliple times with the same finger? As soon as it detects another fingerprint with same finger, it resets the counter to 0. I can't get past 25%
Actually, what I noticed was, if you try registering the same finger, even though it's complaining that it's already registered, it's still adding these new scans to the original fingerprint! I'm pretty sure of it because after another 30-50 touches, it doesn't give me any more duplicate messages and stays at 0%.. if that's true.. that's pretty awesome. I've done every possible angle now and it doesn't show dupes.
Fwiw, I get about a 95% success rate and it only really fails if it's a *very* partial fingerprint. By comparison, I briefly had the Vernee Thor and there I got about 10% recognition rate under normal circumstances and maybe 50% under ideal circumstances (as in very careful positioning directly after I had set up the finger).
And, yeah, in my experience you can't add the same finger multiple times.
I just got an LG G6, and instantly started having problems with the fingerprint sensor. It keeps getting "dirty" and will not scan my fingerprint 98% of the time.
I did not have that issue with my LG G5, so it is very confusing to me.
FoxyProxy said:
I just got an LG G6, and instantly started having problems with the fingerprint sensor. It keeps getting "dirty" and will not scan my fingerprint 98% of the time.
I did not have that issue with my LG G5, so it is very confusing to me.
Click to expand...
Click to collapse
No problem with mine. It is actually the best fingerprint sensor I have ever used (s7, note7, iPhone 7). Sounds like a defective unit.
Mine is working perfectly, works 100% every time unless if I miss place my finger.
I've used mine with wet fingers. Dirty fingers from making pizza. Weird but yeah even with pizza dough on my hands it worked fine. I use mine upside down even with no issues
No issues here. I have 3 fingers/prints set up so far and all work flawlessly.
You should try re-entering your prints. When you enter them keep your head still and steady when pressing. I can barely touch mine and it registers every single time. What's awesome is I can use it to open my investment & work apps.
FoxyProxy said:
I just got an LG G6, and instantly started having problems with the fingerprint sensor. It keeps getting "dirty" and will not scan my fingerprint 98% of the time.
I did not have that issue with my LG G5, so it is very confusing to me.
Click to expand...
Click to collapse
Mine works great. Try clearing your cache in recovery before calling it defective. Thats what i had to do with my jank S7 Active.
kevinhack said:
Try clearing your cache in recovery before calling it defective. Thats what i had to do with my jank S7 Active.
Click to expand...
Click to collapse
I tried this on my new V20 and the very initial results indicate it is right on the money. Thank you for this and I don't know why I didn't think of it myself. I suppose if it doesn't prove to hold, then I'm within my swap period, having the phone only 3 days now.
BTW - I initially scanned my fingerprint with the protective tape over the scanner, and despite re-scanning my prints into the security database, I wonder if that may have set up some initial cached data.
kidziti said:
I tried this and the very initial results indicate it is right on the money. Thank you for this and I don't know why I didn't think of it myself.
Click to expand...
Click to collapse
Glad to help brother
Fixed Fingerprint sensor LG G6 Not Workin
Disable Android's Device Administrator. Some how it asked me to set up a PIN, so after my finger was scanned I had to also enter the PIN
My fingerprint sensor used to work great, however it started prompting me that it couldn't read the fingerprint. I would restart the phone and most of the time that fixed it. Then, it got progressively worse. I would get three separate prompts that the "fingerprint sensor was not working" every time I would unlock my phone. Very annoying. Sometimes the setting for the fingerprint sensor would just straight up disappear. I decided to factory restore the phone, as I was having wifi and internet issues as well. Now, after multiple restarts, the sensor is not even recognized by the phone. No prompts and no fingerprint settings. Also the internet issue seems to have gotten worse. Really upset with this, as this phone is a replacement for my defective LG V10.
Edit: Just tested the fingerprint sensor hardware in Setting>General>Smart Cleaning>Test Hardware. It says "Not Responding. Contact a service center."
Fingerprint sensor works more of the time but suddenly it stops functioning!
Sometimes It does not recognise the fingerprint and, in the worst case, it totally stops to work like it does not exist or not connected; no life signal from it!!
In the first case I have to unlock with pin code otherwise I have to restart the device!
This is one of the reasons because I will never buy an LG!!
Happened twice since picking up my phone Saturday. The fingerprint sensor just stops working altogether. The phone makes no acknowledgment of tapping the sensor when on AOD or lock screen, and swiping the sensor to pull down the notifications does nothing. Reboot the phone and all is well again, so it doesn't seem to be a hardware issue.
Anyone else have this problem, any idea how to fix?
Phone is S8 on Verizon.
I think samsung just want to release update there are soo many bugs i also getting the same bug with fingerprint and iris scanner
Fingerprint sensor works fine on mine but iris scanner does not, times out during setup, i got it as far as 75% once
New phone, a lot of new software, will take time to iron everything out. On a positive note, I have not found any major issue that would actually bother me and some are my errors, I just don't know yet how to do it right. Sometimes clearing cache fixes problems like this, but since I don't have the issue, can't test it.
I guess I could try clearing cache the next time it happens. Happened twice yesterday about an hour apart.
There's a solution that I haven't tried yet in this thread:
https://forum.xda-developers.com/galaxy-s8/help/fingerprint-scanner-issue-solution-t3602551
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.