yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Celestial Fury:
Every time I look at a BBS text dumpfile and see:

========

Services

========

Active since: The time when the service was first made active, either by someone starting or binding to it.

Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)

I get pretty annoyed. I mentioned it last year and even wrote a PM to the Dev but either he thinks he's right or doesn't understand or doesn't care. As there was no reply to either post or PM I'd say all 3.

Here's an example:

Active since: 5 m 53 s

Last activity: 31 m 23 s

First of all, minutes (m) and seconds (s) is not time but duration. "Active since" qualifies that duration but neglects to indicate

any

starting point - since when? 5 m 53 s ago (until the text dumpfile was taken?) OR since the start of the monitoring until 5 m 53 s later?

"Last activity" also intends to show time but words it as duration and also has the whole "since when" issue.

"Active since" is supposed to occur first and "Last activity" is supposed to occur later but in the same dump we have:

Active since: 5 h 14 m 37 s

Last activity: 2 h 59 m 45 s

It looks like we can have "Active since" that can have a longer or shorter time/duration/? than "Last activity" which renders the meaning of "service was first made active" and "last activity in the service" nonsensical.

As such, we can't tell between "what is intended" and "what is worded" and "what is actually measured". This makes the whole Services monitoring practically worthless for measuring drain. It's time the dev get this right.
[BetterBatteryStats] IronTechmonkey:
Perhaps there was some viable feedback in there somewhere but who would want to wade through that vitriol towards a very popular developer to get to it.
[BetterBatteryStats] thinkertank:
Running CM 12.1 (without GApps) on Redmi 2, I was able to get rid of excessive NextAlarmTracker, CalendarPRovider2, and AlarmCLock wakelocks by disabling Auto TIme and Date update from network.

I guess the phone was updateing too often the time, and that forced the time senisitive apps - those that alarm you, Calendar, etc. - to recalculate reminders.

Interestingly, the PWL-s now just seconds, but still getting some awake - screen off time.
[BetterBatteryStats] Galukon:
Hello everyone, ive got a problem when im installing. When i install bbs through the play store i get a failed to install as system app. Then i install it through recovery. But then the companion app cant be uninstalled. Any1 has some tips? I have a oneplus x and android 5.1
[BetterBatteryStats] chamonix:
yes. The complete Alarms are currently only available when parsing dumpsys alarm. On some devices dumpsys is not allows so bbs falls back to API mode", that is currently a less comprehensive implementation. I am working on removing the differences between those modes but it is a tricky implementation
[BetterBatteryStats] chamonix:
it can, by using the uninstall recovery zip
[BetterBatteryStats] mhrussell1:
I think I found the WiFi Running culprit in my Location -> Scanning menu which had Wi-Fi scanning selected to improve location accuracy.

Mark

Nexux 5X, Chroma ROM, Franco Kernel, BBS 2.1.1.0
[BetterBatteryStats] shaggyskunk:
There's a excellent app on the Store - Battery Widget Reborn - You can shut down everything at night - You might want to check in out.

Sent From My SM-N910W8 Running CMRemix 6.01
[BetterBatteryStats] IronTechmonkey:
...and Google's high accuracy location settings, which are often forced by "bugs" in Gmaps, may cause a reversion to that undesirable setting.
[BetterBatteryStats] Nightshadow931:
I have to quote myself. :)

In case anybody knows, I would really appreciate any help.
[BetterBatteryStats] g2tl:
no kernel wakelock info

I'm on stock HTC One A9 with 6.0.1, systemless root.

Kernel wakelock shows "no stats have been collected yet"

Partial kernel wakelocks show just fine
[BetterBatteryStats] RASTAVIPER:
Unfortunately none of these 3 solutions worked.

Can it be that some phone security permissions are not allowing the application to collect all data?

Are there any other users here with Meizu phones?
[BetterBatteryStats] benniewijsNL:
Hi

I use bbs 2.2.0.0B5 on cm13

