Related
Hi everyone. I wanna tell you about something weird happening to my HD2 lately that’s really pissing me off. Every once in a while, when I wake up my device from standby or for instance after receiving a text, I’m not able to unlock my phone!! I try to move the slider all the way to the left or right, but the screen is totally unresponsive. It’s like my fingers aren’t touching the display at all.
I therefore turn the screen off and on again several times and eventually I happen to “resume” the screen sensitivity and reach the homepage. The phone is not frozen since it works fine when unlocked, just the screen.
Even more weird is the fact that if I remove the battery and restart the device, when I get to the PIN Code screen I’m still not able to enter any digit since the screen is still unresponsive and I have to do the whole display off/on routine several other times till it gets sensitive again. This problem is starting to happen more and more frequently and with several ROMs.
At first I thought it was rom related so I switched from “Miri v17.4” to “Energy June,11” and then to “HyperROM Ultimate v12”. Nothing, nada, zip. The problem still remains. Then I tried running Miri v17.5 with no extra apps installed, like BSB or CHT or whatever because I know sometimes programs can have incompatibilities with roms so I tried to keep it as stock as possible, but that didn’t solve the situation either.
I performed a “task 29 by doloop” between each flashing and tried many radios as well (2.10.50.28_2, 2.10.50.26, 2.11.50.20 and now I’m on 2.12.50.02_2).
I’m really desperate because I don’t know what’s causing this. Any help/advice is greatly appreciated!
Sorry for the long post, I tried to describe this issue as accurately as possible.
Thanks.
Many people are having this problem. Many topics about it too, but no final solution.
In my case two things seemed to help: adjusting light settings (turn off automatic adjustment) and taking out SD card and putting it back in, and/or change the SD card to a faster one.
I even reflashed my phone and the problem persisted until I was finally able to put back a stable backup.
First off thanks for your reply. I just checked and automatic backlight adjustment is on. Are you saying this problem might however be ROM related? Some time ago when I was using MIRI v16 this problem occurred just a couple of times and I didn't give it too much attention. I was wondering if the touchscreen might be faulty and therefore in need of assistance..
I don't think it's ROM related, well at least not in my case. I didn't have any problems using stock ROM and an 8 GB card, until I bought a 16 GB card (the exact same day the problem occured for the first time, I just didn't realize it could have something to do with the card, until I read this forum and found my own post about the screen not being responsive dated May 3rd, the day I started using the card ).
I installed Cookie's Home Tab 1.8.5 (on my card) and the screen became unresponsive again and I had a lot of problems uninstalling it, because of that screen problem. So I did a hard reset and the problem still persisted, couldn't even use the wizard because the screen wouldn't respond.
I think it's a combination of hardware and software problems. Hardware meaning SD card and software meaning power settings (automatic light adjustment), maybe the way the software is written to the SD card, I don't know.
I've got it working now, but I'm a little afraid to do any more tweaks and I would very much like to use the light adjustment settings.
So I'm still testing and maybe some day I'll buy a new SD card class > 4. The 4GB card, class 6 seemed to help the last time I hard reset my phone.
Yeah I get your point but still I wonder why has this issue just happened to show recently. With the older ROMs everything was working fine and none of the above ever occurred.
That leads me to 2 conclusions:
1. Newer ROMs (mixed updated packages from different sources) are less compatible with the phone and thus create a new series of problems, mine included (just take a look at some of the latest rom changelogs to see for yourself what I mean). All of this not to mention the extra complications that programs such as CHT have caused..
2. The screen has became faulty. Maybe in the earlier phases the problem just happens occasionally and becomes more and more existent as the touchscreen module “degrades” (or something like that..)
Just yesterday I turned my phone on and the screen was unresponsive (I’m running miri v17.5). I tried removing the SD Card and disabling the auto backlight adjustment but none of these helped.
Anyway, here’s what I’m gonna do in the next days:
I’ll flash MIRI v16 which is a ROM I don’t remember having this particular problem with and I’ll see how it goes. Should the unresponsiveness occur again, I’ll go with a stock ROM (the one the phone came with).
If both of these tests fail then I’ll send it in for repair.
It goes without saying that I’m all ears for any advice/help you guys can give.
Thanks.
http://www.youtube.com/watch?v=VHy_t-DHqq8&feature=related
I did... It's working now...
I've read a couple threads about the fingerprint sensor not working but they all seem to be resolved by a reboot and mine is continuously sh*tty. its not even that i lose calibration and it doesnt permit me to unlock my phone, its that it appears to lack to recognize that im swiping my finger. it always feels laggy and it happens differently each time.
sometimes it works but is really laggy to recognize it, then it progresses to the point where i have to swipe a couple times to get it to even try to authenticate my finger. other times it never does anything. not even deny my finger, just pretends im not doing it.
im rooted, unlocked, running neutrino 2.5 EE now, but the problem started back when i was running gingerblur and then in alien rom too. i have latest romracers recovery. i follow full clean install procedures when i install rom. i really think my fp scanner is simply quitting on me. anyone with similar problems/solutions?
VM0824 said:
I've read a couple threads about the fingerprint sensor not working but they all seem to be resolved by a reboot and mine is continuously sh*tty. its not even that i lose calibration and it doesnt permit me to unlock my phone, its that it appears to lack to recognize that im swiping my finger. it always feels laggy and it happens differently each time.
sometimes it works but is really laggy to recognize it, then it progresses to the point where i have to swipe a couple times to get it to even try to authenticate my finger. other times it never does anything. not even deny my finger, just pretends im not doing it.
im rooted, unlocked, running neutrino 2.5 EE now, but the problem started back when i was running gingerblur and then in alien rom too. i have latest romracers recovery. i follow full clean install procedures when i install rom. i really think my fp scanner is simply quitting on me. anyone with similar problems/solutions?
Click to expand...
Click to collapse
i cant even get it to work at all i got this phone as a Grade A phone from buy/sell shops and it obviosly has barely been used. tried motoblur roms and after a few eractic swipes it shows failed and on Neutrino doesnt work at all.
is there someone specifically that the fingerprint firmware or whatever can be flashed. im really infamiliar with the file system and where these things would be stored but its getting progressively worse
using any rom firmware that supports the fingerprint scanner works all the time.
Of how you described the issue, it would more likely be a hardware issue, dust, dirt or even water residue.
Try some cleaning and puffing even with cold air hair dryer!
I have 3 Atrixes. One works once a while, but not lately; it runs 2.3.4 stock. I can't really say it's a hardware problem since it works some times, but it's really unpredictable. The other two Atrixes always works, and they run 2.3.4/2.3.6 stock.
recordman said:
I have 3 Atrixes. One works once a while, but not lately; it runs 2.3.4 stock. I can't really say it's a hardware problem since it works some times, but it's really unpredictable. The other two Atrixes always works, and they run 2.3.4/2.3.6 stock.
Click to expand...
Click to collapse
,,, which confirms the theory of fp button harware fault or issues... clean and puff, obviously after removing back cover
There are a couple other threads regarding this issue. I'm betting on faulty hardware, too, as this seems to be somewhat common. My first Atrix had this issue after only about 6 months, so I replaced it myself, which wasn't difficult.
The one sold at CellularDr dot com works just fine. (Would post a link, but... noob... ) It's $22.95 right now. If you're on AT&T, you might have luck taking the phone in and just getting a replacement, but you probably should flash a fruit cake first.
For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
can anyone provide a flashable patch to try? Thanks
This problem is starting to annoy me really badly D:
I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.
This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133
Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.
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
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