Related
I've been recently getting some instances where I would lock the phone and the fingerprint sensor won't respond to my finger.
This really started when I changed my lock to pattern swiping. Anyone have the same issue? I rebooted and changed it back to pin lock and it seems to be working all the time again, but I don't know what caused it in the first place.
Thoughts?
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
jbdan said:
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
Click to expand...
Click to collapse
It's not that it doesn't recognize my fingerprints, but it doesn't recognize fingerprints in general. So when I put my finger on it, it doesn't do the double buzz, it's just non responsive.
this happened to me yesterday several times. And i received phone yesterday... . I have two prints. Left and right index fingers. It didnt fail, just was as my finger wasnt in the reader
MDB08L
experienced the same thing this morning. phone was plugged charging and finger print would not detect, had to manually hit the power button then it worked. i find there are a lot of issues when the phone is charging though, screen sometimes becomes very unresponsive while charging. i think there was a similar thread about that as well.
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
ajmalott said:
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
Click to expand...
Click to collapse
Any luck? I did a system wipe after unlocking, and flashed new factory images but still happening.
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
ajmalott said:
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
Click to expand...
Click to collapse
I was able to find a bit more about this issue. When it happened again, I pressed the power button and quickly checked the fingerprint icon at the bottom of the lockscreen and it turned red and said "fingerprint hardware not available" for a split second before turning white again. I searched that error message and got this thread https://www.reddit.com/r/nexus5x/comments/3pm3lv/fingerprint_hardware_not_available/
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
jadesocket said:
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
Click to expand...
Click to collapse
I'm not much of a tinkerer, but I'll give this a shot. If it clears it up then okay, but if it happens again I'll probably RMA too. Not willing to put up with such inconsistencies on a brand new phone with such a highly touted feature.
Unrelated, this is actually already my second Nexus 5X. The first one I received would not take a charge, and I didn't have another USB Type-C cable to test, so they sent me an entirely new package. If wiping cache doesn't do it, I'm really not sure if I should bother with a third Nexus 5X. Kind of disheartening. I really enjoy the device otherwise.
So far so good for me, Let me know how it goes for you!
jadesocket said:
So far so good for me, Let me know how it goes for you!
Click to expand...
Click to collapse
Still happening today.
ajmalott said:
Still happening today.
Click to expand...
Click to collapse
That's a bummer. It actually happened again today for me too.
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
ajmalott said:
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
I had hope Looks like RMA imminent for me. I put that glass screen protector on so well...
ajmalott said:
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
Lots of apps updated in the past week. The problem hasn't resurfaced for a whole 48 hours now. Hoping I can put this behind me
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
It happened to me too, stock phone, no third apps installed. I will keep an eye on this.
off-topic: the discoloration of the back of the phone it's very bad!
ajmalott said:
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
Click to expand...
Click to collapse
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
jadesocket said:
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
Click to expand...
Click to collapse
Did a factory reset, and the problem came back almost immediately. Google tech support wanted me to reinstall OS entirely, but I don't have the right cable (type C to type A) to hook up to computer, so they just gave RMA. Got the new one on Friday, so far so good. But then, with the last phone, the issue didn't appear until after a week or two. Fingers pressed. Tech support really seemed to take my case as a rarity, and they were unable to recreate it with their own device. Here's hoping it's just limited to a few devices.
P.S. Off topic, but Google support wouldn't give me anything for the Black Friday deal. I asked multiple times in multiple ways. Oh well.
So I finally took the jump to Pie. One of the smaller issues I have that I didn't before is when trying to set up my fingerprints again, I get an error on the last press which tells me to try again or try another finger.
Yes, an issue for me also. Sometimes it just does not work and other times it tells me the fingerprint sensor is dirty which it is not. Fingerprint sensor issues have been reported by others too after installing Pie. It does not seem to me to be as common as the notification issues with Pie, (which I also have), but it is talked about. I also did a factory reset a couple days after installing 9.0 which did help a couple of apps to work better but did not help the fingerprint or notification problems.
The fingerprint issue is weird as sometimes it is so bad, I think I will not be able to keep the phone, just will not work at all. Then for no discernible reason it will start working fine. It is not just a pain to have to use another login method every time the phone needs to be woken up, but I also use fingerprint sign in for a few apps and it is much harder to have to enter one of my random 14 character passwords when the fingerprint won't work.
Try to put your Ambient display Always on... see if it fixes the fingerprint problem (Google is aware of this issue) till google issues a permanent fix.
Wasn't that only a workaround for people who had fingerprint lag? I don't think it was for fingerprint reading issues.
I did notice a lot more fingerprint reading errors with Pie then redid my fingers and all has been fine.
itzik_man said:
Try to put your Ambient display Always on... see if it fixes the fingerprint problem (Google is aware of this issue) till google issues a permanent fix.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Hi
I'm searching for anyone else having the same problem as me and other people that i've seen in Lenovo Forums
I'm having different problems, but the most important for me is the proximity sensor, because once I answered a phone call, it makes impossible to hang up because the display turns black and it doesn´t "wakes" until the phone call has ended. The same problem with audios in whatsapp.
Another problem is that Moto Actions like turn on the flashlight with a shake, and open the camera with a twist doesn´t work anymore. Plus, the vibrator started to fail, having an unusual behavior until it just stopped.
And the device is not recognized correctly in any computer I've tried, it just appears as "unknown device", and the device doesn't show the options that use to appear when connected to a computer, it just says "charging".
I want to think that all of them are software problems, and not hardware problems, because they all started after the june 2019 update, and, as I said, there are other people having the same problems, and I think it would be a big coincidence if all of us have the same problems with our hardware.
If any of you have had the same problems, could you tell me if you could find a way to fix it? Or, anyone has any idea how could I solve, at least the proximity sensor problem, it would be better if the device don't turn off the screen anymore during phone calls.
I've tried reinstalling the drivers in 3 different pc's, and any of them worked, but when I tried with another device (Moto z2 force) they all worked. I've done factory reset three times, and one hard reset, with no changes. Could someone help me?
Thanks for reading.
Well, sound like... simply failing phone ? RMA ?
emcom said:
Well, sound like... simply failing phone ? RMA ?
Click to expand...
Click to collapse
Do you think that? I've had this phone for a year and a half, and I've never had any issue, until the last update on june 2019.
Maybe is a coincidence and my phone started to fail just after the update, but to be sure, I want to know if there's someone else having the same issue, and maybe someone could fix it.
I've had these problems a few months ago too, but back then I was thinking it was related to a hardware problem cause I had to send my phone to fix the screen (broken glass) and after that I noticed that the moto actions wasn't working properly, as the flash light from the frontal camera and the most annoying of the problems, the proximity sensor that would stop working when I got a call or audios in whatsapp. All of these was solved a couple weeks ago tho, after I had to fix my screen again (yes, 2 times in 3 months, congrats), just days before the android pie was released, so I can't say exactly what fixed it
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