[Q] Double-tap to wake partially working - Nexus 6 Q&A, Help & Troubleshooting

Hi there,
So I've been running a few rom with different kernels on my N6 in the last month and I noticed that the "double-tap to wake" feature was not always working as expected. Seems like the double tap is not always detected right away and I have to do it several times in order to wake the device.
Some times it will work at first try and some others it won't work at all.
Is there any definitive fix for this behaviour ?

Aanze said:
Hi there,
So I've been running a few rom with different kernels on my N6 in the last month and I noticed that the "double-tap to wake" feature was not always working as expected. Seems like the double tap is not always detected right away and I have to do it several times in order to wake the device.
Some times it will work at first try and some others it won't work at all.
Is there any definitive fix for this behaviour ?
Click to expand...
Click to collapse
Known problem with tap to wake. I use swipe to wake and it works fine.

Thanks for the hint, I'm afraid swep to wake will wake the device in my pocket more easily
But I'll give a shot anyway !

Aanze said:
Hi there,
So I've been running a few rom with different kernels on my N6 in the last month and I noticed that the "double-tap to wake" feature was not always working as expected.
Click to expand...
Click to collapse
You could try a recompiled power.shamu.so.
http://forum.xda-developers.com/showpost.php?p=57770016&postcount=58

NLBeev said:
You could try a recompiled power.shamu.so.
http://forum.xda-developers.com/showpost.php?p=57770016&postcount=58
Click to expand...
Click to collapse
If read the full thread it is still hit and miss and that file may not even be the same .so file for 5.1.1. That zip was made in December for 5.0.2.

prdog1 said:
If read the full thread it is still hit and miss and that file may not even be the same .so file for 5.1.1. That zip was made in December for 5.0.2.
Click to expand...
Click to collapse
I had the same problem and downloaded the attachted zip file shamu_doubletap2wake-s.zip.
After flashing this zip, dt2w works with stock 5.1.1. on my N6 (LMY47Z)
Edit:
and franco's kernel r30

NLBeev said:
You could try a recompiled power.shamu.so.
http://forum.xda-developers.com/showpost.php?p=57770016&postcount=58
Click to expand...
Click to collapse
This is the cause of the issue and I suspect why google didn't release it. Kernel implementation is much better but actually sweep to wake is much safer in the pocket than double tap.

danarama said:
This is the cause of the issue and I suspect why google didn't release it. Kernel implementation is much better but actually sweep to wake is much safer in the pocket than double tap.
Click to expand...
Click to collapse
OK. So I was lucky. Because for me it was a solution for a N6 with stock rom.

NLBeev said:
OK. So I was lucky. Because for me it was a solution for a N6 with stock rom.
Click to expand...
Click to collapse
I use stock rom but custom kernel. Have options for both double tap and sweep to wake.

NLBeev said:
OK. So I was lucky. Because for me it was a solution for a N6 with stock rom.
Click to expand...
Click to collapse
It's unreliable for everyone who uses it, except you maybe? There might be a timing knack to it

danarama said:
It's unreliable for everyone who uses it, except you maybe? There might be a timing knack to it
Click to expand...
Click to collapse
it was more or less reliable for me, too reliable actually. when it got warm around here, i started carrying the phone in my back pocket instead of jacket pocket, and it kept waking in my back pocket. so i disabled double tap to wake, permanently.

simms22 said:
it was more or less reliable for me, too reliable actually. when it got warm around here, i started carrying the phone in my back pocket instead of jacket pocket, and it kept waking in my back pocket. so i disabled double tap to wake, permanently.
Click to expand...
Click to collapse
Yeah between that and ambient display, pocket wake is a huge problem. But for double tapping when you want to wake it up is not as reliable. 50% for some..or 3rd tap not 2nd.

danarama said:
Yeah between that and ambient display, pocket wake is a huge problem. But for double tapping when you want to wake it up is not as reliable. 50% for some..or 3rd tap not 2nd.
Click to expand...
Click to collapse
id say it was about 90-95% reliable here. it might even be a more location where you tap issue (maybe?)

