I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
If you move your phone first, then it will work by double tapping.
I think that quadruple tap works because one of those first two taps moves the phone.
Not from my experimentation. It doesn't seem to matter if i've moved it first or tapped it directly when it's sitting on the table. Then only factor that seems to matter is time since screen off.
Thanks for the input though.
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake, but sometimes two taps don't seem to register even after moving and I have to use the button. Might be something to do with the screen sensitivity being reduced combined with a screen protector perhaps?
I also found the firmware update messed with the proximity sensor and my screen now fails to come on when I want to end a call and move the phone away from my ear. Means I have to use the button to turn on the screen to hang up. Very annoying.
Click to expand...
Click to collapse
I'm on A.5.77, which is the latest, right?
I have this issue about 5% of the time, 95% of the time even if I have the phone lying still on the table double tap works. Must be something (also) else than the firmware!
pipspeak said:
It's kinda flaky in my experience. The new firmware did indeed add the "must move phone first" feature to the tap-to-wake
Click to expand...
Click to collapse
double tap works first time every time even if the phone has been sitting still and idle for 10 hours.
I know theres a few people who have this problem but its something other than just the new firmware.
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
pipspeak said:
I'm curious who has a screen protector and who is using a launcher other than stock (or indeed is rooted). I suspect my screen protector and Nova Launcher are not helping matters, but in my case it was definitely brought on by the new firmware. Before that update I had never experienced any double-tap failure at all... it was 100% reliable.
Click to expand...
Click to collapse
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
had a tempered glass protector on from day one, phone has always been stock, no other launcher. T2W worked brilliantly until the latest firmware update. frustrating when the phone is the car mount, i have to hit the power button to get the screen on instead of just tap-tap.
quarrymanpaul said:
You could be onto something with Nova Launcher. I switched back to the stock launcher and I think things have improved...
Click to expand...
Click to collapse
Full day's use now and replacing Nova launcher with Apex has definitely improved things.
Might help others in the same situation who are scratching their heads wondering why everyone else seems to have perfect tap2wake.
Tried Apex for a day as well. No different than Nova for me.
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
AM Radio said:
hey, just figured out something, by accident.
yup, double tap to wake is still mucked up from the latest update (unless the phone is picked up first) but TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Not working here.
I have a Nillkin tempered glass on mine though.
quack3d said:
I have a Nillkin tempered glass on mine though.
Click to expand...
Click to collapse
me too. weird. fingers crossed the next update takes care of this, properly.
AM Radio said:
...TRIPLE TAP to wake works consistently for me after the phone has been flat/unmoved for some time.
tap-tap-tap
Click to expand...
Click to collapse
Works for me too. [emoji4]
Did Lollipop fix this problem?
quack3d said:
Did Lollipop fix this problem?
Click to expand...
Click to collapse
Not really. In fact it got worse.
quarrymanpaul said:
I've found that after a period of time once the screen has turned off (5 to 10 mins) I need to double tap the screen, then double tap again to actually get it to wake up.
I'm on the .77 FW and while I've heard some of the earlier firmwares could be more responsive I found the screen was TOO responsive and prefer to stick on the latest firmware.
So now that we're all rooted etc, there must be some fix that can be done. Is it a case that the tap2wake process goes to "sleep" after a period of time and the first 2 taps wakes it?
Click to expand...
Click to collapse
Well, I can tell you why this is happening. this happened to me, because I just had too many xposed modules.. once I got rid of them, everything went back to normal
Been a long time since I've posted here but found this thread as had the same issue when the phone is flat on a table.
Anyway, think I've found a solid solution or work around, depends how you look at it. If you use just an extended finger, all other fingers closed or away from the phone, it's very inconsistent but mostly unresponsive.
Solution: grip the top and bottom of the phone lightly with your thumb and middle or 4th finger at the same time as tapping the screen with your index finger. Works every time for me.
So Sony's reduced the sensitivity to the point where it needs additional capacitance so it knows you are holding the phone and it won't unlock in your pocket. Makes sense.
pretty frastrating here too.. but really can't find out the main reason of the problem here as immediately when I got the phone I rooted it, flashed .77, replaced stock launcher with nova, installed expsed and 2-3 modules :crying:
will try the three-taps and olding-phone+index-finger-tapping workarounds, thanks for the hints
Related
Hi guys I'm running into problem that the capacitive buttons sometime do not behave and failed to respond. I have seen a guy on youtube also complaining about the same thing and have it fixed by updating to 1.29. However mine's already on 1.29. Anyone else have the same issue?
Do you use a screen protector that covers the buttons?
henrybravo said:
Do you use a screen protector that covers the buttons?
Click to expand...
Click to collapse
Not facing any such issue, however it does require to hit at correct place on the bar. I observed lot of times in initial days I was hitting slightly above the back button
raundown said:
Hi guys I'm running into problem that the capacitive buttons sometime do not behave and failed to respond. I have seen a guy on youtube also complaining about the same thing and have it fixed by updating to 1.29. However mine's already on 1.29. Anyone else have the same issue?
Click to expand...
Click to collapse
My Xperia S has similar problem... There is point which you need to search and find ( it's easy once u get used to it)
always touch on that pt and the phone should always respond..
I've been trying to get accustomed to swiping through whichever button I need. I put my thumb on the HTC logo (not using any HTCLOGO tweaks), and then swipe over the back or over the home button depending on which I need. It rarely if ever fails this way and it feels pretty slick using a pseudo-gesture to navigate :good:
The only issue with the buttons i'm facing is bringing up the menu on back button long press. Probably works about 75% of the time but that 25% where I inevitably exit the app is frustrating
henrybravo said:
Do you use a screen protector that covers the buttons?
Click to expand...
Click to collapse
Yea I do. Is it really the screen protector that is causing the problem tho?
KY Wildcats said:
I've been trying to get accustomed to swiping through whichever button I need. I put my thumb on the HTC logo (not using any HTCLOGO tweaks), and then swipe over the back or over the home button depending on which I need. It rarely if ever fails this way and it feels pretty slick using a pseudo-gesture to navigate :good:
The only issue with the buttons i'm facing is bringing up the menu on back button long press. Probably works about 75% of the time but that 25% where I inevitably exit the app is frustrating
Click to expand...
Click to collapse
Same. The swiping doesn't work for me sometimes. I'll have to keep tapping and swiping until it finally works. Double tap on the home button is not really a good idea IMO. Sometimes it doesn't register as double tap and brings you back to home.
raundown said:
Yea I do. Is it really the screen protector that is causing the problem tho?
Click to expand...
Click to collapse
Yes your screen protector could be causing the problem. There are multiple posts in this thread where people are complaining about their screen protectors (especially the official HTC branded ones) that are causing the capacitive buttons to be considerably less sensitive and problematic.
raundown said:
Hi guys I'm running into problem that the capacitive buttons sometime do not behave and failed to respond. I have seen a guy on youtube also complaining about the same thing and have it fixed by updating to 1.29. However mine's already on 1.29. Anyone else have the same issue?
Click to expand...
Click to collapse
So myself and a buddy of mine are both having issues with the capacitive buttons as well. We both have screen protectors. I wish someone could confirm if they are having issues even without screen protector. The guy at the tmo store put it on perfectly and I suck at putting these damn protectors on my phone
i am sure this is screen protector problem , i had no screen protector before and i faced none of those problems and now i have one ... its all problematic.
Switching my screen protectors from fosman to amfilm helped me. I'm assuming because the amfilm is thinner than the fosman. It's been about a day since I switched and the back key hasn't failed me once.
Sent from my Nexus 4 using Tapatalk 2
disc0rdian said:
So myself and a buddy of mine are both having issues with the capacitive buttons as well. We both have screen protectors. I wish someone could confirm if they are having issues even without screen protector. The guy at the tmo store put it on perfectly and I suck at putting these damn protectors on my phone
Click to expand...
Click to collapse
I have no screen protector and I am having the same problem although it is worse when a screen protector is on.
I think the button detect area needs to be bigger and the sensitivity needs to go up or they need to respond immediately regardless of whether the app has frozen, especially the home button.
biffsmash said:
I have no screen protector and I am having the same problem although it is worse when a screen protector is on.
I think the button detect area needs to be bigger and the sensitivity needs to go up or they need to respond immediately regardless of whether the app has frozen, especially the home button.
Click to expand...
Click to collapse
And you have also updated to 1.29?
darkgoon3r96 said:
And you have also updated to 1.29?
Click to expand...
Click to collapse
yes, mine is Trickdroid 5.5.1 with ElementalX 0.10, but once I putted my tempered glass protector on, those capacitive buttons not even work at all...
angelky said:
yes, mine is Trickdroid 5.5.1 with ElementalX 0.10, but once I putted my tempered glass protector on, those capacitive buttons not even work at all...
Click to expand...
Click to collapse
I was having a problem with this as well without a screen protector but I have a tempered protector on it now and it is considerably worse now.
what's funny is that I think the screen's touch sensitivity actually needs to come down for me and the button sensitivity needs to go up.
Maybe there's an app for that.
I just picked up an XZ2 for a steal. So far I really like the phone, but one thing has really been nagging me. The lift to wake functionality works pretty well most of the time, but occasionally, it will just stop working completely. It's like the phone goes to sleep and stops recognizing the sensors or something. It doesn't happen after sitting for a long time, either. It actually happens right after I've been using it. Today, the screen timed out and went black and no matter how much I shook the phone, put it in my pocket and took it out, etc., it never worked again until I hit the power button.
Before someone suggests just hitting the power button or fingerprint sensor: You're missing the point. I shouldn't have to. It's bad enough that Sony took tap-to-wake from us and never gave it back. But I expect this feature to work consistently. Really, you should rarely, if ever, have to hit the power button. A similar feature on the iPhone works without fail almost 100% of the time.
I'm just looking to see if anyone else has experienced this. The phone is fresh out of the box, has the latest build (51.1.A.4.225) and was set up manually, not restored from a cloud backup. Has anyone else seen this?
Oh yes, it is one of three really small, miniscule bugs I've got with my XZ2. In my case, the lift to wake only stops working a few times and after I wake the phone manually, it works the way it should work again. But it only happens in those rare times.
AlvinZahran98 said:
Oh yes, it is one of three really small, miniscule bugs I've got with my XZ2. In my case, the lift to wake only stops working a few times and after I wake the phone manually, it works the way it should work again. But it only happens in those rare times.
Click to expand...
Click to collapse
Thanks. Yeah, it's annoying. The inconsistency drives me crazy. It seems to have something to do with the screen timeout.
I wish they would just give us proper tap to wake back.
Sent from my H8266 using Tapatalk
Hello, really new to this thread. My Mi 8 is about 2 weeks old. So recently I noticed that the home button gesture doesn't work sometimes. I have to repeatedly swipe up from the bottom of the screen for it to work...also when pressing something close to the status bar seems to trigger the status bar opening animation. This happens only every now and then then. I'm on stock global rom everything locked nothing tinkered with at all. Anyone experiencing the same thing?
Mike20017 said:
Hello, really new to this thread. My Mi 8 is about 2 weeks old. So recently I noticed that the home button gesture doesn't work sometimes. I have to repeatedly swipe up from the bottom of the screen for it to work...also when pressing something close to the status bar seems to trigger the status bar opening animation. This happens only every now and then then. I'm on stock global rom everything locked nothing tinkered with at all. Anyone experiencing the same thing?
Click to expand...
Click to collapse
what mi8have Home button？
PUBGKING12 said:
what mi8have Home button？
Click to expand...
Click to collapse
I'm talking about the home screen gesture.
Try to test if your screen has some issues, I don't experience any problem
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
You mean using the gesture settings, when you swipe from the bottom it will not go home (takes multiple tries)? If so, do you have a case or screen protector installed? The way you're supposed to swipe is pretty much from outside of the actual display, upwards, so if there is something interfering with this, or you're swiping from in the display, it may not work.
If not, then try using a touch screen test app such as Touch Screen Test from Google Play (developed by Siriuth). Touch the bottom area multiple times (swipe down, left, right, but not up as this may send you to the home screen of course). Swipe slowly to see the path properly. Does it skip at any section? If it does, touch in that area may be damaged. If this phone was purchased used or from a 3rd party seller, this may be why it is damaged.
Crossvxm said:
You mean using the gesture settings, when you swipe from the bottom it will not go home (takes multiple tries)? If so, do you have a case or screen protector installed? The way you're supposed to swipe is pretty much from outside of the actual display, upwards, so if there is something interfering with this, or you're swiping from in the display, it may not work.
If not, then try using a touch screen test app such as Touch Screen Test from Google Play (developed by Siriuth). Touch the bottom area multiple times (swipe down, left, right, but not up as this may send you to the home screen of course). Swipe slowly to see the path properly. Does it skip at any section? If it does, touch in that area may be damaged. If this phone was purchased used or from a 3rd party seller, this may be why it is damaged.
Click to expand...
Click to collapse
Just tried it... Everything seems fine. But still sometimes it tends to require several tries for the gesture to actually register. I'm on global 10.2.3.0, could be a miui bug since this version is not the best. Also has battery drain problems. Could be fixed in the next update.
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
Mike20017 said:
Just tried it... Everything seems fine. But still sometimes it tends to require several tries for the gesture to actually register. I'm on global 10.2.3.0, could be a miui bug since this version is not the best. Also has battery drain problems. Could be fixed in the next update.
Click to expand...
Click to collapse
That's very odd. Does the oleophobic coating in that area feel worn or anything? Does the friction feel high? Mine never fails, not even to open the multitasker. Do you have "Double Check for Gestures" enabled? Try turning this off perhaps? The battery drain I definitely agree. I went from 7 hrs of SOT to less than 5.
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
ok
Since the G973FXXU1ASD5(This one) update trough odin i have a problem with
protection against accidental contact. It looks like it doesnt work anymore.
Several times my s10 made some screenshots from galaxy store etc.. in my pocket.
Anyone else has this problem?
No one?
Ceas4r said:
Since the G973FXXU1ASD5(This one) update trough odin i have a problem with
protection against accidental contact. It looks like it doesnt work anymore.
Several times my s10 made some screenshots from galaxy store etc.. in my pocket.
Anyone else has this problem?
Click to expand...
Click to collapse
No
I had the same issue but it's gone now after I did what was suggested in the thread https://forum.xda-developers.com/galaxy-s10/help/accidental-touches-t3922490
I have that problem too. My penis kept on poking my s10+ screen and turning on my phone.
Player04 said:
I have that problem too. My penis kept on poking my s10+ screen and turning on my phone.
Click to expand...
Click to collapse
Maybe skip commando day and wear underwear next time?
Turned on double tap to wake right after the update, because I was expecting the issue resolved.
Just couple days ago it was warm in my pants, check the phone and it was just finished doing factory reset. Been meaning to factory reset, so thanks Samsung!
So to say guys, when the screen is off and you cover the top of the phone while waking it (double tap or power button), the phone stays "protected" by avoiding wake up or unlock ?
My Exynos S10 doesn't care about it and wakes up normally regardless of the top being covered or not ...
googy_anas said:
So to say guys, when the screen is off and you cover the top of the phone while waking it (double tap or power button), the phone stays "protected" by avoiding wake up or unlock ?
My Exynos S10 doesn't care about it and wakes up normally regardless of the top being covered or not ...
Click to expand...
Click to collapse
Normally while the phone is covered (in pocket) it says something like pocket protection... and a button with ok. After odin flash with newest firmware i dont even get that message anymore.
Ceas4r said:
Normally while the phone is covered (in pocket) it says something like pocket protection... and a button with ok. After odin flash with newest firmware i dont even get that message anymore.
Click to expand...
Click to collapse
That's exactly what I am facing.
It would be cool if users of the latest firmware confirm (or deny) the existence of the bug ...
I confirmed the bug by myself and was forced to disable double tap to wake as a workaround while waiting for a proper fix
I dont know why, but sometimes my screen will stop responding to touch. I can still use the top and bottom of the screen, but the 90% in between the top and bottom lip of the screen wont respond until i restart the phone. This can happen once a week or three time a day, seemingly at random. Anyone know about this problem?
I had this happen the other day and it really surprised me - exactly where you said as well. The top & bottom worked, but the middle was dead. I did have a little skuzz on the phone, so I spat on it & wiped it off and that brought it back to life. Not sure if that was truly the problem, or if it was just coincidence. Which screen protector are you using?
burnxtc said:
I had this happen the other day and it really surprised me - exactly where you said as well. The top & bottom worked, but the middle was dead. I did have a little skuzz on the phone, so I spat on it & wiped it off and that brought it back to life. Not sure if that was truly the problem, or if it was just coincidence. Which screen protector are you using?
Click to expand...
Click to collapse
At the moment i dont have a screen protector on, ive had the problem with and without screen protectors. Its so weird, its like the screen just dies.
Hopefully it's just a background app/service and not a hardware issue. I'd try freezing the snot out of background apps - particularly anything that didn't come pre-packaged with the phone - and go from there. Should this work, enable a handful at a time until you find the culprit. Pretty much anything can lock up an app nowadays, particularly keyboards and the like.
Below is my "final" list of frozen apps on a11 and the phone performs exceptionally. No root & no security broken. This is a preset file for ADB AppControl - I hope this helps.
When you say freezing, do you mean adding to deep sleep or removing with adb?
DS1000RR said:
When you say freezing, do you mean adding to deep sleep or removing with adb?
Click to expand...
Click to collapse
I mean freezing/disabling via adb. I only remove once I'm completely comfortable with a practiced configuration.