yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] chamonix:
Well I am no specialist in GSM implementations but from a user perspective FD is a way to save energy by managing the communication between the phone and the cellular network. FD requires support from your network provider and to make things even more complicated there seem to be different implementations of that standard from the providers, not all with the same results.

To sum it up if your network has FD and that works well with your phone there is a benefit from it but in some cases either where FD is not implemented on the network but running on the phone it is known to cause an overhead and consuming battery. As FD is showing as a cause of awake time I recommend you to try togging it to see if your drain reduces.
[BetterBatteryStats] chamonix:
Well if you need to optimize your screen on drain you should look at ways to reduce the brightness. Depending on the display technology there are tool to go darker than the minimum brightness like LUX or screenfilter.

Now if you ask me when drains your battery when your phone is of I see some potential: the overhead caused by wifi being on all the time is quite huge and it would help to either change your wifi sleep policy to "off when screen off" or turn it off completely when not required.
[BetterBatteryStats] chamonix:
Deep Sleep (): 10 h 52 m 51 s (39171 s) Ratio: 65.6%

Awake (): 5 h 42 m 41 s (20561 s) Ratio: 34.4%

Screen On (): 4 h 13 m 43 s (15223 s) Ratio: 25.5%

With so much screen on time that dumpfile is not really speaking as the biggest cause of awake is you using the phone
[BetterBatteryStats] chamonix:
Since 7 h 40 m 49 s

Awake (): 6 h 20 m 50 s (22850 s) Ratio: 82.6%

"bln_wake_lock" (): 5 h 56 m 49 s (21409 s) Cnt:(c/wc/ec)1/0/0 77.4%

BLN is the main cause of awake and is not supposed to be that way. As long as you cont't fix that there is no way you can improve your drain. The second cause is 58 minutes and it's not worth optimizing before BLN was fixed.

There is really no way to analyse beyond such prominent finding. Compare it to being in a wood and staying that near to one tree that you can't see the forest.
[BetterBatteryStats] chamonix:
Looks pretty much like my profile on the Nexus S. What you may want to try:

- switch to mail poll (with e.g. K9): in my combo with unstable network coverage due to lot of Km by train if works better than push

- if you don't need maps you could try freezing it; I did and use ALTitude to update my latitude location and I am pretty happy that I got rid of all the maps network sniffing stuff.

Note to myself: I definitely should try to prevent part of maps to run to keep some advantages without the unwanted overhead.
[BetterBatteryStats] hars73:
I'm affraid all this didn't help. The phone is still getting the wifi_rx_wake locks every 2-4 seconds.

First there is a "kernel (126) active wake lock wifi_rx_wake, time left 95".

And within a second or so there is a "kernel (126) wake lock wifi_rx_wake, expired"

It seems to happen only when the screen is off. When the screen is on, it looks there are no rx wake locks!

Guess the only way to go around this behaviour now, is to change the wifi policy from 'always on' to 'off when screen is off'.
[BetterBatteryStats] chamonix:
3 minutes awake in almost 4 hours confirms what you say. The only thing that you would benefit from is lowering the monitoring frequency of BMW.

About what other tools tell you: I can not say what that means as I don't know where that data comes from. What I can tell you is that there is no trace of an mentioned activity in the kernel wakelocks.
[BetterBatteryStats] KC Boutiette:
Hey Chamonix, thanks for your reply! Really appreciate it!

I failed to reproduce the problem but the next time I run into it I will, as you suggest, plug/unplug and dump the log after an hour or so. I did not think of that, thanks!

This morning, I did run into my problem again. However, this time it was not triggered by Maps or Angry birds as I did not use them this morning. So my theory is down the drain already, at least partially. The log of this morning is attached, however the log spans 13.5 hours (it includes the night) so please dont bother to read it if you dont expect to find anything.

View attachment BetterBatteryStats-2012-05-21_132328398.txt
[BetterBatteryStats] chamonix:
Thanks for the heads up. Those values are experimental as it seems that not all implementations are passing the right info to the batteryinfo service. I don't know if those differences are kernel, RIL or android related but that is the explanation. In the upcoming version you will be able to suppress those indicators from the "other" stat if they are found to be of no use
[BetterBatteryStats] chamonix:
No that comment was in the context of the BLN wakelock and should not be taken as true in another context. There are implementations of leds blinking and being on without kernel wakelocks
[BetterBatteryStats] chamonix:
You shouldn't be concerned about alarms right now, they are not the driver for your awake times. What I see from userland is a quite with wakelock time due to multiple mail accounts.

