Related
I've had my Note9 (Tmo) since release, so about 2 weeks now. Usually a quick tap of my finger on the fingerprint scanner and the phone immediately jumps to life and I'm on the home screen. But today it's acting erratically. Now it takes like 5 or 6 presses for it to register, and that's only after I turn the phone on first (it won't skip sleep and go directly to the home screen anymore).
I tried a rebooting, recreating my prints, as well as making sure the scanner is wiped perfectly clean, and that worked... But only for a little while, the issue has come right back.
Anyone else seeing similar issues?
Do other sensors work as expected?
On my previous Note8, when sensors stop working due to hardware fault, the fingerprints also did not work.
BTW I have not experienced the same issue on my Note9 yet.
Are you using a theme? If so that could be the issue. Uninstall theme and try fingerprint again.
Wash your hands.
I also have this issue, it's pretty annoying. On the lockscreen, the phone says "fingerprint-sensor not responding, try again later", and that's it. Tried wiping cache from the recovery menu, nothing.
Try typing *#0*# into the dialer and go to sensors test, should be able to determine if your finger print reader is faulty or not there.
Try cleaning the fingerprint scanner or using a wet wipe on your finger. As the lack of moisture is probably what is causing this issue. It happened to me a few times in HK.
I have the same issue.
My scanner is now telling my "fingerprint wet." But my fingers aren't wet, and I wiped the scanner down several times. Like the OP says, it works for 1 or 2 swipes, then won't recognize my fingerprint.
I'm having the same issue with my Note9. In my case, the problem happens ONLY if I had my phone in my pocket more than 1 minute, the fingerprint sensor just won't work, it's not like it doesn't recognize it, it's dead. I have to wait about 10 seconds putting my finger on the sensor 'til it works. I have tried everything. I'm pretty sure it's something in the software related to the phone being in my pocket (not because the phone's been idle), because when I go to bed and put my phone on the table, the next morning I just grab my phone and immediately the fingerprint sensor takes me to my home screen, no problem.
Namuna said:
I've had my Note9 (Tmo) since release, so about 2 weeks now. Usually a quick tap of my finger on the fingerprint scanner and the phone immediately jumps to life and I'm on the home screen. But today it's acting erratically. Now it takes like 5 or 6 presses for it to register, and that's only after I turn the phone on first (it won't skip sleep and go directly to the home screen anymore).
I tried a rebooting, recreating my prints, as well as making sure the scanner is wiped perfectly clean, and that worked... But only for a little while, the issue has come right back.
Anyone else seeing similar issues?
Click to expand...
Click to collapse
Do you guys have solution to this I been having this issue for a month or so now and i think it is getting worse.
Hi guys, be brave and call Samsung. The phone is under warranty.
They will collect it and drop it off for free, after repairing it and putting your phone back to water and dust resistant.
It took me about 10 days all together, if not less.
florin_stann said:
Hi guys, be brave and call Samsung. The phone is under warranty.
They will collect it and drop it off for free, after repairing it and putting your phone back to water and dust resistant.
It took me about 10 days all together, if not less.
Click to expand...
Click to collapse
I've had samsung repair experienced before my Galaxy s8+ it took them about 5 business days turn around repair it was just software issue.. But with this fingerprint if it's just software glitch or setting i rather do that first but if not I might have do warranty claim.. it always take 2-3 tap for me to work on the fingerprint this is way way slower than my S9+.. Did you have fingerprint issue?
It is definitely not software. Days i have spent uninstalling apps and themes and testing and then resettimg it all and so on and so forth!
It seemed at the beginning that a factory reset is enough, but next day it would start again.
It finally gave up and i have called Samsung, as i do not buy insurrance for my phones and they sorted me out.
I knew it was not software when i have booted the Note into safe mode and it behaved just the same.
skyethur said:
I've had samsung repair experienced before my Galaxy s8+ it took them about 5 business days turn around repair it was just software issue.. But with this fingerprint if it's just software glitch or setting i rather do that first but if not I might have do warranty claim.. it always take 2-3 tap for me to work on the fingerprint this is way way slower than my S9+.. Did you have fingerprint issue?
Click to expand...
Click to collapse
Sorry, forgot to quote you in my reply above.
Anyway, now after the repair, the Note responds diferently, it unlocks fast as hell using the fingerprint.
Try erasing all your fingerprints and re-registering them all over again. As sometimes your fingerprint settings maybe corrupted by a OS update.
florin_stann said:
It is definitely not software. Days i have spent uninstalling apps and themes and testing and then resettimg it all and so on and so forth!
It seemed at the beginning that a factory reset is enough, but next day it would start again.
It finally gave up and i have called Samsung, as i do not buy insurrance for my phones and they sorted me out.
I knew it was not software when i have booted the Note into safe mode and it behaved just the same.
Click to expand...
Click to collapse
Mine isn't like that. Fingerprint sensor works once the device is already in use but once in sleep mode for awhile it will take 2-3 taps for it to unlock and it doesnt happen all the time so My issue is sensor sensitivity and it seems to me that the sensor is not getting any power once in sleep mode to save battery that's why it is less sensitive that's just my opinion. But I already made a ticket to samsung and unfortunately the repair center which I dont trust at all the uBreakifix do not have the sensor in stock. So I may have to call in to ship out my phone.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
iceepyon said:
Try erasing all your fingerprints and re-registering them all over again. As sometimes your fingerprint settings maybe corrupted by a OS update.
Click to expand...
Click to collapse
I have already re-register my finger about 20 times but seems to happen over and over.
note 9 fingerprint issues
Namuna said:
I've had my Note9 (Tmo) since release, so about 2 weeks now. Usually a quick tap of my finger on the fingerprint scanner and the phone immediately jumps to life and I'm on the home screen. But today it's acting erratically. Now it takes like 5 or 6 presses for it to register, and that's only after I turn the phone on first (it won't skip sleep and go directly to the home screen anymore).
I tried a rebooting, recreating my prints, as well as making sure the scanner is wiped perfectly clean, and that worked... But only for a little while, the issue has come right back.
Anyone else seeing similar issues?
Click to expand...
Click to collapse
i am and i wish i knew how to fix it
*#0*# sensor test says that the RESET test has failed. I'm getting random reboots while not using the device.
willhemmens said:
Try typing *#0*# into the dialer and go to sensors test, should be able to determine if your finger print reader is faulty or not there.
Click to expand...
Click to collapse
The test shows RESET: Failed. Everything else is a PASS. It must be a hardware problem. I am getting random reboots while on standby when the fingerprint sensor is turned on.
The fingerprint scanner on the Nokia 9 is terrible! Seems to only read it 20% of the time. I use face unlock sometimes which is nice but I can't always hold phone up to face. Tempted to just use smart lock with my android wear watch but there goes my security. May end up trying to add fingerprints again for a 3rd time...
Mine almost always works, but I have to apply some pressure to it. It's not like most other in-display readers that work with just resting your finger on the screen.
I have each thumb trained twice on it.
It fails completely with a glass screen protector (at least for me).
Worst scanner. Works 50 percent or less and with multiple scans of same fingerprint. Utterly useless.Ar least the Galaxy S10 plus was fixed with updates and my success rate is 90% + on that phone.
Sent from my Nokia 9 using Tapatalk
It's a painful fingerprint scanner, but I've found a way to make it reliable. Not necessarily convenient, but reliable..
Before scanning, I lick my thumb of index finger lightly, then run them together leaving them just slightly damp (just enough so they don't slide smoothly across the phone screen), then touch firmly, but certainly not hard, on the sensor patch.
Works almost first time every time. I also used this same method when training the prints.
stiebs said:
It's a painful fingerprint scanner, but I've found a way to make it reliable. Not necessarily convenient, but reliable..
Before scanning, I lick my thumb of index finger lightly, then run them together leaving them just slightly damp (just enough so they don't slide smoothly across the phone screen), then touch firmly, but certainly not hard, on the sensor patch.
Works almost first time every time. I also used this same method when training the prints.
Click to expand...
Click to collapse
Do you know where that thumb has been since the last time you licked it??? :silly: :silly: :laugh: :laugh:
I received my phone yesterday. My fingerprint scanner seems to work just fine. There are a couple times where it did take a couple tries, but it's been nothing like I've been reading. I'm perfectly content with it. I'll also add that it's been working just as well for me with a plastic screen protector on it.
You guys never had a xiaomi mi 5s. If so, you would not complain about fingerprint scanner ?
I've had about a 75% success rate with the fingerprint scanner. I set it up in a dark room and registered both thumbs and index fingers. There are times when it won't read my fingerprint at all, which seems to be software related. Other times, it will say not recognized. In those cases, I've tried to place my hand over my phone as if I'm covering my PIN at the ATM, creating a bit of a shadow or darkness over the fingerprint area of the screen and then trying it, which seems to work a lot more often. Covering it with the other hand might be a fluke, but I am able to repeat the results again and again.
Edit: I deleted my post, because it was not repeatable. Whatever the software issue is, its too intermittent to isolate through physical means alone. Someone with programming knowledge though should be able to see what might be causing the problem and provide some insight on a workaround until then.
Right now for me, it seems to work when its being charged and battery saver seems to affect its success rate.
for me it depends on the situation, sometimes it doesn't work at all. Things like temp etc seems to be influencing the succes rate. my xz3 has a reader at the back and it doesn't work sometimes as well. they are equal in reliability. But if you are used to a Huawei (like the mate 9) it is terrible. I really had to adjust when I got the XZ3 (coming from a mate 9).
I received mine this morning and it performed a system update out of the box.
I put a glass screen protector on the phone straight away and I've had some success with using the fingerprint reader, although not so much that I would like to use it all the time.
These are my observations so far,
- The 'press harder' message is deceptive. I have never got it to work by pressing harder when it tells me to press harder in a spot where my thumb/finger already is. Instead if I use that as a cue to re-position my thumb/finger then I have much more success. When it works, I have never had to press hard at all.
- It doesn't like my thumb very much. It takes some time to find the right position with my thumb, where as my forefinger is fine.
Update: 16:14
I've been persisting with it and have found the right amount of pressure to make it work more consistently. The message on the screen says press a little harder, and pressing it to the point where it flattens your skin out against the screen makes the chance of success better.
Moseman, i did everything you did, unfortunately its a software issue. You are right about the 'press harder' message, its not true. You don't need to press hard at all to get it to work, which i have been able to test successfully. The issue is not about pressure, its about placement. You must place your finger in the exact position that you placed it when you did the first half of the enrollment. Interestingly, i've noticed that apps that use the finger print reader as part of their login, seem to work much better. Such as ADP app or Bank apps.
You will notice that it probably works better while on charger, and works terrible with battery saver on. I tried many ways to find a workaround to get it to work consistently, but eventually it goes back to working 10% of the time. I believe they will create a fix here soon.
I've heard the face scanner login works much better. GL!
I got a good working scan by holding the phone in landscape mode while learning the scan. Might be coincidence , but i figured since the scanner is the shape of a flat rectangle it might cover more of my finger that way. (in normal use i just unlock in portrait mode, i just did the landscape thing to learn the fingerprint)
Interesting. I will try your method and see what i get. Will post an update later. Thanks Bk227865.
*Update: The method does appear to be working somewhat better. I will have to keep testing. Thanks.
*Update2: I don't know why im obsessed with getting this working. But BK you gave me an idea.
So after trying your method, i wondered if enrollment was the issue. Perhaps i wasn't doing it right, and maybe someone else did do it right, so let me know if you did the following.
I deleted all enrollments and tried again, this time with battery saver off (just to rule anything out related to that). I also made sure that my finger placement was exactly as described in the training photo. Originally and before, i had placed the edge of my fingerprints to the edge of the scanner, but actually it wants you to place the middle part on the scanner.
So when i re-enrolled using the exact finger placement the picture showed, it didn't work 100% of the time, but i do get somewhat better overall success with different finger placements.
Anyone willing to test this out?
Sliksta said:
Interesting. I will try your method and see what i get. Will post an update later. Thanks Bk227865.
*Update: The method does appear to be working somewhat better. I will have to keep testing. Thanks.
*Update2: I don't know why im obsessed with getting this working. But BK you gave me an idea.
So after trying your method, i wondered if enrollment was the issue. Perhaps i wasn't doing it right, and maybe someone else did do it right, so let me know if you did the following.
I deleted all enrollments and tried again, this time with battery saver off (just to rule anything out related to that). I also made sure that my finger placement was exactly as described in the training photo. Originally and before, i had placed the edge of my fingerprints to the edge of the scanner, but actually it wants you to place the middle part on the scanner.
So when i re-enrolled using the exact finger placement the picture showed, it didn't work 100% of the time, but i do get somewhat better overall success with different finger placements.
Anyone willing to test this out?
Click to expand...
Click to collapse
I can vouch for this, great discovery, Sliksta! :good:
UPDATE:
After further experimenting, it seems like the results are only slightly better and this is not a permanent solution.
Wow. Really improved! Almost 8/10 now
The way I did it was placing my thumb in different angles from the beginning. Don't have a lot of troubles with it. Some times the light just doesn't switch on. Direct sunlight doesn't help its accuracy. Wet fingers doesn't help as well. But I would say mostly it works
Thanks all and Chaosdark for testing. I still believe that battery saver somehow effects the consistency of its accuracy. I would say it works more often than not with battery saver off. This might be the inconsistency you are experiencing. Can you/anyone confirm it works better w/ battery saver off?
Today I think I've found something interesting, if you go to verification option in the fingerprint section under security and touch the FP scanner to verify which fingerprint enrollment belongs to which finger, I have found that it detects and identifies the fingerprints enrolled easily and quickly and doesn't ask you to press harder as often as on lockscreen ( needs more testing from other users).
This results makes me hopeful that a software fix is possible and in the making according to Nokia CEO how vaguely suggested there will be a fix in an upcoming update.
What do you guys think?
stiebs said:
It's a painful fingerprint scanner, but I've found a way to make it reliable. Not necessarily convenient, but reliable..
Before scanning, I lick my thumb of index finger lightly, then run them together leaving them just slightly damp (just enough so they don't slide smoothly across the phone screen), then touch firmly, but certainly not hard, on the sensor patch.
Works almost first time every time. I also used this same method when training the prints.
Click to expand...
Click to collapse
This works 100% without pressing harder
Incredible
Wonder why is this not yet raised while all devices I have tested has the same critical issues of unreliable Fingerprint sensor and VoLTE as below:
1. Fingerprint sensor randomly stops responding for several seconds when an app or phone needs to authenticate. Sensor itself is working as other gesture controls work fine. However the authentication API sleeps for several seconds to a minute or till the device is put on sleep and woken up
2. Dual VoLTE and Dual 4G cripples while giving false ringing on Airtel and loosing VoLTE symbol and connectivity on Jio. While other phones randomly loose signals, V40 does this false ringing on Airtel while there is no incoming or outgoing call connectivity without giving any error
Both these issues affect all 3 devices tested and factory reset, etc. Doesn't help either. Phone was never rooted or custom firmware installed (as I don't find any useful here)
Appreciate if someone can suggest a possible fix as I love the phone and except for this and random lockup due to choked RAM (0.5GB or less physical RAM available most of the times while also consuming all the 2.8GB swap file)
Both these issues are observed on the latest Android 9 upgrade for India (released on August 1st). I can confirm that Fingerprint sensor never caused any issues before this upgrade on any device. Have tested on several devices and have replicated these issues on 3 of them simultaneously
I'm having the same issue with my fingerprint sensor. It's annoying, to say the least, especially when I'm trying to unlock my phone in a hurry. I have my device for 3 months now, and it only started happening two weeks ago. I haven't received any updates since December, so it can't be a new update that caused this.
I've also done a hardware test, and it shows the fingerprint sensor is working as it should. [emoji2370]
Sent from my LM-V405 using Tapatalk
Thing is android will have worst performance and than what operating system it came with when released other than software issues. This is the reason why people will try and want to downgrade their operating system back to how it came with.
I am also facing Volte issue with airtel, I don't find any solution yet, So i have disabled Volte for my airtel connection. I have noticed this volte issue is only happening from last year October, Before it used to work..
I have also noticed fingerprint sensor issue and it is very random.
Ive had the finger print reader issue, but noticed it had to do with my cover I use.I have a complete shell type case,and over time it collects residue around the edges of the case around the sensor.Removing the phone from the case,and the sensor works fine,sometimes I may have to clean the sensor with a damp cloth.
With my slim fit case,I never have the issue.
I've noticed something a bit odd regarding the fingerprint sensor. After I make or receive a WhatsApp call, my fingerprint sensor usually stops working for a bit. I haven't really had issues for the past week or two, until I received a WhatsApp call. Immediately after the call, my fingerprint sensor didn't work, so I unlocked my device with face unlock. After that, it worked perfectly fine again. And a few weeks ago, I made quite a few calls on WhatsApp, which is when I had constant issues with my fingerprint sensor. I even reset my fingerprint authorization app, and cleared my fingerprints from the device, to help sort it out.
I know it might be a long shot, but is it possible that there's a bug that causes this, either from WhatsApp or on the LG firmware itself?
If anyone has more knowledge about this, your input would be highly appreciated!
Sent from my LM-V405 using Tapatalk
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?
After a few days with the Pixel 7, sadly, I decided to return it.
The biggest reason is the fingerprint reader just didn't work right. 3 out of 4 finger presses don't work. I don't know if it's just a faulty phone that I got, but I got tired of redoing the fingerprint scans.
I have Pixel 6 and the fingerprint reader works very reliably.
The Face Unlock works but I found a bug that if the face unlock is enabled, then for all of the 3rd party apps that use biometric login, the fingerprint unlock stops working and these apps don't support the face unlock.
I had a terrible time getting mine registered and working. I have dry fingers and after moisturizing a little, the enrollment went in one go and the fingerprint works as fast as any other phone.
I have no idea how I got it fixed but I was having the same issue as you. I disabled verity and verification to flash custom kernel (wiped phone after verity) and after that the FP reader is working with 100% accuracy. It was night and day for me.
The fingerprint reader seems to be worse on the Pixel 7 than it was on my Pixel 6. It's fast but has a much higher failure rate.
Has anyone seen a difference with the animation speeds changed in developer options?
My son has my old pixel 6 and the fingerprint reader is working great.
{Mod edit: Quoted post has been deleted}
I tried it in any way I could think of. Dry, wet, sanitized with alcohol, greasy, dirty, you name it. Did not work.
feligoni said:
I have no idea how I got it fixed but I was having the same issue as you. I disabled verity and verification to flash custom kernel (wiped phone after verity) and after that the FP reader is working with 100% accuracy. It was night and day for me.
Click to expand...
Click to collapse
If I pay $600 for the phone and have to do ADB "contortions" to get the FP scanner to work, then I don't need the phone like that.
A "cheap" inlocked Chinese POCO phone with under screen FP reader works 100% of the time without disabling dm-verity.
Wow I find my Pixel 7 to be much better on the FP scanner than my P6 was, I even added a screen protector after enrolling my prints. I also now use the face unlock and have no issues with Apps that use the FP biometric option. This phone is way better than my P6.
xela19115 said:
If I pay $600 for the phone and have to do ADB "contortions" to get the FP scanner to work, then I don't need the phone like that.
A "cheap" inlocked Chinese POCO phone with under screen FP reader works 100% of the time without disabling dm-verity.
Click to expand...
Click to collapse
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
xela19115 said:
After a few days with the Pixel 7, sadly, I decided to return it.
The biggest reason is the fingerprint reader just didn't work right. 3 out of 4 finger presses don't work. I don't know if it's just a faulty phone that I got, but I got tired of redoing the fingerprint scans.
I have Pixel 6 and the fingerprint reader works very reliably.
The Face Unlock works but I found a bug that if the face unlock is enabled, then for all of the 3rd party apps that use biometric login, the fingerprint unlock stops working and these apps don't support the face unlock.
Click to expand...
Click to collapse
Really? I have not had that problem - any conflict between face unline and Finger for Biometric apps. Face unlock is outstanding. Fingerprint reader is meh, ok, sometimes
a1b2c3d4444 said:
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
I have noticed that same thing on my 7 Pro although for me it's more like an hour+ where it gets bad... It will be fine all day then I set my phone down for awhile, pick it up later, and it will instantly fail all three times and then start working again after my PIN goes in. Very strange. Probably can be fixed with software.
No problems here, had the phone for a week now. I don't think I've had any failed reads, maybe one or two. Very reliable and fast, perfect combo with the face scanner.
Mine was failing like crazy. Tried everything. Took it back and exchanged for a new one and the new one is working great. Definitely some faulty hardware out there
a1b2c3d4444 said:
Agree - I'm fairly familiar with Xiaomi phones and their FP readers are pretty reliable. I'm surprised how poorly my Pixel 7's reader is. In this day and age, we shouldn't have to compromise on what's supposed to be a stable technology after paying $600.
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
similarly
Mine works flawlessly every time. The only thing I don't like is using it at night, and not covering it with my entire finger. When it scans, it's so freakin' bright! LOL
My 7 Pro's sensor worked great, my regular 7's is just plain awful. And I know about the dry hands issue, I've been preaching that people moisturize their hands since under-display sensors came out.
At the first time with my pixel 7 the i had your same issue, fp wasnt working 9 time on 10 but then, after registered it again correctly (reading the on screen instruction while do it) is started to work flawlessly every time. Now it is always unlocking the phone, with more light or in the dark (at night for example) and with low or high brightness.
a1b2c3d4444 said:
I do notice something interesting though - the failure rate is very high when I try to unlock it after a little while (a little while being >15m). But, if I fail and enter my passcode, every subsequent try is super fast. It's almost as if the phone realizes it's not doing a good job a the initial recognition, adjusts its stored FP data, and then gets better for a while. Anyone else notice this?
Click to expand...
Click to collapse
This was the case with my P7 too. But since past few days, it started to work like 10/10. I haven't noticed any failure since yesterday. Never changed the fingerprint data too.
Update!
I returned the phone. I waited until I got the refund, took a train ride to NYC, and went to Google's Chelsea store. I bought a new Pixel 7 128 GB, traded my Pixel 6, and spend about 2 hours setting up everything in the store. Another advantage of going to the store is that I don't have to pay $600 + tax immediately and then wait 2-3 weeks for a $490 trade-in credit. They take the trade-in and I paid the difference.
If the fingerprint scanner on the new phone would have given me the same issues, I would have at least dealt with it in the store.
And it did start giving me issues initially, but then I asked for assistance and they (store tech support) admitted that Pixel 7's have fingerprint reader problems. He changed the sensitivity setting on the phone and it works (for now).
So clearly I had a bad, faulty phone before. Now, with a phone that I got over the weekend, everything works.
xela19115 said:
Update!
I returned the phone. I waited until I got the refund, took a train ride to NYC, and went to Google's Chelsea store. I bought a new Pixel 7 128 GB, traded my Pixel 6, and spend about 2 hours setting up everything in the store. Another advantage of going to the store is that I don't have to pay $600 + tax immediately and then wait 2-3 weeks for a $490 trade-in credit. They take the trade-in and I paid the difference.
If the fingerprint scanner on the new phone would have given me the same issues, I would have at least dealt with it in the store.
And it did start giving me issues initially, but then I asked for assistance and they (store tech support) admitted that Pixel 7's have fingerprint reader problems. He changed the sensitivity setting on the phone and it works (for now).
So clearly I had a bad, faulty phone before. Now, with a phone that I got over the weekend, everything works.
Click to expand...
Click to collapse
which sensitivity setting ?
The scanner is bad, that's all. The crucial thing to make it usable is the right inital scan, if it records your fingers flawlesly it will work (but not the way we expect, only in an acceptable way).
There is no sensitivity setting, he probably mean the display setting.