yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] steve austin:
i get that too...

the latest version of your app did this to me constantly. I had to remove it and go back to the previos version. Since I am still using this phone I can not hand it over, sorry. I would love to help in that regard. now, however, BBS is force closing at least once a day. I have no idea what is going on in the background a the time to make it do so. It is still fuctional, but the message pop up and the fact that it is doing it gets annoying. I am using a ROM located here (phoenix 3.6.5 with bricked kernel) http://xdaforums.com/showthread.php?t=1429953 for my Sensation if that helps at all.

Side note, using your app along with power tutor http://ziyang.eecs.umich.edu/projects/powertutor has/had been really effective. I don't know how they collect their data, but the measurments seem to be pretty accurate. This app now partially works as well since my ROM/rooting switch. Thanks for all your work. I greatly appreciate it!
[BetterBatteryStats] jeremysherriff:
Oh, ok. From memory your dump file referred to eclair (Android 2.1) and froyo. If you go Settings/About Phone.. what's the version number etc?
[BetterBatteryStats] itsLYNDZ:
Uvkb5 and 2.2
[BetterBatteryStats] jeremysherriff:
OK, I know *nothing* about the vibrant, but from doing some reading... maybe try the KA7 modem. Unless you know something about the KB series being better perhaps?

It's worth a go, right?
[BetterBatteryStats] itsLYNDZ:
I dont know anything about modems. Does anyone know whats different from the KA7 vs KB series? Whats a good modem for D9 or Frankenstein rom?
[BetterBatteryStats] jeremysherriff:
It would be better to post that question in the frankenstein rom thread, making a point of mentioning the no-coverage scenario and the observed behaviour of network scanning when airplane mode is on. I also suspect (but am not a dev, so not sure) that the scanning is a ROM feature, not a kernel or baseband feature. Have you tried a MIUI ROM? It might act differently, certainly the MIUI ROM I used to run did not have problems with no-coverage or airplane mode.

It's a pity there are no official 2.3.x ROM's for the Vibrant, I wish Samsung would support their devices for longer lifetimes. The lack of genuine kernel drivers for a 2.6.35.x kernel is frustrating.
[BetterBatteryStats] torchedlh:
Just upgraded to CM9 on my Galaxy S2 and am having some pretty bad wakelock issues. My phone is awake about 50% of the time and only about 10% of that is due to the screen being on.

In 2 hours, com.android.email woke my phone 527 times (listed under alarms)! I even froze the app using Titanium backup! How could this be?? FYI, my email is Exchange.
[BetterBatteryStats] jeremysherriff:
What email connection do you use? IMAP? POP3? Exchange?

I assume you are using the stock email client?
[BetterBatteryStats] torchedlh:
I use Exchange.
[BetterBatteryStats] nobnut:
Hi Chamonix,

It's been a while since I've stopped by to say hello. Hello!

I don't know if anyone has responded to your request for a test device but if not, I am able to offer you some assistance (and an early Christmas present ;)).

I have a Nexus S which I have no use for. You can obviously flash MIUI (Yuk!) or whatever you want on it for testing. It is in perfect working order and I will be more than happy to send it to you for free. I'll pay delivery costs also :)

If you are interested, drop me a pm :)
[BetterBatteryStats] bringonblink:
Wow that's really awesome of you
[BetterBatteryStats] bringonblink:
I had this exact problem yesterday. Push right? Either way uninstalling stock email and exchange services then installing enhanced email worked for me
[BetterBatteryStats] jeremysherriff:
Thanks for the elaborate response :p

Without knowing some more, I have had to resort to some maths. Assuming not exactly 2 hours, I'm going to suggest you're getting about one wake every 15 seconds. So, push mode then. It would be logical to assume either your data connection was down, or kept resetting. The other option would be that the email server was having trouble.

After a reboot, did the issue continue?

To be honest, if you need more help with this you should post up a dump logfile, to give us the full context. HTH...
[BetterBatteryStats] bringonblink:
Hey thanks for your help yesterday. I have another dump i was wondering you could take a look at.

https://www.dropbox.com/s/wcxucs0t1f4sdcr/BetterBatteryStats-2012-04-26_072458683.txt

All the wake locks look ok to me, with screen on for 20 mins awake 30 mins, so 10 mins out of 8 hours seems good to me.

But for some reason deep sleep is at 65% , when i thought it should be around 90% :S

