yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] It_ler:
Alarm manager wakelocks are just an indicator for the Alarms:

Google Service Framework (GSF), viber.voip, WhatsApp, Android system itself, kman.AquaMail, Google Play store (vending) and calendar.

If you can reduce the alarms, the Alarm manager wakelocks will be less too.

(Have a look at the bold ones - the other are system alarms ... more or less.)

Good luck !
[BetterBatteryStats] Casanoaa:
All what i say is safe but i dont no about viber and whatsapp autostart settings.

The safest is to delete them
[BetterBatteryStats] chris2busy:
Thanks alot mate!This app was one of my best buys!

By the way, since i have the expert here, could you possibly know if the last post in this thread hold any true?

http://xdaforums.com/showthread.php?t=1462218

In my bbs log i can see that my bootloader is also stated as "unknown" ..Could that be the true?that bootloader version could give wakelocks?
[BetterBatteryStats] Karpfenhai:
I don't think this is true, I'm on unknown bootloader since I flashed ics in January, I'm still on my gb bootloader with no triangle ever. In the meantime I'm on jelly, still using the old unknown bootloader with no issues at all.

Tapatalked from my Samsung GT9100
[BetterBatteryStats] Grigoriy60:
1. Screen rotation is disabled now.

2. Samsung gt-p6810 haven't smart stay feature.

3. BMW is freezed now.

4. logcat is in attach.

5. I beg your pardon, may be it'll be important: the issue persist only when wi-fi is on (this remark applies to 'sensor' version).

Good luck!
[BetterBatteryStats] stanley08:
I guess you are right mate. Though... i just wanted to know who the culprit was. :)
[BetterBatteryStats] Grigoriy60:
The suspend_backoff symtom

Hi chamonix,

1. No. BT is off.

2. Yes. The suspend_backoff symtom goes away if I turn off wi-fi.

3. A fresh dmesg attached.

Thanks, regards.
[BetterBatteryStats] azrash:
Hi guys,

I just want to share my dump file, been getting good results even with my usual apps still on, sync is still on. Left my wifi, 3G and GPS on too

Getting a 0.2%/h

dumpfile http://j.mp/UJhvRS

I still use

1 BMW (battery monitor widget pro) disable the history logging, and no alarms after that

2. Google+ extensively (turn off notification in app, disable the intents in autostarts, and just remember to force stop the app after use)

3. WhatsApp, don't have to disable the autostarts, very minimal alarm unless messages are coming in. Can also disable the daily backups if you really want to squeeze the few seconds of wakelocks it produce at night

4. Viber is freezed using TB widget (freeze/defrost/launch) the widget look like an app shortcut. Just remember to exit viber before freezing it, it'll still produce some alarm if you don't exit or force stop before freezing it.

5. My weather widgets (I use snowstorm), tasks widget calendar widget and etc

6 . GTalk and Xabber (talk client for separate accounts) are running too

7. GoSMS

8. both gmail and k-9

I guess what I am trying to point out is, you don't necessarily have to disable these apps, (although they are the fastest route to better battery life)

Just have to fine tune the apps' settings and play around with autostarts and TB's (freeze/defrost/launch) widget .

Hope this'll help,

Cheers and happy holidays
[BetterBatteryStats] fndpena:
What is Google Play Services?

Freezing it on TB will make Google Play stop working? Someone here in this thread froze it.
[BetterBatteryStats] Casanoaa:
I freeze these google apps see:

http://xdaforums.com/showthread.php?p=36021746

It doesn't harm google play.
[BetterBatteryStats] Karpfenhai:
Thx Sven for hopping into this topic since dmesg it's still a bohemian village to me! ;)

Tapatalked from my Samsung GT9100
[BetterBatteryStats] fndpena:
Google Play Services is frozen in your screenshot!

