Database Users

[Q] Alternative ways to turn screen on/off

Hi all,
I'm wondering if there's any alternative ways to put the Nexus 7 (or any Android device I guess) to sleep/wake it up. I'm thinking something along the lines of an app that forces the touch screen to stay active but turns the display off so you can use touch input to activate wake/sleep.
Might be a bit of a stupid question. The reason I ask is because my N7 is mounted in my car and the power button isn't easily accessible.
Cheers for any tips..

UnitedWeFall said:
Hi all,
I'm wondering if there's any alternative ways to put the Nexus 7 (or any Android device I guess) to sleep/wake it up. I'm thinking something along the lines of an app that forces the touch screen to stay active but turns the display off so you can use touch input to activate wake/sleep.
Might be a bit of a stupid question. The reason I ask is because my N7 is mounted in my car and the power button isn't easily accessible.
Cheers for any tips..
Click to expand...
Click to collapse
Not sure if this helps but I have a case that I bought for my N7 and when I open it and close it the screen turns on and off.
Here it is http://www.amazon.com/gp/product/B0...ASIN=B008D2POAS&linkCode=as2&tag=newyormus-20

MineralGray02K said:
Not sure if this helps but I have a case that I bought for my N7 and when I open it and close it the screen turns on and off.
Here it is http://www.amazon.com/gp/product/B0...ASIN=B008D2POAS&linkCode=as2&tag=newyormus-20
Click to expand...
Click to collapse
Thanks for that but nah, it's mounted in my car dash so a case won't fit..
But that give me an idea.. does sliding a magnet across a specific point on the screen turn it on/off? That's the idea with the smart cases right?

UnitedWeFall said:
Thanks for that but nah, it's mounted in my car dash so a case won't fit..
But that give me an idea.. does sliding a magnet across a specific point on the screen turn it on/off? That's the idea with the smart cases right?
Click to expand...
Click to collapse
Yes,
The magnet is somewhere to the bottom left of the device (i would say to about a quarter from bottom up and on the black contour) . If you can add an sliding magnet (make sure is weak) then you can lock/unlock screen.

Nfc tags dude i wonder if they would work
Sent from my Nexus 7 using Tapatalk 2

I know some kernels can enable touch wake. I imagine it can incorporated soon. On my Galaxy Nexus, there's an app I downloaded that allowed a specific screen swipe to wake the screen.
Sent from my Galaxy Nexus using Tapatalk 2

wyattyoss said:
On my Galaxy Nexus, there's an app I downloaded that allowed a specific screen swipe to wake the screen.
Click to expand...
Click to collapse
What was the app?
Sent from the third Galaxy on the left.

That would be awesome. Do you remember the name of the app?

Gesture Control?

UnitedWeFall said:
Hi all,
I'm wondering if there's any alternative ways to put the Nexus 7 (or any Android device I guess) to sleep/wake it up. I'm thinking something along the lines of an app that forces the touch screen to stay active but turns the display off so you can use touch input to activate wake/sleep.
Might be a bit of a stupid question. The reason I ask is because my N7 is mounted in my car and the power button isn't easily accessible.
Cheers for any tips..
Click to expand...
Click to collapse
Hey man. I used to have an awesome app on my very first Android tab years ago. It would turn the screen completely black (via home screen or notification icon) without actually putting it to sleep. Because it wasn't really asleep, a double tab would turn the screen back on. I CANNOT FIND IT FOR THE LIFE OF ME! Anyway, after reading your question, I searched for an hour, because I could use something like this for my setup in my car.
So, I found something that turns the screen both on and off, and actually works on my N7. Search for Proximity Screen Off. I installed the free lite version, and it works. I found out the screen won't turn on though, unless you disable your lock screen. Play with the settings to your liking.
Oh, and since we don't have prox sensors, you can use your ambient light sensor. Good luck, lmk if it works for ya.

joelhon said:
What was the app?
Sent from the third Galaxy on the left.
Click to expand...
Click to collapse
It's called PGM Nexus. I almost don't want to give up my Galaxy Nexus (but I sadly still plan to) just because of this one app alone...it is so godawful nice to be able to swipe, or simply double tap the screen to fire up the screen. Unfortunately this app apparently requires some deep voodoo to work as its kernel related, and applies strictly to the Galaxy Nexus. I know a bunch of people have already started bugging the developer to make a version for the Nexus 7, I'd suggest piling on. :fingers-crossed:
It's apps like these that make you realize how superior the Nexus devices are at getting really good customized software over other devices.
I do wish there were some other options for the Nexus 7, like using the front camera as a proximity sensor of sorts to detect a handwave, or simply shaking the tablet.