And evry time i onlock mij phone i get requers bbs wants root exses. Whit 2.1.0.0_RC6 i dint haf that. And some time's i haf that i look at the stats it shows phone is on for 4 hours wen its just 1 or 2 unplugt. Did i do sometink rong the rc6 i haf to instal as system app and whit 0B5 it dus not aks four that?
[BetterBatteryStats] Galukon:
I meant, it cant uninstall the companion app so i can't use bbs right now.
[BetterBatteryStats] chamonix:
Sorry but I don't get what you mean. Why would you like to uninstall the system app to use BBS?
[BetterBatteryStats] Galukon:
1. I install from Google Play Store.

2. Install as system app failed try recovery zip. I download the .Zip

3. Install zip through recovery.

4. Install succeeded and reboot into system

5. Open app and tells me: This is companion app blabla, press uninstall. Then i see a message box with : 'Failed'.

I want to use bbs not uninstall i don't understand :)
[BetterBatteryStats] Nimueh:
That's been discussed sooo many times here ... just install BBS again after the reboot, then it'll work.
[BetterBatteryStats] Galukon:
Don't you think i did that, i re installed , rebooted , did a 2 time install..

Btw, i cant read 3000 pages man be gentle
[BetterBatteryStats] Nimueh:
You didn't say that you installed it again, you said you tried to UNInstall.

And FYI: I'm no MAN and this thread (like all the others) has a search function - searching for "companion app" for instance brings up loads of results, most are helpful ones :p
[BetterBatteryStats] Galukon:
I dont know why, i didn't do anything different like the 20 times i tried to install but i works. Thanks i guess :silly:
[BetterBatteryStats] miltonwkw:
Lost 7% overnight. Was losing only like 2% previous days. Nothing has changed except installing bbs & klwp. :confused:
[BetterBatteryStats] Durrz:
Can anyone help me figure this out? For some reason I only see 3 options for my 'from tab'
[BetterBatteryStats] derdjango:
Hey there,

I lost 11% in 4 hours overnight (Yeah, short night..), however, I'd be happy if somebody can help me reading and interpreting my stats. Do I really have to install xposed+amplify or will something like greenify will do? From what I can read, my doze works pretty good.
[BetterBatteryStats] dimm0k:
not sure what else I can do to lower my drain overnight... any suggestions?
[BetterBatteryStats] tjlmbklr:
So I have had BetterBatteryStats installed for a couple of days now. ...

How can you guys help me determine what my battery drain is caused by? I used to lose 3% give or take at night now I lose like 10%+ and with regular use I could go a 8-9 hour shift and still have 50-60% when I went home after work. It seems the more I do to help it, the worse it is. I use Greenfy Donation package with Agressive Doze, I have a MacroDroid set to hibernation all my Greenify apps when I turn the screen off. I have all wake-up paths (That I know of) for facebook blocked and I use PowerNap and Amplify. Have I done too much. Show I just use Greenify?

Am I in the right place?

I am sure you will need logs. I am not sure how to get these.

Thanks in advance.
[BetterBatteryStats] RASTAVIPER:
For the start, why don't you post a few screenshots of your kernel and partial wakelocks screens?
[BetterBatteryStats] TNSMANI:
This is the best guide there is for Amplify, Greenify and PowerNap combo.

http://xdaforums.com/android/general/guide-extreme-battery-life-t3095884

Check there.
[BetterBatteryStats] tjlmbklr:
This is where my battery snob personality originated from. I only made it half way through the settings and realized there were so many settings for Amplify that i t was going to take longer than I had time to dedicate to it. I gave up and have since started using all settings as-is out of the box other than Greenify I have tweaked with aggressive doze and all my chosen hibernated apps and PowerNap I have chose which apps to ignore.

If it matters I am on Pure Nexus ROM latest build coming from Cataclysm thinking Cataclysm was causing my issues.
[BetterBatteryStats] TNSMANI:
You have Tasker eating some battery, MyTransit NYC, Location alarms, alarms related to Alarms, sync etc eating some more, Facebook and Google Play Services downloading about 1 MB each etc etc. In other words, too much activity for a sleeping phone.