On the other hans userland is not your main problem but some kernel wakelocks. Have you tried to find more info about those in your kernel thread?
[BetterBatteryStats] mantian:
I haven't found a thing about it. I'm using Apolo kernel(based on speedmod), but with phenomenal happened the same...
[BetterBatteryStats] nathan14bru:
Hey guys,

Here is the data from BBS, can someone please advise what should I do?

https://www.dropbox.com/s/i46ze1ziigodq1a/BetterBatteryStats-2012-05-22_064946388.txt

https://www.dropbox.com/s/qaki99ddr0u52yz/Screenshot_2012-05-22-06-55-20.png

10x.
[BetterBatteryStats] jeremysherriff:
Hmm I'm going to disable uPnP and see how it goes, my Xperia also suffers from wifi_rx_wake, the GNex also but not as bad, the Galaxy Tab doesn't and the Huawei doesn't. I'll post back.

---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------

Yeah sounds broken. Maybe the aerial connection has become loose.

---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------

Yes, in my experience it does. Especially with Go products! Go SMS can drain my battery flat in 5h if I have the led lights enabled, and don't clear the notification.
[BetterBatteryStats] jaraya13:
Hi, I have a Galaxy Note on ICS LPF and I can't see the graphs, I have read that in some ICS this app doesn't work. Just to confirm please.? Thanks in advance.
[BetterBatteryStats] bsoplinger:
Are there Latitude substitutes that aren't battery burners? Like backtutide (think I have the name correct)? I know you made Facebook substitute suggestions.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[BetterBatteryStats] suku_patel_22:
Altitude by chamonix...

The same dev behind BBS :)

Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!
[BetterBatteryStats] lordgoata:
ALTitude by our very own Chamonix :)

https://play.google.com/store/apps/details?id=com.asksven.betterlatitude
[BetterBatteryStats] CooLasFcuK:
Please help!

Hi, I'm getting a huge battery drain on standby. Around 3% per hour. What is wrong with my phone? Dump file attached.
[BetterBatteryStats] lordgoata:
Interestingly enough I was looking at something totally unrelated to battery drain this morning, and then found something interesting about Access Points. I'll quote Wikipedia as they can explain it best:

http://en.wikipedia.org/wiki/Delivery_traffic_indication_message

Now IF I understood correctly, the majority of access points use a DTIM Period of 1-2, which means it can wake up the devices fairly frequently - typically a computer where battery drain isn't quite such an issue. Where as for a smartphone, a DTIM Period of 4 would be better suited, allowing the device to sleep for longer between pollings.

Not sure if that's of any use, but interesting none the less!

In theory you could run two APs, one for the computers with the standard DTIM and one for smartphones, setting the DTIM higher on that AP. Then you would have the best of both worlds.

Reason I mentioned it, is I thought it might be something people with high network wakelocks could look into, if nothing else helped.
[BetterBatteryStats] yhrn:
The attached dump is only covers 5 minutes. You need to charge the phone, unplug, leave the phone alone for a couple of hours and then create a new dump file (using "since unplugged" reference).
[BetterBatteryStats] xelra:
Hi,

like so many of us I'm having problems with the wlan_rx_wakelock. I'm getting about 1 million wakelocks of this kind per day.

I've looked into things and it seems like the culprit is my NAS. microsoft-ds being the culprit specifically.

It seems like there are a huge amount of packages sent from my NAS's IP address' port 445 (microsoft-ds), going to every port of my phone. In my capture frame it has scanned at least from 48895 to 49352. Without jumping a single one.

I know this is not the thread to discuss problems with my NAS, but I thought that someone here might point me in the right direction as to how to resolve this, and I also thought that the other readers here that also have problems with wlan_rx_wake could learn how to start solving that problem, if we discuss it openly here.

Thank you in advance.
[BetterBatteryStats] jim-bo:
Unless you're seeing TCP SYN packets from your nas to your phone, then you have a slight case of reversed directionality.

Microsoft-ds is a service that runs on the NAS and listens for connections on port TCP:445. The port range on your phone is in the reserved for outgoing connections range, which means that some process running on your phone is periodically contacting your NAS, and each time it does so, the OS is supplying it with a new port number to call out from, which is perfectly normal.

So you need to find out what it is on your phone that is connecting to your NAS. Do you use anything that connects CIFS drives, or browses the windows network, or anything like that?
[BetterBatteryStats] teo2411:
It's me again :D

