First of all I apologize in advance if this is a common problem and I just couldn't locate it, but I have tried searching for this quite a bit now and can't seem to find anything that addresses the problem I have.
I am running my S3 rooted but otherwise pretty stock (4.1.1 - I just never got around to the updates and I am very much a novice at rooting). I have disabled a number of services, apps, etc (with TB) and never really noticed an issue until recently. My android system and kernel usage as shown in GSAM and the built-in stats are top of the list for app battery consumption (screen comes in at #1 overall). I am getting pretty decent battery life I think but I am in the process of breaking in a new battery so it is a little hard to tell. The thing that concerns me is the sheer amount of 'loop' and 'flush' processes showing up in my kernel stats. I am attaching a log with this post. Is this normal? I just have never seen anyone with stats showing that many loop and flush processes listed. For reference that 1 hr 44mins usage in the attached log is with about 61 hours of up time on the phone with moderate usage (hi-capacity battery). I get the same sort of level of activity whether I have Wifi and data on or off, screen on or off, syncing off, bluetooth, gps, rotation off, etc. I may try a factory reset but was hoping someone might know a culprit causing this before I had to take that step. Many thanks!
Related
Hi all, just visiting from the gnex forums. My wife has a desire running the official gingerbread rom. She has a recurring problem whereby she'll power off the phone and it appears to shut down but will still have a grey tint like the screen is still slightly lit. Last night from a full battery it had permanent screen on in the battery stats and was near empty in the morning showing a constant drain all through the night. Has anyone had this issue?, is it related to the gingerbread update or is it just a rogue app??
I've attached an image of the battery stats with the night period being the steep drop on the right...
Any tips or advise is greatly appreciated....
Probably a rogue app. Search for Better Battery Stats app here on XDA to help you see what's keeping it awake.
Furthermore, try disabling fastboot from settings, don't remember which settings, but it should be in there somewhere.
Thanks for the replies. I've got that better battery stats app and just need to read up a bit on how to use it then I'll give it a go tonight. From my searches I found multiple things suggesting it could be an app but it seemed odd to me that it was preventing the phone from powering off and not just preventing it from sleeping.
Regarding the fast boot option I've just found that and it was turned on - what is this option for and why could it cause this problem then? ....
On Better Battery Stats, I usually check Partial Wakelocks - Since Unplugged. Most processes should be below 1% from what I understand. But it will depend on how long you are using a certain app. If you see a process that's been running for so long but you've just used the app related to it for a relative short period of time, then you check that particular app. Maybe the sync option is too frequent or it's just really poorly coded app.
If it appears that a valid android process is the one eating the battery, then an app is probably keeping it awake and you may need to dig a little deeper to figure out what app is causing that.
Regarding the fast boot option, all I know is that it's a feature to reboot the phone without going through the main HTC logo animation. So it's really like rebooting the phone without actually killing the background processes. (Not sure about it though maybe someone can explain this.)
Basically, with the Fastboot option the phone never REALLY turns off, it's a little bit like it's on hibernate, that's why it can boot a lot quicker, as it skips the bootloader and goes straight to booting the system.
Thanks guys. With the fast boot turned off it didn't do it last night so I'll try with fast boot turned on tonight and see what happens - try to confirm what's happening......
Many thanks for your help!
I turned fast boot on again yesterday and the fault occurred again overnight. Went from 100% battery to 55% overnight. Pictures of the stats for useage during this period are attached.
Anyone know what this alarm manager and sleep broadcast are?
Hi all,
I have been using ARHD ROM for a while now, version 5 for a few weeks and noticed the issue on there first and it still occurs after updating to 6.1 over the w/e. I was not aware of the issue before I went to ARHD but was not using/rebooting stock often enough to find out.
I don't think this is ROM related but am not really sure how to go about working out exactly what is causing it.
Normal working is excellent and battery drain is very low - seems to be about 2mA when idle with no WiFi or Data connections.
After a random amount of time - could be 3/4 days or less than 1 day the battery drain increases noticeably. For me it means that after an average days use the battery would be down to 20% or less rather than 40-50%.
I downloaded "better battery stats" to try and identify if possible what was causing it and it seems to be that the "LocationManagerService" is getting stuck with a "Partial Wake Lock". This prevents the phone from going into "Deep Sleep" so I can see on CPU Spy that the 51Mhz time starts increasing considerably and the Deep Sleep stops increasing completely.
A reboot solves the problem for another random amount of time.
After reboot under normal operation the "LocationManagerService" does not seem to register at all for several hours and when it does operate normally it stays towards the bottom of the "better battery stats" list with about 1s of use, even after a couple of days. When it gets stuck in partial wakelock it moves to the top of the list and refreshing shows constant updates indicating that it is maintaining a partial wakelock.
I have tried searching on Google but cannot see any mention of anyone experiencing a similar problem and as I am sure many applications use the "LocationManagerService" I am at a loss as to how I try and work out whether this is a bug in the service or an application that is causing it.
Apart from rebooting every time I notice this I am not sure how to troubleshoot any further, so was hoping one of you knowledgable guys/devs could perhaps make some suggestions as to how I can identify exactly what is causing this?
I would also be interested to find out if anyone else on any other ROM can see the same issue?
Thanks
I have a strange issue with my 32G WiFi FLO that I was hoping the knowledgeable members of XDA could help me diagnose.
Since I got it at launch, it's been sucking the battery dry. But not consistently. I have no idea what or why, but here's what I know so far:
All details are with auto sync OFF. WiFi OFF on sleep, location services ON (but cannot use WiFi)
Not unlocked or rooted (stock)
- From boot, and for the first 20-40 hours after that, battery usage on standby averages out to around 0.13% per hour.
- After that, and for no reason I can discern, battery usage jumps to an average of 0.84% per hour, and keeps draining like this usually until I reboot or need to charge
- Stock battery app shows no apps draining, BBS shows no apps draining stuff or excessive wakelocks and indicates the tablet is spending most of its time in deep sleep.
- Life with screen usage seems to be around 7+ hours either way, so this is as expected.
- Sent to ASUS to diagnose & repair, received with note that front camera unit replaced and OS reloaded.
- Issue is still occurring after "repair"
- apps running at the time are usually Android Keyboard, Android Services, Settings. Sometimes Play Store, Currents (even though I don't use it and have never launched it), Google Play Services as well. These are the only apps that run regardless of state of battery drain.
Can anyone think of any reason this is occurring, or where else I can go to check for more info? I'd prefer to stay stock/unrooted.
I'm looking to send it back for RMA *again*, but I'd rather tell them where to look than try and trust that they'll know where to look to fix it this time.
Guess no-one else has this issue or any ideas on where to look for this, since there are no replies
Hi guys!
I desperately need some help from you experts. I have recently noticed my LG G3 has been draining more battery than it should, especially when idle (or at least, theoretically when idle).
Please take a look at the sequence of screenshots (have in mind the analysis was made overnight, when the phone was sitting idle on my bedside):
Screenshot 1: You can see app usage has been the biggest juice thief, and an abnormal drain (24%) for a (supposedly) idle period of 6 hours.
Screenshot 2: Kernel & Android system are the biggest villains, but only sums up to 45%.
Screenshot 3: Taking a deeper look at Kernel, it shows only 7 minutes of CPU usage.
Screenshot 4: A deeper look at Android system also shows a small usage, only a few seconds shy of 6 minutes.
Screenshot 5: On the chart, we can see there was an absurd drain (around 20%) from 1:30 am to 5 am, and then it got stabilized. Wifi was on the whole time, and you can see it shows the phone was (theoretically) dozed 95% of the time.
Sctreenshot 6: Even though the phone was dozed, we can clearly see it has severe CPU usage throughout the whole night, and no pattern could be distinguished between the hours were the battery got the severe drain and the hours after. Even though the CPU frequency was low between 1:30 and 5 (except for a couple of peaks), the utilization averaged 45%.
This is why I need some expert's help. I cannot understand what is draining my battery, what is keeping my phone's CPU util so high... can someone please shed a light on this for me?
Thanks in advance!!! :fingers-crossed: :good:
Hello there guys. Anyone could please take a look at this and try and help me out?
Thanks!!!
Well, it's hard to answer simply such a complicated problem. There are so many variables to consider, but I would say rule out a few things first.
First, if you have TWRP installed, backup your current ROM and do a complete factory reset. If the problem persists, then you know it's something built into your ROM causing it and I would suggest swapping out that ROM for another. If the problem is gone, you know it's something you installed or modified in the ROM and you can start to narrow that down.
Second, I would try out the app WakeBlock. It's still in development, but it allows you to see active wakelocks (Android programming object used to keep the CPU running even if dozed) and block them if you want to. But the app may be useful for just tracking down battery hogs that are activated at 2am in the morning
Hope that helps! Good luck! :fingers-crossed:
AlwaysLucky said:
Well, it's hard to answer simply such a complicated problem. There are so many variables to consider, but I would say rule out a few things first.
First, if you have TWRP installed, backup your current ROM and do a complete factory reset. If the problem persists, then you know it's something built into your ROM causing it and I would suggest swapping out that ROM for another. If the problem is gone, you know it's something you installed or modified in the ROM and you can start to narrow that down.
Second, I would try out the app WakeBlock. It's still in development, but it allows you to see active wakelocks (Android programming object used to keep the CPU running even if dozed) and block them if you want to. But the app may be useful for just tracking down battery hogs that are activated at 2am in the morning
Hope that helps! Good luck! :fingers-crossed:
Click to expand...
Click to collapse
Hi there. Thanks for trying to help!
I don't have TWRP, as I use stock ROM (phone has MobileIron installed for work use, so I can't have it rooted).
I already have wakelock detector installed on the phone, but I don't how many wakelocks during a night should be considered as OK or not...
ghnogueira said:
I don't have TWRP, as I use stock ROM (phone has MobileIron installed for work use, so I can't have it rooted).
Click to expand...
Click to collapse
True, you would need root to flash TWRP to allow backups/restores. However once TWRP is flashed, you could just install a ROM that does not have root and do not root it. That should pass all of MobileIrons checks which are mostly package name-based. In short, root is not required to keep TWRP installed. Something to consider.
ghnogueira said:
I already have wakelock detector installed on the phone, but I don't how many wakelocks during a night should be considered as OK or not...
Click to expand...
Click to collapse
Well, in reality you don't need any wakelocks active. Especially if you are asleep or not going to use the device for a while. Wakelocks can be doing anything from downloading advertisements for apps, to syncing emails with servers. You could block them all in a certain time frame, but that may be overkill. I suggest just going through the list of wakelock package names before you goto bed or when you know drain is at it's heaviest. The package name may be different from the name of the app, but it should give you something to go on. Just uninstall the heavy drainers or disable them enough so they can not drain you so much.
ghnogueira said:
Hi guys!
I desperately need some help from you experts. I have recently noticed my LG G3 has been draining more battery than it should, especially when idle (or at least, theoretically when idle).
Please take a look at the sequence of screenshots (have in mind the analysis was made overnight, when the phone was sitting idle on my bedside):
Screenshot 1: You can see app usage has been the biggest juice thief, and an abnormal drain (24%) for a (supposedly) idle period of 6 hours.
Screenshot 2: Kernel & Android system are the biggest villains, but only sums up to 45%.
Screenshot 3: Taking a deeper look at Kernel, it shows only 7 minutes of CPU usage.
Screenshot 4: A deeper look at Android system also shows a small usage, only a few seconds shy of 6 minutes.
Screenshot 5: On the chart, we can see there was an absurd drain (around 20%) from 1:30 am to 5 am, and then it got stabilized. Wifi was on the whole time, and you can see it shows the phone was (theoretically) dozed 95% of the time.
Sctreenshot 6: Even though the phone was dozed, we can clearly see it has severe CPU usage throughout the whole night, and no pattern could be distinguished between the hours were the battery got the severe drain and the hours after. Even though the CPU frequency was low between 1:30 and 5 (except for a couple of peaks), the utilization averaged 45%.
This is why I need some expert's help. I cannot understand what is draining my battery, what is keeping my phone's CPU util so high... can someone please shed a light on this for me?
Thanks in advance!!! :fingers-crossed: :good:
Click to expand...
Click to collapse
I'm in pretty much the same boat. I lose like 14-20% overnight and I have no clue why. Factory reset and it still seems to be that bad. I also use GSam and have almost exactly the same stats in terms of Android System and Kernel usage, so that means it shouldn't be an app thing (unless you and I have the same apps installed lol). I'm really at a loss as to why there is so much crazy drain.
AlwaysLucky said:
Well, in reality you don't need any wakelocks active. Especially if you are asleep or not going to use the device for a while. Wakelocks can be doing anything from downloading advertisements for apps, to syncing emails with servers. You could block them all in a certain time frame, but that may be overkill. I suggest just going through the list of wakelock package names before you goto bed or when you know drain is at it's heaviest. The package name may be different from the name of the app, but it should give you something to go on. Just uninstall the heavy drainers or disable them enough so they can not drain you so much.
Click to expand...
Click to collapse
I understand I do not need, but I meant how many wouldn't be "harmful". But I'll keep an eye in a night where this thing happens and get back to you.
Thanks for trying to help!
The same problem here. I lose 20% battery per night. Problem is only appearing on stock rom with stock recovery, I have installed Flumics and stock rom zip from TWRP - problem gone, but I need stock rom with stock recovery.
Hi All
Disclaimer: I'm new to the forum so apologies if this is in the wrong discussion area etc!
I got my Galaxy S9 on Friday 9th, prior to that I had an LG G5 which is now gone. In the last few months of using my LG G5 the battery life was questionable - the phone would get hot (sometimes without even using it a lot) and the battery would drain by 30% an hour. I noticed, but didn't test fully, that Google Play Music seemed to really cane the battery and phone - i.e. was getting hot and draining quickly. As an example, I'd leave home at 7am taking it off charge at the last minute (100%) and get to my office at 9am and it'll be at 50% and very warm. Prior to that (can't exactly pinpoint when the drain started to really kick in) it would only drop to 85% - much more acceptable.
The G5 has a replaceable battery - 2800 if I recall . So I threw down £50 on an official LG site for a new slab of Lithium - slight improvement, but still terrible and warm. 55% instead of 50%.
"Right - time for a new phone" as I assumed that 2 years of app updates meant the CPU was lagging. Bagged a Galaxy S9 - today was my first commute into the office. Started on 100%, arrived at 55% with a 3000 battery! And it got super warm like the G5.
Most of that time I used Google Play Music, which according to AccuBattery the discharge speed was "33% per hour". Second was Google Chrome at 30% per hour (though I didn't use it much at all on the journey).
My question is - what logs can I check, or apps I can use, or something to find out what's going on? I need to test a few things of course to pinpoint the issue. If it helps - I restored from my G5 when I setup my S9.
seems like you might have have some options enabled in Google Play Music / chrome - that is keeping the phone awake
generally when you switch phones they apps and their settings get transferred automatically now - worth maybe uninstalling them for a day and see if you're still experiencing this issue
other than that it could be that your commute involves travelling thru areas of no signal where the phone keeps trying to find a signal - that can drain battery a lot
tim2london said:
seems like you might have have some options enabled in Google Play Music / chrome - that is keeping the phone awake
generally when you switch phones they apps and their settings get transferred automatically now - worth maybe uninstalling them for a day and see if you're still experiencing this issue
other than that it could be that your commute involves travelling thru areas of no signal where the phone keeps trying to find a signal - that can drain battery a lot
Click to expand...
Click to collapse
Thanks - I'll try that next time. Might also try a factory reset but not restore from the LG G5 backup to see what happens then.
how bright is your display? do you leave it on all your commute?
Got your wifi enabled which hunts for a signal even though you aren't using wifi? try turning it off. Same with location setting.
And how strong a signal do you have on your commute. Streaming lots of data on a really weak signal will kill battery, too.
Go into settings and see whats draining your battery.
Battery Drain Issue of S9 - Resolved
:laugh:Hi All,
I could resolve the Battery drain issue but not touching any other setting of the new phone by just disabling the backend data usage of all application expect few like Edge screen, Gmail, Flipboard etc... Now the android system power usage is back to 4-5%. Previously it was 21%-25%. So issue resolved. Need to find out the way to inform this to Samsung so they can identify which app is consuming full battery power.
dondit said:
:laugh:Hi All,
I could resolve the Battery drain issue but not touching any other setting of the new phone by just disabling the backend data usage of all application expect few like Edge screen, Gmail, Flipboard etc... Now the android system power usage is back to 4-5%. Previously it was 21%-25%. So issue resolved. Need to find out the way to inform this to Samsung so they can identify which app is consuming full battery power.
Click to expand...
Click to collapse
Hi, i'm facing ridiculous drains too and factory resetting hasn't seemed to help. I'm trying your resolution, but I don't entirely understand you. Could you kindly guide step by step? also, if you mean going to optimise battery usage, when i go there and select the 'apps not optimized' all the apps there are greyed out therefore not allowing me to select them.