My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
prerunnerseth said:
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
Click to expand...
Click to collapse
When I use the power button on the back of the phone instead of the knock-on, I had this same problem. I was rooted but on stock rom. I've read other posts about the same problem. I would try to put in my pattern and midway through the screen turns off. Sometimes it would be two seconds, sometimes like 10. Don't know what the problem was.
My knock-on feature was barely working. Some guy recommended getting this case: http://www.amazon.com/gp/product/B00FEQU1NG/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
I needed one anyway so I got it. Haven't had an issue with the knock-on feature anymore. No idea why haha but whatever, it works. Kind of a ghetto workaround.
I'm having the exact same issue.
Factory reset several times, installing my usual apps or having just the default apps without updating them didn't make any difference.
After a factory reset I disabled the knock knock feature and still, when I try to bring my screen up and unlock, it immediately shuts off, preventing me from swiping.
Another side effect is, when I make a phone call, the screen immediately goes blank and it will never turn back on unless I restart by holding on to the power button, this is especially inconvenient when I need to dial some options (i.e.) voice mail options, corporate automated options.
All of the above happened while I had my Incipio feather shine case. (incipio.com/cases/smartphone-cases/lg-smartphone-cases/lg-g2-cases/lg-g2-cases-verizon/feather-shine-case-for-lg-g2-verizon.html) I took the case off and did another factory reset last night, and so far the knock-on rate has improved from 0% to at least 60-70%... Strangest thing.... If anyone else can shed some light onto what the hell happened/is happening, I'd really appreciate it! It's been a frustrating ride since this problem surfaced about a couple weeks ago. I had this phone for about 2 months now....
I'm having this problem too. It happens with both knock on and power button wake. I have noticed that the screen is not actually immediately turning off, though. In a completely dark room, I can still see faint outlines of my lock screen. Then, after the brief time out for dimming, the screen will go to its dimmed brightness (which is far brighter than what's concurring after waking the phone). I'm able to unlock, reboot, and usually that will solve the problem for a little while, but this is getting frustrating.
Stock rom, rooted, TWRP, Nova Launcher, and xposed. I'm not sure what's causing this.
I know it's been said many times but if you block the sensors with your fingers after waking the device, your screen will turn back off. Its a security feature/bug and I would assume this is what's happening here.
I ended up getting a certified-like new replacement from verizon... While I had the old one, I did a test with that sensor you're talking about and it didn't really make a difference. I made sure the sensor area was clean without anything covering it and the problems persisted. I really hope LG can find the root cause of this and fix it... Very frustrating.
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
yonba said:
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
Click to expand...
Click to collapse
exactly. the sensor in very sensitive to being covered. Because its hypersensitive and having undesireable effects I would consider this a bug since it is buggy.
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Having this issue with my G2, its very annoying. Knock on does not work and screen shuts off after about half a second that I press the power button. Had to reflash to stock the first time this happened and fixed it but after about a month the same problem occured. I could however open by pressing one of the volume button together with the power button.
Hoping to find permanent fix for this problem.
thirtynation said:
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Click to expand...
Click to collapse
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
bigiuly said:
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
Click to expand...
Click to collapse
Please tell me where to find these settings
taqikazmi said:
Please tell me where to find these settings
Click to expand...
Click to collapse
Settings / Led Control
bigiuly said:
Settings / Led Control
Click to expand...
Click to collapse
There is no option in settings like LED.
taqikazmi said:
There is no option in settings like LED.
Click to expand...
Click to collapse
In settings of Lightflow app
bigiuly said:
In settings of Lightflow app
Click to expand...
Click to collapse
I installed the app and fund the settings but all of them are already unchecked
Related
I got my 32GB AT&T Galaxy s4 one week ago today. Had to make an 8 hour road trip to get one but I would say it was very much worth it. I am having this maddening problem where a couple times a day the Display screen timeout keeps re-setting itself to (2 seconds) Unbelievably frustrating considering I can barely get the screen unlocked in 2 seconds and if I blink I have to do it all over again.
But wait, don't walk away just yet, there's more! I have already factory reset 3 stinking times trying to get to the bottom of this and when I woke up this morning it was back to (2 second). Furthermore it shows (2 seconds) in brackets like that so I assumed this was the default value but after checking just now while I was typing this post I noticed after changing it back to my preferred 30 seconds that the 2 second option vanishes. I'll snap a screenshot next time this happens.
Anybody else seen or heard of this problem? I assumed everybodys was doing this until I started searching and found 0 others with the problem. Is my phone The Chosen One?
Yes, i have it also and i found some forums where they discuss same problem, but no solution . Let's think what we have in common..
I have this app called Light Flow, do you?
Also which things you have on?
I have nfc, snart view, smart scroll, air view, air gesture
whatever61 said:
Yes, i have it also and i found some forums where they discuss same problem, but no solution . Let's think what we have in common..
I have this app called Light Flow, do you?
Also which things you have on?
I have nfc, snart view, smart scroll, air view, air gesture
Click to expand...
Click to collapse
Absolutely have Light Flow. I never leave home without it.
NFC. Yes
Smart View. No
Smart Scroll. No
Air View. Yes
Air Gesture. Yes.
I thought for sure it must be Smart Stay malfunctioning but I don't even use that.
maybe it has something to do with Light Flow?? this app caused weird bugs sometimes...
wanna try to turn it off for a while and let me know if it helps?
whatever61 said:
maybe it has something to do with Light Flow?? this app caused weird bugs sometimes...
wanna try to turn it off for a while and let me know if it helps?
Click to expand...
Click to collapse
Worth a shot. I'll play with it and see. Thanks for the idea!
I'm having the same issue and I also use Light Flow - any developments?
Work around
Guys, Did yo get this sorted? I had exactly the same problem which has been driving me mad but managed to sort a workaround which works perfectly. Let me know if this wasn't sorted and I'll post it.
I turned off "Power Saving" mode and it hasn't done it since.
EDIT: Nevermind... just had to give it more time.
Islandguci said:
Guys, Did yo get this sorted? I had exactly the same problem which has been driving me mad but managed to sort a workaround which works perfectly. Let me know if this wasn't sorted and I'll post it.
Click to expand...
Click to collapse
Would you kindly post the workaround? I'm out of ideas at this point.
You all have LightFlow. LightFlow causes other odd issues with Accessibility settings with the S4. Get rid of it and for now use Light Manager. Its much better IMO because it doesn't need to be activated in Accessibility settings, it just works.
Well, I didn't have power saving on and was still getting the problem. I uninstalled light flow and still had the problem. To resolve this for now I use an app called tasker, I had it already because it is a very cool app anyway but once installed if you don't have it just create a rule to deal with the time out issue. My rule for example went like this.
If the time is between 00.01 and 23.59 then set display timeout to 2 minutes. This fixed the problem for me.
In fact you could create other rules to do the same but this does it nicely.
Sent from my GT-I9505 using xda app-developers app
Islandguci said:
Well, I didn't have power saving on and was still getting the problem. I uninstalled light flow and still had the problem. To resolve this for now I use an app called tasker, I had it already because it is a very cool app anyway but once installed if you don't have it just create a rule to deal with the time out issue. My rule for example went like this.
If the time is between 00.01 and 23.59 then set display timeout to 2 minutes. This fixed the problem for me.
In fact you could create other rules to do the same but this does it nicely.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I set my rule to set the display timeout every time the display is turned on. I couldn't make it work the way you did it. I think I need more expertise.
Thanks again.
I haven't seen this issue again since starting this thread. Go figure. I haven't changed anything at all either. Still using lightflow in its entirety just like I was before and never changed anything else that I can recall. Weird.
Ok, I think I have this issue figured out. Here's how I resolved it:
1. Open Light Flow
2. Open Settings
3. Scroll all the way down to the section "Additional LEDs found"
4. Deselect "lcd-backlight control' and exit
I have the same exact problem.. Tried everything but with no luck!! Any one figured it out!??
OutCell said:
I have the same exact problem.. Tried everything but with no luck!! Any one figured it out!??
Click to expand...
Click to collapse
Just to let you guys know, i was able to fix this problem but with a sacrifice.. I reset my phone to factory settings & reinstalled all apps except for Light Flow (The problem did arise after i installed it) and now the screen times out perfectly with the duration i set. :good:
I just hope Light Flow fix this issue soon because i got used to the LED lights indications,, they were very useful.
Solution (I hope)
It's light flow's turn on screen option. They're patching it in the next update, but for now all you have to do is uncheck switch screen on in the notifications.
I tried this tonight. Will post back confirmation from the link
I just registered so I can't post the link to the forum I found it on.
Screen timeout
So I have a Galaxy s4 and started having this same issue with my phone. I would set the timeout for 3 minutes but it would reset back to 0 after so long. I dont have that application you all are talking about. I did root my phone which I do not think matters.
Essentially there are 2 spots to change the screen timeout I found.
My device>Display>Screen timeout
and
My device>Accessibility>Screen timeout (which was set to 0 even though the other was set)
I will let you know if this resolves the screen timeout issue for me.
Thanks
-Jon
goonies83 said:
So I have a Galaxy s4 and started having this same issue with my phone. I would set the timeout for 3 minutes but it would reset back to 0 after so long. I dont have that application you all are talking about. I did root my phone which I do not think matters.
Essentially there are 2 spots to change the screen timeout I found.
My device>Display>Screen timeout
and
My device>Accessibility>Screen timeout (which was set to 0 even though the other was set)
I will let you know if this resolves the screen timeout issue for me.
Thanks
-Jon
Click to expand...
Click to collapse
Disregard....still having the issue.
mharmon said:
I'm having the same issue and I also use Light Flow - any developments?
Click to expand...
Click to collapse
I also was having the same 2 second screen problem and found the unchecking the (turn on screen) to (Switch the screen on for 5 seconds when the notification arrives) in each of the notifications in Light flow has solved my problem. It seems that it was the cause of resetting the screen time out to 2 seconds.
Can someone else try this and confirm that this is the cause???
My N4 was away to repair a broken screen. Got it back on Wednesday and it immediately updated to 4.3. All was well, except for one weird issue where hitting a notification from the pull down would take me to the app via the pattern lock. I put this down to having played with some lock screen settings in Setting Profiles app (trying to disable it in certain settings), but it might not have been.
I've done the first device restart today, and after rebooting there are a few big issues.
1. I don't appear to have any mobile network, though wifi is connected. I had a good signal before the reboot.
2. I'm not getting a lock pattern or any lock screen at all, and it's not asked for the SIM pin
3. Hitting a notification in the pull-down makes the 'lock' clicking sound as it takes me to the app
4. The home button doesn't work. I see a slight dim of the screen and it makes the lock click sound, but nothing happens. Back and multitask work fine
Help! Any ideas? Are they known issues? Can't seem to find any reference online.
I'm on stock, using Nova Launcher
!!11oneone said:
My N4 was away to repair a broken screen. Got it back on Wednesday and it immediately updated to 4.3. All was well, except for one weird issue where hitting a notification from the pull down would take me to the app via the pattern lock. I put this down to having played with some lock screen settings in Setting Profiles app (trying to disable it in certain settings), but it might not have been.
I've done the first device restart today, and after rebooting there are a few big issues.
1. I don't appear to have any mobile network, though wifi is connected. I had a good signal before the reboot.
2. I'm not getting a lock pattern or any lock screen at all, and it's not asked for the SIM pin
3. Hitting a notification in the pull-down makes the 'lock' clicking sound as it takes me to the app
4. The home button doesn't work. I see a slight dim of the screen and it makes the lock click sound, but nothing happens. Back and multitask work fine
Help! Any ideas? Are they known issues? Can't seem to find any reference online.
I'm on stock, using Nova Launcher
Click to expand...
Click to collapse
Those are not any known issues or anything I have read since Andrid 4.3 came out. Try a factory reset to see if that solves the problem. If not, maybe the screen wasn´t the only thing broken on your device. Ask for warranty.
Thanks, will see how I get on this evening and try a factory reset if it doesn't fix itself.
Seems to be a weird problem related to the lock screen and when it should/shouldn't kick in...
!!11oneone said:
Thanks, will see how I get on this evening and try a factory reset if it doesn't fix itself.
Seems to be a weird problem related to the lock screen and when it should/shouldn't kick in...
Click to expand...
Click to collapse
Glad I could help.
Ok, I've done a factory reset. Not had much chance to play as it took hours to reinstall everything. But I've just had the word issue where selecting something from the notification tray (the setting profiles shortcut) took me to the lock screen to put in my pattern first, then took me to the app.
EDIT no pattern to when it does it, seems random and can be while I'm using the device, so the lock screen shouldn't kick in for any reason
Any ideas? Faulty device?
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
97vulcan said:
I cannot find a solution for this but the issue is when I miss a phone call when the phone is in my pocket, it automatically unlocks, and drains my battery.
I'm running 4.4.2 rooted on my AT&T Moto X, and I thought 4.4.2 would fix it. I do not have a screen lock
Any help is appreciated.
Thanks!
Click to expand...
Click to collapse
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
samwathegreat said:
Hmm sounds like a strange issue...
You mean you don't have a screen pin/code/password, or that you don't have even the sliding unlock button?
Have a look in Settings > Display
What timeout do you have listed under sleep? The default is 30seconds, but it goes all the way up to 30min (which I would expect could definitely drain some battery...
Let us know and we may be able to help you further...
Click to expand...
Click to collapse
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
Ok, that is definitely not normal. Are you BL unlocked, or are you using the Pie root exploit? Or Safestrap?
I would suggest flashing the entire 4.4.2 AT&T SBF file using the manual method as described in the Return to Stock thread:
DO NOT DO THIS IF YOU ARE USING SAFESTRAP
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You will download the 4.4.2 AT&T SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
As I seem to be telling people often, the only way to fix a corrupted filesystem (OR modifications made by previous exploits like Pwn/SlapMyMoto and MotoWpNoMo) is to flash the entire SBF file. Performing a "factory reset" cannot repair a damaged filesystem.
Often, it will fix ALL of your problems.
Good Luck
Did you install any apps, that plays with those settings after rooting?
thanks for the replies guys...I don't think so on the apps after root. IIRC, it did this before rooting the phone, so I thought it was a 4.4 issue.
it will unlock to the home page after every call, unless I answer, or ignore the call.
I'm using Xposed with these modules:
App Settings
GravityBox
HideCarrierMotoX
MinMinGuard
SoftkeysFadeMod
Twisty Switch
Xblast Tools
XPrivacy.
Again, I do not have a lock screen..when I try to enable one it does something funky with my electronic buttons, even after reboot. Not sure if it's because of SoftKeysFadeMod, or what..
I'm surprised others have not had this issue.
Thanks for you help.
97vulcan said:
I do not have a password lock on my phone, Just the active display slide to unlock the phone. When a call comes in, I get the display to answer or ignore, but if I leave it go, it will just unlock to the home screen, then after a short time, the screen will shut off.
Thanks!
Click to expand...
Click to collapse
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
rtm1102 said:
May I ask if I understand correctly? You have no security setting, only active display enabled. If this is the case, this seems like normal behavior.
You screen turns on when you get a call, you don't answer. Until the screen time out kicks in, you see your home screen.
Once it goes dark, you should have an active display notification.
What Am i missing or what behavior are you expecting?
Click to expand...
Click to collapse
you pretty much hit it on the head...I was hoping the phone's display would not unlock to my desktop if I miss a call, but rather show the missed call on the active display.
I'm going to enable a security setting, and see if this changes the outcome.
Thanks
After enabling the swipe to unlock, I no longer have an issue with my phone unlocking when I miss a call. That seems to be the solution.
Thanks for your help
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Devany said:
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Click to expand...
Click to collapse
Disable finger print lock.
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Devany said:
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Click to expand...
Click to collapse
Glad your issue resolved.
I don't wish to entirely disable the front buttons, I only want them to stop responding when the phone is locked (I want them to function when the phone is unlocked). Don't misunderstand: I am not looking to simply disable the light. I want the buttons to be completely 'dead' when the phone is locked up. It's actually my bf's phone, and the buttons get accidentally pressed a lot when it's in his pocket. The phone will drain 60% in just 5 hours with no screen time, just locked and in his pocket (at work). I'm tweaking the phone to last longer, but I feel that having the buttons able to be pressed even while locked can't be good for the battery. :/ Someone correct me if I'm wrong with that (but even if I am, it's still annoying... what is the purpose of the buttons being 'live' while the screen is off???). The phone is a i9505, rooted on CM12.1 with Xposed, so modules could be suggested if any such fix exists. I have the home button disabled from waking the screen, but there doesn't seem to be an option anywhere about the back and menu buttons. I know the battery on my own phone, a Huawei, is much larger, but I only experience about 6% battery loss when the screen is off for 7-9 hours, so losing 60% seems excessive to me. I've checked battery stats on the Samsung, nothing seems abnormal. Is it even possible to fix what I'm asking? Thanks to anyone who helps!
zombunny said:
I don't wish to entirely disable the front buttons, I only want them to stop responding when the phone is locked (I want them to function when the phone is unlocked). Don't misunderstand: I am not looking to simply disable the light. I want the buttons to be completely 'dead' when the phone is locked up. It's actually my bf's phone, and the buttons get accidentally pressed a lot when it's in his pocket. The phone will drain 60% in just 5 hours with no screen time, just locked and in his pocket (at work). I'm tweaking the phone to last longer, but I feel that having the buttons able to be pressed even while locked can't be good for the battery. :/ Someone correct me if I'm wrong with that (but even if I am, it's still annoying... what is the purpose of the buttons being 'live' while the screen is off???). The phone is a i9505, rooted on CM12.1 with Xposed, so modules could be suggested if any such fix exists. I have the home button disabled from waking the screen, but there doesn't seem to be an option anywhere about the back and menu buttons. I know the battery on my own phone, a Huawei, is much larger, but I only experience about 6% battery loss when the screen is off for 7-9 hours, so losing 60% seems excessive to me. I've checked battery stats on the Samsung, nothing seems abnormal. Is it even possible to fix what I'm asking? Thanks to anyone who helps!
Click to expand...
Click to collapse
The keys are never on by default when the screen is off. So you either applied a setting to enable it or you have some mod applied.
Lennyz1988 said:
The keys are never on by default when the screen is off. So you either applied a setting to enable it or you have some mod applied.
Click to expand...
Click to collapse
I wouldn't have enabled a setting for this purposely, as it's quite annoying. I may also be wrong, but if I remember correctly, this was existent even on stock non-rooted. I have CM12.1 on it, Xposed modules are: Always Correct, APM+, BootManager, Secure Settings, Xposed Additions, YouTube AdAway, and YouTube Background Playback.
If there is a setting for this, let's say he or I accidentally enabled it, so would you know any suggestions of how to find such a setting, so it can be switched back? I appreciate you taking the time to answer.
zombunny said:
I wouldn't have enabled a setting for this purposely, as it's quite annoying. I may also be wrong, but if I remember correctly, this was existent even on stock non-rooted. I have CM12.1 on it, Xposed modules are: Always Correct, APM+, BootManager, Secure Settings, Xposed Additions, YouTube AdAway, and YouTube Background Playback.
If there is a setting for this, let's say he or I accidentally enabled it, so would you know any suggestions of how to find such a setting, so it can be switched back? I appreciate you taking the time to answer.
Click to expand...
Click to collapse
When the screen is off then menu and back don't work. Do you have ambient display enabled by any chance? Disable it.
Did you try a different battery? Maybe his battery needs to be replaced.
Lennyz1988 said:
When the screen is off then menu and back don't work. Do you have ambient display enabled by any chance? Disable it.
Did you try a different battery? Maybe his battery needs to be replaced.
Click to expand...
Click to collapse
Oh no, you're right about that. Back and menu doesn't actually do anything when touched while locked, but they do light up and respond in that sense (interestingly, they do also wake the screen while it's locked in TWRP, though perhaps that's irrelevant). Ambient display isn't enabled. We haven't tried a different battery, he just got the phone about a month ago. Then again, I also haven't the health of the battery. Maybe it came with a bad one.
When the screen is off, the back and menu buttons should not work. Not even the lights.
zombunny said:
Oh no, you're right about that. Back and menu doesn't actually do anything when touched while locked, but they do light up and respond in that sense (interestingly, they do also wake the screen while it's locked in TWRP, though perhaps that's irrelevant). Ambient display isn't enabled. We haven't tried a different battery, he just got the phone about a month ago. Then again, I also haven't the health of the battery. Maybe it came with a bad one.
Click to expand...
Click to collapse
I understand you now. Yes when they the phone is locked and the screen is on, they will light up. That's normal and does not give any battery drain. Post some battery screenshots and post screens of the app betterbatterystats.
Lennyz1988 said:
I understand you now. Yes when they the phone is locked and the screen is on, they will light up. That's normal and does not give any battery drain. Post some battery screenshots and post screens of the app betterbatterystats.
Click to expand...
Click to collapse
Ah got it. Good to know it's not impacting his battery, but that also leaves it open as to what IS (though, the buttons lighting up while it's locked still makes me scratch my head at what Samsung was thinking). Currently going to sleep at the moment, so I'll have to take a look at it tomorrow. I know Opera Max, a VPN data compression app, was chewing up battery (did this on my phone too, but eventually it settled down with the ROM), but I froze it for the moment so it won't run until I figure out what else is causing the problem. Battery life was poor even before the installation.
Other than that, battery stats have been normal, with the display taking the majority followed by Opera browser and the Android system, with some others. Nothing outrageous.
But since you mentioned about the battery, I did start noticing more things about the phone today. Perhaps it runs so hot because of it, and I also saw that when he unplugs it from the wall charger, it will immediately drop from 100% to 90-some% (varies). Might be the calibration, but with everything else, I ended up ordering an Anker replacement from Amazon to test.
The S4 heating is normal.
Also, it's not healthy for the battery to spend extended periods of time at 100%. That is why it drops faster from 100%.