[Q] betterbatterystats entry - Xperia Arc Q&A, Help & Troubleshooting

hey guys, hoping someone can help. been using BetterBatteryStats for a few days now to try and monitor my battery drain. I have noticed that under "kernel wakelocks" i get the entry "bq24185_watchdog_lock" and its time over a couple of hours is 25m+.
just wondered if anyone knows what this is and also if this is normal. I am currently using latest BlendMIUI with latest Blend kernel (v9).
thanks in advance
Brezzz

Watchdog is a part of linux kernel which monitors the state of your device. Watchdog needs to recieve a particular event for it not to get triggered.
In human understandable terms watchdog is like guard of your phone. It will reboot the phone if you don't feed it with information so as to protect your phone from total breakdown.
Example scenario is if you installed a program and run it then your phone freezes. Obviously your phone would stop responding thus can't feed watchdog the necessary info it needs so it will reboot the phone to protect it from further damage. So yes it's common I think that watchdog is like that.

brilliant, thank you for your quick response and help
Brezzz

Related

Android System High Usage

Hi guys,
Anyone have an idea what would cause my battery stats to have very high "Android System" usage all of a sudden. No new apps installed.
Thanks
I'm seeing this get pretty high as well. Starting to wonder... TW really limits the information in the Battery Status dialog. Hopefully we'll get ROMs soon that have more detailed information like I had in MikG.
Splaktar said:
I'm seeing this get pretty high as well. Starting to wonder... TW really limits the information in the Battery Status dialog. Hopefully we'll get ROMs soon that have more detailed information like I had in MikG.
Click to expand...
Click to collapse
Did you recently start seeing this? Or has it been from the beginning?
mikea3000 said:
Did you recently start seeing this? Or has it been from the beginning?
Click to expand...
Click to collapse
It has always been a bit higher than I am used to. I just grabbed the new version of betterbatterystats from here: http://forum.xda-developers.com/showthread.php?t=1179809
Hopefully I can use this to figure it out.
Sent from my SGH-T989 using Tapatalk
Splaktar said:
It has always been a bit higher than I am used to. I just grabbed the new version of betterbatterystats from here: http://forum.xda-developers.com/showthread.php?t=1179809
Hopefully I can use this to figure it out.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Please keep me posted if you find anything
System Panel works really well for me I found. Paid version is totally worth it, too.
Just another thought/question...
I am assuming since it is "Android System" causing such high usage ( I have 5% battery left and android system is 30%), that it cant be an app I installed causing the issue.
It has to be something that is either part of the stock ROM (I am stock, not rooted) or something core to the android operating system. PLease let me know if you agree with my logic that it cant be an installed app.
Just trying to find the root cause at this point or determine if I have to hard reset which I dont feel like doing.
Thanks again
The original SGS2 has an issue similar to this.
http://forum.xda-developers.com/showthread.php?t=1290020
They discovered with it that the processor has to ramp back up to 800MHz to do its pre-deep sleep tasks, in addition to taking longer than normal to do those tasks. So with a phone that woke up often to sync, even limiting the processor to 200 MHz with the screen off, it still spends a considerable amount of time at 800 MHz. I don't think they have a fix, but you can work around by limiting the amount of syncing the phone does while sleeping.
Don't know if this is related, since TMO SGS2 doesn't use the Exynos.
Thanks for the reply. My problem is that the battery usage for android system used to be 5% or less and now out of the blue is 25-30%.
Did you change any sync settings? Setting up an email account or maybe a widget to sync could do it. The phone has to do a bunch of system related tasks when it wakes up and goes to sleep, and those fall under "Android OS", so even if it is waking up to sync for an app, the system still has to do stuff, and more than usual when coming out of sleep. Like the other thread said, the original SGSII does all these things at a far higher clock speed than it needs to, and takes longer than most phones do.
I myself don't have the phone yet, nor do I have an original SGS2, but you could look up much of the same information the gentleman who wrote up the OP in that thread I linked to see if the issue is related.
I was so annoyed with this issue that I decided to do a factory reset. I dont think it helped.
So far after being off the charger for 2 hours....I sent 5 texts, browsed web for about 5 minutes. I am down to 87%. Display time is 46%, used for 18 min and android system is 17% with stay awake time at 3 minutes, and there are other items taking up battery at 5% or less like cell standby, android os, market
Does this seem normal, I never rememver android system taking up over 5% even with little usage. I am actually pissed because I would have thought that a factory reset would have helped for sure.
BTW, I am only syncing one acct, Google
I've been watching with betterbatterystats for a couple days now. I've got Skype running in the background so I expect that to use some battery and cause some wake ups.
But it has turned out that location services and updates have been doing a lot more, as much as 7000 in one day. They show up as something related to Maps, but I think that it might be Latitude. So I have disabled that location tracking. We'll see if it helps, there isn't much more using my battery. It is just something keeping it from deep sleeping.
If this doesn't work I'll look at other location apps like weather and such. I already uninstalled Accuweather after reading about how they transfer your location tracking information over the Internet unencrypted!
Sent from my SGH-T989 using Tapatalk

