yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] uumeshh:
Got serious battery issues. Phone doesnot go to deep sleep. It does so only when put into airplane mode. I hardly use sync and very less apps.

Attaching a BBS dump and alarm dump from adb.

Please suggest remedy.
[BetterBatteryStats] precision07:
I'm not sure how to check the modem, I checked the "About Phone", everything are the same(Model Number,Android version,Baseband version,Kernel version,Build number). So far never test before flight mode, will try it out.

Both are on same network (Hotlink Maxis prepaid in Malaysia), both phone network mode set to GSM/WCDMA(Auto mode). Not sure how to check the Fast Dormancy, I guess they 2 should be the same, since bought till now never do any changes to Fast Dormancy.

1 thing I notice is the new galaxy W(the battery draining one) have quite much awake in the "Battery Usage" graph with NO screen on. Meaning its not deep sleep much compare to the old galaxy W. Old galaxy W seldom see awake when screen off. But from the BBS dump file, cant see any thing that cause the awake. Is there something else which cause awake but not capture by BBS?
[BetterBatteryStats] coolfire:
Hello guys, never had this occurring before on my Note - PhoneWindowManager.mBroadcastWakeLock. came anybody assist, please? Getting a huge drain once this wakelock appeared...

http://pastebin.com/yRVM2e7A
[BetterBatteryStats] Karpfenhai:
Hmmm, in this particular case it might be hard to find the culprit, check the maps version, some older 6.0.x are known drainers, not deepsleeping...

Search for google checkin process!

It must not necessarily have a gouge Wackelock count but i had it once on gb causing my phone not to sleep.

It is pretty sure an app, but which one...

Good luck!

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] coolfire:
Just an update... this wakelock magically disappears once I reboot. Appreciate anyone's help anyway. :)

Sent from my SGN
[BetterBatteryStats] precision07:
Tested the Flight mode, still same, battery still drains from time to time. The Awake time is still high but cant be found in partial wake lock/kernel lock/others.

Can see the attached photo, high awake without screen on. No info in BBS for wakelock/kernel lock/others.
[BetterBatteryStats] jeremysherriff:
The phone signal green bar below the graph says you have poor reception often - I'll bet at least some of the unexplained drain is to do with your device looking for better cell sites.
[BetterBatteryStats] chamonix:
Next version may help you as I will add Tasker integration to save dumps automatically
[BetterBatteryStats] chamonix:
Well I found that problem to be related to CM7 but I don't want to excude that other kernels have the same problem.

All 3 dumps show the same profile:

- a huge (really huge) amount of alarms

- a pretty big amount of wakelocks related to wifi

I have never seem such a big number of wifi related activity (especially looking at the first 8 minute run) and I agree that wifi / alarms seem to be related. To confirm that you could provide a dump with wifi off.

Now I see different approaches to break down the problem:

- does the behavior change if you change hotspots if yes then your WLAN may cause the problem rather than your phone

- if the behavior does not change it's rom/kernel/radio related and there should be other people affected on that combo. Depending on the number of people affected using the same rom/kernel you could change on of the 3 menitioned above.
[BetterBatteryStats] chamonix:
===========
Other Usage
===========
Awake (): 4 h 58 m 45 s (17925 s) Ratio: 34.0%
Screen On (): 36 m 17 s (2177 s) Ratio: 4.1%
=========
Wakelocks
=========
FacebookService (com.facebook.katana.Facebook): 10 m 26 s (626 s) Count:111 1.2%
WimaxService (Android System): 9 m 29 s (569 s) Count:1128 1.1%
ConnectivityService (Android System): 4 m 9 s (249 s) Count:2753 0.5%
AlarmManager (Android System): 2 m 26 s (146 s) Count:2715 0.3%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 2 m 3 s (123 s) Count:971 0.2%
CoreReceiver getWakeLock (com.fsck.k9.K-9 Mail): 1 m 45 s (105 s) Count:699 0.2%
SyncLoopWakeLock (Android System): 13 s (13 s) Count:3104 0.0%
CoreService execute (com.fsck.k9.K-9 Mail): 6 s (6 s) Count:1579 0.0%
*sync*_subscribedfeeds_Account {name=darylfigge@gmail.com, type=com.google} (Google Services): 3 s (3 s) Count:972 0.0%
CoreService onStart (com.fsck.k9.K-9 Mail): 2 s (2 s) Count:1305 0.0%
*sync*_com.android.browser_Account {name=darylfigge@gmail.com, type=com.google} ================
Kernel Wakelocks
================
"wibro_wimax_sdio" (): 2 h 36 m 29 s (9389 s) Cnt:(c/wc/ec)1884/39/1884 6.8%
"mmc_delayed_work" (): 2 h 19 m 58 s (8398 s) Cnt:(c/wc/ec)2807/0/2807 15.9%
"deleted_wake_locks" (): 1 h 40 m 30 s (6030 s) Cnt:(c/wc/ec)82792/0/5085 11.5%
"PowerManagerService" (): 45 m 11 s (2711 s) Cnt:(c/wc/ec)2519/0/0 5.1%
======================
Alarms (requires root)
======================
com.zynga.scramble (): Wakeups: 168

