yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] yhrn:
But do you mean that you have around 6-7% drain per hour when the phone is idling? In that case I think there's a bit too much noise in your stats. If you do a full recharge, then reboot (needed to reset kernel wakelocks), then leave the phone alone for a while and then, finally, dump stats to file you will get much cleaner stats of what your phone is doing when it mainly should be sleeping.
[BetterBatteryStats] 18rmiller:
http://db.tt/3ywfun0P

I have attached a screenshot of alarms and a dump file for my battery stats. Last night I charged my phone to 100, put it in airplane mode and went to bed. Got up this morning and it was still full but drained pretty quick while using. The only problem I see is with kernel wakes and alarms. The first couple of alarms I know how to take care of but not really sure they are doing too much damage. I have no idea what to do about the kernel wakes . Can I get some help
[BetterBatteryStats] gorillaCF:
hey i tried it, and my phone got rebooted. any idea why? on stock rom XWKK5 with speemod kernel :/

anyway, i manage to go inside and saw that ccc is the main culprit of having the most counts. any idea whats ccc?

ok will try that! i'm assuming that my phone must be connected to the usb yea?
[BetterBatteryStats] MistahBungle:
Nope, no need to connect your phone to anything via USB. You need to get a terminal emulator app from the Market (there's plenty of free & paid ones to choose from).
[BetterBatteryStats] phoboss:
hey man, i'm using BBS on my SGS2 with MIUI Rom and get constant force closes. "others" wont open at all, and switching from one view to the other FC aswell. any idea why that might be?
[BetterBatteryStats] freaked:
I there guys.

I'm sorry if I'm a little dumb about this, but can you guys help me understand the dumpfile of BBS so I can solve my battery drain problem ?

What should I pay attention too ?

I already have the dump file but I wanted to know what are the main aspects that i should know to understand this battery drain.

Thanks in advance and best regards 2 all.
[BetterBatteryStats] t-pip:
I've disabled Latitude and now back to 2% per hour. Thanks for your help.
[BetterBatteryStats] yhrn:
This is where thread search functionality comes in handy ;)

... it's the Battery Monitor Widget.

---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------

Glad you found it :)
[BetterBatteryStats] tboooe:
Google Voice battery drain?

I am fairly certain that google Voice causes a fair amount of battery drain. Whenever I get a text message through voice I notice an immediate drop in battery. For example, this morning my phone was at 99% battery. I get 2 messages via Voice which I read. I then turn on my phone again about 10 mins later and notice by battery is down to 96%. It seems that once a text is received, Voice continues to wakelock the phone, polling for data??? When I look at BBS, I see that com.google.android.apps.googlevoice Update Service is holding the longest wakelock.

Anyone else seeing this?
[BetterBatteryStats] freaked:
I'm on 7hours 41% drop......

I really have to understand what this BBS means so I can fix this battery drain ...
[BetterBatteryStats] Karpfenhai:
How did you manage to get rid of latitude w/o loosing maps functionality? I tried TB and gemini, but its bundled to maps, please enlight me !
[BetterBatteryStats] chamonix:
OK here's the deal: I believe you haven't looked or at least have not tried to uderstand the information provided by BBS at all.

Above you will see an extract of the dumps summarizing the main things you should focus on.

The good news is: your phone is full of potential, the bad news: you will have to invest some time to learn how to leverage it.

I only have one doubt about awake / sum of kernel wakelocks. Before taking another reading I'd recommend charge your battery to 100% and reboot your phone so that we have the same baseline for kernel wakelocks and for the userland stuff.
[BetterBatteryStats] t-pip:
Sign out of out on maps.
[BetterBatteryStats] 18rmiller:
It says in the help to go back to the start to see the effect after deinstalling or freezing an app. Does that mean there is something that you can see right away or does that mean you have to put phone to sleep for a while and take another reading
[BetterBatteryStats] gorillaCF:
oh ok. let me try to find that. any of the apps in market that u'll recommend? (free is preferable haha)

ah ok. thank u. now i'm not sure whether is it ok to leave the BMW there anot. haha. thanks anyway.
[BetterBatteryStats] MistahBungle:
Terminal Emulator is free & does the job quite nicely. Tho any terminal emulator will do.
[BetterBatteryStats] Sincitybronze:
From reading through this thread, it is my understanding that better battery life is primarily a function of limiting app activity when the device should be inactive (i.e., standby).

