Related
My Atrix's fingerprint sensor stopped working all of a sudden. Anybody experienced this?
Happend to me and restarting my phone seemed to be the trick
Sent from my MB860 using XDA Premium App
I have read about ppl having problems on the 83 FW thread. Are you on 57 or 83?
Same problem with mine today. Version 1.83
I've been on 1.8.3 for four days so far, and the fingerprint sensor seems to be working normally.
Perhaps you can go back and redo your fingerprint calibrations.
I'm on 4.1.57. Never rooted. I tried to re calibrate my finger prints and it the phone would not even sense it. bummer.
Same happens to me every so often. And restarting phone did fix it.
Sent from my MB860 using XDA App
Just happened to me for the first time ever. Just updated to 83 so i guess thats why.
I had the same thing happen to me today. Running .83. Rebooted the phone and it went back to normal
1.26 1.57 1.83 have the same problem.
Just config it again.
You guys tweaking your memory management?
Sent from my Motorola Olympus
If you happen to have your finger on the sensor when the phone is booting, the sensor gets confused and doesn't work.
Reboot and keep your finger off the sensor until the unlock screen and you should be fine.
fingerprint scanner going out for me once a day, reboot fixes it. for now i just shut it off. any permanent fixes or is it because of the latest 1.8 update?
Mine did the same thing after updating it to .83 and a reboot fixed it. One thing I noted was this happened whn the battery is below 20%. I initially thot it would come back after I a recharge, apparently I was wrong and had to restart. It is so annoying. Also, I am experiencing more battery drain after updating.
Sent from my MB860 using XDA App
I've had it refuse to see my finger from time to time, fewer times after each OTA update. I'm not happy about the freezes but this is the only phone with a finger reader, when it fails...pretend it is any other phone, use the passcode. I expect Moto to get this solved sooner rather than later because this is supposed to be a big feature for corporate sales and the attack on Blackberry's native security functions.
Whether it is a memory conflict (let's face it, Android apps are often ill-behaved and there's no one really doing qc testing on them) or an Atrix flaw...no choice but to wait either way.
Has anyone found a permanent fix for this? The Atrix is the first smartphone that my wife has owned and shes losing confidence in it. This is just one more thing that is on the list of problems shes had. My Atrix works fine, but her fingerprint reader stops reading once or twice per day and she has to reboot each time to get it working again.
I've had the same problem since 1.8.3--somebody suggested in another thread that it might be related to Titanium backup keeping settings from pre-update and trying to apply them?
I have to be honest that the fix suggestions were kind of over my head and I've just gone into settings and changed to a pattern instead of the fingerprint reader to avoid it.
My wifes Atrix keeps losing the fingerprint reader still. Maybe 2 times a day. Hers is not rooted. I took a closer look yesterday and looked at her running apps. She had a lot that were running and taking up a lot of memory. Could this be the problem? If she doest exit apps and just hits the home button will this cause the Atrix to use up its memory and lose the fingerprint function?
JohnnyDanger said:
My wifes Atrix keeps losing the fingerprint reader still. Maybe 2 times a day. Hers is not rooted. I took a closer look yesterday and looked at her running apps. She had a lot that were running and taking up a lot of memory. Could this be the problem? If she doest exit apps and just hits the home button will this cause the Atrix to use up its memory and lose the fingerprint function?
Click to expand...
Click to collapse
I have no idea if that could be related/the issue, but I guess it's worth a try, maybe install an app to auto-kill other apps. Something like advanced task killer, I used to use it (and it works well, no particular reason for uninstalling it) but now I just use juice defender and my battery life has increased a significant amount (I keep it on the default setting - using free version)
Every 2-3 days it happens and I have to reboot. When it fails, it doesn't scan your finger at all..
Since DOK2 is new and there are several hopes from many of the new firmware, I figured it would be best to make a thread about it.
To those on DOK2 (Especially 100% stock, i.e. stock kernels), please post your feedback.
One of the main things to look for is directed at FingerPrint unlock users.
After enabling FingerPrint unlock does the phone randomly lock itself?
Does the FingerPrint crash / TouchWiz crashes?
(This should be apparent with in the first 24 hours of enabling the FingerPrint lock)
The next main thing to look for is just general issues after the phone being on for some time. This would indicate memory management issues and would show up after hours / days with out a restart.
Are you loving the new Firmware? Post about that too!
Your feedback is valuable so please take the time out to post your experiences with DOK2.
Thanks!
I'm loving the new firmware. The phone "feels" faster in switching between applications.
The fingerprint lock-screen bug is gone (for me). Memory management has improved drastically. The only thing that is the same is the battery life in power saving mode. The update is worth it for me, so I'm not as eager as I was before to get marshmallow as I was before.
Note: This phone has never been rooted
I got the update and noticed a few bugs here and there. I fully wiped twice and it resolved everything. It's smoother, faster, same battery life, keyboard and fingerprint bugs fixed. I really like it so far. It runs like it should. I'm a happy camper now.
I've never rooted, full stock.
Remember to go to options > storage and clear your cache after updating! From COG2 to DOK2 I have never had fingerprint unlock issues. If anything it seems more accurate and faster. There is more ram I fall between 1.7-1.8gb (instead of ~2gb) used when everything is cleared. There has been no random reboots since the update. There is no more weather widget re-sizing itself and black shadowed font while scrolling through home screens. My antutu score went from 52000 to 48000 though. I am 100% stock never been rooted.
I've heard tell that you can't downgrade your bootloader back to COG2 after installing DOK2 update. Any word on this? Even through Odin?
^Even if you can't, why would you want to? 5.1.1 is better in every way from 5.0.1
My computer will not recognize my phone via sub after the upgrade
chocolatet said:
My computer will not recognize my phone via sub after the upgrade
Click to expand...
Click to collapse
sub? I assume you mean usb.. Did you wipe/reset everything? Even though this is an official update dirty flashing is dirty flashing. Wiping is still a troubleshooting step.
Love it so far.
The one thing that I have noticed is that the task switching is much faster. When I used to press the button, it would take a few seconds to load, now it's pretty much instantaneous.
I tried turning on the fingerprint unlock, but I was still having too many swipes to get it to unlock, so I turned it back off.
Techngro said:
The one thing that I have noticed is that the task switching is much faster. When I used to press the button, it would take a few seconds to load, now it's pretty much instantaneous.
I tried turning on the fingerprint unlock, but I was still having too many swipes to get it to unlock, so I turned it back off.
Click to expand...
Click to collapse
When you register you finger do you swipe at different angles each pass?
That is a must. My fingerprint scanner (when not crashing) works flawlessly. I never have had a problem with swipes.
DeeXii said:
When you register you finger do you swipe at different angles each pass?
That is a must. My fingerprint scanner (when not crashing) works flawlessly. I never have had a problem with swipes.
Click to expand...
Click to collapse
Yeah, I did that. I did it one time and then I did it a second time with different angles.
Can anyone address if their GPS accuracy has improved?
Test
Sent from my SM-N910T using Tapatalk
Test 2 shy did it add a to my name
Sent from my SM-N910T using Tapatalk
Data speeds are much improved with the update. The device is snappier also. I haven't noticed a difference in GPS - seems about the same as before the update. Haven't had time to gauge battery life fully but that also seems improved.
Over all a very well put together update. I'm pleased.
I haven't rooted yet and I'm not sure I want to take this update yet. How can I turn off the auto update feature? The phone is telling me it wants to download the update and the next time I connect to wifi it will. Is there any way to prevent this?
Thanks
Rootabaga said:
I haven't rooted yet and I'm not sure I want to take this update yet. How can I turn off the auto update feature? The phone is telling me it wants to download the update and the next time I connect to wifi it will. Is there any way to prevent this?
Thanks
Click to expand...
Click to collapse
WARNING if you update your tmobile note 4 from 4.4.4 or 5.0.1 to 5.1.1 lollipop then dont do it. problems are the phone download super slow even if your on the best internet connection or using your own data. and if you like 4.4.4 or 5.0.1 then you will not be able to downgrade back to them. its no way to downgrade at all. im trying to sale mine on craigslist and get another one now
So weird, I installed it yesterday, rooted, and loaded a ported version of Kyubi's ROM. It's an awesome ROM, but too laggy on n910t. Reinstalled DOK2, and I canNOT root it again via Odin 10.7 or 10.3. It loads, and then goes into a boot loop. I've tried like, 5 times. Kinda sucks
Michael in ATL said:
So weird, I installed it yesterday, rooted, and loaded a ported version of Kyubi's ROM. It's an awesome ROM, but too laggy on n910t. Reinstalled DOK2, and I canNOT root it again via Odin 10.7 or 10.3. It loads, and then goes into a boot loop. I've tried like, 5 times. Kinda sucks
Click to expand...
Click to collapse
I just learned this recently, so I guess it's my turn to pass this information to others.
You need custom kernel to be able to root. Flash BeastMode Kernel by @freeza.
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
Hello everyone,
I've had my note 4 over two years now and out of nowhere problems started happening after second MM update, model SM-N910F was freezing and restarting and sometimes was not able to boot normally and got mmc read fail.
I'm reading a lot about this problem in other forums and here, so hope someone could help about this issue.
No Success:
I tried anything from removing sd card, removing sim card, changing the battery, resetting the device, cleaning the cache, flashing the room through odin, flashing the rom with pit file and doing a re partition (Didn't tried Nand erase).
Success:
The only way that I was able to fix the freeze issue was by installing app called Wake Lock and enabling PARTIAL_WAKE_LOCK.
But using Wake Lock has its disadvantages. First of all you need to run the app all times which its not practical and second it wipes your battery because it keeps device and processor awake.
Please join this thread anyone who has similar issues with the aim to fix or bring the phone to an usable state again.
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
The Sponge said:
I also purchased my GN4 about 2 years ago and just recently got this error. This is really fishy. Wouldn't be surprised if it was Samsung trying to screw over all the root users and get us to upgrade to newer models.
Click to expand...
Click to collapse
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
shpeendi said:
Did you tried Wake Lock if it works? Which model of GN4 do you have ?
Click to expand...
Click to collapse
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
I really don't think it's an hardware issue but even if so, why this started to happen immediately after the update and why it only happens when the device goes to sleep or when we power on the device.
I also noticed the change on bootloader fonts and interface after the update. I'm suspecting that the problem is there.
Does any one has any thoughts about this?
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
ciscostud said:
It's a hardware issue. It's a bad nand issue in fact. You can find Reddit posts a mile long about it.
Anyways it will slowly get worse over time. Had to replace the main-board in my SM-N910W myself.
Click to expand...
Click to collapse
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
shpeendi said:
Is there any reason at all why it is happening I mean for the nand issue. I don't like the answer that is motherboard fault and we should replace it, which probably means replacing the phone. Is there anyone who can see deeper into the motherboard to find the issue. I also insist that this started to happen immediately after the second MM update.
I still have an IPhone 3G from 2008 and never changed anything on it. Isn't that ironic ?
Click to expand...
Click to collapse
It was a Bad batch of nand chip that started to go bad after a year or two. Note 4s started to drop like flies before April.
I think your in the 1st stage of Loss and Grief. 1st stage is denial.
If thats so than Samsung should repair our phones under warranty and not tell us we have to pay for the repair coz we installed custom roms.
The Sponge said:
Yes, I'm on the Canadian SM-N910W8 model of GN4.
I've been using the Wake Lock app for a few days now and it works perfectly, if you can get the phone to boot into homescreen that is.
For instance, when the phone shuts off due to low battery or an inevitable crash, sometimes getting the phone to boot up is a real pain in the ass because it doesn't boot up correctly most of the time.
However, one odd fix I've discovered is to put your phone and battery in the fridge for about 2-3 minutes and let it cool down completely. And then magically your phone will boot up properly to homescreen again. Activate Wake Lock and you're pretty much good until the next time your phone shuts off and can't boot. My phone will NEVER boot up to homescreen if it is even slightly hot in temperature. In order to boot, it needs to be cool.
I am highly confident that this is indeed a hardware issue, instead of a software issue. The mainboard fails to read memory properly which probably indicates that the mainboard needs to be replaced. I however cannot afford to do this so I hope that I can last atleast 2-3 years of my GN4 surviving through Wake Lock. :crying:
Click to expand...
Click to collapse
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
golden_m said:
same issue here, exactly as described above...
any way to push Samsung to admit bad batch and fix it for us with no charge?
Click to expand...
Click to collapse
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
ciscostud said:
I've already swaped a few main-boards. Ive even put a international exynos n910c main-board in a broken canadian snapdragon note 4 and its works perfect.
If anyone needs help just pm me.
Click to expand...
Click to collapse
I would be more interested in understanding how come so many Note 4 devices started acting up around same time mark...
This is definitely a hardware problem with the motherboard. Mine started giving the same symptoms 2 weeks after the 6.01 upgrade. Wakelock made it stable but after Samsung replaced the motherboard it is so much faster and no issues at all. I wonder if this is a faulty NAND issue whether the 6.01 upgrade and the way it manages memory could have triggered it. Certainly strange but it need Samsung to fix it.
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
anasrizvi said:
I am also having same problem.
I was using custom rom and it was working fine without any lag or freeze suddenly one day my Note fall from bed to ground and since then it is not working properly i thought its the ROM so i reverted back to stock MM rom flashed via odin.
Reset everything erased everything but the problem remains same.
At present i am on stock with hardly any apps just FB and whatsapp.
But my device is so slow and keep lagging and sometimes it becomes very hot and restart itself.
I dont know what to do now. i m on 910 G snapdragon.
Click to expand...
Click to collapse
Sorry to hear that, as for now jut install wake lock and enable partial_wake_lock so you can use your device until it fails completely
Mmm. I was thinking to root my phone (4month old still under warranty ) i think i changed my mind after reading this ?. Thank you guy's for the warning
Sent from my SM-N910G using Tapatalk
Same issues, I downloaded the wake lock and so far so good.
I have the same issue also guys and it started a week after updating to Marshmallow.
Phone worked perfectly fine for 2 years prior to this. So I highly doubt its a hardware issue and more likely a software/firmware problem.
Phone seems to have issues whenever the screen is asleep (hence why the wake lock app seems to help with this problem although not a proper solution)
I'm hoping Samsumg can release a patch fix for this as I truly love my Note 4 and would like to keep it for some time yet.
have anybody tried going back to Lollipop?
golden_m said:
have anybody tried going back to Lollipop?
Click to expand...
Click to collapse
I was thinking about that! but I saw on other threads people downgrading with no success.
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