With some new screenshots and a full BBS dump this time...

EDIT: Looks like there are no alarms in the BBS dump, probably because I just installed it...
[BetterBatteryStats] bsoplinger:
Excellent Latitude replacement. I immediately upgraded to the paid version once I saw how nicely it worked not to mention a chance to get a buck or so more to Chamonix as thanks for BBS.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[BetterBatteryStats] hars73:
Maybe you're onto something! My TP Link router had a beacon interval set to 100ms and DTIM timed to 1. That means 1x beacon interval.

I've now set the beacon interval to 1000ms (just to try) and the DTIM to 8. I'm not sure, but it seems that I've got the rx wakelocks now every 20-30 seconds, where I had them every 2 seconds with the older settings.

I'm going to try this for a few days. I'm not sure what results these settings have on my network (performance).

Here's another interesting article about these settings: http://wireless-nets.blogspot.com/2008/07/beacon-interval-impacts-on-battery-life.html
[BetterBatteryStats] nnay:
I see s*thing strange in the dump of @teo2411 : wakelock time is higher than Awake time ???

I have the same behavior with the same phone and rom. I think that it's a bug of the rom but what is the point of view of the experts of this thread ?

Thank
[BetterBatteryStats] Tungstwenty:
I also see most of the times total KL value above expected value in the 2x2 widget, and when opening BBS and checking KL entries and doing the math, the total is smaller. Dunno if there's something wrong with the reference (since charged, unplugged, etc.) but it's there. I wonder if it might be something related to a reboot persisting some of the values in /proc/whatever instead of a full power down.

I'm on an SGS2 I9100 with Siyah 3.2.5 BTW.
[BetterBatteryStats] Nightshadow931:
My battery life has been pretty bad lately, can someone check what's causing it to drain so fast ?
[BetterBatteryStats] gaui:
com.google.android.apps.maps (): Wakeups: 1385

com.google.android.location (): Wakeups: 35

Maps and GPS is your biggest problem.
[BetterBatteryStats] djelexs:
My battery life has been pretty bad lately, can someone check what's causing it to drain so fast ?
[BetterBatteryStats] chamonix:
You are right correct, kernel wakelocks and alarms are missing a reference. A plug unplug will resolve that.

Your dump shows alarms as a main reason so you should post a new dumpfile.

Besides that:

- sync is pretty expensive because of the availability of the cloud services so you should revisit the options of your Google accounts and make sure you sync only stuff you need

- if unused you should turn off wifi to avoid side effects costing a lot of short wakelocks
[BetterBatteryStats] Birba:
Hi

Could someone please check my stats?

Im running latest slimrom on galaxy nexus with latest cmplus kernel.

But I have the same drain with other roms/kernels.

Yesterday evening my i unplugged my gn from charger at 100%.

Then I went to sleep. The phone was in airplane mode. So data, wifi, gps, bt all off.

When i woke up in the morning after about 7 hours the battery was on 93%.

1-2% drain during this time was normal for me.

I hope someone can tell me whats the culprit.

Thanks
[BetterBatteryStats] teo2411:
Thanks, I'll post a new dump when I get home.
[BetterBatteryStats] nnay:
I post an old dump to see my problem with awake time < partial wakelock time.

For information : wifi off, all sync off, no location service and disconnect from gtalk.

So what do you think about it ?
[BetterBatteryStats] KC Boutiette:
How did you disable Latitude if I may ask? I wanted to freeze it but it is not in the list of installed apps. Or did you replace it by the version of chamonix?

I did not run into my wakelock problem yet but here is the log of this morning. This time it is a proper one, 2h, since unplugged and with no use. Battery use is quite ok, but I wonder is there anything I can improve?

View attachment BetterBatteryStats-2012-05-23_125806678.txt
[BetterBatteryStats] Raistlin82:
Anybody can tell me how to stop google talk having all these wake locks?

Inviato dal mio GT-N7000 con Tapatalk 2
[BetterBatteryStats] azrash:
Hi guys, the phone was 90% when I unplug it from the charger, and after roughly 10 hours, it has dropped to 54% with minimal usage. The phone was mostly stationary throughout the 10 hours with good wifi coverage and was on 2G only.

