yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Oswald Boelcke:
BBS v2.4-265: Haven't check the catlog (yet) as I actually don't really care but I don't get any network statistic on my Samsung Galaxy S5 LTE+ (kccat6), SM-G901F either. On Samsung Galaxy S3 LTE, GT-i9305, all network statistics are available.

Both devices running RR-N-v5.8.5, Magisk v17.2

Somehow, I'm convinced - but unable to prove - that the issue is connected to the CPU of the Samsung S5.

Remarks:

1. Please be aware that signatures aren't shown to users of XDA Labs i.e. they won't know the affected device.

2. I recognised the last line in your signature. Maybe you're interested to join or to offer your skills here?
[BetterBatteryStats] DB126:
For awareness - signature lines are available in the XDA Labs app via poster's profile (tap member meme).
[BetterBatteryStats] DiamondJohn:
New ROM, new log. Again it all looks kind of ok ecept for the fact it has a 4.1% battery loss :mad:

============
Battery Info
============
Level lost [%]: Bat.: -36%(99% to 63%) [4.1%/h]
Voltage lost [mV]: (4046-3907) [15.9%/h]

It all looks OK to me ie nothing standing out, apart from maybe the following lines

======================
Alarms
======================
android (): Wakeups: 94 (10.7 / h)
...
Alarms: 32, Intent: *job.delay*
...

com.google.android.gms (): Wakeups: 48 (5.5 / h)
...
Alarms: 36, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM
...

But I dont really know what I am talking about, Attached is my log, and I have also put it up on hastebin in case someone has a chance to look at it for me:fingers-crossed:

https://www.hastebin.com/fehijanumu.php

And for the more visually inclined ;) Actually, looking at that image, I think I will test it in airplane mode tonight.
[BetterBatteryStats] DB126:
Awake <13 min over 8½ hours. It ain't the ROM. Crappy kernel, stuck sensor or bad battery. Fiddling with ROM knobs & dials will gain little...akin to looking for love in all the wrong places.
[BetterBatteryStats] DiamondJohn:
a little OT

Not wanting to divert from my own last post, and a little off topic, but the following may be useful, in combination with BBS ;)

Its obviously no secret, but I only just found out about it :o

Anyway, if you do the following, the output is pretty dang rich and visual and interactive, but all on PC.

Do your standard running (similar to OP ie "full charge device, put device to sleep for at least 6 hours (no touchy!)" and I probably would not be running BBS ie freeze it or uninstall)

Wake your device

Connect your phone via adb to your PC

run "adb bugreport c:\temp"

[*]extract the bugreport txt file from the zipits actually quicker to use the whole zip file. its smaller than the txt file.

upload this txt zip file into https://bathist.ef.lc/

and be dumb funded!

The attached is a *very* small summary of some of the info it displays, and the graph is interactive! just hover your mouse over just about anything in the graph
[BetterBatteryStats] DiamondJohn:
:crying:

One thing with this ROM (Havoc-OS Oreo) which is pretty dang brilliant, is that it has the following, built into the ROM:good:

1. Wakelock Blocker

2. Alarm Blocker

3. Doze settings

Right now I am recharging my battery after putting some things into the first two. The last one I have not seen before, but it makes sense with the fact the phone is in doze and still drains.

One of the things I did note in my logs from the above "Battery History" is the "smd_dev". Need to understand what that is.:confused: maybe its related to BBS have to run again tonight without BBS

As for "love in all the wrong places", sometimes, its not "love" that I am looking for...;)
[BetterBatteryStats] DB126:
First two are useless; if you need to block alarms/wakelocks something else is wrong; far better to go after root cause. As for the last item you would probably do better with the Mirror of Erised. Doze is well tuned out-of-the-box, especially on Oreo. Good luck with your tinkering.
[BetterBatteryStats] DiamondJohn:
Totally agree. However, I am hoping that finding if one of them has an effect, it will point to what is the actual root cause. Heck, Im grabbing at straws here.
[BetterBatteryStats] DiamondJohn:
Reading the OP, I totally understand it is a simplified list of "states", however, I believe that it has unduly skipped the most important state (which has two sub-states), which I believe is the difference between 5% / hour and 1.5% / hour.

