Database Develop

[Q] Screen won't unlock during phone calls.

Anytime I make a phone call my phone locks. I know phones typically go black when it's at your ear, but when I pull away, it won't wake up/unlock. The only time it unlocks is at the end of the call. I set it up so that the power button will end my calls but that doesn't really fix my problem. If I have to use the dial pad during the call, I can't.
I read that the proximity sensor might be blocked by a phone case. I removed mine and it's still not working. Any idea what it can be?

Do you have a screen protector? If so, remove it and try again.

I am something similar happening, when I remove the phone from my ear after a call I cannot end the call because the phone is locked and I have to unlock it with a pattern before I can end the call or wait for the caller to hang up.
Interestingly I also have exactly the same issue as I had with the LG G3 as well, I take a photo and, if I do not have WiFi, the Nexus 6 turns off, it does it every single time - it's fine if I put it into airplane mode though. As this was the same thing that happened on my LG G3 and no one else is reporting this on Nexus 6, I am assuming it must be an app I am installing ?
Is that possible ?
Simon.

I have the same problem, it's really annoying. My phone won't wake when I take it away from my head and it doesn't respond to the power button until the other person hangs up.
Hopefully it'll be fixed with an update.
Sent from my Nexus 6 using XDA Free mobile app

I am having the same problem. Brand new Nexus 6 that's only a few hours old.

I got rid of my screen protector and it works way better now. Worth a try if you are using one.
Sent from my Nexus 6

If you're using dt2w/s2w/s2s, see http://forum.xda-developers.com/nexus-6/themes-apps/app-s2w-phone-call-disabler-t3018512

I just now am having this issue too. Here's another thread with same type of thing I posted in: http://androidforums.com/threads/black-screen-after-answer-call-on-nexus-4.671499/page-2
Long story short since I already related my post there, I haven't had this problem on lollipop 5.0.1, now after sideloading 5.1, I have this issue. Screen protector is on, but never was issue before. Now all the sudden it's an issue. I feel like it has to be a software issue. Guess i'll need to test few more times before taking off or cutting screen protector; will update with more news.

Same issue for me. Never had this issue before the update to 5.1. Wonder if I can go back. I have had the phone since early December.
A little testing. Holding the phone away from my face, the screen immediately blanks when a phone number is dialed. Tried rebooting - no help. May try a factory reset.
Very annoying!

Definitely is the screen protector screwing with the senors like everyone is saying and you guys are simply ignoring. I had the same issues off and on back on 5.0, 5.0.1 and on 5.1, but on 5.1 it was permanent. As soon as I took the protector off, everything worked as normal.

As a brief work around - you can go settings - accessibility - select power button ends call. Works for me till I decide what to do. I have a screen protector on and yep it's covering the prox sensors. Once removed it works as normal. Need to find a new protector that does not cover.

Rooted, stock, with screen protector.
Was working fine in 5.0.1 now in 5.1 I have two sensor issues
1) Ambient display does not work at all. When I pick up the device or when I receive a notification sitting on a table.
2) When I receive a call the phone goes completely black. The screen will not turn back on until the call ends.
I do not want to remove the screen protector until I know for sure that is what is causing this.
Sent from my Nexus 6

A2CKilla said:
Definitely is the screen protector screwing with the senors like everyone is saying and you guys are simply ignoring. I had the same issues off and on back on 5.0, 5.0.1 and on 5.1, but on 5.1 it was permanent. As soon as I took the protector off, everything worked as normal.
Click to expand...
Click to collapse
geebee1932 said:
As a brief work around - you can go settings - accessibility - select power button ends call. Works for me till I decide what to do. I have a screen protector on and yep it's covering the prox sensors. Once removed it works as normal. Need to find a new protector that does not cover.
Click to expand...
Click to collapse
GMoGoody said:
Rooted, stock, with screen protector.
Was working fine in 5.0.1 now in 5.1 I have two sensor issues
1) Ambient display does not work at all. When I pick up the device or when I receive a notification sitting on a table.
2) When I receive a call the phone goes completely black. The screen will not turn back on until the call ends.
I do not want to remove the screen protector until I know for sure that is what is causing this.
Sent from my Nexus 6
Click to expand...
Click to collapse
GMoGoody....read bold and listen....

