yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] jhuff83:
If anyone is using autostarts or Gemini and Facebook for Android? Would like someone to post some tips like the other user did for maps. Basically I would like to still get my notifications but not sacrifice all these wake locks. I have tried messing with the settings but sometimes my notifications don't come through.
[BetterBatteryStats] decayed.cell:
Anyone getting SystemUpdateService partial wakelock on latest CM 10.1 nightlies for Note 2? I've turned off Play Store updates as well...
[BetterBatteryStats] cdzo72:
There's really no middle ground with Facebook app... you use it and want notifications then it will suck your battery... that's why its suggested to use Friendcaster Pro and set it to push notifications... but you will.still have several wakelocks
[BetterBatteryStats] Casanoaa:
Disable

ait.podka.services.AudioService (ait.podka.Podkicker): 24 m 39 s (1479 s) Count:4 3,9%

Prevent sleeping (com.somafm.SomaFM): 12 m 14 s (734 s) Count:1 1,9%

com.maxmpz.audioplayer.player.PlayerService temp (UID): 8 m 14 s (494 s) Count:72 1,3%

Enable alarms and network in bbs app. Provide an idle log. Unplug and leave phone 4 hours and dump a file.
[BetterBatteryStats] ishyboy15:
http://db.tt/xMjvRqiS

Hi guys please review mine. .9% per hr for 5hrs. However still seeing a lot of wakelocks. Thanks
[BetterBatteryStats] decayed.cell:
Pretty sure that's insanely good. If anything you seem to have Exchange mail set up which may be waking up the phone. You can also try the Autostarts settings for Google Services Frameworks
[BetterBatteryStats] ishyboy15:
Will be trying the auto starts settings :)

What about exchange email? I jave disabled auto sync for eveything
[BetterBatteryStats] melvinaury:
Wish one of the autostart app you recommend, the one with the red car icon.
[BetterBatteryStats] decayed.cell:
======================

Alarms (requires root)

======================

com.android.exchange (): Wakeups: 50