com.zynga.words (): Wakeups: 176

com.facebook.katana (): Wakeups: 176

com.google.android.gsf (): Wakeups: 102
Alarms: 30, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 25, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 18, Intent: com.google.android.intent.action.SEND_IDLE

com.android.phone (): Wakeups: 81
Alarms: 81, Intent: com.android.internal.telephony.cdma-reconnect

That's a pretty messy dump and I see a lot of things:

- you seem to have had pretty unstable data connection conditions during this reading, leading to a huge number of wakelocks on sync and a high number of reconnects of google talk

- I see a lot of overhead cause by wimax and that seems to be the biggest cause of awake time, both in userland and kernel. Now I don't know wimax enough to tell how efficient / bad it is regarding to battery but under your conditions it seems to kill your phone.

If those are your normal conditions wimax is your problem. Now I don't know if as on 2G/3G you can force another battery friendlier connection type but you should if you can.

If those conditions are not normal you should post another dump so we can look at the profile without that overhead (I see quite some potentiel in the apps you run too)
[BetterBatteryStats] suku_patel_22:
This could be due the wifi sync feature in winamp....
[BetterBatteryStats] chamonix:
The reading is missing the kernel wakelocks so the only think I can tell is that partial wakelocks / alrams are not showing anything because indeed your phone is not sleeping. Either we will see something in the kernel wakelocks of you have another problem, maybe related to suspend being aborted. A dmesg would show that
[BetterBatteryStats] chamonix:
Here you go: http://grepcode.com/file/repository...r.java#PhoneWindowManager.0mBroadcastWakeLock

