yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] chamonix:
Indeed, your phone only sleeps 50% of the time. I suggest you look into the alarms chapter: you will find two apps causing lots of wakeups. Looking at data traffic I see facebook (known drainer, fb devs needs to learn how to write android apps)

Fix those obvious causes of drain and repost a dumpfile
[BetterBatteryStats] -viperboy-:
Also, since this guy has an S3, try turning off auto rotation. I found that to be draining my phone with screen off and have found other Samsung owners mentioning the same thing.
[BetterBatteryStats] umermajeed:
I was unaware of this. I have enabled the root features. Network stats was already checked, I've checked the process status as well. will post logs after some idle time. Thanks.
[BetterBatteryStats] mrcorey:
Just an fyi to anyone using the eBay app. It still polls when you unchecked the notifications. This may be the new update introducing this behavior though. I've chosen to keep it on my phone but freeze it with tb.
[BetterBatteryStats] Karpfenhai:
Freezing is not necessary, disabling all autostarts is sufficient too!

Plus, this is not a new information :)

But thx anyway!

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Rob1965:
Samsung Galaxy Advance never goes in deep sleeping mode

Hi all,

I experience a severe battery drain issue in my Samsung Galaxy Advance Phone.

In order to identify the reason, I bought and installed the BBS app both on my Samsung Advance (Gingerbread) and on my previous HTC Desire (Froyo) phone. All the apps installed in the Samsung phone are also present in the HTC one, however I experience this issue only in the first one.

The issue seems to be originated by Google Maps location services, however I need to have Google Latitude running! No battery issues on my HTC phone with the same Latitude!

Please find attached the BBS logs, hoping someone could help me to understand how to solve the issue.

Thanks in advance.

Roberto
[BetterBatteryStats] grognaz:
im trying to trace down a 1min wakelock interval but i lacking a bit of details from this app:(

i end up with the app pointing out the "NetworkLocationLocator" com.google.android.apps.maps.Maps as the cullprint (count:934 after ~9h), however i assume this is triggered by some other app than google maps itself right?

so what i did is installed an other app that i know can show what apps are using a certain "permission" and checked whats using the Approximate (network-based) location that google maps does.

however the only new thing in there that i can see is the gallery from 4.2 which i flashes some days ago o_O i disabled that to see if its the problem but i would like to know if im searching in the right place or how one continues after having knowledge which process causes the wakelocks. is there a different app that gives me apps by processes similar to the permission app? or how do i find out whats behind that process?
[BetterBatteryStats] Jennnn:
Hello guys,

my battery lifetime is like 14h, i know ppl with the same phone and they got 2 days+, i dont really know why my battery drain is like that or why my screen never goes off (only the light goes out) if that has something to do with wake ups.

I've attached a BetterBatteryStats log and an Alarmdump file.

I hope you can help me, thanks in advance =)
[BetterBatteryStats] cool1007:
Hello,

I'm back again, this time with an idle log. I'm running a matching modem / ril UHLPG , and Rootbox 3.1 with Dorimanx 7.15.1.

Please take a look at it.

Thank you,
[BetterBatteryStats] Karpfenhai:
No, you are not, this dump contains just a minute, we need 4-6 hours for a reliable result, sorry mate.. :o

Tapatalked from my Samsung GT9100

---------- Post added at 08:45 PM ---------- Previous post was at 08:42 PM ----------

Hmmm, your phone is barely sleeping at all, but you are using a release candidate which may contain bugs, please update to the most recent version and provide another dump, thx.

But..an idle dump this time..

Tapatalked from my Samsung GT9100
[BetterBatteryStats] rabidpencil:
I always charge my phone at night, so to see if my battery drained fatter than it should I left it off the charger last night. I lost 50% in 6 hours (3500 battery). I use better battery stats and I did a logcat and a "dump to file". Would anyone be willing to look at it/them? I don't know if tasker changing the profile for screen on/off is bad, it mentions my alarms, or what. Thanks. I can't seem to attach anything but pictures with the xda app though
[BetterBatteryStats] f_padia:
Yes I see that as an option but it doesn't actually display how long that is. All I know is 'since charged' but I'd like to know how long ago that was
[BetterBatteryStats] DanielMalmgren:
Same here on a Xperia X10 mini running MiniCM7 (which is kinda CM7). Only blackness. I'll try to get a logcat next time I'm at my computer.

/Daniel