Cheers
[BetterBatteryStats] jeremysherriff:
It's a bug:

Since 8 h 41 m 29 s
...
Deep Sleep (): 8 h 11 m 47 s (29507 s) Ratio: 63.4%

8h 41m 29s = 31289s... your awake is 29507s which is actually 94.3%.

@chamonix not sure what happened here..? It's a "since unplugged" dump so it's not part of the custom reference issue.
[BetterBatteryStats] bringonblink:
Ok hopefully i'm not annoying you now...

But you see that block in the awake time, that doesn't seem right does it? All the wake locks are down to minutes, which shouldnt account for solid awake time? :S

Cheers
[BetterBatteryStats] jeremysherriff:
:D That graph isn't very granular. Go into BBS, and got menu->more->more graphs, have a look around there.

Don't obsess too much, enjoy your smartphone. You're getting damn good battery life ;)
[BetterBatteryStats] bringonblink:
Didn't even know about that ha.

I still think it's a bit odd that it's awake so much then :confused:
[BetterBatteryStats] suku_patel_22:
Hey a feature request

Filter the serie by since custom ref

Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
[BetterBatteryStats] mckr32:
very good application

just need to get my head round how to use it properly

Thanks
[BetterBatteryStats] Vangelis13:
suspend_backoff kernel wakelock, wtf is that..?:confused::confused:
[BetterBatteryStats] Vangelis13:
Sorry, double post :-/
[BetterBatteryStats] yeahtyeaht:
i have many wakelocks with audio_out1 but i deactivated the sounds (lockscreen etc.). i have an galaxy s2 and the drain is very heavy
[BetterBatteryStats] Tungstwenty:
Possible feature

chamonix, here's a suggestion for a new feature, if it makes sense and is feasible...

Currently we can obtain the full list of partial and kernel wakelocks, and you can also present the time of each of them as a % not of the total uptime, but of the time the phone was awake but with the screen on. This is ultimately what we want to avoid, hence the fact that you included this option in the % display.

Well, if we check the "awake - screen on" time, and account for all the time spent on kernel wakelocks (including the aggregator for all partial WLs), that time is higher than the "unnecessarily awake because screen is off" time. That's because the WLs overlap each other, and therefore there's really no root cause blame for particular WL.

What I'm trying to say is that it would be great if it was possible to filter out what is irrelevant and display only the WLs that were "active" during the screen being turned off.

I know this is a huge thing to implement. First of all, both the kernel and the android Power service must be modified to keep track of this sort of granularity.

Also, even after that step is achieved, it's still needed to trace situations in which e.g. WL A is acquired (CPU wakes up and A-ticker starts counting), WL B is also acquired (not counting because the bad guy is still A), then A is released but B is still held, rendering the CPU still awake (so start counting B-ticker), etc.

Just thought I'd throw this into the pile :D since I haven't found any reference to this on the thread.

PS: The current approach I see that is usually followed is eliminating all WLs as much as possible. But in reality, one could eventually have huge time or count of certain wakelocks provided they only happen with the screen on, right?
[BetterBatteryStats] chamonix:
Post a dump so we can have a look
[BetterBatteryStats] chamonix:
Hello too nobnut :-)

That IS a very generous offer and I would be happy to accept as long as you don't insist on covering all the costs. PM will follow as soom as I have a keyboard
[BetterBatteryStats] mahercs:
So I gave up trying to figure all this out, and I didn't see anyone reply, so I ended up calling to exchange the phone assuming it was some bug in my phone. Most RAZR owners weren't seeing it, but others were, so it's worth a shot.
[BetterBatteryStats] yeahmann:
I used to use Facebook with refresh and notifications turned off and the separate Facebook Messenger and that combo gave me acceptably few wakelocks. Now the new Facebook app combines the two apps together so that I have to enable notifications to receive messages and it seems like the wakelocks have increased. Anyone else notice that?
[BetterBatteryStats] chamonix:
You are right, overlapping wakelocks is something that can't be detected and modifying Android services is something that I am not aiming at because I don't build ROMs (the services would have to be signed with the same keys as the system). Now there is one place where that kind of data should be available: in the data collected by the batteryinfo service. Unfortunately there is not much historical data available and what is there is mostly not consistent between SDK versions.

To avoid that there are two ways:

- take care of leaving the phone alone as long as possible to at least limit the effect of wakelocks being held while screen is on: this is the method I recommend

