Tap to wake issues

[Grabber5.0]

It can't just be me. Ever since I got the Pixel 7, it's done this. Sometimes when I double tap to wake my screen, it just doesn't come on. Usually another double tap will do it, and sometimes I just have to pick it up and/or press the power button. It's not something I'd exchange the phone over, but it is a bit annoying.

 

[rvbfan]

Do you have a screen protector on it?

Sent from my Pixel 6 using Tapatalk

 

[Grabber5.0]

Not yet #nervouslaugh (I've had it for several weeks tho, just haven't put it on yet )

This is the only "issue" I've experienced with this phone. And it works fine the majority of the time, so I put up with it.

 

[rvbfan]

I've run my P6 without one for a year now, so no biggie. Try turning it on and see what happens.
Also you only need to single tap the screen, maybe you're putting the screen back to sleep when you double tap?
Sent from my Pixel 6 using Tapatalk

 

[bkeaver]

It can't just be me. Ever since I got the Pixel 7, it's done this. Sometimes when I double tap to wake my screen, it just doesn't come on. Usually another double tap will do it, and sometimes I just have to pick it up and/or press the power button. It's not something I'd exchange the phone over, but it is a bit annoying.

The only time my p7p fails on the tap to wake us if it's plugged into my car and running Android auto, except for that, I have no issues.

Sent from my SM-F936U1 using Tapatalk

 

[Grabber5.0]

...
Also you only need to single tap the screen, maybe you're putting the screen back to sleep when you double tap?
Sent from my Pixel 6 using Tapatalk

Hmm, I wonder if that's what's going on.. I'll try to consciously stop double-tapping. I was used to doing that with my S22.

 

[B. Diddy]

Hmm, I wonder if that's what's going on.. I'll try to consciously stop double-tapping. I was used to doing that with my S22.

Yeah, that was my habit as well, even though I primarily have had only Pixels!

 

[cbreze]

My pixel 7 does the same occasionally. Sometimes one tap will do it sometimes two, I generally just use two out of habit. I've never used a screen protector. Occasionally pressing the power button is the only way that works. Fortunately that doesn't happen too often. I would say 10% of the time a tap won't wake it on the first try. I've just gotten used to it, not that big of a deal. I had to disable raise to wake because it was causing the screen to light up at night in my room when I was in bed off and on all night long. So I've been getting used to the tap rather than the lift.

 

[gomezz]

I sometimes find that my finger does not work especially in cold weather and I need to lick my finger to get it to work.

 

[Grabber5.0]

I sometimes find that my finger does not work especially in cold weather and I need to lick my finger to get it to work.

I have always had the same issue with the fingerprint sensors. Especially during winter when my skin is dry. Doesn't matter if it's under the screen or on the back. If it doesn't work, a quick lick fixes it.

 

[PGrey]

It's very finnicky (by design I suspect), in that if you have another digit/palm/whichever-body-part contacting the screen, it won't wake (on the tap, it's a single-tap, something I don't think I'll ever get used to after so many years of mostly double-tap phones... :-\

Anyway, try to make sure you have no other contact with the screen, and tap it (single or double will typically work, it just "tosses" the 2nd tap, algorithmically); mine is quite consistent if I'm careful like this.

 

[bkdodger2]

I've had the same issue with the last few pixel phones that I've owned. It disappears for a while and then it comes back. But I think what the member said earlier it picks up if you're hands are touching the screen or maybe in the pocket and you need to wake it up with the power button as the double tap or the raise to wake doesn't wake the phone..

 

[cbreze]

The past few days I’ve noticed that tapping the upper portion of the screen it works reliably well to wake up

 

[Grabber5.0]

I've been working on the habit of only tapping once to wake up my phone, and it's been much better. I'm a trained monkey, so of course that's carrying over to my S21, so of course it fails to wake up and I remember to then double-tap it. LOL

 

[PGrey]

@Grabber5.0 I'm the same, with a S7+ tablet, that requires double-tap, hmm... I also came to the Pixel from a long set of OP phones, and Win-Phones, all of which supported (required) double-tap to wake, so I'm a bit of a trained monkey, too ;-]
It definitely works better though, if you try to consciously single-tap; I suspect they're trying to prevent the palm-touch thing, that occurs when you're already touching another area of the phone (as I mentioned above).

I still think double-tap is the way to go, as a standard, and it tends to be more definitive on the whole, when it comes to the accidental secondary touches, but apparently Google doesn't agree (at least not since the Nexus 6P, pretty sure mine had dobule-tap back in the day, hmm...).

 

[Morty2264]

I agree with you! Though not an issue worth returning the device, it's still a bothersome one! Does this issue persist in Safe Mode?

 

[Macdtek]

Old thread I know but did you ever solve this issue. My pp7 has stopped lift to wake and tap to wake since android 14 updated . Works in both safe mode and aeroplane mode.

 

[PGrey]

Old thread I know but did you ever solve this issue. My pp7 has stopped lift to wake and tap to wake since android 14 updated . Works in both safe mode and aeroplane mode.

Most likely you've got an app with overlay permissions, that's hosing the systems' ability to receive the tap.
To diagnose:
- Try flipping through the various app permissions, I think this is now called "draw over other apps", or very similar.
- Disable ANYTHING that's NOT Android-core, and has that permission and/or Administrator App permissions. Take note, if you have a few things like say a password manager, an authenticator app, or similar, you'll want to re-enable those permissions, when done.
- test to see if tap-to-wake works
- re-enable the apps with those permissions, one-by-one, and test after each. At some point you'll find the offending app.

 

[Macdtek]

You beat me to it. Tried every 3rd party app one by one. Turned out to be a radio app that od been using for years. Not updated to well to run with 14 on my pp7. Thanks for the answer. Pixel now like new again and I'm all happy

 

[Morty2264]

You beat me to it. Tried every 3rd party app one by one. Turned out to be a radio app that od been using for years. Not updated to well to run with 14 on my pp7. Thanks for the answer. Pixel now like new again and I'm all happy

That's so great that things are working well for you again!