This issue is more of an annoyance than anything but my S4 screen wakes up for no apparent reason then it returns to sleep a couple of seconds later. There does not seem to be any specific timing or pattern to it that I can identify. What might be causing this issue?
damifineaux said:
This issue is more of an annoyance than anything but my S4 screen wakes up for no apparent reason then it returns to sleep a couple of seconds later. There does not seem to be any specific timing or pattern to it that I can identify. What might be causing this issue?
Click to expand...
Click to collapse
It might be the air gesture to check notifications: if the phone is on a flat surface and the light sensor is blocked briefly, the LED flashes blue and the screen wakes up to show you time and several notifications (missed calls, texts, emails, etc.).
I noticed that mine was doing it at dinner last night every time I reached for my water glass...I finally had to put it face down on the table because it was driving me nuts.
SF Steven said:
It might be the air gesture to check notifications: if the phone is on a flat surface and the light sensor is blocked briefly, the LED flashes blue and the screen wakes up to show you time and several notifications (missed calls, texts, emails, etc.).
I noticed that mine was doing it at dinner last night every time I reached for my water glass...I finally had to put it face down on the table because it was driving me nuts.
Click to expand...
Click to collapse
I currently have Air Gestures turned off and it is still happening. Had to turn the phone face down last night to keep the wife from assaulting me. She said the damn phone was like a floodlight in the room.
Related
So I've searched everywhere and I haven't seen anything for this issue. Even though all the settings are correct and i have vibrate checked in the messages app, my phone won't vibrate for notifications like text messages all the time. Sometimes it will vibrate and sometimes it won't. So my phone will be in my pocket and I'll check it 30 minutes later and see 3 or 4 texts but it never vibrated. I exchanged my phone and am having the same issues. Everything is stock. Has anyone had this problem?
the phone vibrates, it just does it too softly for you to feel it... that's the problem with light phones, the original epic 4g could cause an earthquake but that's because it was gigantic, I never felt the epic 4g touch, and this one I feel it at times...
Sent from my SPH-L900 using xda app-developers app
no it definitely doesn't vibrate. I've set it on the table and texted it and it'll vibrate on every 10th text or so. usually it'll just light up for the notification but it won't vibrate.
m3meems said:
no it definitely doesn't vibrate. I've set it on the table and texted it and it'll vibrate on every 10th text or so. usually it'll just light up for the notification but it won't vibrate.
Click to expand...
Click to collapse
menu/settings/sound...........make sure sound and vibration are checked. that is the default for the entire phone even if vibration is enabled in messaging. also make sure your vibration intensity is all the way up.
t3project said:
menu/settings/sound...........make sure sound and vibration are checked. that is the default for the entire phone even if vibration is enabled in messaging. also make sure your vibration intensity is all the way up.
Click to expand...
Click to collapse
Yes that's already been checked and vibration intensity is all the way up. The phone does vibrate on some texts, but not most, which is what the problem is.
I've noticed it'll vibrate normally when the screen is on and I get a text, but it won't when the screen is off?
I've definitely seen bugs in phones in which things like notification LEDs didn't work when the phone was in sleep mode. Whaddya know, I recall one of them being a Samsung (Intrepid). Granted it was years ago and Windows Mobile 6.5, but whoever was coding notification and power management back then wasn't fully aware of the point of "notifications".
Then again I just sent myself a test to the Note 2 while the screen was off... phone vibrated, screen turned on briefly (I hate that), blue light started blinking, heard my notification sound, and screen turned back off.
So there's something interfering with your phone's ability to wake up while it is trying to notify you. Have you done any power management modifications or installed anything designed to save battery power?
hausman said:
I've definitely seen bugs in phones in which things like notification LEDs didn't work when the phone was in sleep mode. Whaddya know, I recall one of them being a Samsung (Intrepid). Granted it was years ago and Windows Mobile 6.5, but whoever was coding notification and power management back then wasn't fully aware of the point of "notifications".
Then again I just sent myself a test to the Note 2 while the screen was off... phone vibrated, screen turned on briefly (I hate that), blue light started blinking, heard my notification sound, and screen turned back off.
So there's something interfering with your phone's ability to wake up while it is trying to notify you. Have you done any power management modifications or installed anything designed to save battery power?
Click to expand...
Click to collapse
I haven't changed any power management settings or downloaded any apps designed to save power. I've tried factory resets several times. The phone will vibrate for texts but after about 30 minutes or so goes back to not vibrating. I've called samsung and taken it to the sprint store and no one can figure it out. I first thought the motions was causing te problems but it still doesn't vibrate when those are off. I'm completely out of ideas.
EDIT: I may have figured it out, if I turn on "Wake up in lock screen" in the settings in S Voice, the phone stops vibrating on texts. When I turn it off, the phone vibrates again. Toggled it on and off and the changes were immediate. Does anyone else have this problem??
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.
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.
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.
This one really grinds my gears.
I use wired headphones a lot. and whenever I do and the phone is in my pants pocket, the thigh touching through the fabric of pocket turns on the screen many times. So I disable double tap to wake.
Every time I receive a call and phone is in my jeans front pocket, random buttons would be pressed. call would go on hold, or mute itself, or turn on speakerphone, or open keypad, turn on record etc.. and it is extremely frustrating. even more so when a business client calls me and I accidentally put him on hold because my phone is so stupid it does not understand not to turn on the screen touch. The proximity sensor works fine because when talking on call it will turn off the screen. just not the touch. My torch gets activated pretty often when pulling the phone out of pocket. this is so stupid infuriating.
The rest of the phone is amazing. I love the hardware. its pretty fast, runs games fine. camera is also very good. but the bloatware and the bugs are getting on my nerves.
This bug is from the day I got the phone.
Realme UI 3 update did not affect the bug but actually made it worse as the torch triggering issue has gotten worse.
I have not encountered any major bugs in the new update apart from a bluetooth volume fluctuation bug.
Am I alone having this issue?
PS: I forgot to mention that several times the quicksettings toggles are also triggered Like Data/Wifi turning off, VPN getting activated, Airplane mode turning on etc.