- I am working on an automatic reference being stored when screen goes off and compared to another reference when screen goes on (given the time off was long enough). That case would not avoid overlapping wakelocks either but would make it easier to analyse the behavior for screen-off phases and would also allow to send notifications when the screen goes on and telling the user about apps that misbehaved during that time.

I guess this feature will be in 1.9 or 1.10 and the last feature before the big rework on 2.0
[BetterBatteryStats] chamonix:
If you want some founded answer please post a dump file
[BetterBatteryStats] chamonix:
afaik that wakelock is help when the suspend process started by the kernel gets interrupted. Known causes are unreleased exceptions or drivers not shutting down peripherals properly (sensors, etc). If you do a dmesg you should see those interrupted power management (PM) cycle, maybe with some additional info
[BetterBatteryStats] chamonix:
Do you mean setting the start of the serie consistent to any "since" reference?
[BetterBatteryStats] chamonix:
My theory on that (please feel free to confirm / infirm)

The phone was booted and not unplugged after that. This leads to all the reference values to get checked against the reference "pre-boot" except the deep sleep as that one uses the realtime clock and does not go back beyond reboot.

I have detected that bug in the widget at least and I will make sure to delete all references upon boot to avoid that kind off inconsistencies
[BetterBatteryStats] chamonix:
Well thanks to nobnut there's light in the tunnel :) but as I will have to write a diag app for my own testing I may as well make it available. The problem is that a logcat only shows that the error has occured but not the reason. The symptom is the service binder returning a null reference so my goal would be to dump the parcel returned by the service manager to see what went wrong.

Once I have finished 1.8 I will start working on that
[BetterBatteryStats] chamonix:
You guys are moving a little too fast for my taste. Not everything is a bug in the ROM/kernel. I have e.g. had situation with enormous times on AlarmsManager the last days andfound that turing wifi off ended those. The behavior only happened when my phone was connected to one specific router.
[BetterBatteryStats] chamonix:
What I see is kineto causing a large number of wakelocks. I'd say this app is misbehaving, there is no reason for an app to wake your phone up every 30 seconds (900 times on 8 hours).
[BetterBatteryStats] chamonix:
Testing RC8 now, expect following fixes tomorrow:

- order of bars in 2x2 widget consistent with values on top

- colors of bars in 2x2 widget consistent with 1x1 widget

- delete references on boot to make sure to avoid inconsistencies with deep sleep / other values when the chosen reference was before boot

Assuming all bugs are really fixed that will be the last RC
[BetterBatteryStats] stevenh:
could someone have a look at this dumpfile for me? Cheers. Let me know if you want screenshots
[BetterBatteryStats] jeremysherriff:
Update to IMM76I as soon as you can, it'll fix a lot of the drops/restarts you can see in the log for gmail.

Handcent SMS is nagging/reminding you about something (received SMS I guess) - unless you *really* need the reminder thingy, disable it and just let the icon show at the top notification bar.

You can also achieve some efficiencies by changing Facebook clients to Friendcaster or similar - the stock Facebook client is bad for wakes.

Whatsapp is known to be a bit of a battery hog if the network data connection is a bit flakey. Do you use it? Would you consider something else, like Viber?
[BetterBatteryStats] suku_patel_22:
Yes, in the graphs and raw serie as well

Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC

Sorry for the swypos....
[BetterBatteryStats] It_ler:
Oh chamonix, I have an old keyboard that I do not use any more and which I could send to you ;)

Just kidding ... thanks for your great BBS app and much joy with the new phone.
[BetterBatteryStats] leranp:
Can someone help me and chack me battery problem

10X alot
[BetterBatteryStats] klemenSLO:
resolved :)

I'm happy to annouce theat i foud what is the reason behind my wakeups.

There is option Under options "DOWNLOAD ATTACHMENTS:auto-download attachments to recent messages via wifi" in email accounts .

When this is checked, system gets wakeups aprox. 4 times per minute even if the wifi conection is disabled. I would say this is a bug.

Can anyone other confirm this? I tried switching on/off and am certain of this.
[BetterBatteryStats] Karpfenhai:
Well spotted mate!

I don't use exchange but I'm sure this will help others very much!

There is someone making a list of known drainers, hopefully he will add this one.

regards!
[BetterBatteryStats] scott.kev:
Hi Guys,

Another drain issue - basically 50% overnight when the phone is not in use - 1 exchange account, 1 gmail account and 1 twitter account syncing, nothing else in use.