Alarms: 41, Intent: {com.android.exchange

Alarms: 8, Intent: {com.android.exchange

You can see here Android Exchange has woken up the phone 50 times. The only thing you can try is changing to manual sync (which I'm pretty sure you have already done). Other than that I don't think theres anything wrong with your drain

Yeah that's the one $2.00 in my country
[BetterBatteryStats] jhuff83:
Yea that's what I was afraid to hear. I did play with the settings but then notifications would stop working. Would have to clear the data and cache. Might tinker with it some more. Tried Friendcaster in the past and didn't care for it. Maybe they have made some changes.
[BetterBatteryStats] FireBird_89:
Hey everyone I'm running Galaxy note 2 with perseus kernel, and jedi rom. flashed perseus about 4 days ago. for 4 days, there was no problem with wlan_rx_wake, but suddenly it started showing up (i believe that is what is keeping my phone awake according to the log) - just want confirmation and to see whether you see any other culprits. Is there anything that could change the perseus kernel so that is not filtering mDNS packets?
[BetterBatteryStats] Jane Shizuka:
Would be possible to automatically create a dumpfile every 24h (or x hours) of continuous use with a bunch of selected information?

Say: In the last 24h battery drain was 2%/h (88 -> 40); deep sleep was 80%, screen on was 15%.
[BetterBatteryStats] GermainZ:
Sync FB/GMail manually, read the OP for more info on minimizing wlan_rx_wake, Google Maps wakelocks, and GSF wakelocks.

The biggest drainer is probably wlan_rx_wake tho, yes.

You can use Tasker to create a dump then remove the lines you don't need.
[BetterBatteryStats] poo706:
Free on fdroid. Didn't find that out until after I bought it.

[poo]
[BetterBatteryStats] Karpfenhai:
Rom toolbox lite does pretty much the same and is for free.

sent from my Nexus 10
[BetterBatteryStats] GermainZ:
So is autostarts from F-Droid. :)

You don't have to download F-Droid, BTW. Just check the repo page.
[BetterBatteryStats] Tuggbuss:
Just installed the app and i assume its doing what it should really good, but i have no clue what i'm doing. I've changed everything in the app trying to customize some of my views. So my question is simply -How do i reset the app-settings like it was when i first installed and started the app?
[BetterBatteryStats] iamatechnoob:
No idea how to post any stat files from BBS (where do you guys get them) but I have a screenshot of the kernel wakelocks that's draining my touchpad when its supposed to be asleep. Partial wakelocks are fine thus no screenies.

Anyone can help? :/
[BetterBatteryStats] oae08:
Hello everyone, I have a tough one for you :p I am having 1.1% drain per hour even though BBS reports I am achieving 97% deep sleep.

Can anyone help me identify the culprits to the drain? Every tip matters! Thank you.
[BetterBatteryStats] Casanoaa:
Wlan_rx is your problem here listed :

10017 (Wifi) (com.android.email.Email): 242.0 KBytes 49.5%

10018 (Wifi) (com.android.exchange.Exchange Services): 63.0 KBytes 12.9%

10035 (Wifi) (Google Services): 55.0 KBytes 11.4%

10058 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 33.0 KBytes 6.8%

10050 (Wifi) (com.google.android.syncadapters.calendar.Google Calendar Sync): 23.0 KBytes 4.7%

10172 (Wifi) (com.citc.weather.Eye In Sky): 20.0 KBytes 4.2%

10164 (Wifi) (com.google.android.gm.Gmail): 14.0 KBytes 2.9%

10080 (Wifi) (com.viber.voip.Viber): 10.0 KBytes 2.2%

0 (Wifi) (0): 10.0 KBytes 2.2%

10193 (Wifi) (com.asksven.betterbatterystats.BetterBatteryStats): 5.0 KBytes 1.1%

10152 (Wifi) (com.google.android.keep.Keep): 4.0 KBytes 0.9%

10043 (Wifi) (com.whatsapp.WhatsApp+): 3.0 KBytes 0.8%

10027 (Wifi) (com.cyanogenmod.lockclock.cLock): 2.0 KBytes 0.5%

Try mininizing network connectivity with these apps
[BetterBatteryStats] oae08:
Thanks, but may I ask why does bbs use wifi for?

10193 (Wifi) (com.asksven.betterbatterystats.BetterBatteryStats ): 5.0 KBytes 1.1%

Thanks
[BetterBatteryStats] LucentBirch:
Just posting to see what you think

I figured I'd post a dump jut to see if you guys think anything is out of the ordinary.

thanks in advance!
[BetterBatteryStats] GermainZ:
Knowledge base and Google analytics, if I'm not mistaken.

Basically, you can disable autosync for your apps and do what the above posted said, to maximize your battery life. Also, read the OP for more information about minimizing wlan_rx_wake and GSF wakelocks.

Looks good to me. Not sure if some of the traffic was requested by you (7m screen on time), but if not, you can check why Google Music is using your data (I'm guessing you used it).

Read the OP as well for tips to keep wlan_rx_wake and GSF wakelocks to a minimum.
[BetterBatteryStats] oae08:
So I can revoke internet permission from BBS without any problems?

For reducing the GSF wakelocks, i saw the freeze list, and in the list i saw this:

com.android.smspush and Factory Mode 1.0

Does this affect my sms if i uninstall/freeze it? what does it exactly do?
[BetterBatteryStats] GermainZ:
Well, you can disable Google Analytics instead, but you could do that as well. :)

I've personally never used that freeze list, so I can't talk about these.
[BetterBatteryStats] LucentBirch:
Yeah I wasn't sure about the Google music bit. I didn't use it at all. That's what kept calling for my wifi to wake up and I wasn't sure why. Also, I went through autostarts just like the link in the OP said and romtoolbox couldn't keep the updateservices bit from being disabled they would keep enabling themselves...
[BetterBatteryStats] chamonix:
There is no option to reset the prefs so you will have to delete app data from the android settings
[BetterBatteryStats] chamonix:
"Show battery levels" in the display prefs
[BetterBatteryStats] chamonix:
I indeed see a lot of alarms but that dumpfile is the wrong way to start. Please post an idle dump of both situation (work and home) and we can have a look.
[BetterBatteryStats] chamonix:
Yes. As kernel and android counters are reset at reboot there is unfortunately no way to manage timespans across reboots
[BetterBatteryStats] Tuggbuss:
Thank You. Didn't know that.
[BetterBatteryStats] zandgreen:
AlarmManager x2

Hello, I've noticed that there are two occasions of AlarmManager wakelocks since recently:

AlarmManager (Android System): 20 m 23 s (1223 s) Count:51 19.5%

AlarmManager (Phone): 4 m 14 s (254 s) Count:15 4.1%

The second one corresponds to the Alarms produced by the apps and can be reduced with the autostarts. It's not clear to what exactly stands the first AlarmManager (it causes rather big amount of wakelocks).

See the log attached.
[BetterBatteryStats] Karpfenhai:
Hey there, something is wrong with your dump, please upgrade to the most recent version, ensure you get a fresh reference (unplug charger) and repost.

Alarmmanager is just a collector / placeholder for all alerts occurring, it should sum up all others.

Tapatalked from my Galaxy SII
[BetterBatteryStats] zandgreen:
I do use the latest one, will try installing it anew and measuring again. 20 min of wakeup time in 1h40 is rather bad.

Edit: sorry, I haven't noticed there's v. 1.14
[BetterBatteryStats] Peanuts.:
Recently I've noticed very high wakelock from 3 sources.

Android OS - Alarm manager

Facebook - Alarm manager

Phone - RILJ

These were showing on wakelock detector.

Just wondering if you experts have any info and/or fixes for these issues.

Wifi is constantly being woken up during deepsleep
[BetterBatteryStats] oae08:
Where did you get v1.14

I have the paid playstore version and its 1.13.4 latest. I feel it is not working at sometimes and gives wrong "calulating" percentages.

Does 1.14 fix that?
[BetterBatteryStats] guido_glx:
It's in the second post of this thread, you can download it from there.

Enviado desde mi GT-I9100 usando Tapatalk 4 Beta
[BetterBatteryStats] iamatechnoob:
Having 40mins of awake time on my touchpad. its on airplane mode and wifi is off. I do realise battery drain is worse when wifi is off and sleep compared to when its connected to wifi and sleep, no idea why.

Please see log attached. Thank you.
[BetterBatteryStats] zandgreen:
AlarmManager x3

I've installed the latest version and disabled all mods I used but I'm still having multiple AlarmManager wakelocks:

AlarmManager (Android System): 41 m 40 s (2500 s) Count:52 34.3%

AlarmManager (com.google.android.apps.maps.Maps): 57 s (57 s) Count:8 0.8%

AlarmManager (Phone): 14 s (14 s) Count:14 0.2%

I wouldn't have bothered but I'm finally getting a rather heavy drain.

Log is attached.
[BetterBatteryStats] Karpfenhai:
Please do not rely on partial wakelocks for now, they may be miscalculated, divide them by ten to get an overview.

[MENTION=1330150]chamonix[/MENTION], as you can see, the HTC specific counting problem is still present :cool:

Tapatalked from my Galaxy SII

---------- Post added at 09:49 AM ---------- Previous post was at 09:46 AM ----------

Hmm it seems your device thinks the charger was still plugged in..

To get a better picture please ensure a clean reference (since unplugged) and enable root features.

Tapatalked from my Galaxy SII
[BetterBatteryStats] negrobembon:
i took a dump, this one is a real killer

http://db.tt/pgjWapW9

what could be causing this drain? anyone knows?

i think its somewhat related to data but i dont know, google didnt help with those wakelocks but i have 4 hours of awake time with just over 1 hour of screen time
[BetterBatteryStats] Karpfenhai:
Fail, read the op again with care...

But..disable fast_dormancy, post an idle idle idle dump!

Means screen on less than 5 minutes.

Once more..

Tapatalked from my Galaxy SII
[BetterBatteryStats] rajarshi10:
My report. Using Nexus 4 & having weird battery drains. Anyone help me please?
[BetterBatteryStats] Karpfenhai:
Nothing unusual, tick root features, check post 3 for maps, disable Google search box, post another dump.

Note msm_hsic points to active data traffic.

Tapatalked from my Galaxy SII
[BetterBatteryStats] chamonix:
If only my htc one could be affected I'd have something to work with
[BetterBatteryStats] mj_godam:
9% per hour

hi averyone

can you please take a look at my dump file?

my phone is like a monster, draning my battery too much

thanks in advance:good:
[BetterBatteryStats] humy456:
need help bout my bbs dumpfile
[BetterBatteryStats] Karpfenhai:
Maybe it's related to cyanogen derivative roms only?

Tapatalked from my Galaxy SII

---------- Post added at 09:44 AM ---------- Previous post was at 09:44 AM ----------

Do you have viber installed?

Tapatalked from my Galaxy SII
[BetterBatteryStats] It_ler:
Ok, here is your main wakelock:

AudioOut_2 (1013): 4 h 40 m 53 s (16853 s) Count:0 96.9%

AudioOut_2 is sound/voice related.

So something is using your phone's audio module.

Have you got Viber or any other voip app?

(I see you have LINE installed.)

Try to disable/uninstall it and check again, if the AudioOut_2 wakelock is significantly lower or gone.
[BetterBatteryStats] Karpfenhai:
There is nothing unusual in your dump, but you failed reading the op, disable some unnecessary sync and repost a valid (idle) dump.

Tapatalked from my Galaxy SII
[BetterBatteryStats] kg3:
How do I prepare an idle dump log? Can't find it in the app. Thanks.
[BetterBatteryStats] GermainZ:
Menu > Share > Text Dump File > Save/Share To
[BetterBatteryStats] Casanoaa:
1. Read few first pages in this thread.

2. Enable alarms and network in bbs app if you are rooted.

3. Unplug and leave phone 4 hours without touch and dump a file.

4. Use a pc for uploading or a cloud service to dump your file here in this thread.
[BetterBatteryStats] mj_godam:
no i never installed viber or voip app before

but i do have installed app called vitamio, is it related?

for the wakelock it never appeared before but now it appear out of sudden

and for the powermanagementservice wakelock, what can i do to fix it?

thanks in advance:angel:
[BetterBatteryStats] It_ler:
1. What about LINE app?

2. PowerManagementService wakelock usually stand for another wakelock.

PowerManagerService (): 4 h 41 m 18 s (16878 s) Cnt:(c/wc/ec)0/0/0 97.0%

AudioOutLock (): 4 h 41 m 18 s (16878 s) Cnt:(c/wc/ec)0/0/0 97.0%​

As it is exactly the same as AudioOutLock wakelock, I assume that it is showing the same thing ... just a different/generic name.

Can't be separated wakelocks anyway ... 97% + 97% = 194% wakelocks ?! (100% is maximum and would mean 100% awake time)
[BetterBatteryStats] iamatechnoob:
That's weird, i restarted my touchpad and tried to get a clean reference as you suggested, but the wakelock disappeared. Prior to the reboot i was able to reproduce the wakelock, but now i cant. Oh well thanks anyway!
[BetterBatteryStats] MichunB:
OK

but after reboot or shutdown / start I have no reference, I have to set custom reference to start gathering statistics

Is there possibility to create 'system start' reference?
[BetterBatteryStats] Karpfenhai:
What about since boot? doesnt work for you?

or a short plug / unplug action?
[BetterBatteryStats] MichunB:
as I wrote in my post after restart I have NO references, so 'since boot' do not work for me because it is absent

I have samsung galaxy s 3 on stock 4.1.2 rom
[BetterBatteryStats] chamonix:
Since boot will be created unless something prevent BBS from detecting the boot event. Have you:

a) moved BBS to the SD card

b) greenified BBS