jaycustom said:
Hey man. I used to have an awesome app on my very first Android tab years ago. It would turn the screen completely black (via home screen or notification icon) without actually putting it to sleep. Because it wasn't really asleep, a double tab would turn the screen back on. I CANNOT FIND IT FOR THE LIFE OF ME! Anyway, after reading your question, I searched for an hour, because I could use something like this for my setup in my car.
So, I found something that turns the screen both on and off, and actually works on my N7. Search for Proximity Screen Off. I installed the free lite version, and it works. I found out the screen won't turn on though, unless you disable your lock screen. Play with the settings to your liking.
Oh, and since we don't have prox sensors, you can use your ambient light sensor. Good luck, lmk if it works for ya.
Click to expand...
Click to collapse
Thanks for that! Appreciate it. I'll give it a try when I get home after work and report back.

jaycustom said:
Hey man. I used to have an awesome app on my very first Android tab years ago. It would turn the screen completely black (via home screen or notification icon) without actually putting it to sleep. Because it wasn't really asleep, a double tab would turn the screen back on. I CANNOT FIND IT FOR THE LIFE OF ME! Anyway, after reading your question, I searched for an hour, because I could use something like this for my setup in my car.
So, I found something that turns the screen both on and off, and actually works on my N7. Search for Proximity Screen Off. I installed the free lite version, and it works. I found out the screen won't turn on though, unless you disable your lock screen. Play with the settings to your liking.
Oh, and since we don't have prox sensors, you can use your ambient light sensor. Good luck, lmk if it works for ya.
Click to expand...
Click to collapse
Could you please post the settings you are using? Specifically the light sensor settings. I am having trouble getting this to work properly. Thanks!

Screen Off
gtdRR said:
Could you please post the settings you are using? Specifically the light sensor settings. I am having trouble getting this to work properly. Thanks!
Click to expand...
Click to collapse
Hello. I'm not sure if it helps you, but for turning off screen I use Nova Launcer (alternatively you could use Apex Launcher - as far as I remember, it has gestures in its free version) with Screen Off app by Katecca. I've set Nova Launcher to react to swiping up screen by executing Screen Off app. So I have to turn on screen by pressing button, but to turn off I just swipe up screen.
Best regards,
Artur

Added support for nexus 7 to ProximityScreenOffPro v6.0
https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoffpro

[Q] Proximity Sensor Fails

Just wanna ask if there is any temporary fix to the proximity sensor of nexus 4.
During calls the screen doesn't turn off when placed close to the face.
I didn't get the chance to test it on stock 4.2 because when i turned my phone on it updated first to 4.2.1. Ever since then it has had proximity sensor not working during calls.
And i have never had any screen protectors on the screen.
Tried many custom ROMS as well but no difference at all.
Sent from my Nexus 4 using xda premium

how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken

I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.

isnt there a proximity senor app which lets you test it on the market?

dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
Click to expand...
Click to collapse
Using stock. No issues on the sensor. Turns off on calls and turns on when I remove from the face. Have a spigen protector on with a cutout for it
Sent from my Nexus 4 using Tapatalk 2

dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
Click to expand...
Click to collapse
I was on stock 2 weeks ago when I started noticing it.
I am on cm now as well and its very much messed up.
Sent from my Nexus 4 using xda premium

bobola said:
isnt there a proximity senor app which lets you test it on the market?
Click to expand...
Click to collapse
There is.
I've installed and tested.
According to the app results, The proximity sensor seems to know when my hand is on it and when its off it. The value changes from 1.0 to 2.0
It just won't work on phone calls.
Sent from my Nexus 4 using xda premium

noobdeagle said:
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
Click to expand...
Click to collapse
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium

slimldj said:
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mine is stock and during calls it usually goes to my settings menu and changes my clock setting. When I get off the phone, screen is blank and I hit power button to end call. Still annoying at times when the clock changes.

any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.

feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium

feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I'm suffering this same problem too, hope they fix it soon..