If one has no problem with excessive wake lock frequency or persistence, is it logical to assume that there is excessive energy usage due to a radio (or modem)? I'm not sure if I'm using accurate language here but I think the point is clear.

If wake locks are a nonissue due to control of undesirable start up activities through Gemini, deactivation of autosync, and freezing problem apps through Titanium Backup, yet the battery drain continues to be severe, is it logical to assume that the problem is caused by the modem, wifi, gps, or bluetooth?

If so, why is JuiceDefender identified as a tool to be avoided? Is there something about turning off the radio that would be undesirable if there is no unwanted polling in the background?

I know it has been argued repeatedly in this thread that JuiceDefender offers no benefit to battery life. My two questions are 1) How significant can battery drain be as a result of just leaving 2G or 3G "on?" (assuming--theoretically--that there are no, or limited, wake locks) and 2) If there is some benefit to turning radios off, how, if not through JuiceDefender or similar apps, should one do so in a way that's less cumbersome than manually controlling this process?

Also, this is a great thread. The depth of analysis is good to see on XDA.
[BetterBatteryStats] chamonix:
The latter. A wakelock is something preventing your phone from sleeping so the better way to observe the effects of wakelocks / unwanted wakeups is to give the phone the opportunity to go into its favorite state (deep sleep), wait some time and check what prevented the sleeping
[BetterBatteryStats] freddysam:
Under Kernel Wakelocks, I have "usb_bus_active" with a time of 10 hours and 39%. Does anyone know what this is from and what it means? Is this just the charging time on usb?
[BetterBatteryStats] chamonix:
Let's try with an example:

assume we live in a perfect world; all apps behave properly, detect the presence of a data connection before using it and do not use wakelocks if they do not consider themself mission critical.

In that case a helper like JD would have no negative effect doing its job of switching data on and off regularly. The apps would wake up, check for data, return to sleep: no negative effect except for some apps not getting their data as often as in an always on scenario.

Now take a world where everything is non ideal: all apps would consider themself mission critical so they would use a wakelock to make sure their data transactions go through. And if for any reason data is not available they would get back to sleep after timing out but make sure they add an additional alarm for a wakeup at a tenth of the original frequency to retry connecting more often.

The result of that design would be frequent wakeups, each with a wakelock for the time it takes for the connection try to time out, let's say twice in a row.

Now I guess those cases make two things clear:

- turning data on and off has a negative effect in a real world

- the effect has chances to become more negative when many apps try to communicate and fail (assuming all of them use strict alarms to wake up)

In a perfect world jd would have a positive effect, in a bad world it would be the opposite. And as we have smartphones and no Nokia 6310i my experience is that the bad world model is a better model for the real world.

