yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] chamonix:
Sync is causing a high overhead (mail, reader) that may be due to bad network conditions.

You should update bbs to a recent version so we can look into your alarms (or check the details of gsf yourself)
[BetterBatteryStats] chamonix:
That's proof enough. Does it stick after a reboot? In such case you really should try to contact the dev/cook of your rom and / or kernel: I can't imagine you are alone on that one.

Mobidia the an app you want to check: it keeps waking your phone up (see alarms)
[BetterBatteryStats] cricketAC:
But if you see my screen off and awake are sync. Should I be worried to begin with? mobidia is for tracking my data, but what's went wake lock on kernel. That's always on and its bugging me. Should I even be? Or is it my paranoia?
[BetterBatteryStats] t-pip:
Thanks. GPS, Latitude, Facebook location, etc are all off so can't see what the location requests are for.
[BetterBatteryStats] coolfire:
Thanks a million, mate!

I've ditched the prefs up to collect data @ 10mins now. Re: GoSMS, I've to check my settings again. As for whatsapp, the Wakelocks recently seem to have increased, dunno why, though I have the latest version...
[BetterBatteryStats] jeremysherriff:
Looking really nice! The 2x1 widget is pointless if increasing the font size, you might want to rethink how you present data on the 2x1 in that situation.

I think it's ready to release from a GUI point of view, I'll comment tomorrow on the stats collection side (as I've been having trouble with the data and signal strength counters and have just updated my Nexus to 4.0.4 IMM76I that was released this morning, which has fixes for that area).

---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------

I have some small suggestions at this time, both that can be held over to another major release if you accept them:

1. Custom background and text colours for the widgets. Maybe just 4-6 colours to choose from rather than the whole pallet, but up to you.

2. A more modern way of selecting the views in the main app, rather than using the spinners to chose between kernel/wakelock/other/alarms/processes etc. It could be like swipe left/right to change like other similar apps such as Antutu Benchmark and Wifi Analyzer. Or it could be like Android's "Settings->Apps" view selection in ICS, that changes between Downloaded/Running/All.
[BetterBatteryStats] creamgetthe$$$:
This is my second post of battery stats. Took more of the recent advice on how to get better signal, but this is the first dump file from running while I was asleep. 4G was turned on for testing, but wifi was turned off. I can't use K-9 cause it won't connect to my work email (really secured on work's side). went from 100% to 81% in the 10 hours it was on. If there is any advice I would really appreciate it. Running cm9 pretty recent nightly on my p930 LG Nitro.

Thanks again
[BetterBatteryStats] suku_patel_22:
Hey Chamonix,

The latest RC looks fine for me, much more customisable than before, thanks....

Sorry for troubling you a lot :)
[BetterBatteryStats] chamonix:
Then you are left with map doing some location sniffing/caching because wifi is on (see gmaps prefs)
[BetterBatteryStats] chamonix:
That's no trouble..... Your suggestions bring bbs forward and makes it a better tool, that's what I live for: real tools for real use cases
[BetterBatteryStats] chamonix:
The sleep/awake ratio is pretty good and most of the awake time is due to poor connectivity causing SyncLoopWakeLock and gprs stall alarms. With better coverage I bet your battery drain would be pretty awesome
[BetterBatteryStats] chamonix:
I am puzzled: this graph suggests that no wakelock is keeping your phone awake when previous dumps clearly showed much more awake time. If the kernel wakelock still reported/present? Please post a bbs dump and the battery graph side by side, changing reading makes the interpretation of any results pretty hard
[BetterBatteryStats] JoeSyr:
Hi, I'm having some troubles on a newly flashed rom, it appears that the kernel wakelock "gps-lock" is preventing the phone from going into a deep sleep. I've attached logs which show that pretty much 100% of the time the phone should be sleeping, this item is keeping the phone at 350mHz instead. However, it does not show up as "awake". Notably, I had GPS toggled off altogether in this time period.

I'm wondering if it's possible that the 1.8RC line of BBS might actually be part of this. Some users of the rom (Liquidsmooth 1.3 on CDMA Galaxy Nexus) get this problem without fail, others don't see it at all. And I read on the app page for GPS Status & Toolbox: "Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed!". Indeed, my battery drain looks pretty normal. But even normal battery stats thinks Android OS is keeping the phone awake.

So it seems like something is trying to read the GPS module that Samsung never got right but android has figured out how to hide. Since this doesn't affect all of the Rom users, it seems like there must be something a good chunk of people are running... maybe the latest BBS? I'm on 1.8RC5 and will try downgrading to 1.7.1 for a bit and see if the problem goes away.

Also attached a logcat (errors) which BBS appears in quite a bit for an overnight drain. Might be helpful for future development regardless of all of this, I figured.

Edit: Well, problem turned out to be that if the phone is rebooted with GPS on, it will cause all of this. Nothing to do with BBS. Bug in the rom, it seems.

Still, hope that logcat will be of some use!
[BetterBatteryStats] syncopath:
Do you know how to freeze social hub, or have a link? I've searched everywhere.
[BetterBatteryStats] p107r0:
Root App Delete
[BetterBatteryStats] Karpfenhai:
Rc5 review, I'm impressed! But there are some minor issues :-(widgets only)

1. No label = no update functionality..

2. Space to tap for update is way to small somehow, Half of the widget size would be better (diverted by upper and lower half)

3. Its mixed now, imho it should be:

-since

-deepsleep

-awake

-screen on

-anything else

All other functions, perfect as usual ;-)

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] jeremysherriff:
I do not have this problem?

