I've notice this on on my unrooted 1.28.161.9.
It wakes up briefly without no intervention then goes back to sleep I also notice that some residual heat was emanation near where the camera lense was. I can not reproduce it now but it was a strange one ;-(. like some process was running in the background and waking it up. The wifi was turned off btw
Related
Noticed recently that When a phone call is in progress, the screen will go black no matter what and to get it to come back i have to manual hit the top power button.
I first noticed it with energy rom. When autobacklight was enabled, their was no getting back to screen at all. Disabling autobacklight at least allowed me to get the screen back after clicking the power button.
I switched to core cell rom and noticed the same issue, however, i can manually turn the screen on again even if autobacklight is enabled.
I have no further problems with the proximity sensor, just this one.
Is their perhaps some sort of proximity app that i could use to diagnose whether this is a hardware problem or software problem?
Ok, I had a similar issue, where the phone screen would turn off as soon as the "send" button was pressed, and the only way to turn it back on was either hanging up, or waiting till it felt like coming back on.
My proximity sensor was stuck "on". I could see the sensor status in the registry (don't remember offhand the reg entry, but it's a live reading of the sensor, 1 or 0). I installed "Proximity Sensor for Screen Off v0.2" from http://forum.xda-developers.com/showthread.php?t=624206
That was a mistake on my part, though... then the screen wouldn't come back on! It took some real finagling to get the screen on.
To fix it (temporary? permanent? dunno...) I waved a small neodymium magnet over the sensor (near the ear speaker). I have no clue why that worked. I don't know why it stopped. I *definitely* don't know if that's the issue you are having. But it's worth a shot
I've never had this issue after many different iterations of the Energy ROM.
Do you run Task29 when you flash ROMs?
Yeah i always task29. I don't believe it is the rom since i have tried another rom and the problem persisted. I tried the magnet idea but it didn't work. It was a refrigerator magnet though so i didn't expect it to. Anything else that requires the prox. sensor to work, has no problems and that is why this is weird to me.
Hey everyone!
My phone just started doing this today: During a phone call, screen shuts off when phone gets close to my face, as intended. But it doesn't turn back on when I pull it away. I usually have to pull the battery.
Downloaded an app to test the prox sensor. It shows a change when i put my hand it front of it, but never changes state when I move it away.
Any idea what could be causing this / possible fixes?
Hello, recently I've found that my device is draining battery at a substantial rate while in my pocket. And after some testing, I found that even while in pocket mode, the phone wakes the screen up upon notification. This is with ambient screen turned on by the way. So when I get a notification, the ambient screen turns on and you're able to interact with the screen. I guess what I'm trying to get to is: shouldn't pocket mode automatically disable the waking of the lock screen?
Thanks for the help
Rykanator
pocket mode disables interaction, not screen waking from what i understand. test it by covering the prox sensor and hitting the lock button on your phone - you'll see it until you uncover the sensor
also not sure why notifications are waking your screen - they never do that for me. what apps are you using? one of them must be turning on the screen, most apps don't do that
I had this problem recently and discovered it was related to the manner in which the phone/case fit in my pocket. With certain walking or sitting movements, the power button was getting pressed, which turned on the screen. It was highly annoying, but only happened once (so far). I twish the power button was much deeper into the case than it is.
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