I have no rules set for switching into power save modes, yet I keep finding my phone in power save mode with all the radios turned off. I'm using a case with a viewing window if that means anything. Anyone else having this issue?
I had this issue, and my wife had it too. I ended up disabling the power saver on both our phones. I have since enabled it again on mine, and it has been behaving properly. No idea what causes it or why mine now seems to be working OK, but it is a very annoying bug.
How did you disable it?
Dan
I use the "Disable Application" app by BIZKAI Apps from the Play Store. You need root, obviously.
I was afraid of that. I've not rooted the phones yet.
Dan
This has been happening to me also and i dont have it set to switch but it will randomly do it and turn off my network. This phone is really pissing me off.
Something you might want to try is to go to power saver-> smart switch-> switch by schedule and change it from battery saver to normal. It sounds like a bug that someone mentioned a while ago: smart switch's switch by schedule runs even when it is not turned on.
Sent from my ASUS_Z00AD using XDA Free mobile app
Not related to OP's issue as they have the View Case which I hope prevents this, but I have found that the phone activates in my pocket and often enables flight mode, power saving mode, and other random toggles. Noticed that when the phone is in a pocket facing my body, wild things happen. facing away and nothing happens.
Take your phone out, turn the screen on and rub it on your knee. You will see that the touch screen is so sensitive that it responds through the fabric of your plant leg. This seems to be a problem for me from time to time, but the new slide to unlock on the view window has fixed some of the issues.
Related
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.
I realized today my phone was facing inwards towards my leg and that it may be double tapping and turning on in my pants. Any way of stopping this, but also monitoring? I am just curious as I faced my phone outward it kept my battery lasting much longer today.
Dsmwookie said:
I realized today my phone was facing inwards towards my leg and that it may be double tapping and turning on in my pants. Any way of stopping this, but also monitoring? I am just curious as I faced my phone outward it kept my battery lasting much longer today.
Click to expand...
Click to collapse
I had the same issue, but for me it turned out to be neither the back button nor double tap to wake. For me it was greenify, which does evil things when it doesn't have root: it turns on the screen, goes to the app info of an app it wants to hibernate, and "clicks" the "force stop" button, before going back and just leaving the screen on.
Of course this may not be the cause of your problem. You may not even have greenify installed. Have a useful way to debug the issue: install tasker (or something similar, maybe condi can do it too), and make a profile that makes your phone vibrate when the screen turns on. Make sure the vibration duration is distinguishable from notifications, 200 ms worked for me.
This way, you will know exactly when your phone turns on in your pocket. You will be able to reason about whether the back button was accidentally pressed or whether it's double tap to wake, or something else altogether, like greenify in my case.
Just a side note: it's unlikely to be double tap to wake, because double tap to wake will not turn your screen on when the proximity sensor detects that something is close. You can try that by holding your finger over the proximity sensor while trying to turn it on. Double tap to wake won't turn the screen on in the first place, and the screen will turn on and immediately off when using the power button.
So yeah, try the tasker/condi profile and see what your phone does right after it wakes. I saw mine force closing Facebook messenger like 7 times in less than an hour, and it stopped after I uninstalled greenify.
Sent from my LG-H815
Ive noticed the screen on out of pocket but rarely. One new feature is the "slide down" quick peek while the display is off. This new feature may have new side effects.
player911 said:
Ive noticed the screen on out of pocket but rarely. One new feature is the "slide down" quick peek while the display is off. This new feature may have new side effects.
Click to expand...
Click to collapse
That too doesn't work when the proximity sensor senses something is close. Try it by holding a finger over it while trying to pull down the thing with another finger.
Sent from my LG-H815
I seem to be having an issue with the screen turning on at random. I have Always-on screen set to ON and tilt-to-wake set to OFF, but the screen will turn on sometimes seemingly at random and multiple times in a row. I have done Factory Reset a couple of times and it does not help.
Is there anyone else with this occurance and is there a fix for it?
Sent from my VS980 4G using Tapatalk
I have this issue too. I've tried several configurations and it keeps doing it.
Sent from my SM-N910V using Tapatalk
Any apps that send a lot of notifications or any notifications that are automatically dismissed/very briefly show up? Can't think of anything else that would wake your watch.
No, not on mine.
Sent from my SM-N910V using Tapatalk
I have the exact same issue. At first I thought it was tilt-to-wake having poor gesture recognition so I turned it off. However I noticed without touching the screen it would turn on and then turn off after the stand-by time. To verify that was the case I left it sitting on my desk all day and observed that it would in fact randomly turn on and off. I also noticed that when the issue occurs the battery life decreases rapidly.
Also this issue will continue to occur even in theater mode.
Have you find a solution yet? My smartwatch 3 does the screen turn on randomly and then also touch screen issue occurs, and it makes random touches, swipes going into settings and so on, without touching the screen. I'am on the latest wear version mwd49b.
For more info search on youtube for my video about this problem: Sony SmartWatch 3 screen problem.
I recently began having the same problem. The screen does not turn off after it randomly turns on - I have to manually press the button to turn it off. Needless to say, this tend to run down the battery. I did a factory reset this morning, but the problem persists.
EDITING POST JULY 20:
After factory reset, I actually had the watch doubly connected to the phone, so I have corrected that now. However the problem with the random turn-ons began occurring well before the factory reset. I'm not sure what triggers it, or what stops it, but when it begins to happen, it drains the battery very quickly. The problem only began recently (within the past few weeks), so I'm not sure what changed to bring this on.
A bug in Android Alarm Clock keep the watch active after alarm ring. Just corrected yesterday by an update on Google Alarm/Clock app.
On the phone > android wear app > settings icon on top right > device settings (smartwatch 3) >tilt to wake set to off
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!
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