slimldj said:
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes I think the fact that the app testing showed the sensor working so it points to software. Something is missing when the phone is in a call its not connecting to turn off. I thing Jellybean was flawed in many ways. My drop down brightness slider doesn't work for me nor auto brightness its OK for me cause I don't use either but still makes me mad.
Using Tapatalk 2

meetoo
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.

treaty said:
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
Click to expand...
Click to collapse
Having the exact same issue here too on stock ROM.
Good idea on the accessibility settings! Will work until/if they fix it..
Also no screen protector.

I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.

Dav_prime said:
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Click to expand...
Click to collapse
It was the same fix for mine when I first got my bse it worked fine for about a week but then over time it got worse. It was the screen protector just that lil bit worth of it wear caused enough blockage of the sensor. I got some new bse's and they now have a cutout for the proximity sensor and are screen optimized.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2

use Proximity Actions by Novum Inceptum in playstore

rat99 said:
use Proximity Actions by Novum Inceptum in playstore
Click to expand...
Click to collapse
That won't fix anything.

Knock knock not as responsive waking up...

Sometimes I have to knock knock twice in a row to turn on the device. It works well turning off, but on half of the times it won't turn on. Gotta do it twice. Anyone else encounter this?
Sent from my LG-D803 using Tapatalk 4

Brava27 said:
Sometimes I have to knock knock twice in a row to turn on the device. It works well turning off, but on half of the times it won't turn on. Gotta do it twice. Anyone else encounter this?
Sent from my LG-D803 using Tapatalk 4
Click to expand...
Click to collapse
I do not have that issue, but I have read in a few posts that it can be dependent on where you are knocking on the screen.

hd-renegade said:
I do not have that issue, but I have read in a few posts that it can be dependent on where you are knocking on the screen.
Click to expand...
Click to collapse
Yes! Excellent advice
Sent from my LG-D803 using Tapatalk 4

Brava27 said:
Yes! Excellent advice
Sent from my LG-D803 using Tapatalk 4
Click to expand...
Click to collapse
I think the biggest issue is knock speed.... mine works damn near 100% when I slowed down some, and knock slower like it showes at the end of the G2 commercials....

I think it's partially related to the proximity sensor. There are times when I can't get the knock on to work at all and when I hit the power button the screen shuts right back off.
Usually a few swipes over the sensor makes it work again. Sometimes I'll go in and turn the Knock On gesture off and back on and then it seems to work great for a while too.

csmith8507 said:
I think it's partially related to the proximity sensor. There are times when I can't get the knock on to work at all and when I hit the power button the screen shuts right back off.
Usually a few swipes over the sensor makes it work again. Sometimes I'll go in and turn the Knock On gesture off and back on and then it seems to work great for a while too.
Click to expand...
Click to collapse
This is my exact problem. The phone just decides it doesn't want to wake up with knock-on...but after I press the power button, it only turns on for half a second and it's out again. I never tried swiping over the sensor, but hopefully it works because it's mighty annoying when it does it during a call!
I wonder if there's a fix for this?

canecbr600 said:
I think the biggest issue is knock speed.... mine works damn near 100% when I slowed down some, and knock slower like it showes at the end of the G2 commercials....
Click to expand...
Click to collapse
this, if you are trying to do it like you did on the nokia n9 or nokia 8800 then it won't work
slow deliberate knocks are the only way
waiting on the g2 to arrive, but on my review unit, knock knock wouldn't respond correctly if i left the phone on the table, but if i picked it up, it would work nothing scientific here just an experience of one person and one prototype

I had the same issue... What fixed it is: 1. I found that the screen protector was hindering it somewhat. 2. Go to settings->display->screen-off effect-> and change it to simple. This REALLY seemed to help. Let us know!

in_dmand said:
I had the same issue... What fixed it is: 1. I found that the screen protector was hindering it somewhat. 2. Go to settings->display->screen-off effect-> and change it to simple. This REALLY seemed to help. Let us know!
Click to expand...
Click to collapse
I did notice it does seem to behave better when set to simple for the screen off animation.
My screen protector does have a cutout around the sensors. Keeping the sensor area clean enough to qualify as having OCD does seem to make it work properly the first time, every time. Maybe it's overly sensitive?
Edit: Scratch that. 30 seconds later it's behaving erratically again. Maybe it's not the fact that it's clean, but the swiping over the sensor that temporarily resolves it.

