Double tap to wake doesn't always work

[NJMike]

Double tap to lock works 100% of the time, however double tap to wake only works if the phone has been active recently; if not, it requires two double taps to wake it. This occurs regardless of screen protector type and even without one.

 

[B. Diddy]

Which phone do you have? Some phones just require a single tap, while others require a double tap.

 

[NJMike]

Which phone do you have? Some phones just require a single tap, while others require a double tap.

Galaxy A23 5G.

 

[gomezz]

My experience is that taps of any sort sometimes do not work if using the very tip of the finger but need to use a bit lower down where the fingerprint lives. My assumption is that there is not enough natural oils / moisture just below where the finger nail is.

 

[NJMike]

My experience is that taps of any sort sometimes do not work if using the very tip of the finger but need to use a bit lower down where the fingerprint lives. My assumption is that there is not enough natural oils / moisture just below where the finger nail is.

I will have to try that then.

 

[swebb]

I've also found it inconsistent.

 

[NJMike]

My experience is that taps of any sort sometimes do not work if using the very tip of the finger but need to use a bit lower down where the fingerprint lives. My assumption is that there is not enough natural oils / moisture just below where the finger nail is.

Hey this actually seemed to have done it, thanks!

 

[NJMike]

Hey this actually seemed to have done it, thanks!

At least... I think? It was starting to do it again this evening.

 

[B. Diddy]

I moved this from the Android 13 forum to the Galaxy A Series forum, since it's more likely to be a device-specific issue rather than a general Android 13 issue.

 

[mustang7757]

Try in safe mode see if any difference

 

[NJMike]

I think I might have figured it out: It's picky about the intensity of the taps. It's been responding 100% of the time if I barely make contact with the screen. So its more of "touch touch".

 

[mustang7757]

I think I might have figured it out: It's picky about the intensity of the taps. It's been responding 100% of the time if I barely make contact with the screen. So its more of "touch touch".

Sweet

 

[NJMike]

I think it stopped working with that method again, so back to square one.

One thing I always notice, is that this only happens if the phone has not been touched in a long time (think 10+ minutes we'll say), because it responds 100% of the time to the double-tap wake no matter the intensity or speed if it was active.

I had disabled Doze Mode as a suggestion from another topic I created on here, which is the only thing I could think of that makes the most sense as to why the phone doesn't always respond if it hasn't been touched after a while.

 

[J Dubbs]

I think it stopped working with that method again, so back to square one.

One thing I always notice, is that this only happens if the phone has not been touched in a long time (think 10+ minutes we'll say), because it responds 100% of the time to the double-tap wake no matter the intensity or speed if it was active.

I had disabled Doze Mode as a suggestion from another topic I created on here, which is the only thing I could think of that makes the most sense as to why the phone doesn't always respond if it hasn't been touched after a while.

Have you tried changing the speed of your taps? Have you also tried different parts of the screen? I've had phones that were particular about those things

 

[NJMike]

Have you tried changing the speed of your taps? Have you also tried different parts of the screen? I've had phones that were particular about those things

I am trying to do it a bit slower and it seems to be a bit better that way. I just find it odd that it's only for waking the phone; any speed tap works for locking it.