Since upgrading to OOS 4.1.6, when leaving the device asleep for awhile, the display will not want to turn back on. The phone will vibrate for double-tap or fingerprint, however I have to wait about 10 seconds for the screen to actually turn on reguardless if using power button, double tap, or fingerprint.
- I have tried pocket mode both off/on did not work
Badd_blood said:
Since upgrading to OOS 4.1.6, when leaving the device asleep for awhile, the display will not want to turn back on. The phone will vibrate for double-tap or fingerprint, however I have to wait about 10 seconds for the screen to actually turn on reguardless if using power button, double tap, or fingerprint.
- I have tried pocket mode both off/on did not work
Click to expand...
Click to collapse
Reboot?
Puddi_Puddin said:
Reboot?
Click to expand...
Click to collapse
Of course I rebooted already, that's the most obvious first troubleshooting step. I've now uninstalled Greenify since it's the only thing I can think of that has a screen lock feature so I'm trying that now.
Badd_blood said:
Of course I rebooted already, that's the most obvious first troubleshooting step. I've now uninstalled Greenify since it's the only thing I can think of that has a screen lock feature so I'm trying that now.
Click to expand...
Click to collapse
Naptime / Force Doze can be an issue. Especially if your screen is off for a longer period of time. With Naptime you can disable the fact that it will stop your sensors. Might be worth to check out!
The issue seems to be gone after uninstalling greenify. If anyone else has this issue I suggest trying that. I'm not sure if it's a greenify bug I had or because my very dirty flash from OOS 4.1.3 -> 4.1.6. I had many freezing boots and flashed it almost 10 times before it worked.
Related
I've been having an odd problem for the last few weeks. Randomly upon turning on the phone from sleep, the screen stops responding to all touch. It will stay at the lockscreen, the time and everything changes (so the phone hasn't frozen), but whether im poking or dragging there is no response. Double tap 2 wake also does not function in this situation.
I have to adb reboot to get the phone into a working state after, and am worried about this happening when I'm away from my computer. I haven't really seen any pattern to it thus far. I'm on bonestock ROM with obone kernel (doubletap2wake and logo2menu enabled). any ideas?
Are you under clocked or under volted?
cesium said:
obone kernel (doubletap2wake and logo2menu enabled)
Click to expand...
Click to collapse
That could be the problem - both tweaks rely on the touch screen driver and double-tap activates it during deep sleep. See if it goes away after you disable them.
cmlusco said:
Are you under clocked or under volted?
Click to expand...
Click to collapse
Nope I just dropped the top clocks from 2.1ghz to 1.7ghz
wireroid said:
That could be the problem - both tweaks rely on the touch screen driver and double-tap activates it during deep sleep. See if it goes away after you disable them.
Click to expand...
Click to collapse
Yeah that's my thinking, I'll disable it and see what happens
Mine does that every once in a while. Just hold the power button until it reboots.
Sent from the One and Only
Why does doubletap2wake randomly stop working? It has nothing to do with phone being idle, still doesn't work after movement, have to unlock to get it back to work again.
Is this because of deep sleep or power saving mode enabled in sense?
Is my M8 defective - is this a hardware issue?
Running ARHD and ElementalX 0.18. Had the same issue on stock kernel - can't remember if I had it on stock ROM but someone else told me he had the issue too on all ROMs.
This is a stupid question, but I have to ask: Are you sure that you are holding the phone vertically so that it is in portrait mode?
BrandonPrice31 said:
Why does doubletap2wake randomly stop working? It has nothing to do with phone being idle, still doesn't work after movement, have to unlock to get it back to work again.
Is this because of deep sleep or power saving mode enabled in sense?
Is my M8 defective - is this a hardware issue?
Running ARHD and ElementalX 0.18. Had the same issue on stock kernel - can't remember if I had it on stock ROM but someone else told me he had the issue too on all ROMs.
Click to expand...
Click to collapse
sometimes i notice that the double tap to wake won't work because i have some stuff on my screen or something that registers as a screen press. i'll have to wipe my screen down.
It's all in the finger action. One to wake the sensor at any corner of the phone, then 2 deliberate taps, not 2 quick taps, on the bottom half of the screen.
ashyx said:
It's all in the finger action. One to wake the sensor at any corner of the phone, then 2 deliberate taps, not 2 quick taps, on the bottom half of the screen.
Click to expand...
Click to collapse
I have this exact problem. At least 1-2 times a day, motion gestures will stop working and I have to use the power button to turn the screen on. I have tried everything when this happens (making certain phone is in portrait mode and held straight up, shaking the phone, tapping the corner of the phone before doing the gesture, etc.). I am well aware that the phone has to be moved before doing the gestures. This is my second HTC One M8 from T-Mobile. The first had scratches all over the back out of the box so I exchanged it. I don't recall this ever happening with the first phone. Maybe some app is messing things up? Could this be a hardware issue? I'm hoping it's a software issue.
mhajii210
Make sure you don't accidentally swipe up while the screen is off as this seems to lock the gestures out.
ashyx said:
Make sure you don't accidentally swipe up while the screen is off as this seems to lock the gestures out.
Click to expand...
Click to collapse
Really? I haven't heard that being mentioned before. It's possible I accidentally swipe up just a bit when I'm trying to DT2W. Has anyone else mentioned about accidentally swiping up while the screen is off and it locking the gestures out here on XDA?
mhajii210
I've noticed this as well, but only with the double tap(swipe up or to the side always works). I would say mine only does it about 2% of the time though so I haven't been too concerned about it.
Hi guys. I just wanted to report that I updated to the latest stock 4.4.4 OTA 4 days ago. I no longer have any problems with the gestures randomly not working (including DT2W of course). I'm a happy camper =D
mhajii210
Also make sure when you pick it up the meat of your thumb or other part of your hand is not touching the screen. I've caught myself doing that a few times.
Your title pretty much sounds like it is referring to my brother.
I am having this problem too with or without the dot view cover
Sometimes it does't wake up... it's like its in deep sleep like the OP is saying
Any help
two large speakers and some gabba techno should do it
Lol think the phone needs to be at a slight angle when using double tap. i have noticed before when my phone is flat on my desk at work and the screen has been off for a while, its seems to be in deep sleep mode, however when i pick it up, double tap works
It happens to me maybe a couple times a week. I reboot, fixed.
Poop happens is my explanation.
I wouldn't be very concerned. Things get screwy in the system every now and then, that's all.
Whenever it does that, I just rub my finger across the proximity sensor back and forth a few times and then try the double tap again and that always works.
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Not So Pro said:
Has anyone has an issue where the screen won't turn on after using the fingerprint sensor? I can feel it unlock but I sometimes have to hold the power button until the power off/reboot menu comes up which then starts the display up from being all black. Have Magisk beta and Xposed installed so maybe that's the issue?
Click to expand...
Click to collapse
Is AOD on or off? What happens when it's on?
Badger50 said:
Is AOD on or off? What happens when it's on?
Click to expand...
Click to collapse
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Not So Pro said:
AOD is on. So what happens is if the phone is on my desk and AOD is showing time, it'll show the notification briefly then just go black(nothing is covering proximity sensor and notification light is blinking). I then usually have to either do the power menu trick I mentioned or just restart the phone. If it's in my pocket on the other hand I'll pull it out and it'll be black with a notification light.
Oddly enough it usually only occurs with Snapchat so I think it may have to do with having snaptools installed?
Click to expand...
Click to collapse
Quite possibly so. I know nothing about snap face, snap chat, or whatever these social media apps do. Although, you may try clearing the app data and cache on said app to see if it helps. No guarantees though. As is the case with many things android! ??
I've had the same issue ever since I installed, I believe, the nav bar immersive mod. Not sure, around same time. I was able to hurt power button twice for camera and that would pull it up and u could switch back to screen. I don't have xposed or Snapchat, so I don't think either of those are it. It's random when it happens to me.
I've had similar issues. I'm not rooted and have never used Snapchat or AOD. I do use immersive mode for some apps so I've thought that might be causing it. Like stated above, I can get the screen to come on my double tap to open the camera or just holding the phone face down and tap the back a couple times then flip back over and the screen comes on.
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
shmity said:
I'm also having this issue. Ambient display seems to prevent the issue for me. If I reboot the issue is gone for a period as well. Not rooted but have immersive mode acrive via nav bar hider.
Click to expand...
Click to collapse
Ok so a little more testing. When Ambient display is set to always on, I have no issue, maybe a slight lag when waking/unlocking. When ambient is set to tap or pick up i get issues, when ambient display is set to off at all times, i have no issue. Plugging the phone in to charge seems to force the issue to happen.
Edit: Seems that even with ambient display off totally the issue pops up. Strange thing is if i unlock the phone and take a screen shot, its totally black.
I to have this happen and like sportytony I use camera to wake device. Sometimes that too takes a bit. Most of the time when it finally does wake there will be a notification that systemui isn't responding. So I wonder if it's related.
Ok, I've been having this issue happen multiple times a day. I use this immersive app: https://play.google.com/store/apps/details?id=in.tsdo.elw
Since I have turned all ambient display options off and made sure that System UI is unchecked in the immersive app i haven't had an issue at all.
Its definitely related to system UI, com.android.systemui to be precise
i used to try to set up Power Nap on this device, but it can't find System UI in app list, make me unable to whitelist it, thus causing same issue like yours,
Screen wont turn on after sleep, since System UI wake up is blocked
I was using hide navbars and had this issue
I uninstalled and never had that problem again
Sent from my Google Pixel 2 XL using XDA Labs
Didn't expect all these replies but I'm going to try to untick system UI and see what happens. Thank you all!
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Had this happen as well. Not rooted. Can't remember but i vaguely recall this with other versions of android
mcgleevn said:
During phone calls while using the phone on my ear, the screen will dim like normal and touch is not responsive... But after the call, I move the phone away from my ear, the screen will not wake-up and requires waking with power button. I can only recall a handful of times where the phone acted normally after a call...
Anyone else experiencing this? I am rooted w/ magisk and I have verified the proximity sensor is working (using Droid Info app) -
I am turning off adaptive battery not only to see if it helps with this concern, but overall performance and will update w/ changes
Click to expand...
Click to collapse
got a crappy screen protector? that'd be my guess
Nope nothing, naked
mcgleevn said:
Nope nothing, naked
Click to expand...
Click to collapse
Same. And it doesn't happen every time.
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Possibly unrelated, but about every 1 in 5 reboots my screen won't turn on. Stays black, no back light. The phone still responds to ADB and fastboot commands, but nothing will turn the screen on until I hold down power to restart.
Same here.its happened multiple times. naked Pixel here, not rooted. its annoying.
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
honestly after some more calls with this issue, i think my dirty ear and is causing the close proximity reading... after the most recent episode, i went to the droid info app and it was reading the sensor at 0 cm and after wiping the notch off, it started to read correctly (5.0 cm) >>> i dont really want to give the haters another reason to dog the notch but, in my case, i think its going to be an issue. i may switch the "power button to end call" on and see if that will alleviate my issue for now -
mcgleevn said:
Right after I posted this, made a phone call and it blacked out again this time no power button, double tap, shake, twist, etc would wake the phone. Eventually after about 2 mins it woke up again...
Click to expand...
Click to collapse
Same exact thing happened with me yesterday, could it be a RAM management issue?
Roll3r said:
I've made/received 100 calls since Thursday, and it happened for the first time last night. I was able to get it out of black by accidentally doing a screenshot while trying to reboot.
Happened at least 4 times today. Just noticed an update to the Phone app was released, let's see if that makes a difference.
No screen protector, etc.
Click to expand...
Click to collapse
Thanks for the heads up. I have unrooted and naked 3 XL. This screen off thing was affecting all calls. If the remote party hung up, I was fine. If I got into someones VM, I had to sit quietly until the call dropped.
I added myself to the Phone app Beta program and updated. After several test calls, I think it's fixed.
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
RetroTech07 said:
Is anyone else experiencing their camera app no longer functioning? I can't open the app without it closing immediately. I'm on stock ROM and first started to experience this last night out of the blue while using cR Droid. I haven't done anything to cause this type of behavior, so I'm not sure if the latest version is just buggy. I've tried uninstalling updates and reinstalling but I still have the same problem.
Click to expand...
Click to collapse
it just closes? or shows a blank screen? (you checked camera access is enabled in QS).
Go to play store and hit uninstall on the camera (it'll revert the camera back to the default version the phone came with).
Also try the camera in another app (it doesn't use gcam but the camera api). Also try gcam in safe mode..
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
Tasker/Automate script to detect when you're connected to your car's particular Bluetooth (assuming it has that), and when so, turn sensors off, and when not connected to your car's Bluetooth, then turn sensors on.
RetroTech07 said:
Ok, so I figured out what the issue was. I had forgotten I had the quick tile "sensors off" enabled for the entire system, which was causing the app to dismiss itself upon opening.
It didn't appear to ever "crash" because it started out OK for half a second, then it would close. I tried 3rd party apps and the camera wouldn't work either.
I have sensors disabled because my phone's screen is constantly turning itself on when I'm in my car due to movement (which is about 8 hrs of my day), which causes it to hardly ever enter deep sleep or doze because it's constantly waking up, which increases battery drain. I don't have lift to wake, only tap to check my screen for notifications.
If anyone knows of a better way to help my display from turning on due to slight movements I'd appreciate it. I tried using "Naptime" app but that didn't seem to disable motion from turning my screen on. It did at first but idk why it stopped working.
Sorry for the post!
Click to expand...
Click to collapse
there is an adb command to do this
Code:
adb shell settings put secure doze_quick_pickup_gesture 0