Related
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Edit 2: Best solution here: https://forum.xda-developers.com/showpost.php?p=72875604&postcount=18
If that does not solve the issue, also try this:
Edit: solution at https://forum.xda-developers.com/showpost.php?p=71964623&postcount=10
kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Click to expand...
Click to collapse
same here. Samsung makes the worst finger print scanners.
thinking of 4 scan for same finger see if that helps.
Huawei makes the best finger print scanners
kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Click to expand...
Click to collapse
That is not normal, my A5 works 9 in 10 on the first try.
Not a single error in my A3
Mine is totally unusable... any idea?
Well, it seems that I'm not the only one with this problem. Hopefully it can be fixed with an update.
I have to say that my thumb skin is a bit damaged (from doing work on cars, around the house, etc.) but this was never a problem with my S7 Edge. I tried a different finger with healthy skin and it does work a lot better, but still not 100%, it seems to me that the A3 sensor has real issues.
same Problem with my girlfriends A3.
Fingerprint scannner works in 1 of 4 times if youre lucky sometimes doesn't work at all.
She has already made 3 scans with 1 finger but didn't really help
Maybe send it back for warrenty repairs if a factory reset won't work'? I'm sorry but fingerprint sensor should work fine.
Chris.nl said:
Maybe send it back for warrenty repairs if a factory reset won't work'? I'm sorry but fingerprint sensor should work fine.
Click to expand...
Click to collapse
To be honest, I don't think this is solvable via warranty work. I am not sending my almost new phone back just to receive a refurbished piece of thrash. I am putting my faith into a firmware update. The funny thing is, I really like the phone even with this problem, it is very fluid and has even better battery life than the S7 Edge.
So here is a workaround I have found, for those having the issue:
- Instead of using the tip of the finger when adding your fingerprint, use the area just below the tip. In the attached picture, use the area marked with green instead of the one marked with red. It will then work 100%, it's amazing how fast and accurate it is. It's just not very smart like the S7/S8 and other phones and it probably has issues when the skin is not 100% perfect or maybe with pronounced geometric distortions like it is the case when using the finger tip.
Hi folks, a workaround for me was disabling the keep screen turned off, became much more accurate after that
I've got similar problem with always on display. When I turned it off everithyng is fine
I am having similar issues with my phone. I have tried using all three stored fingerprints as just my thumb and I still have trouble getting it to unlock. I do have Always On Display turned on, and I don't really want to disable it as suggested in this thread because it's an awesome feature. Samsung should be able to something as easy as a fingerprint scanner right. Hopefully this is simply a software issue that is patched
hi guys
you lock phone with power key or with widget (like screen off)?
After having the same problem I started turning my thumb much more (even almost fully vertical) during the scanning process. Now it works fine. DHNL
hi actually solved the problem what i did is that factory reset the phone, i schedule a weekly restart, i clean my scanner and i assigned all 3 fingerprints on to the same finger and it worked
Hi folks,
I am experiencing the same issue. I found some relief using a different finger. I have registered three of my fingersprints. For some weird reason only one of the three fingers works acceptably good, the other two are successful very rarely. I therefore recommend you to try with a different finger or several of them to find out which one better works for you.
Good luck !
I can confirm there is indeed a problem with SAMSUNG A5 2017 fingerprint system. The recognition rate can be extremely low in some condition (around 10% positive, meaning almost unusable). This seems to be a software bug
Here is a turn around :
If you record your fingerprint with the screen "always on" function activated , then the recognition rate is extremely poor.
if you unactivate this function during recording process, then the rate is ok (higher than 90%), even if you reactivate the always on function after recoring session
I guess this could be solved by Samsung in the latest firmware A5 (2017) update.
Gautier T., A5 owner
gautierT said:
I can confirm there is indeed a problem with SAMSUNG A5 2017 fingerprint system. The recognition rate can be extremely low in some condition (around 10% positive, meaning almost unusable). This seems to be a software bug
Here is a turn around :
If you record your fingerprint with the screen "always on" function activated , then the recognition rate is extremely poor.
if you unactivate this function during recording process, then the rate is ok (higher than 90%), even if you reactivate the always on function after recoring session
I guess this could be solved by Samsung in the latest firmware A5 (2017) update.
Gautier T., A5 owner
Click to expand...
Click to collapse
The trick seems to be working, thanks !!
kevinlevrone said:
Hello,
Anyone else has this problem where the fingerprint scanner barely works (almost unusable) ? I tried many ways to enter the fingerprints but it registers like 1 in 10 tries...
Edit 2: Best solution here: https://forum.xda-developers.com/showpost.php?p=72875604&postcount=18
If that does not solve the issue, also try this:
Edit: solution at https://forum.xda-developers.com/showpost.php?p=71964623&postcount=10
Click to expand...
Click to collapse
updating to nougat fixes this.
you won.t need the workaround with AOD like on marshmallow
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
1up1up said:
Anyone else notice or experience a slower fingerprint unlock after applying the 8.1 OTA update? A VERY noticeable difference in unlocking speed after the update.
Click to expand...
Click to collapse
No issue here mate, still as fast as it was before on 8.0.0. Might wanna try another reboot to see if it fixes your issue. You could then always try a factory reset as well.
I just downloaded and reinstalled the 8.1 factory image. Went through and setup phone from today's backup and added fingerprints. While the phone was finishing downloading apps from backup, the fingerprint unlock was fast and normal as usual. After apps updated and restore finished, I restarted the phone. Immediately, the slow fingerprint unlock returned. I have very few apps and this wasn't an issue until after I applied the 8.1 OTA side load before the initial posting of this thread. Additional testing of the speed by pressing the power button then unlocking with fingerprint reader yields inconsistent unlock speeds. At this point, I do not want to say that maybe it's because of a particular app that is installed on the phone, but rather it's possibly a problem with 8.1.
Any thoughts?
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
I have this exactly
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Yup. First thing I noticed was this delay between when the fingerprint is actually recognized (vibrate), until I actually get visual on the screen. Around a second or more
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
SOLIDFND said:
I too am facing similar problems. My phone on 8.1 takes about 1.5s to unlock while it only took <1s on 8.0. A workaround I took was to have always on display activated. And I ain't a fan of the always on display.
Click to expand...
Click to collapse
I too, am not a fan of the "Always On" display but can confirm that this does fix the problem. Thanks for sharing your finding.
sn0warmy said:
I actually had this issue on 8.1 DP2. But since doing a fresh install of the 8.1 official release, my finger print reader is just as fast as 8.0. Maybe try a new fresh install.
Click to expand...
Click to collapse
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
I found hit super hit or miss. When I flashed my rma phone to dp2 it was slow to unlock. When I flashed 8.1 final it was fast again. I had to flash 8.1 final again but this time the phone was slow to unlock. I got my new device flashed 8.1 on and it is thankfully unlocking quickly. I wish you all luck
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Today I also noticed a random "static pop" noise coming from the phone while Chrome browser was open. It was quite distinct and loud and happened twice.
SOLIDFND said:
Sadly, I actually went through a fresh 8.1 install but fingerprint scanner is still slow with ambient display off. Off to reinstalling my apps...
Click to expand...
Click to collapse
Same problem, gets fixed with always on display but if the screen is not on in between the seconds of pressing the power button and ambient display kicks in then the problem is still there. Also tried deleting the fingerprints and redoing the fingerprint initiation, but it did not help. The sensor registers the fingerprint by vibrating but screen gets on only after a second or more. sometimes though it is instantaneous. another problem for Google to fix I guess in next month update.
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same issue here since updated to 8.1
The fingerprint is recognized quickly (you fell the short vibration) but the screen turns on with a delay of about a second.
I have the same issue when I just press the Powerbutton - it also takes about a second until screen turns on.
Guys, I'm so disappointed with my Pixel 2 XL. Never had so many issues with a stock firmware phone.
Been running 8.1 through the beta for awhile now and haven't had any of these issues. Not sure if I'm just lucky or what but it's been humming along just fine. Just installed the 8.1 official over the 8.1 beta and haven't noticed anything as of yet. Will pay attention to see if I notice anything being slower.
I am also seeing the issue after updating to 8.1. It takes about 2 seconds for the screen to appear. AOD does make it faster but I can deal with it and hopefully google fixes it soon
I searched he'd the issue on google- obviously because I HAVE IT TOO. This is infuriating. This is major functionality. after 8.1 the finger print reader is slow AF. It feel like my old galaxy s4 that i just came away from when i would swipe to unlock it. How many times do we unlock these things a day? We just went from the fastest unlocking phone to the slowest. Why is this effed up? I'm pissed.
We have ppl whining about the freaking hamburger emoji having the cheese on the bottom and the wrong foam in the beer mug, meanwhile it takes forever to get into the phone to do anything much less get to the Emojis. How does BASIC functionality go BACKWARDS with an update?
What's even more infuriating is I can't go back to 8.0!!! Google doesn't allow it do they? I am coming to this phone off a Galaxy s4. One of the big benefits of the pixel family is the "fast updates."I saw someone argue that this isn't necessarily a plus sometimes these new Android versions slow a phone down, and it's done. Sometimes, like in this case, bugs are introduced. The very first update I took on this phone largely argues his point.
Another thing I'm noticing is the battery life seems to be dropping much faster. I'm wondering if it's the flash kernel 2.0 I installed though.
I will be filing a complaint on the link someone so kindly posted above (thank you), and I will be going into the chat option through the help menu on my phone to file a complaint there.
EDIT: it also seems like Google assistant isn't working now either. "Ok Google" brings her up. The mic registers my talking, but no results are displayed.
EDIT 2: I also forgot to mention that along with the slow unlock the swipe function on the finger print reader has been altered. Smiling up and down to toggle the notification drawer is very inconsistent and buggy. I have the finger print quick action app installed. I had a single tap set up to lock the screen. I had my finger print reader un/locking the phone and toggling the notification drawer. While the notification drawer has always been a little buggy, it was VERY functional and very acceptable. Something has changed on the reader so it is having a harder time differentiating between the different movements. Now it usually registers a swipe as a tap and the screen locks. I expected this to happen when I first downloaded the app on 8.0, but I was pleasantly surprised when everything worked through the sensor. Now I am very disappointed. The issue is NOT constant. It comes and goes. Idk why it does that. I'll be seeing if I can figure out why. I will NOT be activating the always on screen as a means to circumvent this issue. I don't want burn in. I've been concerned with that issue associated with always on before the pixel showed up.
jbarcus81 said:
I submitted it to Google under DP2 and it has been deferred to a future build... maybe re-submit under the final 8.1 as well??
https://issuetracker.google.com/issues/69984153
Click to expand...
Click to collapse
I want to jump on board and file an issue too. What do I select the issue as?it's not a developer preview. Is it android system issue? Framework?
fearfighters said:
I have this exactly
Click to expand...
Click to collapse
-deleted
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
1up1up said:
To put it into perspective, the fingerprint unlock under normal speed feels almost "too sensitive" because it's so fast. Now it registers my fingerprint touch right away but is followed by a slight pause/stutter before unlocking the screen.
Click to expand...
Click to collapse
Same here
Hi everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.
Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.
Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
2x post
when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks
Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
dinoc said:
Hi guys,
Lately I've noticed that my fingerprint sensor does not work properly anymore.
Not sure if it's a hardware or software issue?
Though, the test HW for Fingerprint Sensor from Smart Doctor app reports Good status during all tests.
The behavior is strange and not consistent, most of the times it will work fine but from time to time I cannot unlock/wake the phone with the fingerprint sensor, it's not like the fingerprint is not recognized, it's more like putting the finger on the sensor and nothing happens (it doesn't vibrate like is reading it or not) . Not sure if is related to the phone being in standby for longer period, or I don't know ...
I'm more inclined to believe it's a software issue, and seems to have occurred lately after last update to Android 10 (v30f-EUR-xx, phone type LM-G710EM).
I've tried may method, deleting the finger prints and add them again , even did a factory reset but the issue seems to come back.
Do you guys have such issue?
Any idea how to diagnose this further?
Click to expand...
Click to collapse
Make sure your battery isn't swollen. A swollen battery will take out the fingerprint sensor first because it's right on top of the connection.
Hmm, interesting, from the outside I can't feel any difference, the back seem flat.
Exactly the same problem here. But if I check the sensor while it is not working I get a "sensor not respondong error".
Did you solve somehow?
Thank you
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
My last time updating to the current A12 on TMO LE2127, I couldn't get the fingerprint sensor to work once I set it up in settings. I went back to 11.2.9.9. Fully rooted.
I'm too.
BCXB said:
Hi all, I have the LE2127 T-Mobile version of the OP9 Pro, and recently I have been having a strange issue with it. I am using the stock firmware, locked bootloader, nothing significant changed on it, running OxygenOS 12 (LE2127_11_C.19).
Sometimes, when I wake the phone from sleep, one of two things will happen:
1. The fingerprint sensor will not light up properly, and will instead remain the same brightness as the rest of the screen and appear as a dull white circle.
2. The entire display will get set to maximum brightness, and remain that way until I reboot the phone.
Nothing really screams at me in logcat, and removing and re-enrolling the fingerprint doesn't seem to work either. I also have factory reset the phone, to no avail. The bug happens intermittently with no real way to reliably reproduce that I've found. The only way to get the screen back to normal and to make the fingerprint sensor work again is to reboot.
Any ideas?
Click to expand...
Click to collapse
I'm too
No9p ✨ said:
I'm too.
I'm too
Click to expand...
Click to collapse
That's A12 for you, I suggest going back to 11.2.9.9 A11 and staying there for awhile. I hated A12. Latest is not always the greatest!
I've also been dealing with this issue. Talked to support and they said just to restart the phone when it happens. They are working on a fix