Just look the first item in the seconds screenshot.
[BetterBatteryStats] chamonix:
unfortunately dmesg does not show any pm (powermanager) events. But there are a huge number of "wmi rx" events that I would interpret as incoming wifi traffic (the events are tagged ath6kl from what I believe are the wireless stack. As turning Wifi off stops the suspend backoff that confirms the above.

Now what you could do against that:

- exclude that this is caused by a dirty wifi access point by testing if this occurs also when connected to other access point (upnp or other multicast/broadcast traffic may be a cause)

- if it's a custom kernel talk to the dev or see if other in the kernel thread have the same kind of problem

- see if changing the wifi sleep policy changes the behavior

Hope at least one of those helps
[BetterBatteryStats] Grigoriy60:
I am very proud to be in Sven's hands... :fingers-crossed:

Thank you for opening my eyes on this: chamonix=Sven ;)

Good luck Karpfenhai.
[BetterBatteryStats] MRDOCA:
well just as i thought things were going great, things take a turn for the worst...

what caused 2.1%/h??
[BetterBatteryStats] wlxxiii:
Hi guys, really need your help here. Would really appreciate if someone can give me suggestions on my issue here http://xdaforums.com/showpost.php?p=36018504&postcount=11474

Many thanks in advance!
[BetterBatteryStats] It_ler:
You should disable/freeze Samsung Push Service.

But your main battery drainer seems to be wifi on and running all the time.

Try to set wifi policy to turn off wifi when phone is sleeping (in menu Settings > Wifi > Advanced > ...).

Good luck !
[BetterBatteryStats] Grigoriy60:
The suspend_backoff symtom

Hi chamonix,

I have some questions (may be due to my 'fluent' English :()

1. What do you mean by "dirty wifi access point"? I have access point through my linksys router secured with WPA PSK.

2. I'm very sorry but I do not understand what I have to do with "if it's a custom kernel talk to the dev or see if other in the kernel thread have the same kind of problem"

Thx & Regards.
[BetterBatteryStats] It_ler:
Main partial wakelock is "GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services)".

Try to enable all autostart options/events for GSF again and check if this wakelock gets lower.

(Facebook is also very active on your phone. Maybe you should disable/freeze it to see its influence on your battery life.)
[BetterBatteryStats] chamonix:
No problem ;)

by 1. I meant that there are known conditions where an access point keeps sending packets that may be interpreted by the phone as request to stay awake. The same packets can under other conditions also cause your phone to wake up. Obviously that theory is only valid if the suspend_backout is only seen when connected to an access point as the chances are small that this may happen on all access points (at least then the cause can not be the access point).

by 2. I meant that if you are using a custom kernel you may want to check the thread about that kernel to see if other users experience the same problem and maybe talk to the dev and report your problem with suspend_backout. Of course if you are not using a custom kernel then you can ignore.
[BetterBatteryStats] chamonix:
That's the problem of not being in a lab. The reading shows quite some time awake due to data transfer. Judging by the low amount of data vs. the time awake and the reconnects from gsf I would say that that reading has been taken under pretty bay connectivity. I'd recommend that you repeat the reading under good coverage conditions before changing anything else. Your previous post suggested that you have made multiple changes at once and I would encourage you to not do such things: tuning requires a lot of care and also to verify the result of each action so taking multiple steps at once will always lead to incertitude.
[BetterBatteryStats] chamonix:
Wifi being on and your led blinking
[BetterBatteryStats] chamonix:
that made me LOL!
[BetterBatteryStats] MRDOCA:
thanks. what was casuing the 1000 wakeups?
[BetterBatteryStats] Grigoriy60:
The suspend_backoff symtom

Thus the custom kernel version is not relevant.

The last chance to win the issue is to check it on another access point. It needs some time.

Bye.
[BetterBatteryStats] zetsui:
Not just good but great
[BetterBatteryStats] Karpfenhai:
I don't understand your concern, the attached screenshot was raw kernel wakelock...

Here is a new one:

Plus my current wakeup_sources:

name active_countevent_countwakeup_countexpire_countactive_sincetotal_timemax_time last_changeprevent_suspend_time event0-166106 7 0 0 0 160 102 66763494 160 event1-166100 0 0 0 0 0 0 66085452 0 event3-166102 2 0 0 0 13 7 66509018 13 event2-166107230 7230 0 0 0 861 7 66872135 0 PowerManagerService.Broadcasts67 68 6 0 0 850173 803130 66509717 61714 KeyEvents 318201 318201 15562 0 0 57713 643 66872135 6963 PowerManagerService232444 232448 23055 0 363551 54369143 26983149 66509017 29990919 android-ac 12 12 0 0 0 3 1 66790248 2 android-usb 12 12 0 0 0 6 2 66790248 4 android-battery1923 1924 48 0 0 104113 158 66849390 82911 android-chargerdetect10 22 0 10 0 21478 3370 66792250 2420 android-battery-monitor1923 3846 136 0 0 59807 79 66849337 48927 vbus-manta_otg1 2 0 1 0 3464 3464 10405 0 wlan_ctrl_wake1685 5220 400 1685 0 2009288 4920 66122405 444775 wlan_rx_wake7248 2074367 411444 7248 0 23460715 735615 66766890 16109715 wlan_wake 4752607 4752607 839463 0 0 2425096 1459 66871525 1810255 vbus 10 10 0 10 0 4967 499 66790745 408 manta-board 1 1 0 0 0 0 0 5439 0 alarm 5012 5508 618 13 0 286712 6193 66864080 211887 mmc1_detect 2 4 0 1 0 598 539 7320 0 mmc0_detect 7980 7982 322 0 0 2026 198 66509021 1827 ds2784-fuelgauge1 1 0 0 0 49 49 5071 0 smb347-battery11 16 0 0 0 16203 3589 66789627 4681 smb347-usb 11 11 0 0 0 9116 1826 66789622 3652 smb347-mains6 6 0 0 0 1 0 66789621 1 exynos5-fimc-is20 0 0 0 0 0 0 4954 0 max77686-rtc0 0 0 0 0 0 0 4845 0 vibrator 1298 1298 106 0 0 27830 302 66818318 0 alarmtimer 322 322 322 322 0 645213 2004 65957505 644250 BTHostWakeLowPower0 0 0 0 0 0 0 4395 0 BTWakeLowPower0 0 0 0 0 0 0 4395 0 5-0009 0 0 0 0 0 0 0 4355 0 gpio_input:manta-keypad...0 0 0 0 0 0 0 4325 0 gpio_input:manta-keypad...450 450 61 0 0 4637 20 66763494 494 dock_pd 1 1 0 0 0 250 250 4610 0 dock 0 0 0 0 0 0 0 4310 0 manta-chgredetect0 0 0 0 0 0 0 4310 0 manta-chgdetect10 10 0 0 0 22402 4173 66790247 7306 serial-debug1 1 0 0 0 500 500 625 0 autosleep 74 74 6 0 0 0 0 66509457 0

Hope it helps..

sent from my Nexus 10
[BetterBatteryStats] xelra:
That wouldn't give you conclusive results.

Checking on another AP may but doesn't have to be a valid test.

The other AP could be as dirty as yours.

But in case it isn't, then yes, you would know that it's the source of your problem.

To solve this you need to proceed analytically one step at a time and get your logic straight.

Good luck.
[BetterBatteryStats] Firnagzen:
So here's a new overnight dump, along with a log cat and dmesg... made it with the new version of BBS (realized I was using a very old version). Galaxy Nexus, rotation disabled in the Settings menu. If anyone would be so kind as to help me have a look?

EDIT: By the way, if I've done something wrong with the files that they're unreadable or something, please let me know?
[BetterBatteryStats] Casanoaa:
Sorry i misunderstood you. All that i have disabled doesn't do any harm. Everything works and google playb works.

I think you said google services framework. If you disable that then your google play would not work.
[BetterBatteryStats] zetsui:
Nope no G+ update.

Anyone else having the msm_camera wakelock pop up after using the 4.2 camera apk? I am on 4.1.2 but took the gallery from 4.2 (since its a fullscreen edge to edge camera) and put it in my system file.

It only occurs after I use the 4.2 Apk. Rebooting my phone will take it away.
[BetterBatteryStats] drraptor:
I will add the dump file in a min

http://db.tt/CyVJtLWm dump file
[BetterBatteryStats] Grigoriy60:
The suspend_backoff symtom

So beautifully written xelra. Thx.

And what do you advise to do (step by step)?

Regards.
[BetterBatteryStats] onewayout:
Hi Guys

Thanks to all who helped me reign in my battery issue!!! :good:

Ok since yesterday my battery is going INSANELY strong! coming up to 20 hrs of moderate use with of overnight 8 hrs no use....Anyways, I was holding pretty steady at between 2.2%-3.3% p/h battery usage for the 1st couple hours after full charge. then I was receiving JUST texts from my sister on google+ (12 to be exact over a 8 hr period) and the phone creeped up to 6.0% p/h and even on standby it never dropped from that 6.0%. I forced stopped google+ and even froze it with TITANIUM PRO. The phone would go into deep sleep while we were watching a movie and even the WIFI would sleep....But it still stayed @ 6.0%....

After I woke up, it was at 2.3% after only losing 2% of battery overall for 8 hrs!! And started I STREAMING music w/JANGO on Bluetooth and it went up to 3.3% and STAYED there...

My question is what is bringing it up to the 6% and not letting it drop on standby??

I'm sending 2 dump files one from last night when it was running at the 6% and one from this morning....

Cheers Guys!
[BetterBatteryStats] xelra:
Log your traffic on your phone with shark. Then analyze the saved file on your computer with wireshark.

Look out for multi cast, DHCP and everything that originates from your router.

Keep your network as "silent" as possible while capturing.
[BetterBatteryStats] Grigoriy60:
The suspend backoff symptom

Thx for your advise.

I'm afraid my level doesn't allow me to do such analysis. But I'll try.

Meanwhile did you talk about Wireshark protocols app?

Does the app help to do both: log my traffic and analyze this log?

What do you mean by this: Keep your network as "silent" as possible while capturing?

Thx.

Regards.
[BetterBatteryStats] starbright_:
I try to find the unusual battery drain. After reboot, before enabling WIFI everything seems to be normal.

My phone seems to have problems when wifi is enabled. The time of "Awake" is much higher than the "Screen on".

Kernel Wakelocks show 2 items above "Power manager Service"

- wakeup_driver

- wifi_rx_wake

After disabling WIFI the 2 items that are higher ranked as "Power manager Service" are

- deleted_wake_locks (which seems to to be a renamed wifi_rx_wake ??)

- wakeup_driver

So the only "normal" behaviour is after reboot before enabling WIFI.

I updated quite a few apps last time. So I don't know what might cause this. How can I find out the reason for this?

I googled for this issues with no real result.

If this items are in the "kernel wakelock" categorie - does it means it has no connection to a user app?
[BetterBatteryStats] chamonix:
Sorry for that, I must have misread the screenshots. I will start all over with the last one.
[BetterBatteryStats] chamonix:
Well allow me to disagree. Of course testing with another a/p may not be conclusive but IMHO it's easier that tracing traffic as the dumpfile in that case does not show the typical symptoms of multicast: rx_wake are missing.
[BetterBatteryStats] chamonix:
I noticed that you didn't ask about the effect of the wifi sleep policy. Have you tested the effect of changing it?
[BetterBatteryStats] Grigoriy60:
chamonix&me vs suspend backoff

Hi there,

Wifi sleep policy modes "Never" & "When plugged in" give the same result - suspend backoff persists.

And in mode "Always" - suspend_backoffs disappears.

Dump and logcat (for mode "Always") attached.

Regards.
[BetterBatteryStats] elmexicanoalto:
Anybody else get "wlan_RX_wake" under Kernel wake locks run crazy when un-checking the WiFi optimization option under Advanced WiFi settings? Never used to have problems with WiFi kernel wake locks until 4.2.....
[BetterBatteryStats] MRDOCA:
well another night gone and still im losing battery for no reason!

heres my dump:
[BetterBatteryStats] xelra:
The Android app for capturing is called shark. The windows (I assume you have a PC running windows) app is called wireshark.

Shark is very rudimentary and can't be used for analysis. You need to load your capture file with wireshark on a PC.

There it will show you an immense amount of data that is your "raw" traffic.

What you may find there may differ. I will elaborate one example:

Let's assume your router (you said linksys and linksys are usually nice routers) is fine and when you shut everything of your other home network devices off, you got no problems. But you know that if you have everything on that your battery gets sucked dry in no time.

You look at your capture data with wireshark and see that there are lots of packages sent from 192.168.1.143. You further determine that that's multicast (packages that get sent to every device on that network) from your mom's notebook.

Now you know the source and I you should also check your mom's notebook for malware or trojans.

Now let's assume you have a multicast source that's your brand new smart tv or plex media center or.....

In that case your options to "clean" your network might be limited.

To defend against battery drain from multicast (I'm always talking about it, but it doesn't necessarily need to be the source of your problem. Most times it is though) there are 2 ways to go. You can "clean" your network from multicast sources or install a kernel that doesn't respond to multicast packages. For Samsung Galaxy S devices that would be every AOSP kernel and pre ICS kernel. Unfortunately Samsung opened up the firewall for multicast with the introduction of ICS and that has been the cause for many people's suffering (of the mind).

Networking is a complex matter and requires lots of do it yourself effort.

Once you have a capture file, maybe the guys on the wireshark forum can help you.

And only capture headers. Do not ask for advice with a full capture file publicly. People can read it all and you are compromising your network security that way.

With "as silent as possible" I mean that you should shut off as many devices as possible to reduce the sources of error.

Good luck.
[BetterBatteryStats] chamonix:
There is a reason: WLAN being on and waking up your phone
[BetterBatteryStats] It_ler:
That's not true ... your battery drains for many reasons:

1. NetworkLocationLocator: Disable all location service options in ROM/Google settings.

2. Google Maps: Optimize Maps by following Karpfenhai's description (link in post #3).

3. Wifi on and running all the time: Set wifi policy (in Settings > Wifi > Advanced > ...) to wifi off when phone is sleeping.

4. Google quick search box: Disable/freeze Google search.

Good luck !
[BetterBatteryStats] MRDOCA:
location settings is off

my maps are disabled in autostart.

wifi was on... i did set it to turnoff while sleeping but i reflashed my rom so must have reset (grrr)

google quick search. ok i'll freeze that.

weird my maps is still working even though its disabled in autostarts :S
[BetterBatteryStats] It_ler:
And you are sure that all location service options are disabled?

Also Latitude, etc.?!

If there is one location service enabled, you will get Maps wakelocks and Alarms.
[BetterBatteryStats] MRDOCA:
yea man check it out. although i dont see a lattitude option anywhere??

i dont know why my picture isnt showing up but you can copy the link and open
[BetterBatteryStats] It_ler:
Latitude option should be in Google settings.

Start Google Maps, goto app menu Settings > ... there you should find something like location and then latitude (there it is on my SGS2).

Maybe someone with an SGS3 can assist if you can't find it.
[BetterBatteryStats] MRDOCA:
google maps/location settings/ lattitude location sharing?? no option is ticked
[BetterBatteryStats] elmexicanoalto:
4.2 has really made dislike Android so far... I've never had issues with kernel wake locks and this terrible battery drain has just ruined my experience... BetterBatteryStats has ruined my life lol. Its to the point where I just want to get a reliable and simple iPhone...
[BetterBatteryStats] jlv3:
blank widget with v1.12rc2 and rc3?

I updated to rc2 the other day and the widget was blank. I removed and reinstalled the widget to no effect. Ditto with removing and reinstalling BBS. I also rebooted my phone. Once I open BBS, the stats are all there; it's just nothing is displayed in the widget. Any ideas?

My phone is a rooted Galaxy Nexus currently running 4.1.1.
[BetterBatteryStats] chamonix:
If you were not on 1.11 previously you should revisit your preferences and make sure that the default stat types are set in the widget prefs. The prefs format has changed and the migration does not work properly coming from any 1.12 beta
[BetterBatteryStats] elmexicanoalto:
Anybody else getting modem_usb_gpio_wake and modem_usb_suspend_block run wild under kernel wake locks? Didn't have this issue until this morning and noticed they continue even while on Airplane Mode. Now my phone charges at 1% per hour. I've flashed different Roms, kernels, done factory resets and they continue I've Googled this issue and came across several threads of people having the issue but no solution. This is getting ridiculous....
[BetterBatteryStats] Karpfenhai:
I assume you are using an lg device?

Search this thread, gpio and author myself, you should find several posts handling your issue.

Okay I did it... :p

Tapatalked from my Samsung GT9100
[BetterBatteryStats] connectandroid:
Same battery life on rootbox 4.2.1 not ideal (s2 + mugen 3200mah) went from min 60hrs battery life with 24/7 wifi 8+ hrs screen time on 4.0.4 to initially 17.5 hrs on 4.2.1 and around 5.5 hrs screen and ~11hrs wifi.

For me it is mainly on screen usage that drains at up to 15%/hr, sleep it was like 3-6%/hr. With help of BBS app :) and setcpu with under clocking on certain apps (games) gotten sleep to like 0.5%/hr to 1.5%/hr and on screen to around 3-5%/hr and clawing my way back to around 25-35hrs battery life with sacrifice of less screen time <4hrs and wifi <4hrs.

Definitely give setcpu + BBS apps a go if you want to remain on 4.2
[BetterBatteryStats] chamonix:
Release 1.12RC4

New version is up
[BetterBatteryStats] elmexicanoalto:
I actually have a Samsung Galaxy Nexus - Sprint. I was running 4.2.1 rasbeanjelly with latest Franco nightly. Just switched back to 4.1.2 and it seems like the issue followed me... as for gpio wake are you saying that has to do with my wi fi right? What's weird is that when I did a clean install I chose not to restore apps and settings so I virtually only had gapps (no Maps) and no apps were waking my phone yet I still was getting gpio wake.. could it be if someone else is on my network (watching Netflix) that would be the reason my network wakes my phone up? I'll provide an idle log after work tonight.
[BetterBatteryStats] Perilla_:
RC4 ask to rate the app each time I open it.

Enviado desde mi Nexus 4 usando Tapatalk 2
[BetterBatteryStats] fndpena:
1 day and 6 hours of normal use (calling, games, internet etc).

Good? Or any way to improve even more?
[BetterBatteryStats] chamonix:
Thanks for reporting. I will fix first time in the morning
[BetterBatteryStats] cdzo72:
Getting a BBC Watchdog Processing... message that once it comes up on screen it freezes the phone and won't go away
[BetterBatteryStats] Grigoriy60:
Good morning chamonix

I posted my report about the effects of the wifi sleep policy yesterday.

New Year is coming... Congrats! :victory:
[BetterBatteryStats] djvesic:
This is my dump file.

Can somebody take a look?
[BetterBatteryStats] chamonix:
This may be of interest for nexus 4 suffering from msm_hsic_host wakelock https://github.com/CyanogenMod/lge-kernel-mako/pull/1 (tweet by @pof)

Edit: and you may want to star this: http://code.google.com/p/android/issues/detail?id=41855

Edit2: which was fixed in Franco's kernel in r22
[BetterBatteryStats] slph:
Can't save logcat, file contains: "Unable to open log device '/dev/log/main': Permission denied"

Root checked in advanced, app alowed for root, but app doesn't ask for root.
[BetterBatteryStats] fjkum:
Fix permission...
[BetterBatteryStats] chamonix:
Release 1.12RC5

New version is up fixing the annoying "rate" dialog and with some tweaks.
[BetterBatteryStats] Casanoaa:
It looks good IMO.

You can delete juicedefender and facebook for better battery life.

Turn off autosync on google account.

See post 3 in this thread for maps.

Also you can set up your email as pop3 instead of exchange.