What space to tap for refresh? Soomeone mentioned this before, I thought it was a mistake! Can someone post a screenshot and mark where the refresh area is?? Please?

I agree, generally those people looking at battery stats are going to be trying to get very high "deep sleep" time this this order ^^ would make it "sorted" by bar length ;)
[BetterBatteryStats] chamonix:
I'm happy things sorted out well!

And thanks for the logcat, I opened a bug about that for a followup: https://github.com/asksven/BetterBatteryStats/issues/155
[BetterBatteryStats] chamonix:
Thanks for the always pertinent feedback and for the encouragements. Issues added:

https://github.com/asksven/BetterBatteryStats/issues/156

https://github.com/asksven/BetterBatteryStats/issues/157
[BetterBatteryStats] chamonix:
Or, the ordering is fixed already (that was faster than typing the issue.

For the hot-zone I will try (coded already as well, to be tested):

- widget 2x2: refresh zone on text

- widget 2x1: refresh zone on upper 1/2

There will be a RC6 as soon as I am satisfied, more info on build have been added as well

Edit: just teasing: it works all fine :P
[BetterBatteryStats] chamonix:
Release 1.8RC6

I definitely need a build process: Eclipse makes me soo slow releasing ;)

Enjoy!
[BetterBatteryStats] Karpfenhai:
Thx Sven, your efforts are very appreciated as well!

Waiting for the new release.. B-)

You develop on eclipse? Not the baddest idea ;-) I'm doing this too sometimes, but for Avaya products...

@Jeremy, the upper part of the 2x1 and 2x2 widgets are refreshing the widget upon tap, just try it ;-)

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] chamonix:
Call for device

I feel like fixing the problem where BBS is not able to communicate with the batteryinfo service (like on MIUI but also on other ROMs).

If anyone has a broken device still functioning to the extent of reproducing the problem I would be in to get that device (I'd pay a few bucks + mail to have a device to reproduce the problem)
[BetterBatteryStats] chamonix:
<OT> omfg, I know Avaya from somewhere</OT> we should go for a beer sometimes. You aren't in FRA are you?
[BetterBatteryStats] mahercs:
chamonix,

I just updated to rc6 and tried to dump to a file, but it FC on me. I have been having a helluva time figuring out why my battery drain is so quick and came across this thread. Love your app, and would love to get your insight into the stats, but I can't get a file to post here.
[BetterBatteryStats] Karpfenhai:
nope but i was 3 weeks ago....

I'm from Leipzig, working for a well known IT-company..

Maybe next time for further education I'll be in FFM again.. ;-)

Ja Avaya... Frickelware...

Rc6 tested, widgets are perfect now, nothing left to complain, well done!

Update! Funny but awesome, 2x1 widget has now a double tap feature! Is this intended or an accident?

Means, of you tap nice and slow, the widget gets only refreshed, if you're faster (2 taps under 1 sec) it opens the app, anyone else experiencing this? Kinda cool btw! I'm on 216 dpi..

Update 2:

I have to revert my first update, it happened due to my dpi setting, so please forgive my noise about this.. :)

Its like 80/20 for me, but i like it this way. :-P

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] chamonix:
That's obviously not intentional but I can't reproduce. Would you mind posting alogcat.