This wakelock is abnormally high in your case. Looking at the sources (the AOSP ones can't tell which ones were used to build your android) this wakelock is held while buttons (volume, headset, media button) are processed. The wakelock could be caused by a stuck volume button or a constant pressed button on your headset but also by a defect or stuck button.

Of course a buggy code is not excuded either and you could easily check this in your favorite ROM thread
[BetterBatteryStats] chamonix:
Just to tease you guys a little. I'm currently running 1.8 with Tasker plugin for automatically writing dumps, knowledge base caching to reduce overhead and responsiveness and I just started coding a widget. In this release I also aim at providing an alert for awake situations during last screen-off phase and maybe a few other things. I give myself a timebox of max one more week to be feature complete and will start posting release candidates from then,
[BetterBatteryStats] coolfire:
Wow, thanks a million, mate! Now I realised that last note, the rubber buttons of my case were out of position and hence, kept pressing on my Note's volume buttons. Amazing stuff from you!

Sent from my SGN
[BetterBatteryStats] figgarro:
Thanks for the info, going to make a change with wifi to leave it on when asleep and see if that makes a difference, I don;t have very good signal at home. Also I'm signed out of Gtalk, any other ideas on how to keep that from reconnecting?
[BetterBatteryStats] pike888:
my battery usage shows that android os uses more battery than display.

i've installed betterbatterystats, and found out that kernel wakelocks could be the culprit.

under kernel wakelocks those two are on top:

"event4-120"

27m28s (1648s) Cnt: (c/wc/ec)0/0/0 89.8%

"DPRAM"

9m32s (572s) Cnt: (c/wc/ec)1326/0/11325 31.2%

what could be the problem?
[BetterBatteryStats] azrash:
running over Wifi ie wifi is set to not sleep is always better in my experience. You can disable the automatic log in for Gtalk. From my experience most of the drain happens due to sync, so I use Tasker to set the sync to be in intervals of 2 hours when I sleep(wifi at home) and I only sync when necessary on mobile data connection
[BetterBatteryStats] Konsyst:
ConnectivityService

I've looked through my wakelocks and figured out most of them: I've just tried disabling screen lock sounds to get my AudioOut and AudioIn down.

However, I still have ConnectivityService pop up from time to time, and heavily. Would this be similar to a dialer wakelock due to poor reception while travelling and such? It's only started appearing in ICS, I've never seen it in GB.
[BetterBatteryStats] Konsyst:
The dump was only taken after 8m41s; not much can be said from this.

You should reboot your phone, plug in and unplug your charger, and leave your phone on for 4 hours or so without using it, then post a dump.

JD is known to have negative effects on battery life due to it switching radios on and off and keeping the phone awake. Try turning it off and look at the wake times then.

Also, using code tags, or attaching a txt file would be preferable (:
[BetterBatteryStats] jeremysherriff:
Hi, if you could edit your post above and put [CODE../CODE] tags around the tech info like I have in the quote, it'd be appreciated.

You don't need to read 400 pages, but it would be good to read the first and second posts. But in summary, to get a useful dump file:

make sure you grant BBS root access - especially to the alarms view.

charge your phone for a bit, then unplug - this creates the "since unplugged" time marker.

leave your phone idle for a period of time. 2h is enough. But idle. This should be during a time period that represents your normal day, so if you use tasker or some other profile app, make sure your time period allows your normal activity to be recorded.

take a dump file when you are on the "since unplugged" view, and upload here as an attachment.

???

profit!

It would be good to take a look yourself and see if you can spot the culprits, also check that each of the section have data in them and none show a message "no reference".
[BetterBatteryStats] itsLYNDZ:
I'm not sure what you mean by tags. I will reboot it tonight and charge till it is full and then do the 4 HR drain tommorrow. Should I just upload the txt file to a site and link it?
[BetterBatteryStats] itsLYNDZ:
I reread the first and second post, and I noticed my alarms portion wasn't populated. My phone is rooted and bbs has root rights. Not site why that isn't populating. I don't have any alarms set tho.
[BetterBatteryStats] Konsyst:
When you hit the reply button, you should see a button that looks like #. Paste the dump into the message box, select all the text with Ctrl-A, then click the # button to show your dump as indicated.

Your alarm isn't populated due to your dump being after 8m. It hasn't had time to be populated.

Alarm doesn't exactly have to do with alarms being set, the AlarmManager process handles many events, which is why they are labelled as such.
[BetterBatteryStats] jeremysherriff:
Edit your post, and then click "go advanced" which will take you to the advanced editor. Highlight all the tech part, and then click the "#" button in the editor/toolbar. It will put "[ CODE]" and "[ /CODE]" at the beginning and end and make it go into a pre-formatted, scrollable box. Just keeps the thread a little tidier. If this still doesn't make sense, ignore it ;)

The alarms section should have been populated in the dump file if you can see any info in the on-screen "alarms" view. There is a bug, @chamonix has it on his list to fix. You might need to go into the super-user app and grant some permissions manually, or uninstall then re-install BBS and make sure to always allow the super-user root access requests.

If you go Menu->more->raw alarms can you see data? If so, then something should be in the dump file too.
[BetterBatteryStats] itsLYNDZ:
Here is the stats after leaving it unplugged overnight. It was at 58% when i woke up it was at 30%. keep in mind I also have the 1900 mah battery, so that is still quite the chunk of battery to be eaten.
[BetterBatteryStats] CRXed:
@nam3less: When I leave my Galaxy S2 idle, it drains about 2 to 4% in 8 hours!

That's with the extended 2000mAh battery. And even then I have more Awake time than I see in your logs.

Have you tried using the original battery again?
[BetterBatteryStats] jeremysherriff:
Hi, the short answer is yes, the reception strength being at -90db is going to be contributing to the drain, and in a way that BBS isn't going to report (or any other app that I know of).

Your dump file looks great, very clean and there's nothing that I can see that will help.

The only red flag to me is:

Alarms (requires root)
======================
com.android.phone (): Wakeups: 240
Alarms: 6, Intent: com.android.internal.telephony.gprs-reconnect.2
Alarms: 229, Intent: com.android.internal.telephony.gprs-data-stall

which I believe is to do with the 4g drops and re-polling you mentioned.

In reality, the next thing to try is dropping back to 3g or 2g and seeing how much difference it makes. I have no other suggestions. HTH :)

Edit: Oh, i missed the comment about screen time - is your brightness high?
[BetterBatteryStats] itsLYNDZ:
Any suggestions on mine above? I attached the file rather than coding it, since I really didn't understand that part
[BetterBatteryStats] jeremysherriff:
Hi :) Attachments are best!