it also seems to work much better when knocking at the top of the screen where the statusbar would be.

So I ended up swapping the phone out over the weekend for a new one and now everything seems to work just fine. Seems to indicate that it's not a software problem, but rather a hardware issue with the proximity sensor.

Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.

Walter21026 said:
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Click to expand...
Click to collapse
This is true however there are indications of problems with the proximity sensor as well. Some of the devices are behaving as if tree sensor is covered even when it's not.

Walter21026 said:
Guys if your covering the sensors when turing the device screen on it will turn right back of on you. It's a feature LG implemented so the device wouldnt wake up in your pockets. Don't cover the sensors.
Need a little example? Grab your phone and cover the sensors and knock knock knock.You can knock till the cows come home but it will not turn on. Same thing goes for the power button but its a little delayed and will turn the screen on for half a sec and turn right back off. Practice not to do this because your phone isn't broken. There is actually a thread on this deep in the forums somewhere but its been forgotten now.
Click to expand...
Click to collapse
Thanks for this.. Very insightful.. I tried it immediately LOL

I had the same issue. I have no case or screen protector on, and was not covering the sensor when trying to wake the phone. For some reason though, knocking wouldn't wake the phone, and pressing the power button would only turn the screen on for a few seconds. I want even given enough time to get past the unlock screen. I went into the store and they are sending me a replacement that should come in later this week. It doesn't happen all the time. It is much more noticeable after receiving a call though.
Sent from my VS980 4G using Tapatalk

Definitely is dependent on the proximity sensor. If i just have my thumb on the edge of the phone by the sensor it will display this problem. Even with my finger a half to one inch above it will do this. I will be paying close attention to the proximity sensor from now on when it doesn't work. Still have a few days to return and thought i had an issue but maybe not.
Sent from my VS980 4G using xda app-developers app

sometimes its also greasy fingers, at least in my case, rarely though

As long as you tap twice the same place it's working fine. If distance between first and second tap is greater than 1 - 1.5 cm it won't work.

Got the same problem on my d802...when i left the phone on my table for 2-3min it wont wake up on first knock knock even power key wake it up for 1sec after auto turn off again....even with no screen protector....i noticed that sometimes there is a delay about 5-10sec after knock knock and screen turns on....other thing i noticed when i knock on immediently after turning off it works 100%....BUT i also noticed when i knock on after a while it turns on and i can unlock got vibration and sound of the unlock but i cant see anything. Screen looks like its off but when i look closely i can hardly see widgets and when i set effect to tv out i can see the effect by pressing the power button...when i press the power button again screen turns on like normal...i noticed sometimes on a rerboot the lg bootlogo disapears the led is working an showing all colors but the boot animation is gone like the screen is off at the bootup...dont know why after the bootup the pin lock screen is showing up normal....sorry for my english^^

Help: Camera turns on in my pocket.

I'm using the default screen lock, with swiping, and it happened 2 times in the last 3 days, that my camera was turned on, in my pocket. (The phone is in a leather pouch)
is there a way, to disable the camera on the lockscreen (swipe left)?

It´s not the lock screen. It´s because of volume buttons. If you hold it pressed for some time volume up starts quick memo and volume down starts the camera. I have the same problem: phone carried in a pouch. I wonder if there is a way to disable it since I don´t really use quick keys.

I've never had this issue in the past week and half that I've had this phone without any case on.
The back volume rocker buttons are definitely getting pressed if your camera is turning on. When you put the phone in your pocket, do you put the camera facing towards you or away?

Mine is doing the same, actually. Yesterday I logged into my Google Plus page and saw there were new photos uploaded, ready for review. There were 8 or so pictures taken inside my pocket.

I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?

Klotar said:
I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Click to expand...
Click to collapse
You're right! I completely forgot about that.
I think the proximity sensor (located between front camera and the earpiece) should prevent the camera from turning on and I just did a quick test.
Phone in hand, pressing volume down rocker results in the camera turning on. This is normal.
To simulate phone in pocket, I took a shirt and used 1 layer to cover the proximity sensor and then pressed the volume down rocker. The phone did not turn on.
Quick easy test, took 10 seconds, give it a try to see if your camera still turns on. If not, something else other than the volume down rocker is turning on your phone.