c) changed the permissions to dected "on boot" by any other means?

If non of the above please provide a logcat showing the boot sequence
[BetterBatteryStats] Xoib:
Can alarm & network (root require) information work with `Boot` reference instead of `Unplugged` ?

Because I saw "No reference unplugged was saved yet, plug/unplug you phone)" in some dumps.

PS : By the way, can someone explain me why this two (alarm & network) require root uid ? Isn't it like the other information from a dumpsys or something ?
[BetterBatteryStats] chamonix:
Alarms is from dumpsys, dumpsys requires root.

The network stats are read from the kernel and again that sysfs access requires root.

Edit: no ref since... suggests that that action was not performed since you activated the root prefs
[BetterBatteryStats] chamonix:
I guess it is time to release 1.14 as there has been no negative feedback.

Starting working on a new more user friendly 'package' view showing apps and their symptoms instead of apps categorized by symptoms.

Power users: be not afraid, the current views will stay as well.
[BetterBatteryStats] Xoib:
So why don't you use android.permission.DUMP permission ? (Just asking, I hope it's not a revelation. I think you probably have a good explication)

About the "alarm & network (root require) information work with `Boot` reference instead of `Unplugged`" thing, I didn't understand your answer, because it's something dumpsys can give you, what is the matter if the actual ref is Boot and not Unplugged ? The information are still here.