Anyone else able o reproduce?
[BetterBatteryStats] t-pip:
Ok thanks.
[BetterBatteryStats] mahercs:
I am using a Razr Maxx, rooted but pretty much stock. When I went to pull the logcat, I noticed there were file dumps saved by BBS on my SD card, but they were empty. Anyway, here's the log http://db.tt/nB9zRvLU
[BetterBatteryStats] chamonix:
Ok, there seems to be some kind of incompatibility here:

E/AndroidRuntime( 7180): Caused by: java.lang.NoSuchMethodError: android.os.Build.getRadioVersion
E/AndroidRuntime( 7180):	at com.asksven.betterbatterystats.data.StatsProvider.writeDumpToFile(StatsProvider.java:1354

getRadioVersion is the API to use since API14, before it used to be a static field. I'll take care of both options.

Edit: Added Issue to tracker as to-be-fixed before release: https://github.com/asksven/BetterBatteryStats/issues/158
[BetterBatteryStats] Karpfenhai:
No dump works fine! To the guy with the issue, you are rooted?

If yes, drop bbs from the allowed apps list on superuser app, recreate the dump and grant root again, if this does not solve your issue, reinstall SU-app and/or wipe its data.

Good luck!

Edit: chamonix is to fast for me..

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] mahercs:
So I'll just wait for the next update to provide you with a dump, and I don't need to try what Karpfenhai suggests since it's a bug in the code? Yes?

You guys are pretty awesome and I can't wait until you can help my analyze my issue.
[BetterBatteryStats] Karpfenhai:
Yeah seems so, I've missed some information appeared right during my own writing (need to get faster with Swype). If its an obvious bug in the code you don't need to try my method,i just came up with it b/c during dump bbs is asking for root access (alarms), therefore it could have been possible somehow....

Good night pipol!

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] AllSeeyinEye:
Bbs and/or the widgets are causing freezes on the SGS2 using NEAK kernel. Someone an idea what the problem could be and how to solve it? For your information NEAK kernel is a lightweight kernel that has disabled all logging.

Verstuurd van mijn GT-I9100 met Tapatalk
[BetterBatteryStats] mahercs:
Perfect. That's what I thought. I am streaming some baseball right now with serious strain on the battery, so I won't get a good log today anyway. Oddly, the MLB app has been on for almost 3 hours and still shows less than Android OS. Obviously, there's something else.
[BetterBatteryStats] jeremysherriff:
Not for me - every part of the 2x2 causes the main app to open. i'm going to try uninstalling and re-installing in case something's broken somewhere, but before I do... Sven is there any log I can get that might assst with why my widget doesn't have a hotspot area?
[BetterBatteryStats] Paragon_X:
Hi guys I hope you don't mind me posting this question here but it seems like the perfect place to pose it. I already looked at my log and pretty much I'm down to my gmail keeping my phone awake just a slight bit to offset my screen off time. However, I need my email notifications to come the sec I receive an email. My question is, can I receive instant email notifications and still maintain that sleep mode when the screen is off without sync? Or must I leave it on at all times. Running Nexus S, Matrix 19, Codename 2.0 Rom.
[BetterBatteryStats] chamonix:
Release 1.8RC7

No time for basball :P

Fix is up....

Did I mention you guys rock?
[BetterBatteryStats] chamonix:
Sync, whether it's push or pull will be triggered by an alarm, meaning your phone will wake up and notify you. Push in a sense is an illusion as of course your phone is not staying awake and waiting to be notified. The notification in case of push is the nearest you can get to realtime though, as opposed to poll when the interval is fixed.

Hopr that answered the question
[BetterBatteryStats] chamonix:
TAG should be either LargeWidgetProvider of MediumWidgetProvider, text on manual update is "APPWIDGET_UPDATE called: updating", on alarm it's "Alarm to refresh widget was called".

Edit: The listener is set in UpdateMediumWidgetService / UpdateLargeWidgetService so you may want to look at those in the log as well in case an error occured before the listener was added (a stack trace would come up then)
[BetterBatteryStats] mahercs:
Confirmed to work, no FC, and file has data. :D

Will recharge tonight and send you a clean dump tomorrow. Keeping my fingers crossed it's an easy fix I'm just missing!
[BetterBatteryStats] jeremysherriff:
Well, seeing as how you released two updates while I was in one long meeting.. :) i cleared data and cache, uninstalled RC5 and installed RC7. 2x2 widget now works as described so I'll go back to figurng out if my wifi is sleeping with the IMM76I Nexus update.