the very important state missing in this list, which I really do not think should be overlooked, is "Doze". For instance, my phone goes into "Sleeping" (a CPU state) almost immediately after the screen goes off. However, I have found that it is not staying the whole time in doze, and therefore I am getting my 5% drain / hour.:mad:
[BetterBatteryStats] DB126:
Unfortunately, doze is not the culprit in your situation nor is a missing state in accessing device status. Doze is a Google marketing term that describes a suite of conditions that can (and does) prolong battery life. Your logs do not suggest any level of activity that would be quelled by "doze".

Likely culprit is trying to jam Android 8 on a 5+ year old device that was engineered for Jelly Bean. At minimum you'll need an updated kernel. More likely the battery has nowhere near the design endurance regardless of when purchased (almost always old stock). Beyond that 2013 vintage hardware was not especially power efficient. That said, 5%/hr idle drain is a clear indication something is amiss. In your shoes I would be looking for a well established L/M/N ROM that plays nice with the kernel assuming HW and battery check out.

Moving on; not going to reinvent the wheel based on the behavior on one balky device.
[BetterBatteryStats] justjr:
I tried to install Mirror of Erised and my battery is going havoc now. :silly::cyclops:
[BetterBatteryStats] J.L.C.:
I'm trying to troubleshoot what seems line excessive overnight drain on my 6P: ~2%/hr

Am I correct that it's the wakelocks from timerfd and alarms from nine email that are preventing my phone from entering deep sleep?

Anything I can do?

Dumpfile attached.
[BetterBatteryStats] pjadec:
Yep, also if pocket detection is on, it also drain battery
[BetterBatteryStats] J.L.C.:
Do I block timerfd? And add nine email to greenify?
[BetterBatteryStats] pjadec:
No it's internal system. You can try, but then no notifications. Or try new clean flash
[BetterBatteryStats] justjr:
I just checked the link, never saw it before. Of course, I may as well offer it there. :)
[BetterBatteryStats] DB126:
Kernel wakelocks can't be blocked. Not that you should...better to identify and rectify root cause. Try reconfiguring your mail apps (multiple!) to poll on demand vs continuously checking for new items. Dump Facebook in favor of 'lite' alternatives. Consider whether you need WhatsApp running 7x24. Question if weather apps need to be running in the background. And that's just the low hanging fruit.
[BetterBatteryStats] Damoedge:
Hi all,

A question.... How do I set the app up to show me stats from "since full charge" all of the time on the main screen? Because it reverts to boot after a reboot and I can't see the total screen on time since full charge....?

I think years ago the app used to do this but I have not used it in a very long time...

Great app thanks to the dev for your hard work.
[BetterBatteryStats] senny22:
How frequent wakeups are considered somewhat normal for play services and Android system?
[BetterBatteryStats] DB126:
There is no "normal". The only things that matters are stability and idle battery drain. Everything else falls into the category of trying to interpret and apply meaning to raw data with no further context. Imaging if medical personal did that based on a single vital sign.
[BetterBatteryStats] shaqman89:
Not that I am complaining about my average battery drain on my HTC M9 also running Oreo, but would you also document what are the dials and knobs that you turned to achieve that? It might be a good reference for me and maybe others later for those who would want to go down that route.
[BetterBatteryStats] DB126:
Thanks for taking time to assemble a thoughtful, well organized post outlining your observations, experiences and learnings. No doubt many hours have been invested getting from point A to B. I am happy your device (single data point) is now performing at a level that meets/exceeds your expectations. I encourage you to share those learnings here and in other public forums so others can benefit from your new found knowledge. Of course, anything 'public' invites (hopefully structured) discourse which you appear well equipped to handle. ?

I am going to respectively decline a point-by-point response as few want to wade through lengthy, self-serving posts on arcane matters. Your world is as you wish it to be with numerous 'facts' (does such a thing exist anymore?) and opinions intermixed into a sauce that seems more than logical. I also have a special sauce, made up of different ingredients, that satisfies my tastes. I have high confidence in my brew, as you do yours.

I will leave you with four acronyms of which I'm sure you are quite familiar: RCA, TCO, ROI and SME. They are pillars upon which I stand and keep each other in balance. XDA is full of the latter often ignoring one or more of the former. It's what makes visiting threads such as this such a joy.

Best wishes moving forward.
[BetterBatteryStats] henningsieh:
I have something similar here:

10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603): ERROR:
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603): java.lang.NoSuchMethodException: getCpuSpeedSteps []
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at java.lang.Class.getMethod(Class.java:2068)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at java.lang.Class.getMethod(Class.java:1690)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at com.gsamlabs.bbm.lib.NotifyingService.getMethod(NotifyingService.java:1221)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at com.gsamlabs.bbm.lib.NotifyingService.getPowerSince(NotifyingService.java:1724)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at com.gsamlabs.bbm.lib.NotifyingService.getStats(NotifyingService.java:4315)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at com.gsamlabs.bbm.lib.NotifyingService.getStats(NotifyingService.java:4289)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at com.gsamlabs.bbm.lib.NotifyingService.showNotification(NotifyingService.java:2847)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at com.gsamlabs.bbm.lib.BatteryBroadcastReciever$1.run(BatteryBroadcastReciever.java:31)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603):	at java.lang.Thread.run(Thread.java:764)
10-01 13:50:14.102 E/com.gsamlabs.bbm.lib.NotifyingService( 8603): ERROR: StatBean is null...why?NORMAL

Do you have an idea, what could cause this? Thanks!
[BetterBatteryStats] nola mike:
So been doing mostly daily logs, both when sleeping (after a reboot) and no sleep (usually starts a few hours after a reboot). Haven't been able to figure out why it kicks out of deep sleep, but as [MENTION=5488402]Davey126[/MENTION] mentioned, it doesn't seem to affect battery life. I've been getting mostly 0.4-0.5%, with a couple of outliers in both directions. Which is fantastic I think. Only odd one is firefox consistently has 15m or so of usage time under "processes". That's with firefox in the background, all phone-home functions disabled in the app, background use and allow wakeups disabled in privacy guard, and greenified. Strange. If I kill the app it stops.
[BetterBatteryStats] Oswald Boelcke:
I know that the decision for a specific browser is a very personal one pending on own preferrences, desire, utilisation and many more things. Guess that's one of the reasons why so many are out there - besides browsers to be a perfect tool for fishing personal data. Have you every had a look at FOSS Browser in the F-Droid repo?
[BetterBatteryStats] DB126:
If app is greenified (and stays that way) you either have a false indication or a secondary background service in play - common with modern browsers. Check Running Services and Inactive Apps under developer options for additional clues.
[BetterBatteryStats] Damoedge:
Bump...

Anyone?
[BetterBatteryStats] nola mike:
The references all reset on a boot.

http://asksven.github.io/BetterBatteryStats-Knowledge-Base/help.html

"Boot: is saved when your phone boots, deletes all other refrences"
[BetterBatteryStats] solquest3:
Hello.

I've just checked my stats and I see Wifi Running 100% (while Wifi on 17.1%).

What's the difference between them?

I actually have wifi on only when I'm at home, so it can't be 100% (should be around 50%)...How is it measured then?

Thanks.
[BetterBatteryStats] peterlee928:
do u have wifi scanning on in location services?
[BetterBatteryStats] DiamondJohn:
An FYI or a big sink of time...

Just an FYI of something I found that may possibly be of use, haven't actually looked at it too closely (since I do not currently have a drain issue) , but I thought someone may find it of some use; if it is not just a great waste of time ☺

The command to run is

dumpsys batterystats

It appears to return a VERY detailed history of what is running/when/and the battery level at which it occurred (090=90% in quote below). The thing that caught my eye, is that along with showing when a wake_lock occurs, it would appear to actually identify/explain why the wake_lock occurred and what caused it, including which app triggered it.

The below is a short extract (its big and detailed) from my phone. As can be seen, it actually appears to show which app (the widgets com.devexpert.weather & com.anddoes.fancywidgets in my case) are triggering "stuff". NB: my phone was in deep sleep (or possibly deep idle maintenance) when all the below was happening, and I got about 0.85% drain / hour. So all was good for me, but if I wish to get better than the 0.85% i got, it is maybe showing some options ☺