Maybe I miss understand something.

Thanks for the answer ;)
[BetterBatteryStats] chamonix:
As I said, root is required anyway to access network info. I didn't think of it as an alternative for not rooted users and will make a check to see if that perm is accepted for a not system key signed app.

About the missing ref: once root features have been enabled all refs saved after that will contain the info. But if the ref was created prior to enabling the root features the data will not show. The only other reason I can think of is that your device does not deliver that info (a look into the raw stats will confirm that)
[BetterBatteryStats] rskyline:
Thanks for this awesome app

Enviado desde mi Nexus 4 usando Tapatalk 4 Beta
[BetterBatteryStats] MichunB:
I did not moved / greenified / changed permissions, I am on stock rom and the only modification is cf-root

and here is logcat - I hope I did it well :)

https://www.dropbox.com/s/nw3qwejq97q88me/logcat-2013.07.10-16.22.zip
[BetterBatteryStats] Xoib:
Ok I'm glade that I may have helped you to improve your app ;)

About the missing ref, in fact, I just checked again and I have :

======================

Alarms (requires root)

======================

Boot event was not registered yet, it will at next reboot (): Wakeups: 0

======================

Network (requires root)

======================

-1 () (Boot event was not registered yet, it will at next reboot): 1.0 Bytes 100.0%