If this is you developing slowly then... may data allowance would be used up on your updates if you developed fast! Good work, again!
[BetterBatteryStats] kborer22:
I've attached the BBS dump file from "over night". From what i can see the major offenders are facebook, google maps, and GPRS data stall from com.google.android.

Let me know if there are any additional things you think are worth investigating, thanks!
[BetterBatteryStats] suku_patel_22:
Some thing is not right here

Custom ref and data has mismatch

Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
[BetterBatteryStats] jeremysherriff:
Well spotted. Please confirm what version of BBS you are using?
[BetterBatteryStats] cheezzzz:
hey guys its me again, this time with kinda better news. Phone has actually managed to enter 96% deep sleep which is something I've nver seen before, however gtalk heartbeat and reconnect is still killing me keeping my phone awake every now n then x.x any suggestions?

thanks again guys!
[BetterBatteryStats] wadokai:
Hey,

I recently changed my kernel and rom, and well even though my screen time isn't high, i'm not getting best battery performance.

Attached is my batterystats from the app. Please take a look and help me out! Thank you!
[BetterBatteryStats] chamonix:
Well spotted. Is it the "since" value of the data that is wrong in your case?

With an old custom Ref it looked to me that the data is correct but since is based on "since unplugged" what is obviously wrong. Can you confirm that?
[BetterBatteryStats] sp8y:
chamonix, well done on the rapid updates :)

I'm using RC7 with the 2x1 widget & all seems to be good so far - widget updates nicely with a tap.

The only thing for me is the "deep sleep" stat on the widget always shows "0 seconds" (although it works correctly in apps like cpu spy) - is that another froyo thing like the "wifi running" stat that doesn't show up.

Just thinking out loud can we have (or do we need) a further entry in the widget update settings eg: "never" (as we can use the manual "tap to update" on the widget).

Now that deep sleep is included is there a need to include further cpu states (again as shown in cpu spy) - I'm not wanting to just endlessly ask for extra features as it may be going away from what BBS started out to achieve.

I'll run this RC as my daily app instead of the market (play store) version as the widget is a really good idea & provides a quick look into awake versus screen on time for me.

*edit - deep sleep stat is now working fine - after a full charge & reboot & plug/unplug charger it's now showing correct value - sorry :)
[BetterBatteryStats] suku_patel_22:
Since is proper. The data below is wrong. It is from unplugged

Edit, just tested, unable to reproduce. Will try to reproduce

Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
[BetterBatteryStats] riskaa:
Hi all,

I'd like some input on this most recent dump file. this is after having used the phone for the whole day.

My current worry is that the battery seems to deplete very fast when i'm actually using the phone, and I'm not sure this is normal.

When the phone is asleep/idle...I'm pretty happy with the results.

What do you all think? Some screenshots from bbs and Badass battery.

Also, could someone explain to me the different between the red lines/blue lines in the second screenshot. thanks

http://dl.dropbox.com/u/8231578/Screenshot_2012-04-23-23-07-23.png

http://dl.dropbox.com/u/8231578/Screenshot_2012-04-23-23-07-55.png

http://dl.dropbox.com/u/8231578/Screenshot_2012-04-23-23-08-13.png

http://dl.dropbox.com/u/8231578/Screenshot_2012-04-23-23-08-28.png

http://dl.dropbox.com/u/8231578/BetterBatteryStats-2012-04-17_195852838.txt
[BetterBatteryStats] mahercs:
Chamonix,

Got my dump and screen shots all ready for your expert analysis. The suspend process is out of control and I don't know what to do. Any advice would be greatly appreciated!

http://db.tt/lsmgFOls
[BetterBatteryStats] jeremysherriff:
As mentioned here time and time again, disabling gtalk means breaking a lot of the google framework. Few of the experts on this thread are going to advise you to disable gtalk. Give me a moment to find the dump file you're referring to, hang on..

Edit: OK, got it. Your "problem" is your data connection, not gtalk. Gtalk entries are a symptom only. The data connection has been dropped a couple of times, causing gtalk to reestablish its connection when the alarm wakes happen.

Kernel Wakelocks
================
"bq275x0" (): 7 m 18 s (438 s) Cnt:(c/wc/ec)849/0/421 1.4%
"DATA5" (): 5 m 55 s (355 s) Cnt:(c/wc/ec)244/79/244 1.1%
"radio-interface" (): 5 m 44 s (344 s) Cnt:(c/wc/ec)303/0/0 1.1%
"PowerManagerService" (): 5 m 13 s (313 s) Cnt:(c/wc/ec)671/0/0 1.0%
"mmc_delayed_work" (): 4 m 22 s (262 s) Cnt:(c/wc/ec)408/103/408 0.8%
"alarm_rtc" (): 44 s (44 s) Cnt:(c/wc/ec)114/0/3 0.1%