My first thought was "the phone hasn't been idle". Screen-on time is just over an hour, so you've been using the phone and it's a bit harder to figure out what is background processes vs your own usage.

In regards to wakelocks etc, these three items are all related I think:

Kernel Wakelocks
================
"mmc_delayed_work" (): 19 m 22 s (1162 s) Cnt:(c/wc/ec)923/140/923 3.8%
"radio-interface" (): 14 m 1 s (841 s) Cnt:(c/wc/ec)1256/0/0 2.8%
"svnet" (): 13 m 44 s (824 s) Cnt:(c/wc/ec)3580/442/3581 2.7%

and they are all about poor reception, dropped data connections, and trying to re-establish data connections. But overall, the wakelocks don't seem to account for the awake time.

One app i noticed in the alarms section is GoSMS - i personally have had trouble with this app and had to change my configuration of it several times before I managed to stop it draining my battery. The main points are:

don't have GoSMS enable lights for the notifications

don't have it pop a notification box either

don't have it repeat notifications (it holds the wakelock the whole time)

Hope this helps ;)
[BetterBatteryStats] itsLYNDZ:
I do have gosms popup notifications set, but that's so I don't have to enter my unlock code every time I get a text, and I get allot of them, haha. I will try again in a few days and post
[BetterBatteryStats] nam3less:
I never put the original battery in. I ordered the extended from VZW because it was $25 (50% off thing they were running). I can try breaking the stock battery in and seeing any difference. I can see where you would think a potentially bad battery. I will break the battery in this week (take a charger to work, just in case) and report back if anything has improved.

I will take a final log tonight and then swap to the original battery tomorrow and run it dry a few times.

Also, in the past 3 or so days, i've never actually charged my phone full. So maybe some of that has to do with the battery lying in terms of charge level. I'd start charging it and the minute I saw 30, 35, or 40%, pull it from the charger and let it idle to log.

Brightness is almost at the lowest setting. I am in low light places most of the time so the brightness works best for me. It's definitely under 20%, and not set to auto. I will find a 4g toggle and try running on 3g and see what I get. I do think because of those alarms, that the data gets dropped often or at least the phone has to reconnect to a new tower because the signal strength is so low.

The main goal here is to try to get above 3 hours of screen time. 4 may be unrealistic unless it comes out to be a bad battery or unless i'm doing something horribly wrong :P. I really enjoy the 4g speeds but I guess if the poor signal strength is the main culprit here, then I might just have to toggle 4g when I do my browsing. I'd fine with that, but it sort of defeats the purpose of why I bought this phone. (No, i'm not returning it and yes, I'm happy it's a nexus device). As far as i'm concerned, I blame VZW for the signal strength :P

So far, the most I've actually seen in terms of screen on time was 2.5 hours and I REALLY had to milk the remainder of the battery to make it last until I got home (didn't use the phone in case I needed to make a phone call).

Thanks for the help thus far. :) I'll try out that battery and as always, if anyone has any other suggestions, i'm all ears. If it comes to it, I can always warranty the phone. Last resort though.

EDIT: I realize 4g and 3g signal strength aren't the same. I'm mainly talking about how 4g drains the battery more than 3g when used, hence the using 3g to improve battery life. 3 hours of screen on time with 4g is my goal. that would get me through the day easily. If I can make it from 8 AM to 11 PM without having to do things like go without checking twitter for 6 hours toward the end of the day so my battery won't die, that would be fantastic.
[BetterBatteryStats] jeremysherriff:
do you have the notification light come on via go sms? that one is probably the biggest drainer.
[BetterBatteryStats] algie17:
,does my stats is good?,my battery still draining,
[BetterBatteryStats] itsLYNDZ:
I don't have a notification light, but the screen does turn on. If I select to not have the screen turn on then the option to automatically unlock my phone when I get a text goes away.
[BetterBatteryStats] cheezzzz:
changing hotspots doesnt change the behavior, the drain generally occurs when wifi toggle is left on (elixir widget). ill try to look up the 3 mentioned n see how, already considering to flash to another rom+kernel haha.

once again, thanks Chamonix! will post my next dump once ive tried to fix!
[BetterBatteryStats] jeremysherriff:
Stats looks good to me. Your phone signal is terrible!! Are you on new baseband or old?
[BetterBatteryStats] algie17:
,i use 2g only,ahm im in new baseband and also i have low signal in my room,ahm what do you think cause my battery drain?,
[BetterBatteryStats] jeremysherriff:
The poor reception is most likely the issue causing drain. The p500 is not good when you have poor cell strength.