danarama said:
It's unreliable for everyone who uses it, except you maybe? There might be a timing knack to it
Click to expand...
Click to collapse
I've seen several posts about dt2w, and there are issues and solutions, and indeed not always successful.
My dt2w actions were as follows.
I started using an app untill I flashed a custom-kernel. Franco's kernel.
In the kernel settings there is an option to enable dt2w. But enabling had no effect.
Therefore I decided to flash the mentioned power.shamu.so.
Now it works for more than a week.
When there are issues I will post it here.

Works on stock with LeanKernel. Has option for stock dt2w, haptic dt2w, sw2w or both haptic dt2w and sw2w at same time.

simms22 said:
it was more or less reliable for me, too reliable actually. when it got warm around here, i started carrying the phone in my back pocket instead of jacket pocket, and it kept waking in my back pocket. so i disabled double tap to wake, permanently.
Click to expand...
Click to collapse
This is understandable because the screen is touched when you put the N6 in the back pocket. But you have an option to switch it off.
It is different with the magnet sensor.
I was using a belt case (vertical) with a magnetic closure. Every move activates the sensor. Screen is turned on/off frequently.
Solution: another belt case,
EDIT
. . . I hope that in an new Android it will be possible to switch this sensor permanently off.
Because my magnetic car mount is not usable.

Related

[Q] How to disable auto-screen off?

Forgive me if this was answered somewhere else, but I have not been able to find any information anywhere. I am not sure if my search terms are weak or what.
Okay, here is my question. How do I disable the auto-screen off feature? Meaning, when I hold the One in my hand and flick my wrist downward, the screen turns off by itself. I have looked into every setting on the phone but can not find any switch for it.
I am running OneDriod rom (cyanogenMod). I am unsure if the rom is causing this, as I remember it doing the same thing with stock.
Again, if this was answered elsewhere, feel free to delete/lock this thread. I was hesitant to even create this thread.
EvilTrance said:
Forgive me if this was answered somewhere else, but I have not been able to find any information anywhere. I am not sure if my search terms are weak or what.
Okay, here is my question. How do I disable the auto-screen off feature? Meaning, when I hold the One in my hand and flick my wrist downward, the screen turns off by itself. I have looked into every setting on the phone but can not find any switch for it.
I am running OneDriod rom (cyanogenMod). I am unsure if the rom is causing this, as I remember it doing the same thing with stock.
Again, if this was answered elsewhere, feel free to delete/lock this thread. I was hesitant to even create this thread.
Click to expand...
Click to collapse
you must be using tbalden's or neo's kernel for CM11
this feature is called Flick 2 Wake/Sleep
kamilmirza said:
you must be using tbalden's kernel
this feature is called Flick 2 Wake/Sleep
Click to expand...
Click to collapse
Thanks for the reply. I will be honest and say I have no idea if that is what it is. I have seen no reference to it on my phone or in any settings, etc. Though it seems my phone only turns off when I flick my wrist (or any other slight jerking action). However, it does not wake the phone up with a flick, it just turns the screen off. It is super annoying and I can not find the switch to turn it off.
EvilTrance said:
Thanks for the reply. I will be honest and say I have no idea if that is what it is. I have seen no reference to it on my phone or in any settings, etc. Though it seems my phone only turns off when I flick my wrist (or any other slight jerking action). However, it does not wake the phone up with a flick, it just turns the screen off. It is super annoying and I can not find the switch to turn it off.
Click to expand...
Click to collapse
it must be in settings
or you can use Trickster MOD from PlayStore to disable it
kamilmirza said:
it must be in settings
or you can use Trickster MOD from PlayStore to disable it
Click to expand...
Click to collapse
Thanks, that tool seems to be doing the trick. I can not believe this was so hard to figure out. I am normally pretty good at these sorts of things. Thanks again!
EvilTrance said:
I am normally pretty good at these sorts of things
Click to expand...
Click to collapse
lol yeah i can see that

[APP] S2W Phone Call Disabler