See the thread I linked above for guidance to limit the damage.
[BetterBatteryStats] Portgas D. Ace:
Most people tend to misunderstood the purpose of the guide (me too, in the beginning): don't limit everything according to the guide. Take two or three idle runs first, save the dump files and make an analysis of those dump files afterwards. Then use the guide to limit only all the stuff that is draining your battery according to the BBS logs. In some cases it is even making things worse by blindly limiting everything from this guide.

In addition, enabling the GCM push notification feature of Greenify might also increase your drain. Greenify only those apps that you don't want to run permanently in the background (e.g. games or seldom used apps). All other things can be handled by Amplify. It takes some time to set up everything to your personal needs, true. But in the end, you have full control about what and when is running.
[BetterBatteryStats] tjlmbklr:
Unfortunately I have GCM unchecked. This causes crashes on my device when using things like Cerberus and other seemingly GPS related apps.

Its a know issue, not sure if its an Xposed thing or what.
[BetterBatteryStats] TNSMANI:
You need Amplify donation package. Greenify alone will not be sufficient.
[BetterBatteryStats] derdjango:
Edit: Sorry, we posted at the same time. I really don't want to install xposed, would just like to know what drains my battery and maybe I can prevent them without amplify.

I ran BBS again, this time for 12 hours. Can anybody please help me to identify my battery drainers?
[BetterBatteryStats] TNSMANI:
This is normal. You will get one more ie "Custom" when you click the three dot menu and choose 'create custom reference".
[BetterBatteryStats] crypticc:
Crazy stats when charging

Hi

Had anyone ever seen the attached before?

Stock nexus 7 2012 razor with systemless root. No other modifications.

The jump at the end was me rebooting the device. The shading beforehand was supposed to be charging.

This is the second time that it's done this.

Wireless charging if that is significant

Cheers

Chris
[BetterBatteryStats] magukraine:
kernel wakelock lli_cp_wlock

Hi!

One day cellphone began to lose battery. Using betterBatteryStats I’ve discovered that it’s caused by kernel wakelock lli_cp_wlock. It seems with none pattern and i can stop it handiest rebooting the cellphone. I’ve tried to reinstall the system and flash newest firmware, but it surely hasn’t helped. looking the internet I’ve found that lli is low latency interface controller which is attached one way or the other to the modem. Any thought take care of it? samsung g850f
[BetterBatteryStats] TNSMANI:
Alright, here goes:

ConnectivityService (Android System): 3 m 18 s Count:111 0.4%

*net_scheduler* (Google Play services): 10 s Count:1129 0.0%

NlpCollectorWakeLock (com.google.android.googlequicksearchbox.Google App): 9 s Count:25 0.0%

NlpCollectorWakeLock (Google Play services): 9 s Count:185 0.0%

UlrDispSvcSlowWL (Google Play services): 9 s Count:130 0.0%

NlpWakeLock (com.google.android.googlequicksearchbox.Google App): 3 s Count:157 0.0%

NlpWakeLock (Google Play services): 2 s Count:771 0.0%

Alarms: 18, Intent: ALARM_WAKEUP_LOCATOR

Alarms: 14, Intent: ALARM_WAKEUP72853

Alarms: 41, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM

Alarms: 16, Intent: com.google.android.intent.action.GCM_RECONNECT

Alarms: 50, Intent: android.appwidget.action.APPWIDGET_UPDATE

Just a sample. As far as I know, only Amplify (with donation pack) is capable of controlling them.
[BetterBatteryStats] derdjango:
Thanks for your input. I was under the impression that the total time for these wakelocks would be more important than the counts and was thinking that they are quite good considering a 12h+ time frame. I guess, I'll have to live with a sub-optimal battery then for now. Thanks again!
[BetterBatteryStats] TNSMANI:
Times are definitely more important than the nos. Once you take care of the alarms/wakelocks with high times, you can then tackle those with high nos.
[BetterBatteryStats] tjlmbklr:
Here are my logs. Am I doing this right?