...snip...
+1h15m12s781ms (3) 090 +running +wake_lock=u0a200:"*walarm*:*job.delay*" -wifi_radio +job=u0a200:"com.devexpert.weather/.controller.UpdateService"
+1h15m12s814ms (2) 090 -job=u0a200:"com.devexpert.weather/.controller.UpdateService"
+1h15m12s816ms (3) 090 -running -wake_lock wake_reason=0:"318:qpnp_rtc_alarm:200:smd_dev:203:fc4281d0.qcom,mpm:222:fc4cf000.qcom,spmi" stats=0:"wifi-data: inactive"
+1h15m18s766ms (2) 090 +running +wake_lock=u0a225:"*walarm*:*job.delay*"
+1h15m18s767ms (3) 090 -wake_lock wake_reason=0:"318:qpnp_rtc_alarm:200:smd_dev:203:fc4281d0.qcom,mpm:222:fc4cf000.qcom,spmi" +job=u0a225:"com.anddoes.fancywidgets/com.evernote.android.job.v21.PlatformJobService"
+1h15m18s773ms (3) 090 +wake_lock=u0a225:"*job*/com.anddoes.fancywidgets/com.evernote.android.job.v21.PlatformJobService" -job=u0a225:"com.anddoes.fancywidgets/com.evernote.android.job.v21.PlatformJobService"
+1h15m18s846ms (1) 090 -running -wake_lock
+1h16m13s753ms (3) 090 +running +wake_lock=1000:"*walarm*:DeviceIdleController.deep" wake_reason=0:"318:qpnp_rtc_alarm:200:smd_dev:222:fc4cf000.qcom,spmi" +job=u0a200:"com.devexpert.weather/.controller.UpdateService"
+1h16m13s791ms (2) 090 -wake_lock device_idle=light -job=u0a200:"com.devexpert.weather/.controller.UpdateService"
...snip...

If you aren't interested in typing the command in adb or a terminal and redirecting the output to a file etc etc but prefer pushing a button on an app ☺ I built the following utility to run stuff like this (and it was how I found it) which you can download at https://xdaforums.com/android/apps-games/app-temefi-comprehensive-documentation-t3806260

NB: there are NO ad's or any other money-tisation or cripple-ware involved. You can find the above function in the menu at Dynamic Lists>Dumpsys calls>Svc: batterystats
[BetterBatteryStats] skimo12:
WiFi running 100%

Hi [MENTION=5192802]solquest3[/MENTION],

I guess that you created the dump overnight when you were at home, so the WiFi toggle was on for the whole time. This is why you have the 100%. In that timespan, WiFi was used actively by the phone, and connected through your router for 17% of the time.

This is my understanding, but the other senior forum members can maybe help here.

Regards.
[BetterBatteryStats] Oswald Boelcke:
Personally I think your explanation is based on assumptions that can't be deduced from the provided information. In any case, when I'm at home WiFi is always enabled, and the device is always connected to the home network. Under these conditions, I've never seen anything else in my BBS stats than both, WiFi On and WiFi Running, at 100%. The one and only exception was once during a blackout with an obviously dead router; in this case WiFi Running time was less than WiFi On.

I'd rather get an answer to the question first that @peterlee928 stated here.
[BetterBatteryStats] solquest3:
Actually in the night Wifi is always off..Anyway, I've just found out that there's a 'wifi scan option' under Settings/Location/3 dots...

Unchecking it wifi is not running 100%, so now seems to be ok.