My own experience: turning data on and off (not using JD but tasker and Brandall's script helped me to tune my settings by amplifying the negative effects. After being finished the helper has been turned off because my wakelock profile is better without it.
[BetterBatteryStats] xdp:
Yep, I have had similar problems, have no idea why. Considering returning the device.
[BetterBatteryStats] It_ler:
[OT]

Congratulations mate for becoming a Recognized Contributor :victory:

Well done and well deserved IMO :good:

[/OT]
[BetterBatteryStats] chamonix:
Here it goes: some background info about why KitKat first broke BetterBatteryStats and forced me to find a not perfect workaround: http://xdaforums.com/showthread.php?p=47514548#post47514548

Please feel free to rate that thread and upvote the request.
[BetterBatteryStats] Peanuts.:
Vote done. Is a comment required?
[BetterBatteryStats] chamonix:
From the situation you describe (partial wakelocks are shown, kernel wakelocks are not) I assume you are not on kitkat.

I that case there are two possible explanations:

- your kernel does not expose kernel wakelocks (permissions)

- the format is not standard

Please check the permission on /proc/wakelocks (should be world readable). If it is the case please post the file in order for me to look at the format and see what is wrong (the file as attachement ond not inline) would be great fo me to do some testing.
[BetterBatteryStats] chamonix:
Thanks!

No comments are not required
[BetterBatteryStats] gabriolinari:
Hello

I know i played a bit when installed jb with autorun manager. Could you kndly point me to check the framework recivers?? I checked now and they are not listed anywhere under autorun manager. I know i removed bunch of stuff there...

Thanks

---------- Post added at 12:40 PM ---------- Previous post was at 12:36 PM ----------

Hi there

Did you manage to improve it?? 10% for 8 hours seems a bit high for me as wellm definitely more than what it was doing with ics before..

Also i noticed if i disable sync not much change. Again in ics that made a difference...

Any clues helpful guys.. i have root and new battery as well..

Thanks and have a great weekend everyone

Gabrio

---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------

Hi there

Did you manage to improve it?? 10% for 8 hours seems a bit high for me as wellm definitely more than what it was doing with ics before..

Also i noticed if i disable sync not much change. Again in ics that made a difference...

Any clues helpful guys.. i have root and new battery as well..

Thanks and have a great weekend everyone

Gabrio
[BetterBatteryStats] Socotroco:
Hi all,

I had upgraded my S4 to JB 4.3 and since then I have noticed that BBS is reporting a kernel wakelock that is unusually high, it's 'sec-battery-monitor', it's the first one in the 'kernel wakelock' list.

Does anyone has a clue how to reduce that wakelock?

Thanks.
[BetterBatteryStats] Shudder123:
I am getting this issue on my device right now. Not sure what the culprit is ask have GPS turned off at the moment

Anyone know ?
[BetterBatteryStats] tomurbanowicz:
I have got big MQTT (facebook) fakelock in CM10.2... Have You got that in CM? I'll check this in STOCK. (Galaxy S4).
[BetterBatteryStats] guido_glx:
You're right, I'm not on kitkat.

I'm on stock 4.2.2 with stock kernel.

I'd like to be able to upload the file, but I can't find it on my file browser. I don't have a /proc folder or at least I'm not seeing it...

What can I do? Uploading a dumpfile or a logcat would help you figure this out?

Thank you!

Enviado desde mi GT-I9100 mediante Tapatalk
[BetterBatteryStats] chamonix:
A logcat would only confirm but not give me enough info to find a fix.

The easiest way to go would I guess be to use a terminal. If you don't have one installed use this one: https://play.google.com/store/apps/details?id=jackpal.androidterm

Once installed open a shell and type:

ls -l /proc

the output should be something like:

-r--r--r-- root root 0 2013-11-16 14:05 uptime
-r--r--r-- root root 0 2013-11-16 14:05 version
-r--r----- root log 0 2013-11-16 14:05 vmallocinfo
-r--r--r-- root root 0 2013-11-16 14:05 vmstat
-r--r--r-- root root 0 2013-11-16 14:05 wakelocks
-r--r--r-- root root 0 2013-11-16 14:05 zoneinfo

So we can check that the file exists and its permissions (in that case world readable as it should be).

Then you can save the content to a file by doing:

cat /proc/wakelocks > /sdcard/wakelocks.txt

and upload /sdcard/wakelocks.txt here.
[BetterBatteryStats] kfallz:
So.. yeah.. Any help? (Galaxy S4 I9505) As you can see the per /h drain is still good, but, before it was even better at 0.3 - 0.5% per /h deep sleep drain. Uninstalling updates from google services seems to help, but that's not an solution imo. Gonna try an older modem again that gave me better % and see if this still happens but, would like to know what this reconnect stuff is? Google doesn't really help here
[BetterBatteryStats] Karpfenhai:
Read this:

http://xdaforums.com/showthread.php?p=47177180

Regards.

Tapatalked from my Galaxy SII
[BetterBatteryStats] chamonix:
First RC is up with final fixes and hints for Kitkat users to understand the situation.
[BetterBatteryStats] Perseus:
Google Play and Facebook seem to be your cause. Please follow this thread to contain Google Play

Follow the thread I have linked above.

Are you using an App called Line Free SMS ? If so

Post a Screenshot of Partial Wakelocks. To answer your question, this is a Cumulative Kernel Wakelock for Battery Service. Its usually seen when you have some form of "Battery Savers" like Juice Defender.

Is your Location Service completely off ?
[BetterBatteryStats] altusan:
Yes, but I used it before the update and it went ok. Is it the cause of the battery drain?
[BetterBatteryStats] mbze430:
Does it work with KitKat using ART?
[BetterBatteryStats] ernest101:
hey guys, please advice. Thanks in advance :laugh:
[BetterBatteryStats] palluk33:
My Wi-Fi is not on but is running in background

SGH-T999 4.3.1 pac man Rom Tapatalk (⊙o⊙)
[BetterBatteryStats] Perseus:
Yes.

The Wifi's Background scanning even when off is going on. Either that or the Wireless location by Google apps even when turned off. Both settings are under advanced Wireless settings.

3G Watchdog and the Blackberry messenger are draining the battery.
[BetterBatteryStats] warezxts:
Hi Guys!

I couldnt find any relevant information about my wakelock triggers, especialy related to Led (??)

Screenshot attached. Please help

+1 ELM Agent (com.sec.esdk.elm) is safe to freeze,am i right?
[BetterBatteryStats] skivnit:
Guys can you help with first wakelock

Sent from my Perseus powered octa
[BetterBatteryStats] aerozolic:
Converted Google Play services to user app and selected to greenify it. Auto-hibernate doesn't work with it. Even if I hibernate it manually, it shows as visible next time i start Greenify.
[BetterBatteryStats] chamonix:
I don't know. Be the first one to find out
[BetterBatteryStats] ernest101:
depends what rom you're using, but it's in the wifi settings, somwhere along the lines of "scanning always available" (for AOSP)

cheers mate, is there an alternative to 3G Watchdog which doesn't drain so much battery? I use it because I flash ROMs and i use the app just in case I can't transfer system data from Titanium Backup Pro.

and what can i do about the BBM besides uninstalling it?
[BetterBatteryStats] skivnit:
Getting the same thing it's driving me crazy

Sent from my Perseus powered octa
[BetterBatteryStats] maisi:
Works here with Art.

Gesendet von meinem Nexus 5 mit Tapatalk
[BetterBatteryStats] chamonix:
Google+ is responsible for 5 hours of awake. Either some backend problems or you should check your settings (maybe picture backup).

In the future please upload dumpfiles as attachments for a better readability
[BetterBatteryStats] anil2653:
No it is not working

In ART not getting root permission

But it is build 1.5 is working in dalvik mod
[BetterBatteryStats] imlgl:
Thanks, I'll make sure to do that next time, I don't even use Google+ so I'll remove it through Titanium Backup, thanks for the help :)
[BetterBatteryStats] Socotroco:
I made a BBS dump which I'll try to upload, but just in case I Copy/Paste, the main issue is the SEC-BATTERY-MONITOR wakelock.

================

Kernel Wakelocks !!! wakeup_sources !!!

================

sec-battery-monitor (): 1 m 58 s (118 s) Cnt:(c/wc/ec)79/1/0 1.9%

wlan_rx_wake (): 1 m 11 s (71 s) Cnt:(c/wc/ec)378/2/379 1.2%

PowerManagerService.WakeLocks (): 48 s (48 s) Cnt:(c/wc/ec)205/3/0 0.8%
​

I have uninstalled an app named 'Wakelock detector' to see if that helps but has no effect, the wakelock still there.

Any ideas?

Thanks.
[BetterBatteryStats] qwerty22:
About wlan_rx_wake.

I ran tcpdump. In the dump, I see many HTTP requests. One request per minute for a long time.

request:

GET /generate_204 HTTP/1.1\r\n
User-Agent: Dalvik/1.6.0 (Linux; U; Android 4.3; GT-I9500 Build/JSS15J)\r\n
Host: clients3.google.com\r\n

answer:

HTTP/1.1 204 No Content\r\n
Server: GFE/2.0\r\n

What application can be traced who is sending requests? How to turn them off?
[BetterBatteryStats] ICuaI:
Can someone pls help me with annoying AudioIn_22 wakelock? It appears since yesterday of my wifes phone. Can't post a log at the moment. Sorry for this. But it kept the phone awake the whole night, about 10 hours.

She didn't installed an app yesterday and rebooting the phone did not make disappearing this wakelock.

I would be thankfull for advices.

via Razr I & Tapatalk 4
[BetterBatteryStats] guido_glx:
Hmm I don't see wakelocks folder.

I've attached a screen capture.

Thanks again!

Enviado desde mi GT-P5210 mediante Tapatalk
[BetterBatteryStats] eep2378:
Just updated to latest RC1 from B5 and partial wakelocks are not seeing root privileges.
[BetterBatteryStats] chamonix:
Can you please be a little more specific? Have you enabled the advanced prefs for root? What error message are you seeing? Can you attach a logcat?

See also the first posts of this thread about reporting bugs
[BetterBatteryStats] chamonix:
You kernel does not write wakelocks. This is a standard output on Linux and I can come up with any reason why someone would remove that. Are you using a custom kernel?
[BetterBatteryStats] chamonix:
Could you please post a full dumpfile instead of snippets preventing is from seeing the whole picture?
[BetterBatteryStats] chamonix:
Come on guys. RC1 has 800+ downloads.... I need feedback describing error situations if any or confirming that everything is fine
[BetterBatteryStats] eep2378:
I apologize. Enabling root preferences under advanced menu seems to have fixed it. With the previous beta's I didn't have to enable this feature. I'm assuming because of your workaround on the beta releases? Now with RC1 there is no need for the workaround used in the previous beta's?
[BetterBatteryStats] Socotroco:
CHAMONIX the fifile is uploaded, but just in case here it goes again, thanks for your help.

Regards.
[BetterBatteryStats] chamonix:
No problem!

The workaround is still present and will probably stay (read this for more details).

The thing is that BBS has a policy of not accessing root until the user has enabled it in the advanced prefs. Now the betas did not respect that policy and called root even if that setting was not enabled: this has been fixed in the RC to make it consistent with the rest of the app.

Future version (2.0) will change that as it seems tedious to have to enable root at two places but for now I prefer to stay consistent but this is a future plan. There will probably be a 1.16 release before we start the 2.0 iterations
[BetterBatteryStats] eep2378:
Ah. Thanks for the clarification, that's what I suspected. BTW, this is an amazing app/project, been using it since my i777(SGS 2) a few years ago. Much respect! :D
[BetterBatteryStats] azrash:
Just to add, same here! Used it first with the G1, then the G2/Desire Z, now on the N4. Worth every penny!
[BetterBatteryStats] caplja:
ZeroWakeLag

Can anybody tell me what does this wakelock under partial wakelocks means?

I have just flash fresh clean NEAT rom with Apolo 4.12 kernel on my SGS2 and I'm having huge wakelock under this name. Interesting is that wake lock time is the same as total time of phone being used on battery BUT battery usage is ok, about 2%/hrs !? :S
[BetterBatteryStats] masterchif92:
Anyone can help me with this wakelock?
[BetterBatteryStats] chamonix:
http://xdaforums.com/sitesearch.php?q=ZeroWakeLag
[BetterBatteryStats] chamonix:
sec-battery-monitor (https://github.com/wanam/Adam-Kernel-GS3/search?q=sec-battery-monitor&ref=cmdform) is a wakelock that is held at a kernel when the battery level is read. This occurs when the phone wakes up so it's a symptom, the cause is a wakeup. Unfortunately your dumpfiles is incomplete and does not show alarms so I can't tell you what causes the wakeups but alarms is the chapter to look into
[BetterBatteryStats] Socotroco:
Might these screenshots help?
[BetterBatteryStats] chamonix:
Guys I may break the rule and add something to 1.15 even if normally for RCs the code is frozen. Let me know if you want to see this feature added or if I should keep it for the next release:

Edit: image was borked
[BetterBatteryStats] Karpfenhai:
Do it, question is, does it work on unrooted devices?

Tapatalked from my Galaxy SII
[BetterBatteryStats] chamonix:
Nope :-/ On unrooted devices we are stuck with missing functionality thanks to Google (see my rant here: http://xdaforums.com/showthread.php?t=2529455)
[BetterBatteryStats] chamonix:
RC2 is up, adds the ability to install BBS as system app (requires root). If you don't have kitkat there is no point in doing so (there may be in future as we could avoid a few root calls and speed up processing).

Now because of the changes made by google BBS has two ways of processing stats on Kikat, depending on whether the app is installed as system app or not:

- Other stats: as normal app (with root) the available info is reduced, without root is only has awake, deep sleep and screen on, as system app the data is complete

- Partial wakelocks: as normal app (with root) the partial wakelocks are accessed using a fully features workaround, without root no luck at all, as system app the data is complete

- processes: - Partial wakelocks: as normal app (with root) the processes are accessed using a fully features workaround, without root no luck at all, as system app the data is complete

Of course I keep on searching for a workaround for non rooted devices to get partial wakelocks but for now that's all I have. For those who missed the post I have written a short rant explaining what happened with Kitkat and why it is that bad: http://xdaforums.com/showthread.php?t=2529455
[BetterBatteryStats] biliskner:
Thanks. Just updated to 4.4 on SNote2 and this is the only battery wakelock monitor that's got some traction in updates. Installed and will update tomorrow
[BetterBatteryStats] Peanuts.:
I've gone into the bbs settings & selected the "Not installed as system app" button and it comes back with Failed.

I then used Titanium Backup to convert the app to System, restarted device. But it's still showing a dialog saying "Failed".

Wondering if I'm doing this right or not?

Please see the screenshot below
[BetterBatteryStats] anil2653:
It will be good thing to overcome this issue

Better to do it :thumbup: