Related
Got my Gear Live yesterday. The raise arm gesture was flaky compared to my Gear 1 but it was no big deal. Today the raise arm gesture doesn't work at all. My Gear Live does not have notifications disabled. I've reset the Gear multiple times, uninstalled and re-installed the android wear software multiple times (cleared cache and data too) and made sure it was unpaired and re-paired on my phone. If my screen is set to off, it will never come back on unless I press the button or touch my screen. If my screen is set to always be on, it will stay in the lower brightness mode until I touch the screen or press the button.
It seems like the motion sensing or the gesture itself is totally broken after only a day. Anyone else have issues with the gesture? (flakiness or otherwise)
novadaemon said:
Got my Gear Live yesterday. The raise arm gesture was flaky compared to my Gear 1 but it was no big deal. Today the raise arm gesture doesn't work at all. My Gear Live does not have notifications disabled. I've reset the Gear multiple times, uninstalled and re-installed the android wear software multiple times (cleared cache and data too) and made sure it was unpaired and re-paired on my phone. If my screen is set to off, it will never come back on unless I press the button or touch my screen. If my screen is set to always be on, it will stay in the lower brightness mode until I touch the screen or press the button.
It seems like the motion sensing or the gesture itself is totally broken after only a day. Anyone else have issues with the gesture? (flakiness or otherwise)
Click to expand...
Click to collapse
Mine works fine with always-on enabled. If anything it works too well. I wish I could turn the functionality off because my screen is always waking up when I don't want it to.
There were complaints that it was too sensitive, perhaps the latest update has toned it down a little too much.
You do now need a definite arm movement to make it come on.
Lift the arm and roll the wrist around towards you.
Rik
I've had mine since Monday and the gesture worked great. About half way through the day yesterday the gesture completely stopped working. I tried to reboot, factory reset but nothing worked. Eventually I held the power button down for about 10 seconds in order to bring up the power menu. Instead the watch just rebooted itself and after that, the gesture started working again. Weird.
czonin said:
I've had mine since Monday and the gesture worked great. About half way through the day yesterday the gesture completely stopped working. I tried to reboot, factory reset but nothing worked. Eventually I held the power button down for about 10 seconds in order to bring up the power menu. Instead the watch just rebooted itself and after that, the gesture started working again. Weird.
Click to expand...
Click to collapse
What the hell..... I've held down the power button before and the menu usually pops up. I just tried this and it worked! It also rebooted like you said, and now it works again. holy ****. thank you so much!
novadaemon said:
What the hell..... I've held down the power button before and the menu usually pops up. I just tried this and it worked! It also rebooted like you said, and now it works again. holy ****. thank you so much!
Click to expand...
Click to collapse
No problem, glad I was able to help!
i've also found that it responds to the rolling towards your face more than the raising of your arm. (for me at least)
adiliyo said:
i've also found that it responds to the rolling towards your face more than the raising of your arm. (for me at least)
Click to expand...
Click to collapse
+1
However, I thought the gesture worked better before the recent update. I don't KNOW that the update changed the gesture but it seems less reliable than it did when I first got the watch. Now I seem to get quite a few false activations and sometimes now have to repeat the gesture to make it switch on.
This is not a major issue, don't get me wrong.
czonin said:
I've had mine since Monday and the gesture worked great. About half way through the day yesterday the gesture completely stopped working. I tried to reboot, factory reset but nothing worked. Eventually I held the power button down for about 10 seconds in order to bring up the power menu. Instead the watch just rebooted itself and after that, the gesture started working again. Weird.
Click to expand...
Click to collapse
Same boat (reboot, factory reset, etc). Held down for 10 seconds, it rebooted, and fixed!
The gesture does NOT work when the watch is on silent. This is most likely your issue.
Held down for 10 seconds, it rebooted, and fixed!
seh6183 said:
The gesture does NOT work when the watch is on silent. This is most likely your issue.
Click to expand...
Click to collapse
This is correct - I just tested this with my Samsung Gear Live. If notifications are not muted, the 'lift arm and roll wrist' gesture will wake the watch.
This works even when the watch face is not set to 'Always On' in the Android Wear settings menu.
I come from the Gear Fit where you can switch off this automatic gesture completely. I hope this setting will show up within Android Wear soon. I drove with my car tonight and the watch was constantly waking up showing me the same card all over again and again while steering... Argh.
Is there some kind of patch or adb setting where I can change this?
TIA
Greetings
plant
plantagoo said:
I come from the Gear Fit where you can switch off this automatic gesture completely. I hope this setting will show up within Android Wear soon. I drove with my car tonight and the watch was constantly waking up showing me the same card all over again and again while steering... Argh.
Is there some kind of patch or adb setting where I can change this?
TIA
Greetings
plant
Click to expand...
Click to collapse
I guess for the time being, you could just mute notifications while driving. Unless of course you want them to come through while driving.
My problem is it is too sensitivity.
Scratch my nose the watch wakes and this drains the battery
Hi friends !
Just received mine today, and released it on 4.4w1....But no issue to this fu...g problem of automatic switch on gesture !!!
Please Google, lesson to us !!
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
I'm still on a Tmobile Note 8 and just got the One UI update today and was so disappointed to find that it doesn't have the 'double tap to wake' feature. I always thought this update would bring this feature. As I walked into a Tmobile store couple weeks ago and confirmed this feature was on a S10 so I thought this update would do it. Anyway, just wanted to know if any of you Note 9 owners who have the One UI update have this feature? if so, that would be awesome, and will get a Note 9 soon; if not, hmmm don't know, will just keep using my Note 8, thanks!!
slamming_sammy1 said:
I'm still on a Tmobile Note 8 and just got the One UI update today and was so disappointed to find that it doesn't have the 'double tap to wake' feature. I always thought this update would bring this feature. As I walked into a Tmobile store couple weeks ago and confirmed this feature was on a S10 so I thought this update would do it. Anyway, just wanted to know if any of you Note 9 owners who have the One UI update have this feature? if so, that would be awesome, and will get a Note 9 soon; if not, hmmm don't know, will just keep using my Note 8, thanks!!
Click to expand...
Click to collapse
Double tap to wake always on screen display works.
Sent from my SM-N960U1 using Tapatalk
sorry, I meant 'double tap to wake' screen, not always on display. this already works on my Note 8
Nope, d2tw is only on s10 series (that doesn't have the virtual key feature)
marcovittori said:
Nope, d2tw is only on s10 series (that doesn't have the virtual key feature)
Click to expand...
Click to collapse
ok thanks for the info! darn. ahhhh!!
Honest question, why would you need that when there's the soft, pressure-sensitive home button? Doesn't it do the same thing, with one less tap?
because when I'm driving, I could easily wake it up by tapping anywhere on the screen. it's not that simple finding the home screen button when you are driving now that there's no hardware button. I know I shouldn't be touching the phone at all but at times there's still a need to. sure, I can unlock it with google and do some things (and bixby I think but haven't try it yet), but it's not the same as google is waiting for me to tell it to do something.
slamming_sammy1 said:
because when I'm driving, I could easily wake it up by tapping anywhere on the screen. it's not that simple finding the home screen button when you are driving now that there's no hardware button. I know I shouldn't be touching the phone at all but at times there's still a need to. sure, I can unlock it with google and do some things (and bixby I think but haven't try it yet), but it's not the same as google is waiting for me to tell it to do something.
Click to expand...
Click to collapse
I bet a front facing FP comes in handy when driving and phone is on a mount.
Sent from my SM-N960U1 using Tapatalk
marcovittori said:
Nope, d2tw is only on s10 series (that doesn't have the virtual key feature)
Click to expand...
Click to collapse
Limeybastard said:
I bet a front facing FP comes in handy when driving and phone is on a mount.
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
what's a FP ?
slamming_sammy1 said:
what's a FP ?
Click to expand...
Click to collapse
Finger Print sensor.
Sent from my SM-N960U1 using Tapatalk
Limeybastard said:
Finger Print sensor.
Sent from my SM-N960U1 using Tapatalk
Click to expand...
Click to collapse
do these usually work by pressing anywhere on the screen, or needs to press in a certain section of the screen?
slamming_sammy1 said:
because when I'm driving, I could easily wake it up by tapping anywhere on the screen. it's not that simple finding the home screen button when you are driving now that there's no hardware button. I know I shouldn't be touching the phone at all but at times there's still a need to. sure, I can unlock it with google and do some things (and bixby I think but haven't try it yet), but it's not the same as google is waiting for me to tell it to do something.
Click to expand...
Click to collapse
I see. I personally don't think it's tricky to press on the soft home button while driving (it's not that fussy about where you tap), but I use Android Auto while driving so my screen is always on anyway.
Guys, please don't use your phones while you drive.?
djbutter said:
Honest question, why would you need that when there's the soft, pressure-sensitive home button? Doesn't it do the same thing, with one less tap?
Click to expand...
Click to collapse
+1
OP, you could try decreasing sensitivity of the button. Feels just like tapping plus having a dedicated area.
I'd your use case is while driving, a recommend turning on 'Skip Lock Screen' and adding your car's Bluetooth to trusted devices. This way, you need only a tap on the button and you can go directly to the home screen surpassing your lock screen and the need to scan fingerprint.
Also, did you know you can double tap any notification to wake screen. Enabling 'Skip Lock Screen' as mentioned above will route you to the app directly when you double tap it.
Hope this helps.
Sent from my SM-N960F using Tapatalk
Coming from a OnePlus 3T, I do miss DT2W as well. Sitting in a meeting, in a bus, on a plane or in the car - you never have to "search for the right spot", you can just tap on the (dark) screen in order to wake it up.
I really miss it. Once you get used to it, you´re lost.
Hi. There is Fast Wake (not sure about translation, i have another language) by Double Tap options in Accessiblility menu.
slamming_sammy1 said:
I'm still on a Tmobile Note 8 and just got the One UI update today and was so disappointed to find that it doesn't have the 'double tap to wake' feature. I always thought this update would bring this feature. As I walked into a Tmobile store couple weeks ago and confirmed this feature was on a S10 so I thought this update would do it. Anyway, just wanted to know if any of you Note 9 owners who have the One UI update have this feature? if so, that would be awesome, and will get a Note 9 soon; if not, hmmm don't know, will just keep using my Note 8, thanks!!
Click to expand...
Click to collapse
Double Tap on Playstore works perfectly.
No ads, no internet connecting and almost no battery consumption.
Double Tap Off - Apps on Google Play
Double Tap on Home Screen to turn off the screen.Work with fingerprint & MIUI
play.google.com
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
I use a widget called screen tap to lock or something or another for the double tap to sleep on any launcher. Have been using it for a while across a few phones. However when I got the S10 I just started using face unlock due to this slow and clunky FP sensor.....but I've discovered this issue where double tap to sleep with face unlock on makes the phone immediately wake back up to the lock screen for a second unlike pressing the power button which acts correctly. I tested it out on nova's built in settings without the widget (which I was using on one UI launcher) and it does the same thing so obviously it's some sort of conflict with face unlock and double tap to sleep. Anyone know why?
carnivalrejectq said:
I just started using face unlock due to this slow and clunky FP sensor.....
Click to expand...
Click to collapse
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Ripthulhu said:
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Click to expand...
Click to collapse
Oh, I'm on cricket in the US , so still stuck on 9 (with no hope in sight for 10 lol). I've deleted them and reset them a few times now and idk it's just not as fast as I'm used to with capacitive ones, there's an extra second, even compared to the one in the OnePlus 7t I was using for a few days , it cannot compete. It works a lot better if you press hard and firm I guess, but again I'm not used to that. But yeah idk why it's doing that, did it to me on Nova too if I use double tap to sleep at all it immediately opens back up to the lock screen. I don't think it's looking for my face in that scenario either because it doesn't face unlock when it does it, but it definitely IS happening because of the face unlock because it doesn't happen if I turn it off altogether and use the double tap to sleep......if I press the power button to turn the screen off this does not happen.