I posted a few days back asking for help figuring out why my battery life seems to have gone down hill. I was told to post screen shots when I wasn't sure where to get my logs. Well, here are what I hope are the right logs.

I have since uninstall Facebook and Messenger and I still lost 10% over the course of the night while sleeping. I even have sync turned off.

This just doesn't seem right.

Thanks in advance.
[BetterBatteryStats] retr13:
help with alarm manager wakelock

hello

i need help with figuring this out

so what bothers me - is constant partial wakelock, which caused by alarm manager in android system, but i cant see what cause this alarm manager to manage. Wakelock goes from 1h every 24h and up to 2-3h every 24h, and this is when device is used only for standby mode.

What i saw is sometimes there is dialer RILJ alarm in alarm category that goes up to 600-1000 times in 24h, but never keeps device in wakelocked state(and also probably forcing looped earlyer lock to go down), in this case the partial wakelock goes down to acceptable 10-15min every 24hours.

i kinda need help either know what to shut down in system, or force this rapid alarms with no wakelock time
[BetterBatteryStats] Perseus:
Seems like you had location Service on. If you are not using location based app, may I suggest turning it off? It can be a drain especially indoors.

Next, you have a Chatty wireless network. It created a constant wakeup loop for the device. Can you configure it so that the device gets a Static IP ? Otherwise whatever device you have on your WAN that's constantly polling for network map needs to take a rest.

You watching Youtube for half hour has skewed the Log results. Can you please post another log, completely idle device in standby, preferably overnight ?

From the log it seems like Nextapp Systempanel is your culprit for that Alarm PWL. For RILJ to die down, a short toggle of Airplane mode once in a while helps.
[BetterBatteryStats] retr13:
rilj is actually helping

and system panel alarms, or any other alarm population app does not cause bothering wakelock time, or so it seems to me

i saw content of bbs dump file, and i did not saw any helpful data there to my case(or are there?)

so i attached alarm dump file, but i dont know how to read it, know which is what there
[BetterBatteryStats] tjlmbklr:
I have since turned my GPS to device only. I have struggeled with a way to keep my GPS active for it's benefits but still save battery. I tried running a Macrodroid profile to enable/disable GPS when opening/closing the apps that need it but it's not without problems. Plus I like having smart lock for places like at home and for this GPS needs to be enabled.

I guess we can't win it all if we want functionality and battery. I guess we have to settle for a happy medium.
[BetterBatteryStats] Perseus:
Where alarms are concerned, you look for number of alarms in a given timeframe. The higher the number the more phone is up and more the drain. Here in this case,

nextapp.systempanel.r1*api* (): Wakeups: 354 (10.7 / h)

tells me Systempanel woke the phone 354 times or 107 times per hour. From the alartmdump,

nextapp.systempanel.r1
116100ms running, 417 wakeups
[COLOR="DarkRed"]417 alarms: act=nextapp.systempanel.action.MONITOR_UPDATE flg=0x4[/COLOR]
com.fihtdc.datameter
40209ms running, 0 wakeups
[COLOR="DarkRed"] 415 alarms: act=com.fihtdc.datameter.DATA_COLLECTION flg=0x4[/COLOR]

followed by

com.vito.lux
14406ms running, 0 wakeups
3 alarms: flg=0x4 cmp=com.vito.lux/.NightModeService
[COLOR="DarkRed"] 256 alarms[/COLOR]: flg=0x4 cmp=com.vito.lux/.AutobrightService
[COLOR="DarkRed"] 408 alarms: [/COLOR]flg=0x4 cmp=com.vito.lux/.CompatibilityCheck

tells me System Panel was the top cause of wakeups closely followed by Data meter and a third one from Lux auto Brightness. This is how you need to read the log.
[BetterBatteryStats] DKDroid3:
OK, finally have a dump following post #6, I had a notification from BBS that the phone was awake 99% when screen off? This is a verizon S4 running a stock rooted touchwiz 5.0.1 OF1 build and I have a Gear 2 smart watch.