Can anyone explain what's keeping the phone running at 200MHZ for hours on end?

Thanks
[BetterBatteryStats] Karpfenhai:
Yes i can ;)

Its a Bug in Touch, just kill it once (Force Close) and the issue will be gone until the next reboot.

Kill it, restart it, drain temporarily gone.

Good luck!

Update, i was too fast ;(

Touchdown is not Touch / Pingchat, im sorry..

So after a closer look, here are my recommendations:

- Dont use JD if not really needed

- Try K9 instead of Touchdown.

- Get rid of Battery Monitor widget or decrease its update rate.

- bring down your sync activity, maybe use pull instead of push

- disable /freeze unneeded samsung stuff

Come Back afterwards and provide a fresh dump (4-6 hours idle)

regards.
[BetterBatteryStats] scott.kev:
Thanks - Will give it a go and see how it goes over the weekend
[BetterBatteryStats] Karpfenhai:
Im sorry, just read my post once more, thx ;)
[BetterBatteryStats] iovaniorgovan:
Today I ran also into the *overflow* thing. It started appearing when the battery went under 20%. I'm keeping my eye on the drainage because it accelerated over the last charge cycle.

Chamonix, what do you mean by shorter readings?

Also, com.sec.android.app.clockpackage.Clock is second under *overflow*. But why? I have no alarm set, I didn't touched the clock app, what could be wrong with it?
[BetterBatteryStats] o0boiboi0o:
Hey mate, do u happen to who is the 'someone'? perhaps a link here to the list will be helpful to us all! :D
[BetterBatteryStats] cdmackay:
Minor point; the web page: https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/svnet

says: "Rationale: basic radio management (Galaxy S II specific)"

but since I'm seeing it as a big hitter on on my S (CM9), this is perhaps misleading?
[BetterBatteryStats] jetway1122:
Battery help

I was hoping someone could have a look at my log as Im trying to figure out why I'm have 2%+ battery drain with the screen off. By no means this is horrible battery life Im just trying to learn how to spot/understand whats going on and how I can improve it.

Galaxy Nexus (Canada)

AOKP B32

Lean Kernel (hotplugx, aggressive undervolt, minium freq 230mhz, max 1200, gpu 384)

Battery was at 91% when this log was captured.

Phone was logged out of Gtalk, and in airplane mode.

http://pastebin.com/z1EAiHYX
[BetterBatteryStats] Boat Traveller:
Hi,

It's been 3 days since I flashed Siyah 3.1.2 and my battery life is still shorter than when I was with Gingerbread. In BetterBatteryStats, in the Process category it's full of Kworker. The bars are nearly red full.

In Setting => battery utilisation

the Android OS uses 41%

the screen 30% (on for 1:40)

for a total of 16 hours. I've got 40% battery left.

Deep sleep : 81%

In Badass Battery Monitor, the kernel is the app that drains most of the battery : 35%

Can someone help me please ? :(

My ROM is ICS 4.0.3 LP4

Kernel : Siyah 3.1.2

Phone : LPS

Frequency range : 200-800 Mhz

Governor : Conservative

Slightly undevolted at 200 Mhz

1900mAh Anker battery
[BetterBatteryStats] jeremysherriff:
Hiya, this is a pretty simple one ;)

Your problem is Lightflow (com.rageconsulting.android.lightflow) - see in the Alarms section. I don't know the appp so I can't be sure, it might be a configuration issue or it might just be bad software. Either way, it looks to be accountable for almost 90% of the wakeups draining your battery.

You also have poor data connection issues. Were you connected to wifi the whole 18h of this log file? The IMM76I update for your phone will help as it fixes a lot of data connection issues.

You might want to consider changing the Facebook client to Friendcaster, it's a lot easier on your batter than the one you have.

Once you've dealt with the above, come back if you continue to have issues. I see some other possibilities, but lets see how you go with these first.

---------- Post added at 11:39 AM ---------- Previous post was at 11:34 AM ----------

Post a BBS dump logfile, or post questions in the kernel thread. We can't guess, we need information. This isn't a general "my battery sucks" thread, its a thread about a specific process-monitoring application.

---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------