I believe every one of these kernel wakes is to do with radio and data connections, except the PowerManagerService which refers to the Partial Wakelocks section.

Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 65
Alarms: 21, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 26, Intent: com.google.android.intent.action.GTALK_HEARTBEAT

com.google.android.apps.maps (): Wakeups: 18
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR

com.android.email (): Wakeups: 10
Alarms: 10, Intent: com.android.email.intent.action.MAIL_SERVICE_WAKEUP

So you have something requesting your location - find it and turn it off if you're worried about it. Your "awake" time is fantastic, yes you could improve it but you have already fixed all the main issues. Every other wake-up is to do with the fact that your data connection had stalled (maybe your cell reception is poor in some places?). You also have others from whatsapp and friendcaster but this is minimal.
[BetterBatteryStats] chamonix:
I have had a weird behavior lasting for the two last days and I would like to hear if someone has observed the same.

I must point out this is pure spéculation.

I have had major problems with the AlarmManager partial wakelocks showing counts and times as high as hours a day. The count was also higher than the count of Wakeups from the alarm dump.

Also a dumpsys showed large amounts of pending alarms of all sorts attributed to googleplus and gsf, most of those to be triggered at the same time or within a few seconds. Rebooting the phone or closing gplus got rid of those pending alarms but after a while they summed up again with the same pattern. It stopped today morning (about 10 hours ago).

My theory (to be confirmed or rejected if I was the only one with that) is that an error condition has lead gplus to create bunches of alarms and deleting/creating them, causing the overhead without increasing the wakeups count so I would call that overhead due to excessive management of alarms.

I am thinking of a way to detect this kind of situation where a large number of pending alarms (not repeating) are created by one package by parsing the first part of dumpsys

Feedback appreciated
[BetterBatteryStats] chamonix:
Also one feedback about inconsistent data as reported earlier today. On boot certain counters (like the one for deep sleep) gets reset but bbs does not delete all references on boot. I think this is the cause of the problems reported with "since custom" showing weird data as well as deep sleep being 0 on since unplugged.

I will make sure all references are deleted on boot to make sure this does not occur as even if the problem gets fixed by itself it is causing doubts.
[BetterBatteryStats] jeremysherriff:
Can you lay out some step by step instructions on how to check?

And on a similar note: Google+ generally gets uninstalled asap on my phones, but I do currently have it as I didn't notice it a when I flashed my last ROM. I find it very buggy.
[BetterBatteryStats] Karpfenhai:
Sorry, can't help, google+ not in use and wiped from my system ;-)

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] Vario_User:
Hi,

I just installed the 1.8 RC7 and using the 2x2 widget. Seems to work except the deep sleep is always showing 0 seconds - even though CPY Spy says Deep Sleep for hours.

What I´m doing wrong? :(.

Any ideas?
[BetterBatteryStats] bringonblink:
Hey guys.

New to the whole wake lock thing, but its starting to make a lot of sense. Been going through my apps and checking etc and i believe i've saved qutie a bit of battery.

I have a question however, i can't seem to find any information about what the 'alarms' is exactly.
[BetterBatteryStats] basmaje:
Wonderful ! Thanks for your report.
[BetterBatteryStats] dave-:
My A500 tab constantly wakes up at random times which destroys battery life. That is after using it, I press the power button to force sleep or let it goto sleep on after inactivity timeout, the screen will power up and sit at unlock screen until inactive timeout again.

I'm running an ICS ROM but not sure if its ICS or an app I have installed. I should be able to get more than 2 days battery life from a full charge and basic web/email usage. I'm not watching videos, flash web or music.

Here is the dump after a full charge and being disconnected for over a day.

http://pastebin.com/n46iLhBh

Any ideas on how to resolve would be much appreciated.
[BetterBatteryStats] jeremysherriff:
Think of an alarm as similar to you setting your alarm clock so you can remember to do something (get up and go to work) - apps and system processes set alarms to wake up in the future and do something. An example is Facebook sets an alarm for one hour from now to check on new notifications. Once woken, it does its thing and goes back to sleep, maybe setting another alarm, maybe not.