Related
I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?
Nothing's changed for me :c
Sent via Telnet
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!
I m also facing same issue
Any solutions to resolve this issue?
Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk
I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.
anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch
Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app
Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/
Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..
Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.
I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?
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
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 just got this. The first October update was 105mb and I updated yesterday. IDK what this one is about.
Me too
I too have got it. Interesting..
It appears that they fixed the fingerprint and CPU lock bug along with the Smart Lock blank screen bug and the read and write speeds issues. I guess they finally did it. Next up is Pie I hope...
Here also. After yesterday an update was delivered, I am now offered a new update. The installation is now running. I noticed after yesterday's update that there were significant "memory / processing delays", which had previously not occurred on my device. The update is 203 mb, yesterday only 103.5mb were delivered.
Updated again with the 203mb . No the smart lock empty screen is not fixed. ?
¿? any change
hrizuwan said:
Updated again with the 203mb . No the smart lock empty screen is not fixed.
Click to expand...
Click to collapse
Go to Settings, Security and Location and under Trust Agents disable Smart Lock, reboot the phone, go to Trust Agents again and enable Smart Lock and then try.
Version OPM1.171019.011.V9.6.15.0.ODIMIFE
Toke some time to install. It didn't disable CAMERA2API (installed before 9.6.14). I hope my battery gets better. Since last update battery was being drained really fast.
Which "base" version of GPlay Services do you have with october's patch? (For example, i can install an older version in august patch, like 12.6.89) is this possible in the latest update?
Catsonvi said:
It appears that they fixed the fingerprint and CPU lock bug along with the Smart Lock blank screen bug and the read and write speeds issues. I guess they finally did it. Next up is Pie I hope...
Click to expand...
Click to collapse
Ui still locks up when writing big files
kadu20es said:
Version OPM1.171019.011.V9.6.15.0.ODIMIFE
Toke some time to install. It didn't disable CAMERA2API (installed before 9.6.14). I hope my battery gets better. Since last update battery was being drained really fast.
Click to expand...
Click to collapse
Buddy is camera 2 api still not enabled by default by xiaomi yet?
IjazCI said:
No. No camera2api by default. Hope Xiaomi enable it when they release pie. They are embarrassed to enable it as Gcam mods , put Mi camera application to shame.
Click to expand...
Click to collapse
Yeah lol
Also i find sometimes photos are not that good inside my house but photos of daylight are nice
Is proximity sensor issue fixed?
Varun.Shanbhag said:
Is proximity sensor issue fixed?
Click to expand...
Click to collapse
Xiaomi can't move it so it will never be "fixed". You need to hold your phone differently.
IjazCI said:
Agree. With proper daylight it perform well . But Google's post processing is extraordinary.
Click to expand...
Click to collapse
Finally someone agreeing on bad camera quality in low light
And google should allow google camera for android one devices we are install here port of it
Benjamin_L said:
Xiaomi can't move it so it will never be "fixed". You need to hold your phone differently.
Click to expand...
Click to collapse
Put your finger on the sensor and It will still fail, its software related
ramir0 said:
Put your finger on the sensor and It will still fail, its software related
Click to expand...
Click to collapse
Here you go, you can reset the proximity with this app.
https://play.google.com/store/apps/details?id=com.mobiledirection.proximitysensorreset&hl=en
But the position of proximity sensor is really bad, especially for the left arm holding phone users, like my self...so, that will never be fixed of course.
@Benjamin_L What @ramir0 is saying is right. This is a bug which existed even before the phone went on sale and still not fixed.
Ok, so this update seems to be the real one with some bugs fixed, the first one (100Mb) was just security update, this one should have some fixes, but without changelog, who knows what...
EDIT:
I just did a quick Andro Bench test.
My writing speed goes up, from 174Mb to 220Mb, everything else is like before update.
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