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.
Has anyone else noticed that when in a dark area, pressing the main button will turn on the screen but it will then automatically and immidiately turn off?
Several times I've gotten into a battle with the phone only to lose, turning it on and it turns off, then turning it on again and so on...
To compound the issue, in these situations it seems that double tap is signifigantly less responsive to activate the screen as well.
I'm pretty sure this phone is using some sort of facial recognition, it has smart stay doesnt it? I think it has gravity/accelerometer to turn on the screen when you pull it out of your pocket. In the back of my mind I'm thinking that since it cant see me it is shutting off but this doesnt seem consistent...
I'm running stock rom, rooted with twrp. Any ideas?
I have not experienced that. Did your G3 do that out of the box?
Sent from my LG-D851 using Tapatalk
Never heard of it. Screen is set to auto off in 30 seconds. Change it to 2 min and you should be good. If u running without a case then maybe the hand is touching the edges of screen this will also shut screen off in double tap.
BAD ASS G3
sublimaze said:
I have not experienced that. Did your G3 do that out of the box?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I didn't notice it until the last week or so. but I kind of feel like that was because I hadn't used the phone that much up until then. I didn't make any major changes to the phone immediately before I started noticing it either, I had already had it rooted for about a week. I feel like the stock rom does have some glitches to it.
The G3 does have a "smart screen" feature that detects your face (Settings > Display). Disable that and see if it helps.
I've not run into this in the dark but have when I try and use my arm band holder when running. The holder covers the ambient light sensor so the phone thinks it was accidentally turned on like in a pocket and shuts right off. Super annoying.
Noticed similar behavior when the phone is in my bike mount at night. Basically it's acting like the proximity sensor is covered. In my bike mount's case, it is covered by a clear screen cover, but normally that doesn't trigger the proximity sensor. But when it's very dark out (not under a street light etc.), it seems to think it's blocked and turns itself off. Annoying.
randyspants said:
I've not run into this in the dark but have when I try and use my arm band holder when running. The holder covers the ambient light sensor so the phone thinks it was accidentally turned on like in a pocket and shuts right off. Super annoying.
Click to expand...
Click to collapse
speedrabbit said:
Noticed similar behavior when the phone is in my bike mount at night. Basically it's acting like the proximity sensor is covered. In my bike mount's case, it is covered by a clear screen cover, but normally that doesn't trigger the proximity sensor. But when it's very dark out (not under a street light etc.), it seems to think it's blocked and turns itself off. Annoying.
Click to expand...
Click to collapse
Have you tried disabling smart stay as sublimaze recommended?
Apache0c said:
Have you tried disabling smart stay as sublimaze recommended?
Click to expand...
Click to collapse
Tried but remains the same... This was the only thread I found concerning this.
Ive had this issue too investigating now
Had that issue when I was using the lock screen face unlock. In the dark it didn't see my face and then it shut off. Setting is in lock screen section
Sent from my G3
gabrielshaste said:
Had that issue when I was using the lock screen face unlock. In the dark it didn't see my face and then it shut off. Setting is in lock screen section
Sent from my G3
Click to expand...
Click to collapse
Lol.
I have the same issue EVERY night. Why is that? It's very annoying
Same issue here
it seemed to resolve itself when I factory reset my phone
but after I got my apps reinstalled from my google backup it started again
so it seems like it's a software issue - not sure to which app it is related to
let me know if you find a fix - this is quite annoying
Me too. I've been facing this issue at night, when it's very dark.
Me and my buddy were in the car during a roadtrip and it was very dark, I mean like: No lights outside, no lights inside the car, the double tap feature didn't even work to begin with and whenever I tried to use the "Power Button" It would come on and then suddenly 'boom' Turn off, now this would happen a few times until it stays on. Weird...
I just experienced this myself, first time I've seen it happen in the 30 + G5's that I've sold. If it's in the dark it just doesn't turn on at all. I hope LG is fixing this. I'm about to Factory Reset it right now and hope for the best! Someone else mentioned that this is the only forum that is disccusing this issue. It must be a very few that are effected. I'm testing another one as we speak.
Has this issue been resolved? My friend's G3 also has this issue. Day time no problem. When it is dark the screen wont' stay on.
Same problem, no fix yet
Same problem here - Pointing it at any light and pressing the power button will turn it on. (As will plugging it into power). Tried tinkering with all sorts of settings (face recognition/auto dimming feature/etc) nothing worked. Tried factory reset, that didn't work either.
My issue started after i had my screen replaced (by a shady shop) who probably didn't do a good job of packing it back together....I'm going to see if I can have someone open it up and clean it out a bit..
I have the same issue on my G3. Even if you're under the covers in bed, the thing doesn't turn on until it gets light. It basically doesn't turn on in the dark through double tap and actually not even with the power button. It could become a safety hazard for someone in an emergency situation.
Nahdont said:
I have the same issue on my G3. Even if you're under the covers in bed, the thing doesn't turn on until it gets light. It basically doesn't turn on in the dark through double tap and actually not even with the power button. It could become a safety hazard for someone in an emergency situation.
Click to expand...
Click to collapse
I have also same problem. No solution yet.
Got a Pixel 2 xl off ebay and everything seems fine just the ambient display (always on) screen flickers at middle brightness. In the dark it is fine and the bright light it is fine just mid brightness I can notice it. Has anyone else noticed this? Pretty happy with the phone so far and know the camera will make up for anything just find it pretty annoying at times.
Also the fingerprint sensor is random, sometimes it works other times it won't recognize the print others it says the sensor is dirty. Thinking this phone has a couple of hardware faults and that I should sent it back but for £300 I don't know if it was worth it,any thoughts??
Did hard rest no luck with that so going to try development package, then maybe custom rom to see if they can iron out the issues.
I disabled "New Notifications" toggle from the Settings which keeps the ambient display on but does not wake the phone up and show lock screen for new notifications. Seems to work.
I guess the problem is about this new "Silent Notifications". You can not see them but they come and go momentarily waking the phone up.
I just got my Pixel yesterday and started having this issue, so I thought I'd check in with the fine folks at XDA.
I had Ambient display set to "always on" and "double-tap to check phone" set to on. After a while of being in my pocket, the screen will be black when I pull it out. Double-tap to wake does not work and it never comes on. The only way I can wake the phone after that is the fingerprint reader or power button (which I never use on my Android phones). It seems like Ambient display is going to sleep due to the proximity sensor and then just not waking up.
I changed it to lift to wake and the problem is mostly gone, but I would rather have ambient display on all the time. This is brand new out of the box. It's not rooted or anything. I haven't even unlocked the bootloader.
My OnePlus 6t was doing something similar (to a lesser degree) and it drove me crazy. This is something I need to work consistently. I expect to take my phone out of my pocket, glance at the AOD, and then tap twice to wake it and interact with the lockscreen. That's how I use all of my phones.
I just wanted to see if anyone else is having the issue. I haven't wiped it because, really, it's been doing this since I took it out of the box (new). And I have seen some other scattered reports online. Rebooting also did not resolve it.
This has happened to me a couple of times. Quite annoying.
Yeah, I have this problem too. Another bug...
Yep. Happens to me fairly frequently
It started happening to me recently too.
Thanks for the confirmation, guys. Glad I'm not crazy. This may actually be a deal-breaker for me, though. I'm pretty anal about the consistency of tap-to-wake on my devices.
One of the touch screen issues I sometimes experience is when swipes are "broken" and register as shorter swipes and taps. This makes me think maybe the accidental touch protection, which is supposed to be triggered by the proximity sensor, is being triggered when it shouldn't. We all have read complaints about how the proximity sensor does not work very well.
So on a hunch, last time I had this issue (trying to swipe in gboard), I stuck my finger on the front-facing camera, and interestingly, swiping worked fine (I expected the screen to be disabled - guess that only actually is supposed to happen when you're on a call?).
Since this issue is so random it's hard to really test it. But I've had quite an experience with the proximity sensor.
I wanted the AOD to turn off when the phone is in my pocket, which is the norm on other phones I've used but for some reason Samsung does not do. So I set out figuring out how to do this in Tasker. I got a sensor test app and noticed the proximity sensor basically has two values: 0.0 and 5.0. It is very slow to respond (slower for "uncover" events) and seems to only switch to 0 if my finger is right on the camera. So I set up Tasker to turn the AOD off if the proximity sensor value is < 1, or on if it is >= 1. I also made it vibrate briefly so that I could tell when the sensor was toggling even if I couldn't see the AOD.
At first it worked fairly well. If I manually covered and uncovered the camera, the AOD would dutifully toggle (not instantaneously). But in "real life" practice, it turned out to be quite unreliable. There would be phantom proximity changes while I was using the phone or carrying it -- most interestingly, it often toggles the AOD off briefly when I pick up my phone -- but I didn't really notice any surprise vibrations while the phone was in my pocket. After a couple hours, when my living room got darker (not completely dark), the whole thing went crazy and the AOD would toggle every few seconds with the phone sitting on a table.
So I think the whole "let's ditch a dedicated proximity sensor and use other things to get the same result" is not quite mature yet. And perhaps it is buggy enough to cause one of the issues we think of as a touchscreen one.