S2W Phone Call Disabler
If you have sweep2wake enabled, you may notice the touchscreen is active while the screen is blanked during phone calls. This app will disable sweep2wake and doubletap2wake during phone calls and re-enable them with your previous settings after the call is finished. I couldn't find a way to do it reliably in the kernel, so I made this companion app. It will work with any Nexus 6 kernel that has sweep2wake.
It requires no configuration, just install it, and run it once. After that, it will automatically work, even after rebooting.
There is one option in the app. Since this app only needs to be opened once, you can click a check box that will remove this app from your app drawer. If you change your mind and want it back in the app drawer, you will have to uninstall and reinstall the app.
This app shouldn't use many resources. It runs an intent service when the phone state changes. That means the app wakes up, does its thing, and then stops itself. In other words, it is not always running in the background.
This app requires root!
Download:
S2WPhoneCallDisabler.apk
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Thanks wanted to run your kernel but kept having issues in call.
My so glad to be able to run your kernel been with Vzw m8 for last year... an this app has worked great for me all day. An also I just wanted to throw out I'm on .24 an having zero call issues
3rd!
Works great thanks man
This issue bugs the crap out of me. I'm testing now. Thanks flar.
Nexus 6
I assume it's working good for everyone?
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Ngo93 said:
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Click to expand...
Click to collapse
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Will do!
flar2 said:
I assume it's working good for everyone?
Click to expand...
Click to collapse
You have no idea. This app is pure genius.
Nexus 6
Not sure why but my copy doesn't have the option yo hide from the app drawer.
Great idea for this app, I'm surprised that there isn't greater call for it, or maybe I'm alone in having major screen issues when in a call with 2t2w enabled.
My issue is that it never turns double tap back on after a call. I'm using LK with it set up through lkconfig. Anyone know a solution to this? Thanks
Sent from my Nexus 6 using XDA Premium HD app
In fact I've experienced the same once or twice with ElementalX Kernel. I'm going to observe if it is happening again on my next call.
Edit: Tried it twice, no problems, so false Alarm. Everything working as it should be!
Thanks for the app, Flar2! I wrote a guide for this on my website (here), and also made a video tutorial:
https://www.youtube.com/watch?v=bHjN6jUdgzs
Feel free to use either, and thanks again for the great work!
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
datajosh said:
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah it's been happening a few times over the last couple days, but nothing major.
Nexus 6
Great!
Works perfectly, and removed from the app drawer. Screen is completely unresponsive (as it should be) when on a call with the prox sensor covered.
Thanks for this!
Hey @flar2 ... I think I may have found a sequence that keeps disabling dt2w and s2w. It seems if I get a call and swipe to ignore the call within a second or two that it's disabling those two features, they only come back on after I re-enable them in your ElementalX app.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
I've been getting this behavior lately where it would disable itself but it seems completely random to me.

Making phone calls on this phone is almost impossible

When I make a call or get a call and I use the phone as a phone the screen goes black when I bring the phone to my phone but the screen still responds to touch. So my face touches lots of things like the notificaiton pull down, the mute and pause button in the phone app, I end up opening apps. Then, the phone doesn't turn on when I pull the phone from my face. This is really getting frustrating. How can I fix this? Why is this going on?
Krunk83 said:
When I make a call or get a call and I use the phone as a phone the screen goes black when I bring the phone to my phone but the screen still responds to touch. So my face touches lots of things like the notificaiton pull down, the mute and pause button in the phone app, I end up opening apps. Then, the phone doesn't turn on when I pull the phone from my face. This is really getting frustrating. How can I fix this? Why is this going on?
Click to expand...
Click to collapse
Are you running a custom ROM with double tap to wake? I've read somewhere (can't exactly remember where) that modification is responsible for this behavior. If you want it to not do this, try to disable dtw, look for a ROM without this option, or return to stock.
cam30era said:
Are you running a custom ROM with double tap to wake? I've read somewhere (can't exactly remember where) that modification is responsible for this behavior. If you want it to not do this, try to disable dtw, look for a ROM without this option, or return to stock.
Click to expand...
Click to collapse
@flar2 wrote an app to disable this during a call whilst his dt2w is enabled in elementalx
cam30era said:
Are you running a custom ROM with double tap to wake? I've read somewhere (can't exactly remember where) that modification is responsible for this behavior. If you want it to not do this, try to disable dtw, look for a ROM without this option, or return to stock.
Click to expand...
Click to collapse
rootSU said:
@flar2 wrote an app to disable this during a call whilst his dt2w is enabled in elementalx
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/themes-apps/app-s2w-phone-call-disabler-t3018512
cam30era said:
Are you running a custom ROM with double tap to wake? I've read somewhere (can't exactly remember where) that modification is responsible for this behavior. If you want it to not do this, try to disable dtw, look for a ROM without this option, or return to stock.
Click to expand...
Click to collapse
Interesting.
Nexus 6
rootSU said:
@flar2 wrote an app to disable this during a call whilst his dt2w is enabled in elementalx
Click to expand...
Click to collapse
simms22 said:
http://forum.xda-developers.com/nexus-6/themes-apps/app-s2w-phone-call-disabler-t3018512
Click to expand...
Click to collapse
Thank you guys so much. Can't wait to try this out. Great stuff.
Nexus 6