Thanks!
[BetterBatteryStats] Perseus:
do you use Exchange or the stock email client ? If yes, can you disable its polling for new email ? Or Greenify it since you do have THAT. Can you live with ESPN Sports Center being refreshed manually ?

Also just a suggestion, since you are rooted, you can consider removing Sammy Bloat if you think its ok.
[BetterBatteryStats] retr13:
it's not alarms count that bothers me, its wakelock up time

and alarm count does not striktly correlate to wakelock up time, thats why it is confusing

for example everything is great when there are 1000+ every day alarms from rilj with some small wake ms ammount

and usually its not great when there are no rilj alarms, no system panel alarms, no data meter alarms and generally almost none alarms, but wakelock up time is there and it is even bigger, and i dont see through alarms bookmark what cause is.
[BetterBatteryStats] Perseus:
you have to understand that the reported up time is cumulative due to the way Android Reports it. [MENTION=1330150]chamonix[/MENTION] has discussed this earlier at length when Lollipop was introduced it. I haven't seen any of his posts to say that Marshmellow is reverting that process.

This is partly why you need to look at alarms. Thoughts [MENTION=1330150]chamonix[/MENTION] ?
[BetterBatteryStats] DKDroid3:
I have greenify set on auto, what is the best way to disable email from polling for new mail? I have tried to limit ESPN with AppOpps is there a better way?

thanks so much!
[BetterBatteryStats] rignaneseleo:
Thank you man! I'm buying the app to support you!

Can I flash the zip only with cwm?
[BetterBatteryStats] lazostat:
Is there any guide about this app? I dont understand what should i check in order to see what causing the battery drain.. Can someone help me?
[BetterBatteryStats] IronTechmonkey:
Many people have already helped you. You just need to read the information. The first several posts in this thread and the sources that they link to (including a very nice "How -to") provide a great deal of information.
[BetterBatteryStats] Perseus:
You will have to check into email client's settings. For ESPN, check if the app settings have any control otherwise appops is the way to go,
[BetterBatteryStats] deepu458:
HI folks & [MENTION=1330150]chamonix[/MENTION], i am recently seeing a huge awake at screen off almost 98 -97% awake the whole time. And when i try to look at the BBS logs i wont see a nasty alarm or Wakelocks registered. I tried everything i can to figure it out. Please help me as its really annoying me to fix the rogue app or service. although the attached log is for 24 min but the awake rate is almost the same if i leave it like tht for a period of time.
[BetterBatteryStats] Perseus:
Is your Battery Okey ?

Level lost [%]: Bat.: -1%(100% to 99%) [2.5%/h]
Voltage lost [mV]: (4306-4248) [145.0%/h]

tells me there might be some issue with battery. Perhaps its going bad or had a short ?
[BetterBatteryStats] deepu458:
Yes i see this issue only at my office location but when i move to my house i don't see this issue at all.
[BetterBatteryStats] cobr:
Hi, I have a problem since the begining of the month, my battery is drain hugely by android system, can someone help me?

Thanks.
[BetterBatteryStats] TNSMANI:
There is something wrong with the dump. According to it, the stats are from 'unplugged to current' but your battery percentage shows an increase from 62% to 91%. Obviously the phone was charged but that doesn't seem to reflect in the stats.

Better take an idle dump of about 6 hrs. and post here so that someone may be able to help you.
[BetterBatteryStats] cobr:
Will do that tonight. PowermanagerService.wakelocks and PowermanagerService.display are the 2 main concerns for me.
[BetterBatteryStats] TNSMANI:
They relate to your screen on time. You can't do anything about them AFAIK, unless you stop using the phone.
[BetterBatteryStats] Perseus:
could be the charger in office ? Do an Idle dump overnight at home and post.

Kernel wakelocks in general are symptom of a bigger problem. They simply qunatify the problem, not pinpoint the reason.
[BetterBatteryStats] deepu458:
Thanks for ur input, but i have posted the same log on lightning Kernel thread as well as i saw huge wakelocks coming from kernel wakelocks section as below.

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