Thanks.
[BetterBatteryStats] strongst:
WYSIWYG... Not in Android, sadly.... ;)
[BetterBatteryStats] DB126:
Yep - Google can get pretty aggressive reenabling that pup which can (and usually does) result in increased battery drain. Nothing wild but a bit of an annoyance if you don't use or care about the functionality it enables (faster WiFi locks; better location estimates when HW GPS is disabled, etc.) Also allows Google to collect info on nearby APs so you become an unwitting contributor to Alphabet's obsessive mapping of the electronic universe.
[BetterBatteryStats] Oswald Boelcke:
Correct. And that was exactly the hint @peterlee928 gave by his question and my assumption, too. And @Davey126 is so true...
[BetterBatteryStats] Papaya59:
I have the same kind of problem : Data disabled 100% will i have data very often (and managed through leandroid) and just tested it on android 8.1 and on android 9.0 and this bug appeared only in android 9.0 (I'm on OxygenOS 9.0 stable with my Oneplus 6)

BBS version : 2.3-248

---------- Post added at 03:17 PM ---------- Previous post was at 03:17 PM ----------

I have the same kind of problem : Data disabled 100% will i have data very often (and managed through leandroid) and just tested it on android 8.1 and on android 9.0 and this bug appeared only in android 9.0 (I'm on OxygenOS 9.0 stable with my Oneplus 6)

BBS version : 2.3-248
[BetterBatteryStats] DB126:
Likely a kernel integration vs a ROM (Android 9) problem. Kernel handles most hardware interactions; ROM is largely presentation & switches. Observed behavior is not uncommon layering new Android builds on an older kernel.
[BetterBatteryStats] Fif_:
Pretty much every time you use Maps without the WiFi on, Maps will prompt you to "optimize location", which pretty much turns background scanning on for WiFi and Bluetooth.

It sucks so much that I wrote an Automate flow to turn either back off automatically if they're switched on by Google, in our best interest of course... You should be able to do the same in Tasker or any other tool that allows you to take a root action when a setting is changed.
[BetterBatteryStats] solquest3:
It's good that I uninstalled Maps then! :)

Thanks
[BetterBatteryStats] DB126:
It's easy to avoid if one pays attention to the prompts. Annoying that Google doesn't take 'no' for an answer and asks every time. Grrr...
[BetterBatteryStats] skimo12:
Fairphone sim and messages question with bbs dump

Hi there,

I have two questions please:

1. 'Messages v3.5.053' made 106 wakeups, so what's the best way to fix it. Disable Messages (which i think will go back by one version) or just delete all conversations?

2. I often have "poor signal" for 86% of the time. I think maybe i should get a new SIM card. Can i test this by just removing the SIM card overnight? I am sure that there is a better way to know if the SIM is problematic.

Please see my 5.5 hour dump attached
[BetterBatteryStats] strongst:
1: I would clear the cache of the messages app instead of blocking the wakelocks when you don't know the reason for it. Blocking wakelocks from a messaging app will likely lead to no messages until you open the app.

2: poor signal doesn't relate directly to the sim card(it has only authentication functions towards the providers HLR and storage capabilities for sms and contacts in the first case).

If the cellphone towers won't provide a good signal or obstacles are disturbing the signal or the frequency band isn't the best for your geographic environment then it's the main issue. Changing the sim card without changing the provider will not help you out of poor signal quality. You can try to make a similar dump file within an area of better signal quality to see the impact on the drain.
[BetterBatteryStats] DiamondJohn:
Maybe switching to a different network type. eg turning off LTE and switching to 2G might be worth a try. I know ROMs I have used, have this as an "on screen off" option action.
[BetterBatteryStats] DB126:
Saves very little power on modern devices and may actually be offset by activity spikes surrounding network drops/restarts. Old school at best.
[BetterBatteryStats] rignfool:
Also... At least in the US... Carriers are cannibalising their old 2g and turning it into higher bandwidth bands... So where you used to have 2g... You might not anymore
[BetterBatteryStats] skimo12:
[MENTION=5417899]DiamondJohn[/MENTION], thanks for the suggestion. I tried this before, using first only 4G, then only 2G, but came back to 3G (which is what i always had).

Funny thing is that with 4G, the battery consumption was the lowest, only 1% overnight (6.5 hours, see attachment). I will try it again tonight. My problem there is that although the consumption was low, the signal was poor for 99% of the time.

I deleted the cache of 'Messages', and deleted its data. I already backed up my messages, so i can delete all the messages there (since 2016 haha). I will wait till tomorrow to try this out. However, it seems the only way to bulk-delete all messages is to select all the threads then delete them. I'll try this out tomorrow.
[BetterBatteryStats] justjr:
I think you mean it is true in a case where the two have the same signal. But the fact that on LTE my signal is really bad, and keeps going offline, and on GSM/3g, it stays 100% all the time, drives me to think it worth it to change it if it's anyone else's case. Specially since I don't need LTE all the time. But 2g is too slow, that doesn't worth it. If one is not using mobile data, more reason to use a band where you get the best signal. Correct me if I'm wrong.

Enviado de meu SM-G900M usando o Tapatalk
[BetterBatteryStats] DiamondJohn:
Not a recommendation, but to delete all messages, wouldn't you simply be able to delete the data for the messaging app? Not sure I understand why you are doing this for battery concerns.

As for your strange 2G/3G/4G reception/battery drain, as the signals are on different frequencies, maybe the 4G antenna is actually stronger / closer than the other towers :confused:
[BetterBatteryStats] dustinraditya:
Is betterbatterystats able to show percentage by percentage like battery drain analyzer? I was a BDA user but since BDA isn't working on pie, I'm looking for a replacement
[BetterBatteryStats] Deni_NS:
Am I blind, but i can't find 2.4 version?
[BetterBatteryStats] justjr:
https://rink.hockeyapp.net/apps/43837e1e08b04ce09d3b50ed1aed6768