I am still new to the fingerprint reader so my old habit of swiping, which takes you to an pin pad. It says to Use fingerprint or enter pin, but about half the time it doesn't take the fingerprint. I'll either have to let it time out and get it on the main lockscreen or just enter the pin.
Actually the first day it was so bad that I didn't even think it was accepted on that pin screen. It wasnt until last night when I even saw it say "use fingerprint" but it works about half the time.
The fingerprint scanner works pretty reliably everywhere else so I don't think its a hardware issue. Just curious if others are having problems scanning on the pin screen.
Only time I have an issue is the first time Samsung Pay reads my print. 99% of the time, I have to put my finger on it again. Best way to solve your issue that I found is by unlocking your phone as follows:
Press and hold the home button with a finger that you have saved. When the phone unlocks, remove your finger. This way your finger is firmly on the reader. If it is still giving you issues, try making the fingerprint again in the settings.
I have big fat fingers lol. And I use my thumbs to unlock. In the fingerprint settings, I now have multiple fingers set to unlock the phone, that way, if I'm having maybe a problem hitting it right with one finger, I can get it with the other. I've got both hands covered. Multiple fingerprints to me is key. Also, when I was first learning to scan my prints, it took me a little while to get it right. For my thumbs, I'm pretty methodical... I start at the bottom left, lift up bottom middle, lift up, top left, lift up, etc... Basically let it scan a small quadrant of my thumb at a time. Seems to work really well. I have very few bad readings. Usually happens when my fingers have something on them, or the button has something on it, or my finger is laying too far sideways...
Sent from my SM-G935V using Tapatalk
No its not about reading my finger. I have multiple fingers setup (4).
I dont have an issue unlocking via fingerprint from the main lockscreen. The problem is when I try to swipe and it asks for a pin. Its this screen where it works half of the time. Its not that it isnt "matching" because when it works it will throw an error like "no match". But half the time it doesn't even recognize me trying to scan a finger.
I've been testing it more and more and it is a bug.
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
mwshows said:
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I just moved to the Note 5 and grabbed Marshmallow. I can say that the issue was specific to the S7E. Even on the same screen, it is responsive regardless of whether it was successful or failed, at least it prompts and responds.
On the PIN screen, it just would recognize a fingerprint input half the time.
Update
My Note 5 did it a few times today too. Aggrevating.
When you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Im having this exact issue as well. So annoying to be not able to unlock via fingerprint at the PIN screen!!!!
Having exact same issue, and it pretty much makes the
fingerprint unlock method useless. I'm using a Galaxy S7 Edge, in Australia with an Australian carrier, so it's a safe bet the issue isn't isolated to Verizon (perhaps move the thread in the main s7e thread to get more attention?)
*The fingerprint works
100% time on the main lock screen, but whenever you tap a notification or swipe
to unlock, and you are presented with the PIN/Fingerprint or
Password/Fingerprint screen, the fingerprint unlock method rarely works. You
either have to enter the pin/password, or go back to the main lock screen and
use your fingerprint there to unlock the phone.
Seeing as multiple people have reported the issue, safe to say its not an isolated issue. I'm surprised more people haven't complained
about it, as it really defeats the purpose of fingerprint unlocking.
*Is there a way to raise the issue with Samsung so they can address it in a future update? Or does anyone know of a temporary fix?
To solve the problem you can have your home and work address saved as a safe place and the phone will not lock at those locations.
For me this helps to not use the fingerprint scanner all of the time. I also never have a problem with it anyways.
Sent from my SM-G935V using XDA-Developers mobile app
Good suggestion, thanks for that : )
I'm hoping Samsung acknowledge the issue and fix the problem soon. TBH, I'm surprised more people haven't encountered and complained about the issue. I noticed it within a day of getting the phone. Perhaps people don't bother with fingerprint unlock? Either way, fingers crossed an update comes soon.
I traded out for a Note 5 and its MM update is doing the exact same thing. I switched to a pattern backup and I think its working much better.
I am going to try that new Good Lock that updates the UI. Running good and will report if its still broken or if it fixes the fingerprint reader.
Did some testing of my own. Issue is not present with goodlock. Did you find the same mate?
player911 said:
IWhen you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Click to expand...
Click to collapse
Same identical problem here. It worked only one time, after that it doesn't worked anymore.
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
invision1 said:
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
Click to expand...
Click to collapse
I will wait for more stable version, in the meantime I continue to keep this annoying bug. I just don't understand why if it is a bug, most people doesn't have this problem.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Apparently yestrday a dutch user got a new update on his phone. I have an unbranded phone, i will wait for it. I keep you guys posted.
invision1 said:
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Click to expand...
Click to collapse
Could it be an hardware issue? Has anyone installed last Samsung's update? Maybe it solve this issue too.
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
invision1 said:
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
Click to expand...
Click to collapse
I didn't tried Good Lock yet, but i wonder why some users have this issue and others have not. Anyway when i will receive the update i'll let you know
Related
FYI for WidgetLocker lovers..........the latest update has fixed the issues where the fingerprint scanner did not work on the WidgetLocker screen. The fingerprint scanner now unlocks and takes you right to your home screen. If you use the slider bar in WidgetLocker, it no longer takes you to the normal lock screen, but brings up the code unlock screen instead as the regular lock screen does. I have checked this multiple times on my phone on 4.1.83, GladiAtrix, and Cool Blue.
WidgetLocker Market Link
You do have to swipe the scanner a wee bit slower it appears, almost like Atrix was prior to 4.1.57 update, but other than that it works fine.
+1 Yea noticed that been using it again with no problems as well ^_^
Sent from my MB860 using XDA App
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
It happens to me also.
Sent from my Chuck Norris powered PRO RED DXblurred Atrix
badnokia said:
It worked for me only half a day, then it was back to its old tricks. I'm bummed because I was really hoping this would fix it.
Click to expand...
Click to collapse
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
blunted09 said:
i just tried widgetlocker for the first time yesterday. It was nice and definitely modifiable (word?) but it slowed down my phone ever so slightly.
Click to expand...
Click to collapse
When you say slowed down your phone..............in what way? I know it slows down unlocking slightly, but I notice no other slow downs once the phone is unlocked.
CaelanT said:
When did you update? There was an update yesterday or the day before which did not address this particular issue. The update today wasn't there earlier because I check several times a day for Market updates out of boredom. It appeared this evening in the Market for me. Working great for me now.
Also, how fast are you swiping on the reader? You can't swipe as fast as when not using WidgetLocker.
Click to expand...
Click to collapse
I updated this morning. I just checked the market again just now & no additional update was available; I'll check back again later. Re: swipe speed, I'd say I didn't change my speed at all. Again, that seemed to not be a problem for ~1/2 a day.
The only known issue right now is that Exchange can break things. I'm working on a method for rooted Exchange fingerprint scanning users to bypass this (the trick actually allows for some other things too so it's not as niche of a group as it sounds), but it requires manual XML changes right now and could mess up your system. When it's wrapped into an apk and ready for user testing I'll post somewhere in the Atrix section to let you guys know.
If you're not using Exchange (or a similar device admin that "Requires password") and having issues with it not working in cases that the Motorola lock screen would, then Settings > Report Bug and provide as much details as you can about when it's not working.
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
dLo GSR said:
mine doesn't work at all anymore now. before, it would work about 50% of the time, now no response at all. i tried rebooting, clearing my lock screen settings and re-enabling fingerprinting, etc. no dice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same here. Mine was working, now it's completely unresponsive. Back to the stock lock screen.
I am one of the elusive Exchange users he mentioned though...
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
dLo GSR said:
is anyone else having problems? i can't get it to work AT ALL. i've uninstalled, reinstalled, rebooted, gone through every setting in the settings menu... what gives?
Click to expand...
Click to collapse
Still not working consistently enough for me to continue using...bummer... I've been back to stock lock for awhile now & waiting for next update with fingers crossed.
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
dLo GSR said:
ok i think i've narrowed it down.
if you set a FP profile, and use a PIN, then it will work. BUT if you are using the pattern unlock and the FP (which you can set by setting as pattern first, then FP with existing profile), it will not work.
Click to expand...
Click to collapse
I use FP with pin, so maybe you have hit on something there, as I have no issues with it.
yup, confirmed it's true with the dev, and also that it's Motorola's fault.
"I did notice this in testing, however Motorola does not support the Fingerprint scanner with Pattern so I decided not to either. What you found is unintentional and may have issues on it's own (I haven't tried with the latest firmware, but I had played with that setup on the original firmware and found it unreliable. Setting a delay with the Fingerprint scanner (via sqlite) also caused weirdness).
With regard to WidgetLocker, there's some code in there to handle Motorola's pattern and some other code to handle Motorola's fingerprint scanner. I did try to get both to work, but in limited testing was unable to do so and since it's not officially supported by Motorola I decided not to pursue further. (I actually also thought they fixed the loophole you found in the later firmware so the only way of doing it was sqlite, but apparently I was wrong)"
hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please
honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.
244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.
biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!
Is there a root app to disable it or not
biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate
Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug
Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
JDM9499 said:
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
Click to expand...
Click to collapse
The update was to improve the security. You may need to resetup. They made it more sensitive so it can't be unlocked with a pic as easily
bossg4 said:
The update was to improve the security. You may need to resetup. They made it more sensitive so it can't be unlocked with a pic as easily
Click to expand...
Click to collapse
After the update, it was a night and day difference. I tried registering my face again multiple times, and it worked maybe 3-10 times. It was terrible. I just reset my device though after I registering another facial input, and it's back to how it was - super fast. I'll continue to monitor if it reverts back to being unusable.
It's horrible... I can't even open my phone half the time...Just came to XDA to see if I was the only one having this issue
Same issue. The first day I got my phone I was actually bragging to everyone how amazing and fast the face unlock was. After the update it sucks, to the point where I just can't use it. I did register my face again multiple times as well.
kuulhus said:
Same issue. The first day I got my phone I was actually bragging to everyone how amazing and fast the face unlock was. After the update it sucks, to the point where I just can't use it. I did register my face again multiple times as well.
Click to expand...
Click to collapse
It's back to be crap now. After I reset the phone, it was working great again, but now not so much. I even get a pop-up sometimes saying to clean the lens!! It's spotless!
The iris scanner now is what the facial recognition WAS before the update. So, I'll start using that until this is figured out and solved because at least facial recognition works with glasses on.
Try registering your face much closer , cover most of it but not 100%, leave a gap of 2 or 3 cm. Also have you tried turning on the "faster recognition" option?
eniorodriig said:
Try registering your face much closer , cover most of it but not 100%, leave a gap of 2 or 3 cm. Also have you tried turning on the "faster recognition" option?
Click to expand...
Click to collapse
Where's the faster recognition setting
No problems with mine whatsoever. Crossing fingers it'll stay that way.
JDM9499 said:
It's back to be crap now. After I reset the phone, it was working great again, but now not so much. I even get a pop-up sometimes saying to clean the lens!! It's spotless!
The iris scanner now is what the facial recognition WAS before the update. So, I'll start using that until this is figured out and solved because at least facial recognition works with glasses on.
Click to expand...
Click to collapse
Yup using the iris scanner as well now. Surprisingly faster than the first day which is weird, but still not as fast as face unlock . I wonder which takes more battery
laz45 said:
Where's the faster recognition setting
Click to expand...
Click to collapse
Settings -> Lock Screen and Security -> Face Recognition
You should be able to find the "Faster Recognition" option in there. I believe this came bundled with an update i received today, i cannot remember also having this option before. Take a look there and make sure the phone is up to date.
I believe there is improvement to be made here, hopefully once we start rooting this puppy , someone can come along and tweak a few settings.
eniorodriig said:
Settings -> Lock Screen and Security -> Face Recognition
You should be able to find the "Faster Recognition" option in there. I believe this came bundled with an update i received today, i cannot remember also having this option before. Take a look there and make sure the phone is up to date.
Click to expand...
Click to collapse
AT&T user here. Got the OTA update yesterday that made the facial recognition terrible and I don't have the "Faster Recognition" option.
EDIT: I should also mention that I have redone the facial setup multiple times since the update and it's still noticeably worse than before the update.
Mine got slower, but I cleared cache and redid the facial set up, seems to be better again (after TMobile update).
JDM9499 said:
When I first got the phone yesterday, unlocking the phone was crazy fast with the facial recognition. This morning, I got the latest software update, and now, it's basically unusable. Has anyone else experienced this?
Click to expand...
Click to collapse
I have noticed the same I can hardly use facial recognition after update was so fast before. Now using iris
Iris is significantly better, safer and faster.
how safe is the iris scanner - from a medical POV
when activating it - you get loads of disclaimers including one saying to always keep at least 8 inch between eyes and phone to prevent retina damage - i mean WTF!!!!!!
has anyone looked into this ****?
tim2london said:
how safe is the iris scanner - from a medical POV
when activating it - you get loads of disclaimers including one saying to always keep at least 8 inch between eyes and phone to prevent retina damage - i mean WTF!!!!!!
has anyone looked into this ****?
Click to expand...
Click to collapse
Yeah I saw the warning that scared me. I'm a delivery driver and drive around 350mi a day Monday- Friday can't have my eyes damaged. Plus just payed 4500 for lasic
I have had lasik also. I would not worry about it. All things have warnings like that... heck, even your basic computer screens have warnings.
Yeah since the Att update face recognition doesn't work at all for me, wellaybe 1 time out if 10. Annoying. I'm not bothered someone could use a photo of me to unlock. If my phone is ever out of my possession for that long, I'm disabling it remotely anyway
Yep, got my s8 last night, was showing my GF how incredible facial recognition was, THEN I applied the update. Doesn't work at all, the fingerprint scanner is in the worst possible place, and I wear glasses so the iris scanner won't work for me. I can't believe I'm starting to miss the fingerprint scanner on the S7.
I have 2 PH-1s one of them has this random issue that Essential support says is software related.
Would appreciate input from fellow owners
https://youtu.be/61TOTt7iERk
Sent from my PH-1 using Tapatalk
I had this happen to me today after the Oreo update, but it was perfectly fine with stock 7.1.1
Anyone else seeing this?
I have noticed ghost touches as well following 8.1 official update. They now happen about 1-2 times per day. Nothing changed from before except OS version. Didn't have this issue on the beta either.
Turning the screen off and back on fixes it temporarily, but it comes back.
FYI
I got in touch with Essential Support the second time, and they got the phone replaced with in warranty service.
I also got in touch with Essential support a few days ago for the second time. I can tell their support is from the US which I appreciate in a company, but this phone is agitating and their troubleshooting makes it worse. All manufacturers from Apple to Samsung may make you jump through these hurdles but it's same issues with this phone. I believe they know it. So why waste my time asking about water damage and drops? Come on. I'm going to do a hard reset since I took the latest update but have already switched back to my s8 as my DD. I'll check if turning the screen off and back on again fixes it. Even if it's briefly I could maybe live with doing that. I couldn't get any letters to register when typing a text in the standard messaging app.
I bet the issue has something to do with the hardware. Ceramic and titantium? I know my reception is so much worse when Sprint's network is being put to the test on the highways with the Essential when compared to the s8. It may just end up being the perfect media player in the car. 128GB of music and use it as the Waze/Google Maps device...
coolmaster121 said:
FYI
I got in touch with Essential Support the second time, and they got the phone replaced with in warranty service.
Click to expand...
Click to collapse
Good to hear. In Canada we don't have that option. Let us know when f the problem is fixed or if it happens again. Like I said in my case the issue really started on Oreo 8.1.
Could grip detection have something to do with this?
sam2c said:
Could grip detection have something to do with this?
Click to expand...
Click to collapse
No, literally you don't touch the screen and this issue happens. Turning the screen off and back on fixes it.
dhorgas said:
No, literally you don't touch the screen and this issue happens. Turning the screen off and back on fixes it.
Click to expand...
Click to collapse
Exactly... It keeps occuring more often than not.
Hi guy's.
I've had the 6t for several months and the only thing I'm not happy with is the fingerprint. What I've noticed is that when I put in a fingerprint it works fine until I start using Face unlock. After that I have to re-erase and pass the fingerprint because it almost never works. Does anyone have a similar problem?
Rom. 9.0.11
I haven't enabled Face Unlock but I can say that over time the finger print reader DOES get better, and continues to learn to deliver faster reads. Based on strong performance of the FP reader (better than my work-provided iPhone 6), I don't need to use anything else.
Frankenscript said:
I haven't enabled Face Unlock but I can say that over time the finger print reader DOES get better, and continues to learn to deliver faster reads. Based on strong performance of the FP reader (better than my work-provided iPhone 6), I don't need to use anything else.
Click to expand...
Click to collapse
Same thing, I disabled face unlock immediately, no point securing your phone with a fingerprint when a good picture will get you through most face unlock software. But when I first got the phone I was very disappointed with the fp sensor. Now it's very rare I have to try again, and it's normally because there's something on my finger while I'm at work.
I've been disappointed in the sensor as well.
I bought this used and it had a tempered screen protector.
I took that off thinking that was the issue.
How long did it take for you guys for it to get better?
I'm also disappointed that the custom ROMs don't have it working yet, but I understand why.
exhibitA said:
I've been disappointed in the sensor as well.
I bought this used and it had a tempered screen protector.
I took that off thinking that was the issue.
How long did it take for you guys for it to get better?
I'm also disappointed that the custom ROMs don't have it working yet, but I understand why.
Click to expand...
Click to collapse
Did you registered your fingerprints again after removing the the screen protector? I've read somewhere on the phone that changing the glass cover may affect accuracy and registering your fingerprints after changing it is highly encouraged. Mine was working bad the first time (the FP registration you perform while you setup the phone) but it improved significantly after I deleted the FP and tried again within the phone security menu. Now I don't remember the last time it failed to recognize my finger
DeadPotato said:
Did you registered your fingerprints again after removing the the screen protector? I've read somewhere on the phone that changing the glass cover may affect accuracy and registering your fingerprints after changing it is highly encouraged. Mine was working bad the first time (the FP registration you perform while you setup the phone) but it improved significantly after I deleted the FP and tried again within the phone security menu. Now I don't remember the last time it failed to recognize my finger
Click to expand...
Click to collapse
Yep, I did re-register my fingerprints after I removed it. I always had the face recognition enabled. I did try & disable that after reading this thread, but I only gave it a day. Maybe I need to be a little more patient.
Quite honestly I got the 6T thinking of the fingerprint scanner as a gimmick more than anything else, but since day one, I have been more than impressed and pleased with the accuracy and speed of the screen unlock while using it. And yes, it keeps getting better and better over time. Couldn't be happier!
Sent from my ONEPLUS A6013 using Tapatalk
exhibitA said:
Yep, I did re-register my fingerprints after I removed it. I always had the face recognition enabled. I did try & disable that after reading this thread, but I only gave it a day. Maybe I need to be a little more patient.
Click to expand...
Click to collapse
Try registering each finger at least twice. That helped me a lot. My thumbs also work better than my index fingers for some reason. I have each thumb registered once and both index fingers 3 times and it works great.
I'm always using my right thumb and it's working 95% of the time with it.
But my other fingers are total crap! But that's cause I never use them for unlocking.
So it will get better with every usage. At first it's a bit annoying but after weeks it's just awesome.
And try to put your phone down and pick it up while training your fingerprint. You get different angles this way
I must admit that I'm a bit disappointed by the fingerprint reader. It is very fast right after registering but then slowly started to get slow and even fail over time, instead of getting faster as some mention.
I have cleared cache many times, removed and re-added the fingerprints, added the same finger twice, used the fp reader 30 times in a row, but still the same happens overtime.
This has been done with and without a screen protector.
I'm on ob4 now, but it was the same on stock and previous betas.
I also noticed that after removing all fingerprints, when I register a finger, it sometimes says that a similar fingerprint was detected (although there are no other fingers registered). This is not normal. When fingerprints are removed, any previous registered data should be wiped from the database/partition used to store the fingerprint data.
Having to completely wipe the phone to clean old data should not be necessary.
I thought the fp sensor was crap at first. Once I realized I had face unlock on at the same time, I figured out that was my problem. After turning it off, unlocking by fingerprint is super quick and accurate. Like others, I was careful to register my thumbs multiple times, making sure I turned it at slightly different angles each time. Working great!
I'm using the Cosmos animation.
No issues here and I have both of those options enabled. I am also using a liquid skin protector as well, not glass. But that has nothing to so with face unlock. I find they both have their scenarios that compliment each other quite nicely. Unlocks damn near as fast as the HW based ones
joaste said:
I must admit that I'm a bit disappointed by the fingerprint reader. It is very fast right after registering but then slowly started to get slow and even fail over time, instead of getting faster as some mention.
I have cleared cache many times, removed and re-added the fingerprints, added the same finger twice, used the fp reader 30 times in a row, but still the same happens overtime.
This has been done with and without a screen protector.
I'm on ob4 now, but it was the same on stock and previous betas.
I also noticed that after removing all fingerprints, when I register a finger, it sometimes says that a similar fingerprint was detected (although there are no other fingers registered). This is not normal. When fingerprints are removed, any previous registered data should be wiped from the database/partition used to store the fingerprint data.
Having to completely wipe the phone to clean old data should not be necessary.
Click to expand...
Click to collapse
I have observed the same issue too and I'm sure most people here are also facing the same issue.
When you register your finger prints again, unlocking is blisteringly fast, it's as if your phone has magically increased the unlock speed and the speed it takes for the fingerprint sensor technology to do it's job.
This doesn't last long as after the device has been asleep for some time, the fingerprint reader becomes basically lazy again, it will still read your fingerprints, but the success rate noticeably decreases.
I've noticed this for some time now.
Another observation I've made is that changing the animation type, also results in the fingerprint sensor suddenly becoming super fast, again this is not permanent as it becomes noticeably slower after some time.
To me these issues appear to be software / coding related, as the scanner is clearly capable of recognising and unlocking the device at fast speeds, the issue is with consistency.
When you guys talk about registering the same fingerprint again, are you deleting the first one or just adding it again? I keep getting an error saying that fingerprint is already registered. The weird thing is, I don't have any issues with my banking apps that I sign in with my fingerprint.
exhibitA said:
When you guys talk about registering the same fingerprint again, are you deleting the first one or just adding it again? I keep getting an error saying that fingerprint is already registered. The weird thing is, I don't have any issues with my banking apps that I sign in with my fingerprint.
Click to expand...
Click to collapse
We are adding the same one again. Just keep slightly moving it so that it registers different areas of your fingerprint. I've registered both thumbs twice and one index finger once for my five total prints.
Finger print scanner is pure garbage. I welcome the one on my old OnePlus 3t. I had to keep registering my finger prints over a dozen times. I've even disabled face unlock but it doesn't make any difference. Tht in screen finger print scanner is a nice idea but hopefully it'll get fixed.
Jank4AU said:
We are adding the same one again. Just keep slightly moving it so that it registers different areas of your fingerprint. I've registered both thumbs twice and one index finger once for my five total prints.
Click to expand...
Click to collapse
Ok, thanks. I added both of my thumbs again. I'll just give it some time. I don't see the point of registering any other finger, the placement of the sensor makes the thumb the most logical choice.
Does it make any difference if the phone is unlocked/not a T-Mobile version? I have the A6013 with the bootloader unlocked. Still on the stock (updated) OOS.
What I find weird is that I sometimes have issues unlocking my phone using fingerprint but I've rarely ever had issues with apps that use my fingerprint(Starbucks, Chase/Google pay, BoFA, Google play). Anyone else notice this? I do have both fingerprint and facial recognition on.
I have the same issue as others who have said the fingerprint sensor gets worse over time, not better. I was hoping the 9.0.12 OTA update would fix it. Just received that update today, but the problem remains.
I deleted all the fingerprints and re-entered them afterwards. Nothing has helped, not even factory reset. It's so frustrating because the sensor worked great for me prior to a previous update (9.0.10, I think it was).
I've seen other complaints here and there about the sensor not working. But it seems relatively uncommon, so not taken all that seriously. Guess I'll keep watching here to see if any solutions are uncovered.
bigdogdon said:
I have the same issue as others who have said the fingerprint sensor gets worse over time, not better. I was hoping the 9.0.12 OTA update would fix it. Just received that update today, but the problem remains.
I deleted all the fingerprints and re-entered them afterwards. Nothing has helped, not even factory reset. It's so frustrating because the sensor worked great for me prior to a previous update (9.0.10, I think it was).
I've seen other complaints here and there about the sensor not working. But it seems relatively uncommon, so not taken all that seriously. Guess I'll keep watching here to see if any solutions are uncovered.
Click to expand...
Click to collapse
Use the McLaren animation