Kernel Wakelocks !!! wakeup_sources !!!

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

event2-1600 (): 7 m 16 s Cnt:(c/wc/ec)3575/15/0 29.5%

event3-1600 (): 7 m 15 s Cnt:(c/wc/ec)3575/15/0 29.5%

event0-1600 (): 7 m 14 s Cnt:(c/wc/ec)3620/0/0 29.5%

qcom_rx_wakelock (): 3 m 37 s Cnt:(c/wc/ec)4553/25740/4553 14.7%

PowerManagerService.WakeLocks (): 49 s Cnt:(c/wc/ec)53/11/0 3.4%

someone was mentioning that it can be sometimes with the router as well. And after that i started investigating from that angle as well as because when i get the log at my home with same setup the drain is normal. So trying to identify what exactly these events and qcom_rx_Wakelocks are and how to control them.

If any input provided on this aspect would be highly appreciable.
[BetterBatteryStats] Perseus:
qcom_rx_wakelock is related to Router. The router might be configured to expire the ip address issued by DHCP. Either that or some other reason to ping the device constantly. You can turn off WiFi at work to see if that closed it. Based on your log, it doesn't seem like qcom_rx_wakelock is a big issue.
[BetterBatteryStats] deepu458:
I really thank you so much for ur help here buddy, but i have attached a new log now which shows again some high awake and could you see here in both kernel wakelocks and wakelocks section and let me know ur thoughts. For now i have disabled Wifi and left the device idle and look at it after 30 min and let u know.

Battery Info

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

Level lost [%]: Bat.: -1%(100% to 99%) [1.7%/h]

Voltage lost [mV]: (4330-4226) [176.3%/h]

===========

Other Usage

===========

Deep Sleep (): 11 m 49 s 33.3%

Awake (Screen Off) (): 23 m 25 s 66.0%

Screen On (): 12 s 0.6%

Wifi On (): 35 m 27 s 100.0%

Wifi Running (): 35 m 27 s 100.0%

Doze Interactive Time (): 12 s 0.6%

Sync (): 31 s 1.5%

Sensors (): 5 m 9 s 14.6%

No Data Connection (): 35 m 27 s 100.0%

No or Unknown Signal (): 35 m 27 s 100.0%

Screen dark (): 12 s 0.6%

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

Wakelocks (requires root / system app on Android 4.4+)

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

GOOGLE_C2DM (0): 37 s Count:18 1.8%

AudioMix (1013): 27 s Count:9 1.3%

*sync*/gmail-ls/com.google/f2f7c00053a6a5b0085ea0462bd9f617@gmail.com (com.google.android.gm.Gmail): 21 s Count:11 1.0%

Icing (Google Services): 10 s Count:39 0.5%

GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s Count:17 0.3%

BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 3 s Count:2 0.2%

GCM_CONN (Google Services): 1 s Count:69 0.1%

CloudNodeSyncWakeLock (Google Services): 1 s Count:26 0.1%

GcmService (com.pushbullet.android.Pushbullet): 1 s Count:52 0.1%

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

Kernel Wakelocks !!! wakeup_sources !!!

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

qcom_rx_wakelock (): 4 m 6 s Cnt:(c/wc/ec)5223/4120/5223 11.6%

PowerManagerService.WakeLocks (): 2 m Cnt:(c/wc/ec)45/10/0 5.6%

event0-1775 (): 1 m 45 s Cnt:(c/wc/ec)4737/0/0 5.0%

event2-1775 (): 1 m 43 s Cnt:(c/wc/ec)4715/10/0 4.9%

event3-1775 (): 1 m 41 s Cnt:(c/wc/ec)4717/10/0 4.8%
[BetterBatteryStats] FernBch:
Still no fix for this?

Log:

https://www.dropbox.com/s/co121tu500yvscr/Log_2016-01-30_07-08-17.txt?dl=0