Android OS killing battery

Hey everyone
Got a Nexus a couple weeks ago after having iphones for a couple years. Loving it so far.....ICS is very polished.
Initially, my battery life was adequate. However, recently the OS is using 45% battery and the phone gets a very hot when idle (I can feel the heat in my pocket)
I did a factory reset and still the same problems.
Is anyone else coming across these issues?
An old bug cropping up again?
http://forum.xda-developers.com/showpost.php?p=13247149&postcount=57
Can you please install Watchdog (https://market.android.com/details?id=com.zomut.watchdoglite) and let us know if it's the suspend process (which shows up in the battery meter as part of "Android OS") burning through the battery?
My phone has been on standby for about a day and has 80% battery left. However the battery consumption shows:
42% Android OS
37% Phone Idle
16% Cell Standby
- Also what is the difference between phone idle and cell standby
MY BACKGROUND APPS RUNNING ARE:
- Battery Monitor Widget (I need this on so I can tell what my battery life is easily)
- Google Services (What is this, can I kill it?)
Media (What is this app, can I kill it?)
Music (Again what is this, what happens if I kill it/should I? I never used it.)
I have the same problem. My SGN died after 7 hours without any usage.
Sent from my Optimus 2X using XDA App
Yup, me too. This morning, I took my phone off the charger at 98% for an hour and 15 minutes and didn't touch it. The battery had gone down to 88%, with Android OS using 64% and Android System using 14%. The phone was 'awake' for the entire period. I've had my Nexus since Wednesday and I haven't been getting great battery life. I'm hoping there's a fix for this.
Same problem here... (I testing radio UGKK7, XXKK7 and XXKK1... all with the same problem).
- Lightflow increment "Android OS" battery use.
- By using, Wi-Fi "Android OS" uses less battery.
try disable wifi when not on and unchecked "use wifi network" for location.
another thing could be some active widgets, i remember this was a problem a while back.
Note sure that this has got to do with wifi at all as I reset my phone to factory and I still have the 'Android OS' usage taking 23% of battery. I have no apps nor have I yet linked phone to my Google account.
I have read some comments to do with the Galaxy S2 which too suffered from the same problem. I remember reading something about Samsung driver implementation causing this with the S2. I will update the links when I find something conclusive. Also I have another HTC desire that has the AOSP code compiled rom and that does not suffer from this at all and it is happily sitting idle at almost 2 days with nearly 70% battery still left.
s1977 said:
Note sure that this has got to do with wifi at all as I reset my phone to factory and I still have the 'Android OS' usage taking 23% of battery. I have no apps nor have I yet linked phone to my Google account.
I have read some comments to do with the Galaxy S2 which too suffered from the same problem. I remember reading something about Samsung driver implementation causing this with the S2. I will update the links when I find something conclusive. Also I have another HTC desire that has the AOSP code compiled rom and that does not suffer from this at all and it is happily sitting idle at almost 2 days with nearly 70% battery still left.
Click to expand...
Click to collapse
Yes, the problem was with the suspend process eating up CPU. You can install Watchdog and set it to watch non-Android processes, and that will be able to tell you which "Android OS" process is actually the one eating up battery.
Chirality said:
Yes, the problem was with the suspend process eating up CPU. You can install Watchdog and set it to watch non-Android processes, and that will be able to tell you which "Android OS" process is actually the one eating up battery.
Click to expand...
Click to collapse
Is samsung aware of this problem? We need to file complaints.
Sent from my Galaxy Nexus using xda premium
Do you have your email or anything set up to receive things instantly? That can have a noticeable impact on your battery if so
Thanks Chirality, but I assume that this is happening to all users? Samsung have seen this before so shouldn't this be fixed from the very start? Wrong person to ask this question to, but it is annoying..
Anyways I will install Watchdog like you say, but unless I can kill the 'suspend' process, I am helpless.
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
xHausx said:
Do you have your email or anything set up to receive things instantly? That can have a noticeable impact on your battery if so
Click to expand...
Click to collapse
No, that's why I reset the phone to factory settings and the current behaviour is without any apps, or registration with google, no emails, nothing installed.
---------- Post added at 10:03 AM ---------- Previous post was at 10:00 AM ----------
Additional links indicating the problem and response:
http://androidforums.com/samsung-galaxy-s2-international/337492-s2-battery-drain-problem-solved-now.html
http://code.google.com/p/android/issues/detail?id=16721
Is there anything in the logcats that could hint to a problem? Like errors or something unusual that it keeps repeating
I have the same problem with high system CPU usage. I used SystemPanel to monitor the phone (unplugged, standby mode) during my 8-hour sleep and here's the results.
The System Processes were using 49min of CPU time while the phone was idle
When I clicked on the system processes I got a list of individual processes. Anyone knows what are there kworker processes for?
When I clicked on one of the System Processes (kworker/u:1), I got its CPU usage. It was doing something almost the whole time
Finally, I should also mention that the phone lost about 7% in these 8-hour test. Seems ok but I think it would be even better when this high system CPU usage is fixed.
xHausx said:
Is there anything in the logcats that could hint to a problem? Like errors or something unusual that it keeps repeating
Click to expand...
Click to collapse
Hmm...Now that you asked this, I remember watching logcat output and was getting a null Notification event almost one every minute a couple of days back. I therefore proceeded to uninstall all my widgets/apps but I could not reach to a conclusive outcome.
Anyways as Chirality pointed out this post (Link) indicates a 'suspend' process issue. And this guy identified the process causing it (Link), I think!
s1977 said:
Hmm...Now that you asked this, I remember watching logcat output and was getting a null Notification event almost one every minute a couple of days back. I therefore proceeded to uninstall all my widgets/apps but I could not reach to a conclusive outcome.
Anyways as Chirality pointed out this post (Link) indicates a 'suspend' process issue. And this guy identified the process causing it (Link), I think!
Click to expand...
Click to collapse
A driver issue definitely sounds plausible but there are also a lot of things different between these two phones, especially between GB and ICS.
Watching /proc/kmsg should show something if it is an issue with the kernel
xHausx said:
A driver issue definitely sounds plausible but there are also a lot of things different between these two phones, especially between GB and ICS.
Watching /proc/kmsg should show something if it is an issue with the kernel
Click to expand...
Click to collapse
Do i need to be rooted to be able to read this?
Chirality said:
Yes, the problem was with the suspend process eating up CPU. You can install Watchdog and set it to watch non-Android processes, and that will be able to tell you which "Android OS" process is actually the one eating up battery.
Click to expand...
Click to collapse
Chrality, xHausx
I have installed Watchdog and set the settings to what you indicated. I am a bit confused around the app, so I have added screenshots to update you of the data at my end.
Do let me whether you see the issue immediately or need any further information.
My experience is somewhat the same.
Out of the box battery life seemed pretty good. After the update to fix the volume issue I started to notice that the battery would fall even when the phone was idle. Android OS was the culprit. I am now running MCR and I have the same issue.
It's not terrible battery life, but it's substantially worse than it was out of the box.
I did wonder if the problem was related to how they fixed the volume bug. Is something always running to pick up the volume bug problem and deal with it when it happens?
Just a thought.
paulpenny said:
My experience is somewhat the same.
I did wonder if the problem was related to how they fixed the volume bug. Is something always running to pick up the volume bug problem and deal with it when it happens?
Just a thought.
Click to expand...
Click to collapse
Interesting. I've been thinking the same thing, and the annoying thing about that is the problem doesn't affect my network (T-Mobile), so I could be getting reduced battery performance for no reason! Ah well.

[Q] 'loop' and 'flush' processes issue

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!

[Q] Strange procesos drianing battery somebody know what is?

Hi everyone i have an extreme drianing battery with a no name process only a stick of android somebody can help me to fix it or what kind of app is doing this? Thanks. more info on pictures
pochin01 said:
Hi everyone i have an extreme drianing battery with a no name process only a stick of android somebody can help me to fix it or what kind of app is doing this? Thanks. more info on pictures
Click to expand...
Click to collapse
Go into settings then apps then running on your phone and see if you can see anything there, check for connect (moto connect) tap it and see what is running. There are likely 4 processes, if you have wakelock detector you could use that also to possibly narrow it down (requires root). Also check your location settings the watch could be using GPS to find your location which will affect both batteries (phone and watch).
I have the same thing. No processes under running apps on my phone that standout
Download cpu spy from playstore and let it run for a while. See if your phone is entering deep sleep after about half an hour. I am going to guess it is running at 300mhz and no entering deep sleep. What this will mean is the watch is communicating with the phone and not letting it sleep. Would be helpful to know what you have running on the watch ie. fit, moto body, google now cards and how many...
Just received my Moto 360 too. Got the same processes. And also a kind of very high android wear usage...
What do you guys have turned on? ambient, tilt to wake, card previews? I have all that turned off on mine, for me, watch idle is at the top followed by android wear 16% idle, 4% android wear.... then some other lower numbers.

Help understanding battery drain

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.

Categories

Resources