This might be a stretch, but I've noticed the phone turns on by itself sometimes when putting it down on the desk. I'm thinking it's picking up a double-knock signal some how in the pocket and further movements cause the lock screen to slide to the right (which is the camera).

I would have thought that the proximity sensor would immediately put the device back to sleep if the camera was turned on inadvertently while holstered or pocketed...?
Click to expand...
Click to collapse
I can confirm this is not accurate. I put my g2 in my pocket and launched the camera with the vol down action, and it loaded.. Multiple times.
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Sent from my LG-LS980 using xda-developers app

bearsblack said:
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Click to expand...
Click to collapse
I don't think so. I'm on T-Mobile, and while I rooted my phone last night, I had the issue prior to rooting.

bearsblack said:
I can confirm this is not accurate. I put my g2 in my pocket and launched the camera with the vol down action, and it loaded.. Multiple times.
However I'm on the sprint g2 and removed a bunch of junk I didn't think I'd need so I could have deleted something that would prevent the phone from waking if the proximity sensor was tripping. Maybe?
Sent from my LG-LS980 using xda-developers app
Click to expand...
Click to collapse
Cover the proximity sensor and hold down the volume down rocker button to see if it goes to the camera app.
I tried it about 8-10x and during that time, the phone never goes to the camera app if the proximity sensor is covered.

yyz123 said:
Cover the proximity sensor and hold down the volume down rocker button to see if it goes to the camera app.
I tried it about 8-10x and during that time, the phone never goes to the camera app if the proximity sensor is covered.
Click to expand...
Click to collapse
Obviously lol... But nope.. Still loading the the camera with sensors covered. I'm not too worried about it tho. I haven't unlocked this phone in my pocket yet. Even with knock on active.
Sent from my LG-LS980

I have the T-mo one and I keep getting the camera and quick notes opening. It's super annoying. I have recently turned my phone arround, now the screen faces outward. It seems to be helping, I have not had it happen since.

Stop wearing your girlfriends pants
Sent from my LG-D803 using XDA Premium 4 mobile app

Must be some thin ass pants. Never once had happened to me. Proximity cover still lets cam launch.

xdafoundingmember said:
Stop wearing your girlfriends pants
Sent from my LG-D803 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol... I wish it was that easy.
I wear black 5.11 tactical pants everyday at work that have plenty of room and I have this issue.

did anybody find a way to turn the Vol Up/Down functions on lockscreen off?

I reckon an Xposed mod could help you with that.

I have been having the same problem and yesterday deleted 17 photos taken from inside my pocket in the last 2 days while I was at work. I have no case on the phone at the moment and I am not rooted.
Sent from my VS980 4G using xda app-developers app

I had the exact same problem when I first got this phone. Had no idea the camera was on until I felt my phone extremely hot in my pants. A case solved that problem for me.

robogo1982 said:
I reckon an Xposed mod could help you with that.
Click to expand...
Click to collapse
strangely enough, it lets you control the Vol keys only for the screen off (which would help everybody in this thread, yes) but i'm also looking to disable it for the lockscreen.

Tap to Wake issues

Hey, guys. I'm a huge fan of this phone.. I can't get over what a good value it is for the money. I have almost zero issues with it. The one issue I do have is the inconsistency with tap to wake. It seems like after it has been in my pocket for a while, it just fails to work. This happens periodically throughout the day, to the point where I just can't rely on it. It drives me mad because that's kind of a must have feature for me. To be fair, the only device I have never had tap to wake issues with is LG phones. They just seem to work all the time.
I did raise the sensitivity following the guide found on these forums. It's something else, like the pocket protection is stuck on or something. Anyone else experience something similar? I don't want to use the fingerprint reader. Is there something I don't know? Some setting I'm not seeing? Or is this just how it is?
Still a great phone otherwise. I wish I could fix this one little thing.

Is your screen clean or dirty? Have you tried wiping it down with 70% isopropyl alcohol and seeing if that improves the responsiveness. Is the phone hot when it's not responding? Are your fingers dirty?

It's not very sensitive, you definitely need to give it a couple of thumps unlike the taps on an LG phone.
There's a learning curve with this phone. I nearly dislocated my shoulder trying to shake the flashlight awake before I realized you had to wake the screen first