edit: Ok, this is strange. I was just about to send my logcat to chamonix but I thought I'd rather try again and let it run for a while (in case something interesting would turn up in the logcat after a while) and then suddenly it works! Is it normal for this app to take like minutes to start the first time?
[BetterBatteryStats] jonny68:
Just downloaded will test thanks..
[BetterBatteryStats] veyka:
Fantastic app, just what the doctor ordered!

Lack of wakelock and detailed info in the GB battery stats is awful.
[BetterBatteryStats] chamonix:
No it's not, it's rather a sign that I'm spoiled with my dual core SGS2 and should spend some time profiling the app to see why it takes so long (todo for me added). Just out of curisity: did it open the "Process" of "Wakelock" list?
[BetterBatteryStats] f_padia:
Mine doesn't open process list. On HTC hero.
[BetterBatteryStats] iRide113:
I have a Gmail account syncing push because you cannot change that,

And a FaceBook syncing at every 6 hours.
[BetterBatteryStats] LuffyPSP:
Guys, i have set my latitude to manually. The network location/maps still in wakelock. Do i need to sign out from latitude?

Nuked from Galaxy S II conquered by VillainROM v2.1.0
[BetterBatteryStats] nobnut:
If you are signed in to Latitude at all it will still seek your location. To remove the wakelock you have to sign out of Latitude altogether.

Sent from my Motorola StarTac using Voodoo
[BetterBatteryStats] LuffyPSP:
thanks. done. now after full charge i'll be testing it out again.
[BetterBatteryStats] shpapy:
hello,

i got optimus 2x , rooted with v10c and bb622

after 1st startup the app had to be F.C

after the 2nd startup it works.

if u need some logs let me know.
[BetterBatteryStats] DanielMalmgren:
Yes it did. Also it does start a lot quicker now, seems like it was only the first time that took long time.

edit: Haha... I realize now that was a kinda stupid answer, right? :-) Well, it opened the process list. Didn't see the end of the question on my tiny phone screen...
[BetterBatteryStats] chamonix:
That would be great if you could send me an extract of logcat where a callstack trace ist to be seen. Thanks for your suport
[BetterBatteryStats] chamonix:
If I were you I'd try to reproduce and if it happens again try first to disable facebook. If it solves the wakelock you have narrowed it down a bit more.
[BetterBatteryStats] chamonix:
Lol, there are no stupid answers just wrong questions ;-)

As the process list is the longest I'll start profiling that. Thanks for the feedback
[BetterBatteryStats] nobnut:
Hi Chamonix,

This may be asking the impossible...

EDIT: but to avoid users asking for different time in state or start points, might it be possible to set a 'start point' for BetterBatteryStats to run from? Possibly a button in the app to click and then results are recorded from that point. I'm not sure how this might be achieved, possibly an entry written to logcat.

Just a thought.

Thanks again!

Sent from my HTC Flyer using vodka
[BetterBatteryStats] chamonix:
That's indeed an interesting idea. As I'm still not sure to have understood "current" and "last" correctly I have planned (see features) to have a look into those and I'll look if there is a way to tell the batteryservice to reset its stats upon uder action.
[BetterBatteryStats] chamonix:
BetterBatteryStats 0.5.1

New version's out for you guys:

- improved performance of process/wakelock lists

- better name resolution for processes giving more insight to the origin of cpu activities

Enjoy!
[BetterBatteryStats] chamonix:
I'd like to hear your feedback about performance on single cpu devices. If you feel it's still not reactive enough I have some ideas left but that would steal time for implementing features so it's up to you.
[BetterBatteryStats] Szczepanik:
Performance on single CPU devices

No problem installing on my HD2 nor with performance. Main concern is understanding what it all means. A useful features would be selection & copying items to paste here. It has helped me spot that Facebook and GPS were running so it has been very useful.

Lots of people have the 60ma drain problem and if you can guide them on resolution that would be great. Maybe a Wiki with common problem entries and meaning of / resolution?

Cheers

Tom
[BetterBatteryStats] carlos67:
Actually, freezing google services framework (gsf) stops Market app from running at all. It just won't open. Tried it twice - same result. Unfrozen it and market works again although you have to log into google services again on first run. I tried freezing it because it was appearing in my wakelocks list quite heavily, but if you want the market, you have to leave it well alone!

Regarding gtalk, I have had this frozen now for weeks and weeks without any ill effects at all. However, I still wonder why gtalk_async_conn still appears in wakelocks list. I "think" gtalk_async_conn is linked in to something else other than just gtalk app. If this is not true, then why does it cause wakelocks when gtalk is frozen?