I feel like there is something I can do to further improve the battery usage. Disabled syncing for unnecessary accounts, and also removed unnecessary apps. Would be glad if someone can give me pointers about my dump file stats here http://pastebin.com/k1c2PSsL
[BetterBatteryStats] Karpfenhai:
Wlan and Alarm Sync are your main Issues ;)
[BetterBatteryStats] azrash:
Thanks for getting back at me, really appreciate it. May I know how can I reduce my wlan power consumption? Or this is due to hardware. I have already set the wifi search refresh rate to 120 seconds.

After reading a bit about the sync manager handlesyncalarm, what I understand is that it is the account & sync setting. Am I right? I only have two gmail account, Whatsapp, Viber and twitter syncing. I guess I can disable Whatsapp and Viber syncing.

One thing that baffles me is Alarm manager is quite high. does it relates to account syncing as well or that is just the normal alarm clock that isn't built in into Android?

Edit: have just switched to Alarms view, Android is the highest with Time tick to be the highest contributor.

Thanks for helping me out!
[BetterBatteryStats] teo2411:
Here it is.
[BetterBatteryStats] mikey4226:
I just installed BetterBatteryStats last night and I took these screenshots of the partial wakelocks after leaving my phone alone overnight. Wifi was left on (I have it set to turn off during deep sleep). I'm not quite sure what to make of all this, but it seems like "network location locator" and "alarms manager" are the biggest culprits. I'm a noob to this stuff, so if anyone has any input on ways of optimizing my battery, it would be greatly appreciated. Should I also post a screenshot of the kernal wakelocks?
[BetterBatteryStats] jonneymendoza:
Hi All. i am trying to track down exactly whats hammering my battery as i am down to 8% now after 13hours only since last unplugged with only 1hour screen time

Below is screenshots of the standard power management in my htc one x:

2012-05-23_22-36-40 by jonneymendoza, on Flickr

2012-05-23_22-36-53 by jonneymendoza, on Flickr

2012-05-23_22-37-07 by jonneymendoza, on Flickr

And here is screenshots and dump file from BetterBatteryStas app:

2012-05-23_22-39-48 by jonneymendoza, on Flickr

2012-05-23_22-38-57 by jonneymendoza, on Flickr

2012-05-23_22-38-27 by jonneymendoza, on Flickr

Thanks in advance
[BetterBatteryStats] xelra:
LOL! I think there is nothing wrong here. Bad reception maybe. But apart from that you just USED your phone.

Playing music, screen on. Maybe lower your screen brightness.
[BetterBatteryStats] gaui:
Put on WiFi sleep policy. Turn off GPS when you're not using it and uninstall Google+ (or disable it sync).
[BetterBatteryStats] kid1da:
I have vibrate on but I still have audio out wakelock
[BetterBatteryStats] gaui:
Do you have sound on keypress?
[BetterBatteryStats] Karpfenhai:
Or Swype sounds?
[BetterBatteryStats] kid1da:
Ya, does that still have an effect even if it's on vibrate? I have sounds with SwiftKey x.
[BetterBatteryStats] Karpfenhai:
Any sound generated by your device will produce this wakelock, you have to decide between wanted and unwanted sounds.

Respectively make a difference between them.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] fsrkewd:
Here is my log, and it said Alarammanager kept my phone awake for 4 hours and 20 minutes. Can someone give me a hand?
[BetterBatteryStats] jonneymendoza:
how do u put on wifi sleep? i can only turn it on or off.
[BetterBatteryStats] jago25_98:
I still can't find a reliable way to trace the wakelock to the.process that requested it. Instead I have to post here and guess really.

What we need is to have.a look at the Dalvik source code and intercept and log the wakelock requests as they happen because afaik BBS doesn't have this (crucial?) Info in the logs it is using

Full dump:

http://pastebin.com/QQa40hjc
[BetterBatteryStats] Karpfenhai:
Where is your dump mate? Maybe we can see something..
[BetterBatteryStats] dimebagdan65:
Lol dump mate... Friends don't let friends go alone... (sorry, I had to!)
[BetterBatteryStats] jonneymendoza:
i have already posted my dump file
[BetterBatteryStats] Karpfenhai:
Okay, Mate, where is your dump? ;)

Please read some sites with care how to post a dump which is useful for further analysis, a dedicated Idle Dump.