I have recently sold my p500, I know them well. Sorry, I don't think there is much you can do.
[BetterBatteryStats] zappoo:
Cool feature would be to auto-kill a process that has high wake-lock when screen off.. like the notorius MAIL_SERVICE (Exchange Services). possible?
[BetterBatteryStats] Okur90:
hey guys! I asked this at the CM9 nightly thread and was redirected here. Any idea what the top two are? Lost 40% over night. Checking CPU Spy tells me: 5 hours of 200 mhz and 6 hours of deep sleep. What can the top two items be and how can I get rid of them?
[BetterBatteryStats] tomassan:
Additional tool perhaps?

I found out about Catlog in another thread that I will try out also. Apparently that app can be configured to save logs, so hopefully I might be able to get some useful information out of it.
[BetterBatteryStats] nam3less:
Post a dump so people can actually help. screens only do so much without alarm data and partial wakelocks.

UPDATE: I came to work, noticed my signal strength at an abysmal -102 dbm. Turned on wifi. Rebooted phone. Going to test and take another log on wifi and see what happens. Then doing the battery swap. So far, with wifi on, my battery hasn't dropped 1% in 40 minutes and i've checked every 15 or so. But I need to do a log to make sure. If it is indeed poor signal strength, I might attempt to get a new phone, if VZW can promise me they will send a new and not refurb.

When switching to just 3g, I get an improvement of about 10-15 or so dbm (different measurement, I know). I suspect the towers are located toward downtown Raleigh and I work in Cary and live on the very edge of Cary.

EDIT: checked the 4g signal and I live in an area of strong 4g signal (not Extended 4g where my service might drop in and out). I can understand at work having terrible signal due to building construction. At home I still only get -90ish.
[BetterBatteryStats] test9876543:
I got exactly the same problem and posted in the [REF] Known identified battery drainers thread already as someone else had the same issue and Entropy512 seems to have an idea as to what's causing it, but no solution (yet).

My post including BBS dump: http://xdaforums.com/showpost.php?p=24303262&postcount=559

The thread with Entropy512's posts:

http://xdaforums.com/showthread.php?t=1308030&page=56

He said on 30/March:

"I'll need some time to do research, but based on the name, multipdp may be the new name for svnet-dormancy."

I'd appreciate any hint as to what this may be exactly and/or how to stop it. These two processes don't run when I'm at home and connected to wifi, so it has something to do with mobile data.
[BetterBatteryStats] itsLYNDZ:
I'm noticing even during the day when I'm hardly using it, something is just sucking the life out of my battery. I also have an extended battery and am using Frankenstein blue rom. I'll try to charge it and let it die again tonight for stats.
[BetterBatteryStats] wadokai:
hi there,

can one of you look over my logs and help me out?

There seems to be partial wakelocks.. but i don't know what they are or how to deal with them. Please help, thanks!
[BetterBatteryStats] itsLYNDZ:
I also have titanium backup run at night about 3 times a week or so. Should I move that to during the day to avoid waking up my phone at night?
[BetterBatteryStats] Lightfield:
Besides the high number alarms/wakeups in the Alarm section of BBS, I cannot determine why my drain is so high. The drain occurs mostly when my screen is on and when I'm using the phone. When my phone sleeps, battery drain is minimal.

A dump from overnight:

http://pastebin.com/d6YTavMX

The high number of wakeups from com.google.android.gsf concerns me but I have no idea what it means.
[BetterBatteryStats] jeremysherriff:
26 wakeups for GSF is nothing to worry about. Your stats actually look very good, and as you say - it's only when the screen is on that you experience drain.

One thing I noticed:

Wakelocks
=========
SyncLoopWakeLock (Android System): 12 m 5 s (725 s) Count:193 4.2%

This indicates you had a problem with a data connection to a push service (maybe Beautiful Widgets updates). If you get this all the time, you'll need to try and track down which one is dropping connection, and decide if you need that app.

Your phone has both a dual-core processor and a huge screen - if you turn it on to use it, you are going to be draining your battery. The battery size is "OK" but not "big" @ 1520mAh. I would estimate you should be able to get about 2 days if you are careful, and only about 15 hours if you use it quite a bit.

Suggestions:

- Use auto brightness mode, to ensure the screen is not too bright when it doesn't need to be.

- Don't over-clock the CPU.