A2CKilla said:
GMoGoody....read bold and listen....
Click to expand...
Click to collapse
A2CKilla. Much thanks. I did read, but it was odd it went from 0% to 100% failure rate after the sw update. I work embedded sw and that is very uncommon for a sensor. I wanted to make sure since I just flashed this morning.
I cut down the protector and everything is good.
Sent from my Nexus 6

A2CKilla said:
Definitely is the screen protector screwing with the senors like everyone is saying and you guys are simply ignoring. I had the same issues off and on back on 5.0, 5.0.1 and on 5.1, but on 5.1 it was permanent. As soon as I took the protector off, everything worked as normal.
Click to expand...
Click to collapse
*****UPDATE*****
Well A2CKilla, we all just wanted to avoid the inevitable and hope it was a software issue we could just "fix" instead of being a $10, god forbid more, for a screen protector. Always try the more simpler things first than to destroy others first (which I accidentally did btw with my amazing tempered glass, now I must find one that doesn't block the sensor. In my professional opinion, if a sensor worked while having a protector over it on a previous android version, why in the actual F*** would it not work on the newer ones, UNLESS they increased/decreased sensitivity on the code somehow? Well that was my first line of thought anyway.
Also tl;dr PROBLEM WAS INDEED SOLVED BY TAKING OFF TEMPERED GLASS (that previously wasn't an issue at all) AND NOW ALL IS NORMAL.
ps. sensor is literally right next to the top speaker grill on the left side. Best to find a protector that doesn't block that.

ducky06 said:
*****UPDATE*****
Well A2CKilla, we all just wanted to avoid the inevitable and hope it was a software issue we could just "fix" instead of being a $10, god forbid more, for a screen protector. Always try the more simpler things first than to destroy others first (which I accidentally did btw with my amazing tempered glass, now I must find one that doesn't block the sensor. In my professional opinion, if a sensor worked while having a protector over it on a previous android version, why in the actual F*** would it not work on the newer ones, UNLESS they increased/decreased sensitivity on the code somehow? Well that was my first line of thought anyway.
Also tl;dr PROBLEM WAS INDEED SOLVED BY TAKING OFF TEMPERED GLASS (that previously wasn't an issue at all) AND NOW ALL IS NORMAL.
ps. sensor is literally right next to the top speaker grill on the left side. Best to find a protector that doesn't block that.
Click to expand...
Click to collapse
I really wasn't trying to sound rude at all with what I said, but seriously, there's many a thread about this issue way before 5.1 even came out, and every single time the screen protector was brought up to be the issue, but everyone had to try to find 101 ways for it to not be that, granted my tempered glass protector was less than $5 and I've already found one with the proper cut out for again, less than $5 so I was fine with discarding it, but for so many people to really try and deny something that was the clearly the problem really was sad for a moment. Once again, not trying to sound rude at all but this wasn't the first rodeo about this issue
Sent from my Nexus 6 using XDA Free mobile app

Wow I never had an issue on 5.0 or 5.0.1 with my tempered glass screen protector. After spending all day thinking it was a software bug and reverting back and trying multiple sources for stock images and ota for 5.1 I decided to remove the screen protector and it worked! Cant believe how 5.1 made the proximity sensor sooo sensitive.

A2CKilla said:
I really wasn't trying to sound rude at all with what I said, but seriously, there's many a thread about this issue way before 5.1 even came out, and every single time the screen protector was brought up to be the issue, but everyone had to try to find 101 ways for it to not be that, granted my tempered glass protector was less than $5 and I've already found one with the proper cut out for again, less than $5 so I was fine with discarding it, but for so many people to really try and deny something that was the clearly the problem really was sad for a moment. Once again, not trying to sound rude at all but this wasn't the first rodeo about this issue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hey can you link me where you bought it with proper cut outs for sensors? And to clarify its tempered glass I'm after. Thanks

A2CKilla said:
I really wasn't trying to sound rude at all with what I said, but seriously, there's many a thread about this issue way before 5.1 even came out, and every single time the screen protector was brought up to be the issue, but everyone had to try to find 101 ways for it to not be that, granted my tempered glass protector was less than $5 and I've already found one with the proper cut out for again, less than $5 so I was fine with discarding it, but for so many people to really try and deny something that was the clearly the problem really was sad for a moment. Once again, not trying to sound rude at all but this wasn't the first rodeo about this issue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
This is not acceptable behavior for the device. Mine worked fine, 0 issues before update. Now ambient display is broken and in call the screen goes black. This should be a non issue. My other phone has the sensor covered with a glass protector and it's not a problem at all. This can be fixed, since it was working before. Taking off the protector is not an option for me since I don't have a replacement right now, and should only be a temporary fix at most.

ducky06 said:
Hey can you link me where you bought it with proper cut outs for sensors? And to clarify its tempered glass I'm after. Thanks
Click to expand...
Click to collapse
http://www.ebay.com/itm/311297199450?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
---------- Post added at 10:09 PM ---------- Previous post was at 10:02 PM ----------
thacounty said:
This is not acceptable behavior for the device. Mine worked fine, 0 issues before update. Now ambient display is broken and in call the screen goes black. This should be a non issue. My other phone has the sensor covered with a glass protector and it's not a problem at all. This can be fixed, since it was working before. Taking off the protector is not an option for me since I don't have a replacement right now, and should only be a temporary fix at most.
Click to expand...
Click to collapse
so it's not acceptable for a device to not work properly with something it was never designed nor intended to have? and maybe you were a lucky one because there were many people having this issue and I also stated that it was an off and on issue for me until it was permanent after the 5.1 update. Also, that's another phone, not the nexus, every phone has different settings for their sensors. And technically speaking it is an option for you to take it off, are you forgetting that your screen is gorilla glass???, a type of glass they developed to be scratch resistant, outside of some dust here and there, I've notice no difference having taken mine off until the new one gets here

Phone calls

Hi, has anybody else experienced that their screen goes blank and doesn't come back on when on a call and what makes it worst is I can't hang up my phone after I'm done with my call. Basically I'm at the mercy of the other person hanging up when the conversation is done, the only way that I have resolved this problem is when I restart my phone. What causes this problem?

Do you have a tempered glass screen protector on?

Look to the left of the top speaker and you will see two sensors (proximity and ambient light). Is there anything covering these, such as a screen protector, skin, or case?

I do have a screen protector on the phone. Should I just remove it? I just find it strange that once I restart the phone that everything works as it should.

mr.pnutt said:
I do have a screen protector on the phone. Should I just remove it? I just find it strange that once I restart the phone that everything works as it should.
Click to expand...
Click to collapse
Because it doesn't check that sensor except when you're on a phone call.

mr.pnutt said:
I do have a screen protector on the phone. Should I just remove it?
Click to expand...
Click to collapse
When I bought my first smartphone, a Galazy S2, I bought an expensive (£10) screen protector. All it did was attract grease and fingerprints, so after a couple of months, after a sudden attack of common sense, I threw it away. The screen was suddenly always clean and smooth, and on every phone I've had since there has never been a single mark on any screen. Admittedly I do look after it - unlike colleagues who seem happy to literally throw their phones on to tables - and keep it always in an empty pocket with no coins or keys.
It seems very odd to me that we have incredibly tough glass on our phones (see the many people on Youtube trying to scratch their phones deliberately) and yet we feel the need to reduce their performance with pointless pieces of plastic...? Bizarre...

mr.pnutt said:
I do have a screen protector on the phone. Should I just remove it? I just find it strange that once I restart the phone that everything works as it should.
Click to expand...
Click to collapse
It sounds like your sensor maybe going. I have always kept a screen protector on my device and never had issues until I used a tempered glass one. The tempered glass was to thick to allow the proper amount of light in which kept the screen from coming on when a call came in or when on a call.
I would run a logcat and try to catch it happening. This will tell you just what is going on.

dahawthorne said:
When I bought my first smartphone, a Galazy S2, I bought an expensive (£10) screen protector. All it did was attract grease and fingerprints, so after a couple of months, after a sudden attack of common sense, I threw it away. The screen was suddenly always clean and smooth, and on every phone I've had since there has never been a single mark on any screen. Admittedly I do look after it - unlike colleagues who seem happy to literally throw their phones on to tables - and keep it always in an empty pocket with no coins or keys.
It seems very odd to me that we have incredibly tough glass on our phones (see the many people on Youtube trying to scratch their phones deliberately) and yet we feel the need to reduce their performance with pointless pieces of plastic...? Bizarre...
Click to expand...
Click to collapse
I just find it to be strange that I have put screen protectors on all of my phone's even some with the sensors but this is the only phone that does this.

dahawthorne said:
When I bought my first smartphone, a Galazy S2, I bought an expensive (£10) screen protector. All it did was attract grease and fingerprints, so after a couple of months, after a sudden attack of common sense, I threw it away. The screen was suddenly always clean and smooth, and on every phone I've had since there has never been a single mark on any screen. Admittedly I do look after it - unlike colleagues who seem happy to literally throw their phones on to tables - and keep it always in an empty pocket with no coins or keys.
It seems very odd to me that we have incredibly tough glass on our phones (see the many people on Youtube trying to scratch their phones deliberately) and yet we feel the need to reduce their performance with pointless pieces of plastic...? Bizarre...
Click to expand...
Click to collapse
I just find it to be strange that I have put screen protectors on all of my phone's even some with the sensors but this is the only phone that does this.

mr.pnutt said:
I just find it to be strange that I have put screen protectors on all of my phone's even some with the sensors but this is the only phone that does this.
Click to expand...
Click to collapse
First before you get ahead of yourself. Find out if it is the screen protector. It is a cheap fix if it works and cheap to replace if it doesnt.

zelendel said:
First before you get ahead of yourself. Find out if it is the screen protector. It is a cheap fix if it works and cheap to replace if it doesnt.
Click to expand...
Click to collapse
How am I about to get ahead of myself? Like I stated, I find it strange that this is the ONLY PHONE that I have ever had this type of problem with.

mr.pnutt said:
How am I about to get ahead of myself? Like I stated, I find it strange that this is the ONLY PHONE that I have ever had this type of problem with.
Click to expand...
Click to collapse
Because you are not sure if that is even the problem. The only time I had this issue was with a tempered glass one. This is a known common issue. I never had this issue with a normal one.

zelendel said:
Because you are not sure if that is even the problem. The only time I had this issue was with a tempered glass one. This is a known common issue. I never had this issue with a normal one.
Click to expand...
Click to collapse
First off, I've never used a tempered glass screen protector. And I have multiple devices with the same sensors but, this is still the ONLY DEVICE that has this problem.

mr.pnutt said:
First off, I've never used a tempered glass screen protector. And I have multiple devices with the same sensors but, this is still the ONLY DEVICE that has this problem.
Click to expand...
Click to collapse
Have you bothered to pull a log at as I advised? This will tell you. Have you tested it without the screen protector as I also advised?
Just because it is the same sensor (which I doubt) doesn't mean it is programmed the same way.

zelendel said:
Have you bothered to pull a log at as I advised? This will tell you. Have you tested it without the screen protector as I also advised?
Just because it is the same sensor (which I doubt) doesn't mean it is programmed the same way.
Click to expand...
Click to collapse
Yes I have. And what I've noticed is that if I erase my call log history or restart my phone, everything goes back to normal.

mr.pnutt said:
Yes I have. And what I've noticed is that if I erase my call log history or restart my phone, everything goes back to normal.
Click to expand...
Click to collapse
Ok then next will be to run the logcat. This will tell you why it is failing.

zelendel said:
Ok then next will be to run the logcat. This will tell you why it is failing.
Click to expand...
Click to collapse
I am running a logcat now and so far I have not experienced the same issue. I'll see what happens this weekend.

I had the same problem some weeks ago WITHOUT a screen protector but it never happened again. Could be the sensor which fails sometimes or a software related error. Are you using the stock phone application and stock kernel?

GioBozza said:
I had the same problem some weeks ago WITHOUT a screen protector but it never happened again. Could be the sensor which fails sometimes or a software related error. Are you using the stock phone application and stock kernel?
Click to expand...
Click to collapse
Yes, everything is stock, not rooted and, my bootloader is still factory locked.

mr.pnutt said:
Yes, everything is stock, not rooted and, my bootloader is still factory locked.
Click to expand...
Click to collapse
If it's a Phone app bug the only thing you can do is deleting its cache and/or reflashing the factory image. If this doesn't solve it, I would say it's an hardware fault, but I'm still prone to think it's software related.

P30 Pro Lock Screen Not Secure???

Please you guys try this on your phone? It can't just be my girlfriends? Read the description for details on the circumstances
https://youtu.be/Sj2Gs-TKpVg

No but I now have a nice clean screen, so thanks for that

Was your girlfriend near screen phone?
Remember, face id is activated when fod is working

Not with me. I tried several times but except clean screen i didnt get anything with that

maverickmarc said:
Please you guys try this on your phone? It can't just be my girlfriends? Read the description for details on the circumstances
https://youtu.be/Sj2Gs-TKpVg
Click to expand...
Click to collapse
Nope, dont work

She was no where near the phone.. I'm so confused, I keep doing it over and over, it works for me.
She does have a tempered glass screen protector, but the first time it unlocked while wiping the screen before I installed it. I'm not crazy lol.
It also doesn't always work like in the video, that just happened to be the video that made it look the easiest. 2-3 fingers on the wipe, slide up and down on the screen.

You have a tempered glass installed?
Can't possibly just be this phone. Keep trying lol

Did you have a tempered glass installed?
If I had a good secondary camera, I'd take a longer more detailed video

maverickmarc said:
She was no where near the phone.. I'm so confused, I keep doing it over and over, it works for me.
She does have a tempered glass screen protector, but the first time it unlocked while wiping the screen before I installed it. I'm not crazy lol.
It also doesn't always work like in the video, that just happened to be the video that made it look the easiest. 2-3 fingers on the wipe, slide up and down on the screen.
Click to expand...
Click to collapse
Face unlock is mistaking you for her, turn Face unlock off and try again
Either that or you are managing to enter the PIN with the cloth

Neither, I ain't an amateur, my face doesn't unlock it, and I'm not "accidentally" entering a 6 digit pin that I don't even know

I think it may be the screen protector, similar issue that the S10 had.. I'm pretty sure I did it without it, but I'm not about to tear it off to see, it's the last one in the pack

Using adb without functioning screen the prevents me from pressing auhtorization prompt

So I dropped my phone, the display under the screen shattered somehow (not sure how that works) without the glass breaking. Anyway, the screen is black with just a few pixels blinking blue or green.
I have previously activated USB debugging and I'm able to see my phone with adb devices but since I can't give authorization when the prompt pops up on the phone i'm not quite sure how to proceed. Since I also previously used scrcpy successfully I thought I could simply back everything up that way before sending the phone in.
I'm also not able to boot into the bootloader blindly as far as I'm aware.
Any suggestions or am I simply screwed?
Thanks!

Use a case in the future. Glass is witchy stuff, is subject to some of the laws of fluid hydraulics, and can behave in unexpected ways. Stress points can be present when new or develope over time from insults. Sometimes it takes very little force to cause a stress point to fracture.
If the digitizer is still functioning guess where the popup is and punch it until you hit its sweet spot. May take a few attempts.

blackhawk said:
Use a case in the future. Glass is witchy stuff, is subject to some of the laws of fluid hydraulics, and can behave in unexpected ways. Stress points can be present when new or develope over time from insults. Sometimes it takes very little force to cause a stress point to fracture.
If the digitizer is still functioning guess where the popup is and punch it until you hit its sweet spot. May take a few attempts.
Click to expand...
Click to collapse
I actually had a case and protective glass cover so I guess that's a big reason why nothing else broke. I feel pretty damn unlucky that this still didn't prevent this from happening.
To hit that lucky spot I would need to have the phone unlocked right? I'm not even sure If I can manage that.

Kashmir33 said:
I actually had a case and protective glass cover so I guess that's a big reason why nothing else broke. I feel pretty damn unlucky that this still didn't prevent this from happening.
To hit that lucky spot I would need to have the phone unlocked right? I'm not even sure If I can manage that.
Click to expand...
Click to collapse
I use the Zizo Bolt on my N10+, it's taken some hard hits on concrete, zero damage.
It's possible the tempered screen protector caused uneven distribution of the impact too.
I use Gorilla IQ Sheild.
Yeah pretty sure you need to unlock it first. Make up a template of where the buttons are to help you.

Question Fingerprint sensor issues? WASH YOUR HANDS!!!

I've been plagued by fingerprint issues just like everyone else. But I've also been running an experiment. Every time my fingerprint won't unlock the phone I wash my hands. AND IT WORKS EVERY SINGLE TIME!! The sensor is EXTREMELY sensitive!! If you have even one speck of dust it could fail to unlock.
I promise you.... try it!! It will work every single time!!
I mean really, thanks Google!!! I probably should wash my hands more if they're dirty enough to keep the sensor from working.

Helps to clean the sensor now and then, too. I have this issue on my Pixel 5 all the time.

I actually find the opposite. If my fingers have any dampness at all, it won't read properly.

I only wash my hands once a week and the sensor works fine

Do you have any protection applied on the phone ?

Wash my hands? I never had a device with in display fingerprint which needed washed hands.
I just added a new tempered glass screen protector, and that one is known for being awesome. I added all four fingerprints again, and it all worked like a charm for like five hours. 10/10 instant unlock. Today it does not work anymore. 3/10 unlock and slow. It's a software issue I guess and by now I'm totally fed up with the incompetence of the Google developers. It's a 750€ device, and even 200€ BBK phones got better working fingerprint readers.
I'm quite pi**ed.

t-ryder said:
Wash my hands? I never had a device with in display fingerprint which needed washed hands.
I just added a new tempered glass screen protector, and that one is known for being awesome. I added all for fingerprints again, and it all worked like a charm for like five hours. 10/10 instant unlock. Today it does not work anymore. 3/10 unlock and slow. It's a software issue I guess and by now I'm totally fed up with the incompetence of the Google developers. It's a 750€ device, and even 200€ BBK phones got better working fingerprint readers.
I'm quite pi**ed.
Click to expand...
Click to collapse
That happens to me too sometimes. Like perfect for a day or so then no matter what I do it's 3/10 just like you. I then reboot and it usually clears it up. One fail safe method it to rub your thumb (or whatever finger you use) across your forehead then try again. I've heard licking your finger but that is disgusting and I'd never do that. Try those 2 methods see if it helps. The March update also seems to make it quicker but it could be placebo.

t-ryder said:
It's a 750€ device, and even 200€ BBK phones got better working fingerprint readers.
I'm quite pi**ed.
Click to expand...
Click to collapse
I've gone from being pissed to being amused at how bad it is. For me 7 is worse than 6 ever was. Hell, just getting a couple digits enrolled on 7 has been impossible, and for an extra rub it teases and craps out at the 11:55 mark every time.
To be fair, I work with lumber and my digits tend to be rough. But this never stopped me from using fingerprints with older and cheaper phones.

hp420 said:
I've been plagued by fingerprint issues just like everyone else. But I've also been running an experiment. Every time my fingerprint won't unlock the phone I wash my hands. AND IT WORKS EVERY SINGLE TIME!! The sensor is EXTREMELY sensitive!! If you have even one speck of dust it could fail to unlock.
I promise you.... try it!! It will work every single time!!
I mean really, thanks Google!!! I probably should wash my hands more if they're dirty enough to keep the sensor from working.
Click to expand...
Click to collapse
What that means is the fingerprint sensor on your phone is of poor quality, just like some of the other components.
Google Pixel phones and their clean (read very basic with lack of features) software are both overrated and overpriced. You're essentially paying the premium to cover their marketing costs, and not for buying a better device.

I live in a dry environment, and I find that if my fingers are particularly dry the FPS doesn't work. Just breathing on my fingertip is usually enough to get the FPS to work. That being said, the March 2023 update seems to have improved the FPS significantly for me. Or it may be placibo effect.

It's 2:00 AM here, I switched off the lights in my room, took my P7, removed all four fingerprints, added them again sitting in full darkness. Turned on lights again. Well... now the fingerprint reader has never been so fast, unlocking so snappy and even with a soft and short touch with the tip of my finger. Hilarious.
I hope the devs at Google optimize the software for this mess of a sensor. What a sh*tshow.

And now at 10:30 AM it does not work anymore... LOL. No matter how I press the sensor, it forces me to put in my PIN to unlock.

This is weird that some people have problems with FPS while others don't.
I was initially afraid about this FPS issue reading all the bad experiences but it works basically 99% of times.
I still suspect it has more to do how you position your finger on the learning phase and is the finger dry or moist.
Because during learning phase it didn't ask to retouch the sensor with moist fingers but did ask to try again with dry finger. I suspect if you teach with moist finger it expects moist fingers but with dryer fingers it seems to not matter that much. On learning phase i pressed slightly harder compared to normal use.
I relearned finger 3 times because on the first two tries it would work about 50% of times. I remember i pressed quite gently on first tries since it looked like it registered it.
On the last try i had semi-dry fingers and tried to mimic normal unlocking position while giving the whole footprint. Even the very bottom part of thumb that normally don't touch the sensor.
Now it's pretty much like OnePlus6 experience with FPS with the exception that when the finger is super dry need to press slightly harder and it will register it.
If it matters i have screen film applied on screen. Not tempered glass.
Also with March 2023 update i haven't had a single fail yet with fingerprint detection.
Initially when received the phone i had October 2022 software and i didn't want to update. Then i exactly remember that it would stop working normally after a day or so. Like it forgot some areas of finger or expected very precise location.
I did buy phone in february and it could be that earlier batches had different FPS hardware revision. Smaller resolution/memory ... ?
I played around with FPS trying to get it to fail and when pressing too gently it fails so i would conclude the right pressure is quite important. Didn't find any difference in total darkness vs well lit room.

t-ryder said:
And now at 10:30 AM it does not work anymore... LOL. No matter how I press the sensor, it forces me to put in my PIN to unlock.
Click to expand...
Click to collapse
It is a fairly well know thing after Google moved away from the ultrasonic finger print scanners last used on the Pixel 5s, it has not worked well for many people. If you did the research prior you would have seen this has been issue ever since. Easy solution is don't use it and go back to the old style of a pin or pattern.
Can't comment on the face recognition portion, since I haven't done any research on it, nor do I want to, since I don't have a desire to use it, but I am sure other here have extensive experience and knowledge about it. Just have to do the research before trying it if you want to know what may or may not come of it before trying.

rekids said:
Easy solution is don't use it and go back to the old style of a pin or pattern.
Click to expand...
Click to collapse
Even easier is to not use any protection at all.
Both are impractical suggestions.
Having been spoiled by Face Unlock, there is no going back for me. Fingerprint is used mostly in dark environments where Face Unlock struggles.

TheMystic said:
Even easier is to not use any protection at all.
Both are impractical suggestions.
Having been spoiled by Face Unlock, there is no going back for me. Fingerprint is used mostly in dark environments where Face Unlock struggles.
Click to expand...
Click to collapse
and the darkness is where my fingerprint on Pixel 7 fails 100% of the time.
Pin is difficult while in motion. Pattern for me is easiest.
To OP, I wash my hands religiously. I won't touch a door knob and then touch my face, so washing alone is not the solution. I imagine it has to do with screen protectors installed since everyone uses different ones that have varying thicknesses and see-through visibility.

richb518 said:
I imagine it has to do with screen protectors installed since everyone uses different ones that have varying thicknesses and see-through visibility.
Click to expand...
Click to collapse
I wonder what kind of special fingerprint sensor the Pixel 6 and 7 have then. My last few devices (Realme & OnePlus) with in-display fpr ... well you could have slapped a $2 or a $50 tgsp on it, and it did not matter in any way. They worked just like a charm. I had a Pixel 6 (yeah, f* that pos) and now a Pixel 7 (I really like it) and both fpr are the worst mess.

t-ryder said:
I wonder what kind of special fingerprint sensor the Pixel 6 and 7 have then. My last few devices (Realme & OnePlus) with in-display fpr ... well you could have slapped a $2 or a $50 tgsp on it, and it did not matter in any way. They worked just like a charm. I had a Pixel 6 (yeah, f* that pos) and now a Pixel 7 (I really like it) and both fpr are the worst mess.
Click to expand...
Click to collapse
You gotta figure out what is wrong. Not too many responses here because most are not having those issues any longer. Originally, yes for sure. But lately it's been working a good 90+ % of the time. Never can get an unlock after swimming though until I moisturize but that's excusable. Get rid of the silly screen protector which is useless unless you are in the sand/gravel business which I see you are not. (nice walls) If it still doesn't work perhaps an RMA would be in order. I've seen that happen and the replacement is way better. But you shouldn't live with a flawed device that is otherwise very good.

bobby janow said:
You gotta figure out what is wrong. Not too many responses here because most are not having those issues any longer. Originally, yes for sure. But lately it's been working a good 90+ % of the time. Never can get an unlock after swimming though until I moisturize but that's excusable. Get rid of the silly screen protector which is useless unless you are in the sand/gravel business which I see you are not. (nice walls) If it still doesn't work perhaps an RMA would be in order. I've seen that happen and the replacement is way better. But you shouldn't live with a flawed device that is otherwise very good.
Click to expand...
Click to collapse
All good points. I don't have opinions about which screen protector works best since my Pixel 7 sensor is a dud without one. If my 7 is worse than 6 then simple logic suggests there's a defect.
I bought a used Pixel 5 a few months ago as a backup, plus it helped verify my P7 problem isn't my fingers. My wife called the P5 "cute" so now she has it. I've never gone through Google's replacement process before but it should be a breeze compared to getting the P5 back.
t-ryder said:
I wonder what kind of special fingerprint sensor the Pixel 6 and 7 have then. My last few devices (Realme & OnePlus) with in-display fpr ... well you could have slapped a $2 or a $50 tgsp on it, and it did not matter in any way. They worked just like a charm. I had a Pixel 6 (yeah, f* that pos) and now a Pixel 7 (I really like it) and both fpr are the worst mess.
Click to expand...
Click to collapse
One of the issues seems to be Tensor/Exynos versus Snapdragon. Apparently, the former can't use the latter's ultrasonic sensor tech without infringing on patents. But I think the overwhelming problem boils down to tolerances and inconsistencies in the manufacturing process, especially in the past couple years, and whether our Pixels were assembled during first shift Monday morning, hump day, payday...

@manjaroid lol you have no idea what it took to get my wife to trade in her p5. The p7 cost $100 after so she went for it. Of the rumors of the p8 at 5.8 are true then Black Friday is looking really good. As for your device it does sound like a lemon. Try to get an rma of you can.