ludovicien said:
It's not very sensitive, you definitely need to give it a couple of thumps unlike the taps on an LG phone.
There's a learning curve with this phone. I nearly dislocated my shoulder trying to shake the flashlight awake before I realized you had to wake the screen first
Click to expand...
Click to collapse
I mean, this only happens when I take it out of my pocket. Tap to wake works fine the rest of the time and my screen is definitely clean.
Sent from my ZTE A2017U using Tapatalk

greyhulk said:
I mean, this only happens when I take it out of my pocket. Tap to wake works fine the rest of the time and my screen is definitely clean.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I'm coming from an lg phone as well, I have found the taps must be slower. The pause between taps needs to be just a little longer and it works for me almost every time.

Double tap to wake doesn't work when the phone has gone into doze mode. ZTE knows about this issue and is working on a fix.

xxBrun0xx said:
Double tap to wake doesn't work when the phone has gone into doze mode. ZTE knows about this issue and is working on a fix.
Click to expand...
Click to collapse
That actually explains a lot. Thanks!
Doze seems to break a lot, including notifications on other phones.
Sent from my ZTE A2017U using Tapatalk

greyhulk said:
That actually explains a lot. Thanks!
Doze seems to break a lot, including notifications on other phones.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
The doze should not kick in if the phone is moving. One of the conditions is that phone should be static for a while. More likely it's something based on proximity sensor to prevent accidental turn ons. I found that i would have to tap several times to wake it up most time i have to do it twice. The force touch is buggy
Sent from my shieldtablet using XDA-Developers mobile app

peramikic said:
The doze should not kick in if the phone is moving. One of the conditions is that phone should be static for a while. More likely it's something based on proximity sensor to prevent accidental turn ons. I found that i would have to tap several times to wake it up most time i have to do it twice. The force touch is buggy
Sent from my shieldtablet using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, I haven't had any issues since I disabled doze and I doubt that's a coincidence.
I agree that doze shouldn't kick on in your pocket, which is why I originally suspected the proximity sensor, but it could be a bug in ZTE's ROM.
My Mate 8 had a malfunctioning doze mode that would cause all notifications to stop as soon as the screen went off, even if the phone was moving. I fixed that by disabling doze also.
Sent from my ZTE A2017U using Tapatalk

The same issue I'm having on both colors I'm having .
Most of the time when picking the device from my jeans pocket refuses to open with double tap even after several attempts.
I have to unlock by pressing with power button and then when holding my phone it stating to work fine.
It's really annoying and frustrating.
Only double tap to sleep with nova prime or 3D next launcher working 100% perfect in all situations from home screen.
Also I'm using glimpse notification and enable the option to double tap to sleep from lock screen and works perfect all time.
Another feature having is it wakes up the screen automatically every time having notification alert and after screen being off continuous the led to be on as a reminder.
Sent from my iPad Air 2

So, I was wrong. Disabling doze didn't fix it. I went back to my OnePlus 3 for a day to get perspective. That phone pretty much never misses a tap-to-wake. It just works. Conversely, the Axon regularly "goes to sleep" when it's in my pocket and I can tap on the screen as many times as I want and it will never come on until I hit the power button. It's definitely not working like it should, at least not for me.
I'm not sure how anyone can say that it's working fine. I like everything else about the phone. This is just annoying because I can't rely on using tap-to-wake. I spend more time tapping on the screen when it's not working than I would if it just didn't have the feature and I had to use other methods. If ZTE could fix this to work as reliably as an LG or the OnePlus 3, I'd be in heaven.

greyhulk said:
So, I was wrong. Disabling doze didn't fix it. I went back to my OnePlus 3 for a day to get perspective. That phone pretty much never misses a tap-to-wake. It just works. Conversely, the Axon regularly "goes to sleep" when it's in my pocket and I can tap on the screen as many times as I want and it will never come on until I hit the power button. It's definitely not working like it should, at least not for me.
I'm not sure how anyone can say that it's working fine. I like everything else about the phone. This is just annoying because I can't rely on using tap-to-wake. I spend more time tapping on the screen when it's not working than I would if it just didn't have the feature and I had to use other methods. If ZTE could fix this to work as reliably as an LG or the OnePlus 3, I'd be in heaven.
Click to expand...
Click to collapse
Totally agree.
Hope ZTE makes improvements on that very useful feature to become just like LG.
Sent from my iPad Air 2