Underdisplay fingerprint

When you move the phone slightly the underdisplay fingerprint glows, can anybody tell me how to turn it off? I want it to goow only when I press on the phone, is this possible?
Doesn't seem so, as it's the only way to know where to put your finger.
It seems to be implemented at the "hardware level".
I'd you mean the fingerprint icon that shows up when you pick the phone up, you can't disable it currently.
Ahmad Shawawreh said:
When you move the phone slightly the underdisplay fingerprint glows, can anybody tell me how to turn it off? I want it to goow only when I press on the phone, is this possible?
Click to expand...
Click to collapse
RedWave31 said:
Doesn't seem so, as it's the only way to know where to put your finger.
It seems to be implemented at the "hardware level".
Click to expand...
Click to collapse
Mohammed779 said:
I'd you mean the fingerprint icon that shows up when you pick the phone up, you can't disable it currently.
Click to expand...
Click to collapse
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
cd993 said:
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
Click to expand...
Click to collapse
Damn, i might flash this rom just for this feature, it's super annoying at night, and it keep activating the screen in my pocket.
Can you flash it over the global rom, or does it require a wipe? (probably..)
Gokh said:
Damn, i might flash this rom just for this feature, it's super annoying at night, and it keep activating the screen in my pocket.
Can you flash it over the global rom, or does it require a wipe? (probably..)
Click to expand...
Click to collapse
Hmm given the rom is different, I'd say you may run into issues. But with that said, worth a shot! If dirty flashing, perhaps wipe system and the caches, then flash rom and magisk (if rooting), and keep those fingers crossed!
Any issues then yeah do a clean install
RedWave31 said:
Doesn't seem so, as it's the only way to know where to put your finger.
It seems to be implemented at the "hardware level".
Click to expand...
Click to collapse
Does seem somewhat like this because if that and the ambient display is disabled, the fingerprint doesn't respond from screen off. But if that and/or ambient display is enabled, it works. But at least something has to be turned on keeping at least some part of the screen awake.
I chose to enable ambient but disable fingerprint icon because ambient goes around the whole screen giving me peace of mind from burn in unlike the icon
Sent from my Xiaomi MI 9 using XDA Labs
cd993 said:
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
Click to expand...
Click to collapse
I'm running on the global room not the EU one
Would you recommend me installing the EU room?
I like everything about the phone, but if they would tweak the SOT usage
Ahmad Shawawreh said:
I'm running on the global room not the EU one
Would you recommend me installing the EU room?
I like everything about the phone, but if they would tweak the SOT usage
Click to expand...
Click to collapse
Yeah I recommend the weekly EU roms for sure. I've not tried the global ones, but this EU one is great, with weekly updates and great features. Definitely worth a try!
Check my battery thread on the Discussion area on XDA for my battery saving tips
cd993 said:
OP, which firmware are you running? I'm on EU rom and there used to be a bug, which resulted in being a workaround to disable the fingerprint icon.
However now there is a dedicated setting, see attached, which allows turning off the icon
Click to expand...
Click to collapse
Ohhh man, I have been looking to switch this annoying feature off for ages and you just showed me how to do it. Awesome and thank you
perryano said:
Ohhh man, I have been looking to switch this annoying feature off for ages and you just showed me how to do it. Awesome and thank you
Click to expand...
Click to collapse
You're welcome!

Touch response delay when waking up the phone

I've got the 8gb/128gb version of the phone the last weekend. I'm having this issue where the phone is not responsive to the touch for about 1~2 seconds after I wake it up (either by double-tapping the screen or pressing the power button).
This happens after the screen is off for a few minutes (even if playing music in Soundcloud/Youtube Vanced). It'd turn on the screen but I can't interact with the screen right away.
I used to have a similar problem with my Razer Phone 1 and it happened whenever I tried to hide the navigation bar or use a different navbar/gestures. I have gestures enabled in the ROG 2, but not sure if it's related. Also, I think it came with WW ROM, I don't know if that'd matter.
I'd really appreciate any input from you guys on how to solve this. Thanks
el4nimal said:
I've got the 8gb/128gb version of the phone the last weekend. I'm having this issue where the phone is not responsive to the touch for about 1~2 seconds after I wake it up (either by double-tapping the screen or pressing the power button).
This happens after the screen is off for a few minutes (even if playing music in Soundcloud/Youtube Vanced). It'd turn on the screen but I can't interact with the screen right away.
I used to have a similar problem with my Razer Phone 1 and it happened whenever I tried to hide the navigation bar or use a different navbar/gestures. I have gestures enabled in the ROG 2, but not sure if it's related. Also, I think it came with WW ROM, I don't know if that'd matter.
I'd really appreciate any input from you guys on how to solve this. Thanks
Click to expand...
Click to collapse
I've got same phone on the latest ww rom (there's an update, might help) and haven't seen this yet. So you use double tap to wake? Any screen off gestures? Would be interesting to figure out which feature is misbehaving
xxBrun0xx said:
I've got same phone on the latest ww rom (there's an update, might help) and haven't seen this yet. So you use double tap to wake? Any screen off gestures? Would be interesting to figure out which feature is misbehaving
Click to expand...
Click to collapse
It doesn't show any new update when I check. I believe it's because I dont have the CN ROM. Yes I do use double tap to wake. I will disable it and use it during a day to see if it change. If not, I'll try using the navbar instead of gestures. I haven't set up any screen off gesture. I'll report back if I find something
el4nimal said:
It doesn't show any new update when I check. I believe it's because I dont have the CN ROM. Yes I do use double tap to wake. I will disable it and use it during a day to see if it change. If not, I'll try using the navbar instead of gestures. I haven't set up any screen off gesture. I'll report back if I find something
Click to expand...
Click to collapse
This also happened to me when I converted to WW ROM, and to many others as well. It affected my gaming experience so much so I converted back to CN ROM. I will be using the CN ROM until this problem is fixed.
Guys can u tell me where to set the double tap to wake the phone? Thanks
Found it. Dang all this time I didn't know this exist
Nb I tried using it and my phone is working great and fast. I'm using ten cent version.
It has nothing to do with what I mentioned. I think I'll reset my phone or convert it to the CN Rom
I have the same issue unfortunately - A 1 second delay when I tap to wake (screen kinda just freezes for a split second then turns responsive again).
Not a big deal, but wondering what is the issue.
Enigmatic331 said:
I have the same issue unfortunately - A 1 second delay when I tap to wake (screen kinda just freezes for a split second then turns responsive again).
Not a big deal, but wondering what is the issue.
Click to expand...
Click to collapse
I still have the same issue. I went from WW rom to CN rom, but it did not fix that issue. Most of the time does not happen, but sometimes it can freeze up to 5 seconds, which can get quite annoying
el4nimal said:
I still have the same issue. I went from WW rom to CN rom, but it did not fix that issue. Most of the time does not happen, but sometimes it can freeze up to 5 seconds, which can get quite annoying
Click to expand...
Click to collapse
Mmm. Hey, I am currently on Android 10, and the problem seemingly is gone (actually it kinda looks like there's a split second animation which makes the delay unnoticeable) - Give that a try to see if it helps?
5 seconds is horrible!
Enigmatic331 said:
Mmm. Hey, I am currently on Android 10, and the problem seemingly is gone (actually it kinda looks like there's a split second animation which makes the delay unnoticeable) - Give that a try to see if it helps?
5 seconds is horrible!
Click to expand...
Click to collapse
Im not sure about going to Android 10, is it still a beta right? The issue disappeared for me the first days when I changed to CN rom, but it came back a couple of days later :/
To update - Am on Beta 6 - So far so good. The problem hasn't come back yet. Only catch is double tapping is a slight bit less sensitive than before.
Once the official Android 10 release is out, hopefully that would sort you out for good!

Categories

Resources