Edit: Hmmm, I wonder if unfreezing gtalk would eliminate the gtalk_async_conn wakelocks. The fact it's frozen might actually be causing the wakelocks. Might give that a try.
[BetterBatteryStats] nobnut:
You could also delete the apk from system/app or data/app, wherever it it is residing. You can also uninstall it with Titanium backup. Then reboot.
[BetterBatteryStats] codryn:
ty for your answer.Now I`m using Gemini App Manager to disable all my apps startup and deleted everything with .laputa because I don`t use that. From last nigh battery is 100% and I`ll be posting again with some results when battery will be 1-2%
[BetterBatteryStats] k1000716:
Damn, I was looking forward to having a tinker with the files to get it working...

Deleting the apk and uninstalling via tb worked perfectly. I'm now running the market version.

Thank you. :-)

Sent from my GT-I9100
[BetterBatteryStats] Jason93:
Can somebody help me what to do??Android OS is very high and also I have high battery drain when not using the phone.Maybe some crappy apps.Check the attatchment.
[BetterBatteryStats] nobnut:
That's a pretty impressive set of statistics! But not in a good way. As you can see your phone is rarely gong to sleep with the screen off and when it does, it isn't for long before it wakes up again.

The most significant causes of wake in your case appear to be alarm based:

AlarmManager (Android System): 6 h 11 m 43 s (22303 s) Count:2816 29.4%

SyncManagerHandleSyncAlarm (Android System): 3 h 43 m 6 s (13386 s) Count:959 17.6%

There are a few things you can do, including removing calendar reminders, not using too many alarm clock functions (turn them off when you don't need them - don't delay/snooze them, dismiss them), for more hints, search this thread.

Event Log Service (Google Services): 1 h 3 m 58 s (3838 s) Count:184 5.1%

I'm not quite sure what is causing this. Googling around a little leads me to believe that it may be linked to the above. Maybe Chamonix has some thoughts on this.

com.motorola.blur.service.sync.engine.wakelock.notification (com.motorola.blur.service.blur.Motorola Services): 26 m 57 s (1617 s) Count:100 2.1%

If you check back a few pages (or search) another Motorola user had a similar experinece and Chamonix provided some useful information/suggestions.

*sync* (com.google.android.apps.docs.Docs): 16 m 4 s (964 s) Count:38 1.3%

*sync* (com.google.android.gm.Gmail): 14 m 12 s (852 s) Count:66 1.1%

This obviously relates to Google Docs and Gmail. Check your sync settings. Do you actually need to sync Docs? I use Docs but have removed the app's autostart permissions and I sync manually when I need it.

WakelockMonitorSvc (Android System): 12 m (720 s) Count:419 0.9%

This will go down when you sort out the other partial wakelocks.

KpiLogger (Android System): 10 m 36 s (636 s) Count:1426 0.8%

Lots of people searching for this and a solution on Google. Not much by way of definitive answers. Some users reported seeing it in Titanium. If you have it, freeze it (make sure you have a Nandroid backup in case however!)

Do you have lots of calendars? Your above wake seems extremely high for a 'normal' calendar user.

No attachment.

Do you have any apps installed which disable the lockscreen, or hide/show the keyboard? Possibly swype related. You could freeze/uninstall swype for a few hours and test to see if it improves.

11 minutes is not amazing but it isn't too bad in 3 hours worth of use.
[BetterBatteryStats] Jason93:
Edit:It's ok now.Check it out
[BetterBatteryStats] DarkSorcerer:
Disabling the lockscreen.. ? I didn't even know that was possible for an app. :)

As for swype, I'm using the most recent beta. Suddenly, this drain stopped, curiously. It only added 1second more in the last 5 hours.

Another question:

SyncManagerHandleSyncAlarm (Sistema Android): 4 m 32 s (272 s) Count:56 18,4%
*sync* (com.google.android.gm.Gmail): 1 m 16 s (76 s) Count:34 5,2%

Isn't this redundant (two instances for the same thing)? I mean, in accounts and syncing I have Facebook (disbled), Twitter (disabled) and only Gmail is syncing... Does this means FB or Twitter are misbehaving?
[BetterBatteryStats] nobnut:
Not too bad. Nothing to get upset about but things can always be improved.

Easy, three words... Maps Maps Maps is your biggest issue. Or to be more precise BackgroundFriendService. In other words, sign out og Google Latitude... unless you want it running.

BackgroundFriendService (com.google.android.apps.maps.Maps): 3 m 29 s (209 s) Count:14 0.4%

RILJ (Dialer): 1 m 16 s (76 s) Count:875 0.1%

AlarmManager (Android System): 1 m 13 s (73 s) Count:2172 0.1%

For RILJ and AlarmManager, search this thread for some great tips.

All apps misbehave sometimes. But if you have turned syncing off, I suspect they are not the cause of the problem. Check you Gmail sync settings. E.g. every hour is better than every 5 minutes.

Also different phones (manufacturers) behave differently, so an HTC Sensation might be very efficient with regards to Location services, whereas a Motorola Atrix might be much better at syncing email (I made that up as an example before I get blasted by anyone).
[BetterBatteryStats] DarkSorcerer:
Thank you for your help. :)
[BetterBatteryStats] chamonix:
thank for your feedback nd for showing your support.

I would be very grateful if you could help us finding a way to help litening users and solve this problem by providing a clean way to get rid of the app included in litening. If / when such a solution is reached I'd bw happy to link it to the market's description as well as here in post 1 with proper credits.

I would really like to help the litening users that can not use bbs because of an ignorant and arrogant OP (litepro).
[BetterBatteryStats] nobnut:
You forgot 'talentless' and 'thief'.

Sent from me to you using stuff
[BetterBatteryStats] nobnut:
Titanium can be used or just remove the apk from system/app or data/app... whichever he put it in.

Sent from me to you using stuff
[BetterBatteryStats] chamonix:
Anyone with that rom installed with a little spare time to help?
[BetterBatteryStats] k1000716:
As nobnut suggested, I used root explorer to delete the apk from system/app, then rebooted. It worked fine.

Luckily I have cwm back-ups from before and after, so can help if you want me to try something else.

Sent from my GT-I9100
[BetterBatteryStats] Sycobob:
I installed BBS this morning, and I'm loving the app. I'm investigating what kind of battery life is possible from my Photon, and I'm having just a bit of trouble understanding the app.

I did a factory restore and I've only installed BBS and screengrab currently. I have never opened any of the preinstalled apps like messaging and my email does not currently sync. I noticed what appeared to be a high wake time before the restore so I'm seeing what the wake time looks like with nothing interfering, then I'm going to watch it closely as I add apps one at a time.

The main problem I'm having is what appears to be conflicting information on awake time. For example, sorting by partial wakelocks I see this:

which makes me nervous (it's out of 15.5 hours). It looks to me like Google and my alarm are sucking up a significant amount of awake time. But when I go to other, I see this:

Only 35 minutes of awake time versus >4hrs according to the other screen. Also, the Gingerbread battery usage plot shows a decent amount of awake time:

So I'm not sure what to make of it all. The partial wakelocks screen and battery usage plot point to high wake time, but the other screen and the knowledge that nothing at all is installed or syncing says it should be the lower amount.

Is anyone able to point me in the right direction here for figuring out my awake time?

Other questions:

It looks like Froyo used to show both up time and awake time under Settings > About Phone > Status, but I'm running Gingerbread and I only have up time shown here. Is there any way to check the awake time (value, not bars) from Android itself?

Does anyone actually know what the color of the line on the battery usage plot means? It changes between green, yellow, and red (not the phone signal, the graph itself).

If you look back at the battery usage plot, the first 10% drops faster than the rest. Normally it's much worse too, within 5 minutes. Any ideas what causes this?

Some of the items listed under partial wakelocks have quite high counts, is this normal?

Sorry for the huge post, just trying to optimize what I can.
[BetterBatteryStats] mi3x:
Hey guys, I have a dilemma.

So I have the Awake time 2h 24m and the Screen On + Phone On time is about 2h 31m. Isn't that weird?

So screen on surely means the phone's awake and Phone on as well, means that I'm during a call, therefore awake.

How is that possible?

LE: not that I'm complaining, I get awesome battery life, my highest wakelocks being *sync* by Google - 0,7%, ie around 7 min in 17h (have it sync hourly with tasker), GSM Dialler 0,4% and Tasker 0,1%.

I'm sooo mad I have to rogue app to track down :))

Thanks for this app again!!! Already marked as spam that ignorant KARAM who 1starred this wonderful tool.
[BetterBatteryStats] desean:
what is weird? phone has to be "awake" to be "on" right?
[BetterBatteryStats] alex_cai92:
Hi all,

I actually don't quite understand how to read the figures so I'm wondering if any of you here can help me to read my dump files and find out for me whats draining my battery overnight? I lose about 20% over 7 hours on my galaxy SIII

Thanks alot! :D
[BetterBatteryStats] cool1007:
WTF, that's wrong. I made sure to unplug the phone after full charge at around 1am, left it idle (unplugged) until 9am and then took the BBS dump.

I'll try again tomorrow, right now I won't make it in time, it's 12am and phone is not fully charged. :-\

Edit: are you sure? I checked the log again and it says 7h 21m 55s deep sleep (93.8%). Anyways, I'll post another dump tomorrow like I said.

Thanks,
[BetterBatteryStats] AttiM:
Battery drain's horrible

Hi All,

I'm using Galaxy W I8150 with CyanogenMod 9 BETA (Build 3) with forfivo kernel.

As I originally posted in [ROM][ICS][IMM76L] CyanogenMod 9 BETA (Build 3) thread, I have a big problem:

Then I got some ideas and suggestions, and here is my answer:

I attached two zip files with all of the result (screenshots and BetterBatteryStats (from Custom Reference Point what I set earlier)).

Thanks in advance for any help!
[BetterBatteryStats] Karpfenhai:
Your drain cannot be explained with your dump, i would like to ask you to reattach the stock battery for a test, since "super-power-high-capacity-but-cheap" batteries often do not reach the quality of the stock Battery.

Good luck!

You are suffering the usual candidates, to much sync, Locations servics, Maps and probably google now, but the dump does not show the full picture so im a bit puzzled, i suggest you to disable all maps related autostarts, sign out and disable all location based services, freeze google now if not needed and dont sync search results and calendar..

Then upgrade to the latest version of BBS and post another dump.

Good luck!

---------- Post added at 10:04 AM ---------- Previous post was at 09:55 AM ----------

Your Main Problem is sync and Location Services, they literally eat your Battery:

NetworkLocationLocator (Google-szolgáltatások): 14 m 29 s (869 s) Count:409 3,5%

*sync*_com.android.contacts_Account {name=attimm@gmail.com, type=com.google} (Google-szolgáltatások): 2 s (2 s) Count:1915 0,0%

LocationManagerService (Android rendszer): 39 s (39 s) Count:560 0,1%

GpsLocationProvider (Android rendszer): 1 s (1 s) Count:788 0,0%

SyncLoopWakeLock (Android rendszer): 1 s (1 s) Count:1580 0,0%

GTALK_ASYNC_CONN_attimm@gmail.com/android_talk1cccc836b2a6 (Google-szolgáltatások): 22 s (22 s) Count:462 0,1%

So, disable all location based services, try to decrease your sync activities, set gmail to pull instead of push.

Have fun ;)
[BetterBatteryStats] justinliu:
Can someone take a look at my battery stats? Galaxy Note 2 LTE N7105

I've been looking around to see what Audio_Out2 is but cant' find a definitive answer. Its not the keyclick or lockscreen sounds because those are all off already.

Out of the kernel wakelocks

fast_dormancy and mdm_hsic_pm0 are always high. Does this look like a normal number for fast_dormancy? Does it indicate my carrier doesn't support the feature? Also what is mdm_hsic_pm0? I can't find anyone else with this issue.
[BetterBatteryStats] Karpfenhai:
mdm_hsic_pm0 is afaik the same as l2 Hasic, just a new name under Jellybean, so its traffic related, i would keen an eye on my background activity..

regarding AudioOut_2 disable talkback, i wonder if the issue goes away then...

Here are your main Problems:

*backup* (Android System): 27 s (27 s) Count:498 0.2% --> Disable Google cloud backup, use offline solutions like Titanium

GpsLocationProvider (Android System): 3 s (3 s) Count:372 0.0% --> Disable location based services ...

SyncLoopWakeLock (Android System): 1 s (1 s) Count:873 0.0% <shocked> decrease uneccessary sync...

SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:1245 0.0%

"fast_dormancy" (): 16 m 57 s (1017 s) Cnt:(c/wc/ec)154/0/154 7.6% --> keep in mind, its just a symptom, not the cause, if your phone is waking up lets say 20 times per hour, this counter will increase too since it fires every time your modem idle status is changing.

Alarms (requires root)

jp.naver.line.android (): Wakeups: 60 -->Whats that? Do you need this?

Note, many useful information can be found on Post 3, just read it ;)

Good Luck ;)
[BetterBatteryStats] justinliu:
Thanks for your help! I'll try to reduce as much auto syncing as possible. Line is a chat program I use so I can't really get rid of that. So when looking at the wakelocks, the count number is more critical than the percentage or time counter?
[BetterBatteryStats] Karpfenhai:
The Time shows the time ;) where the app is really active, the counter shows the wakeups caused by this particular app, any wakeup produces an overhead, lets say 5-10 seconds where your device is not deepsleeping, the Cell state changes from idle to pch to fach and back, so many wakeups can cause lot of awake too.

Hope u understand what im trying to say ;)