So you are right, I didn't knew that I had to reboot after I allowed root features in the advanced tab :( That broke my 3 days benchmark (only for alarm and network part stats). Anyway I will do it again for the next few days.

If you take a look at my actual log (14% at this time), it pretty good. I just have to track down my wifi (dhcp crazy) problem and I think I will be done for this part (special sync settings).

(it's from my nexus 4 testing device)
[BetterBatteryStats] GermainZ:
You could also reduce GSF/Maps wakelocks (more info in the OP), disable location services, and sync FB/Weather/Gmail manually if you want.
[BetterBatteryStats] Karpfenhai:
Now we're getting closer, setting a static ip might avoid the dhcp overhead, don't forget to tell the router which one..

If you don't need nfc, disable it.

Good luck.

Tapatalked from my Galaxy SII
[BetterBatteryStats] aber82:
hi and thanks for this informative programm.

i hope i can expand my sleep standby a little bit .

i found some wakelocks and wondering about gtalk, cause i freezed it .

also i can see no kernel wakelocks . i use arhd 6.1.5 on my dhd and aktually i am testing the lordmod kernel 4.0 . no kernel wakelocks on this and also on the rcmix 10.(just for info)

perhaps somebody can give me a startpoint by looking on my log.

should i provide screenshots also?

thank you
[BetterBatteryStats] chamonix:
Can you please provide a logcat?
[BetterBatteryStats] chamonix:
I can't see anything really wrong as the potential is pretty low (10 min / 4 hours)

Nevertheless I suggest you turn off your gps when not using it. You may have noticed the log showing you weather widget accessing location and it would use GPS if turned on.
[BetterBatteryStats] tristecire:
herm... i tried, and will try again

C:\Users\user\Downloads\android-sdk_r06-windows\android-sdk-windows\tools>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

~ # logcat

logcat

Unable to open log device '/dev/log/main': No such file or directory

~ #

I will try to activate it.

i've seen a CWM zip to do it in my fvourite thread, i think so.

See you later and thanks for this little great adventure in the deep inside of Linux, Android and sammy processes.
[BetterBatteryStats] zicovsky:
I rebooted and now have stuff in kernel wakelock also. Funny cause I had rebooted before but it was still blank..
[BetterBatteryStats] aber82:
thank you very much , i will give it a try.

when i look on the battery monitor widget history , i see many peaks with 20 - 200 mA among the deepsleep 3-8mA.

perhaps often caused by weak signal.

will give further feedback after testing the new kernel some more.

thanks
[BetterBatteryStats] tristecire:
Got it now, big zip, or unzipped text file if it's better, but don't know how to send it to you and not to everyone... sorry, i'm a kind of old noob.

So if you want to teach a bit.

Kindest regards.
[BetterBatteryStats] yhrn:
Ok, installed 1.3.1, started logcat from terminal emulator, opened BBS, went to Kernel wakelocks (empty as always for me) and finally stopped logcat. Hope that was the intended procedure. Otherwise tell me exactly what to do and I'll try to help.

Cheers
[BetterBatteryStats] beepsilver:
Rebooted and now reflecting wakelocks--one wakelock stands out after 7 hours. I haven't researched it yet: "kgsl" 14m 57s (897 s) Count: 474 1.2%
[BetterBatteryStats] s2d4:
You are aware of the issue with USB debugging so I am pretty sure it isn't intentionally crippled. This comment is a major cop out for the following reason:

if its crippling, why does /proc/wakelocks tells me exactly what is there? Why don't you just output that, parse it and load into a database. It's inbuilt into android/linux so why not use this option?

Everyday people won't know how to find wakelocks without betterbatterystats which is pretty much the main market so maybe those sentiments will be better felt with those individuals.

btw, it seems the reboot does solve the problem just like the usb debugging problem that people have had before, even on Villian Rom.
[BetterBatteryStats] nobnut:
Your comment is a cop out. Your reasoning is flawed.

Why blame BBS for kernel Devs' ignorance? You keep stating a solution. Fine... but why not have kernel Devs sort their own problems? They are the ones who defy convention, stock kernels report correctly. Theirs don't.

If you have a better solution for uniformity across Android... go sing it from the hilltops. And tell Google while you are at it.

Open f*****g source? You are arguing against just that. But I bet you can't see what you are doing...

Don't blame app Devs because individual kernel 'Devs' are non-compliant.

Sent from me to you in the vague hope you understand the English language and have some semblance of intelligence to assimilate the context of this post... sent from a handheld device running an 'open source' *cough cough* OS.