Shorter period of time for the log files. "overflow" means the counter literally has overflowed, if you have a shorter dump period (say, 2-3h) then the wakes won't overflow and will show their proper name.
[BetterBatteryStats] KJ98653:
I'd use 3g but I have a poor signal. Internet is fast but subjectively it seems I have bigger drain. Also which WiFi setting should I choose? I read it should be set to never...is that correct? I don't really notice a difference with battery usage. I'll also go to my ROM thread and see if devs will look into app.
[BetterBatteryStats] Boat Traveller:
Here's the dumpfile : http://dl.dropbox.com/u/23398734/BetterBatteryStats-2012-04-28_091602056.txt

Thanks for helping me :)
[BetterBatteryStats] jeremysherriff:
In the BBS preferences, change the default stat type to "since unplugged". The dump file you posted includes some time on the charger I think (or, you have a kernel bug). It'll be interesting to see if you have the vbus_present kernel wakelock in the "since unplugged" dump file.

Then, plug in to the charger for a while (a few seconds is enough), unplug, then let the phone sit idle for 2 hours or more before taking another dump file. Always use the "since unplugged" view.

Sorry, I know you want to get on with improving your battery life, but the dump file info isn't all that helpful yet. But, you can do this to improve things in the meantime:

Change the refresh setting in Battery Monitor Widget to at least 5m or even higher (data is still collected fine),

and remove the Battery Monitor Widget widget itself off your home screen. You can access it from the normal apps drawer, or put a simple standard shortcut on your homescreen

At the moment, your battery monitoring is chewing up your battery faster than anything else. :D
[BetterBatteryStats] Boat Traveller:
Thanks for your reply !

Just plugged/unplugged the phone. I'll be back in 2hours then
[BetterBatteryStats] jeremysherriff:
Sweet, I'll be asleep ;) Make sure to adjust BMW as per my last post.
[BetterBatteryStats] Boat Traveller:
Could you just tell me what kworkers are ?

Thx
[BetterBatteryStats] Hk.Tang:
About phone wakelocks / alarm

my phone deep sleep 7hours + , It's dropped bout 15% ++ battery ..

All apps closed

No wifi no data

bt my phone keep on awake bout '' com.android.phone- Alarms: 191, Intent: com.android.internal.telephony.gprs-data-stall '' & '' com.google.android.gsf-Alarms: 70, Intent: com.google.android.intent.action.SEND_IDLE

'' even when i sleep off my phone , that's also keep increasing .. It's drain my battery alot

i think it's not kernel prob .. Coz those screenshot is using siyah kernel v3.1.2 , bt i changed to dorimanx also same issue ..

May i ask what's the prob n how to fix it ? anyone help .. :confused:

EDITED : Freezed google talk ..

Here is my screenshot and log bout the problem (using siyah v3.1.2) .. Betterbatterystats log *

ROM : Remix ics 1.7 AOKP 4.0.4 LPS

Kernel : Dorimanx kernel 1.2

Extweak : Battery profile

Freq range : 200-1000mhz
[BetterBatteryStats] Boat Traveller:
Here's my dump file. Left the phone for 2 hours idle.

Is there something wrong ? Is there an app that drains too much battery ?

Thanks !
[BetterBatteryStats] MSAKK:
This is my Kernel wakelock after 1:30hrs idle:

It seems that I get high deleted_wake_locks, what is that?

Everything looks normal apart from that

I get very high android usage with WiFi on, and battery drains rapidly on idle.
[BetterBatteryStats] chamonix:
Overflow is caused by too many samples collected by the batteryinfo service (android core). Reducing the timespan between unplug and dump will reduce the probability of this kind of overrun
[BetterBatteryStats] chamonix:
Thanks! I updated the wiki
[BetterBatteryStats] chamonix:
Release 1.8RC8

Sorry for the small delay guys, I switched ROM yesterday and lost some time setting up all my stuff again.

RC8 is out!
[BetterBatteryStats] suku_patel_22:
Restored a nandroid backup, opened RC8, set a custom ref, it didn't show up data

Set another custom ref, data showed up just fine

Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC

Sorry for the swypos....
[BetterBatteryStats] riskaa:
please help analyze dumpfile

Could someone help me analyze this dumpfile please. I changed my kernel recently and wanted a fresh look at this.

I unplugged my phone and let it run for about 8 hours, using it on and off.

I see that K9 push email is using a lot of battery on idle. I need it to be on Push however, for another app that I'm running.

Apart from K9, could you explain what is going on?

Does "no data signal" correspond with the time when my wi-fi was on and running. is this normal?

My main concern is how much my battery seems to drain when the screen is on.

Any help appreciated.

Thanks so much.