Better this way? :cool:
[BetterBatteryStats] dimebagdan65:
Learning and laughing, gotta love XDA
[BetterBatteryStats] KC Boutiette:
My wakelock problem arose again. I have no proof, but again I believe it is connected to using google maps. This time after using google maps, my phone stayed awake (see picture). The service which is causing this is the LocationManagerService, see the big dump file that spans 8h (the 10kb one). This file contains other use as well, but I made the file when I found out I had a problem. The second dump file is the 'idle dump' I took this morning after plug/unplug. Usually the phone does not stay awake anymore after a reboot, but by the time I find out my battery might be drained already. Very annoying. Any tips for what I could do?

I do know that the LocationManagerService is my problem and I think I know the wakelock is caused by some problem in Google maps. I tried freezing google maps but if I reboot while maps is frozen, keyboard functionality is lost and I would like to keep using google maps :(
[BetterBatteryStats] jago25_98:
http://pastebin.com/QQa40hjc

Thanks for the thought :-)

You know, I know it's a lot of work to look through and to be honest I wasn't sure if someone would.

I'm trying to keep on top of the thread and keep going with it because I think having knowledge on this is a very useful thing to have. Those who try to help are going to learn and that means being able to help friends in the future too.

In my case I'm using Gmail as the only thing in sync being used. I guess I could switch to a 15min interval check and use K9mail but it's just clean to not need to do that if possible.

At the mo I have sync being toggled every 30mins by Tasker to save battery but is that really helping? I have keysounds off btw.

Subscribed feeds must be NewsRobber, which is interesting because I set that to no/lowest sync and quarentined it.

I had gTalk unquarantine for this test so I will reQuarantine it and the Talk sync I expect to reduce.
[BetterBatteryStats] Don MC:
Got rid of the WiFi Rx icon blinking. Turned off Spanning Tree Protocol (STP) on my router. Now let's see if that has any impact on my battery life. Will report back.
[BetterBatteryStats] hars73:
It seems my battery lasts much longer now with these settings, although I still get wifi_rx_wake wakelocks, but that's now around 1-2% of the time since unplugged instead 48-50% with my older router settings.

But it seems also that my network acts a bit slower. Going to play with these settings to see what's best.
[BetterBatteryStats] Flomaster:
My awake time is always double my screen on time. I can't figure what app or process is causing this. Here is a dump of normal usage while at work. I tried doing a dump the other night with my phone unplugged, but it died during the night, my alarm didn't wake me and I was late for work. http://pastebin.com/z4ZamEkt

-=Jason=-

sent from my Gnex via Tapacrap
[BetterBatteryStats] itsLYNDZ:
Is there a call blocker that doesnt eat so much battery? i was using Call Master, but that kept waking up my phone.
[BetterBatteryStats] mahercs:
I use Mr. Number. It also wakes the phone up, but maybe not as much?? Won't hurt to try it and compare.
[BetterBatteryStats] gaui:
When in WiFi screen, tap on settings button on the phone and go to Advanced :)
[BetterBatteryStats] Karpfenhai:
Thx for your dump .... mate :-)

For an 12 day 25 mins of additional wakelocks are pretty good!

Taker itself is waking your phone way often, maybe you should try Llama instead, it's running as a service and produces nearly no wakelock.

Wlan_rx could be more less too, read some pages back there are several options for that.

All good, youre done, enjoy your phone!

Btw, here is my wlan rx after more then 2 days wlan always on except during sleep so minus 16 hours:

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] Karpfenhai:
Hello Jason,

Your main culprits are Facebook and gmail sync.

Use friendcaster instead of fb.

Stop syncing gmail, use k9, set to pull every 30 mins, come back with a new dump afterwards for fine tuning ;-)

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Karpfenhai:
Why don't you use the internal blacklist?

Works straight, not much battery life afaik.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] mahercs:
Karpfenhai,

Where is that? I've never seen that option. If it's an ICS feature, I don't have it yet!:(
[BetterBatteryStats] Karpfenhai:
It's right under system settings --> call --> call rejection..

Tapatalked from my Samsung GT9100
[BetterBatteryStats] mahercs:
Must be a Samsung thing. My RAZR doesn't even have System Settings, just Settings. Even under that, then Call Settings, Call rejection isn't there
[BetterBatteryStats] Flomaster:
Thanks, I've installed K9 mail, disabled gmail sync and Facebook sync. I'll let it run over night. I could find the setting in K9 to check for mail every thirty minutes.

-=Jason=-

sent from my Gnex via Tapacrap
[BetterBatteryStats] itsLYNDZ:
The Samsung blaze doesn't have the blocking capabilities other phones do. I can block unknown callers but not private callers. They still get thru for some reason. If I turn blocking off then both get thru so I know they are not the same.