yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] DB126:
Plus a ton of Context_Manager_Alarm_Wakeup_xxxxxxxx entries. Not sure how to interpret those. Not an advocate of limiting w/Amplify (not possible w/your ROM) as it only masks the symptoms while root cause goes unchecked. Best option may be to switch ROMs if other options are available for your device.
[BetterBatteryStats] JLius:
Damn, I just discovered why my battery drain improved drastically, I accidentally toggled the battery saving profile in the FKmanager. So formatting data probably didn't do sh**. Sorry about that. Back to square...
[BetterBatteryStats] paco_ramirez:
Normal battery consumption for a Galaxy S5 with new battery?

hi!

I've bought a new battery for the S5 and this is the battery stats result. I was expecting to have an improvement of the performance but I just feel its performance is similar to the old one. Despite this, I think bluetooth consumption is just too much considering I use it for a Mi Band 2. Could you have a look on the file and give me your opinion? Thanks!

PS: After charging it to 100% from 0% and turned it on, I got -5% in 17 minutes with the screen off. Why?
[BetterBatteryStats] Tayx:
Lol, I actually did it. Yesterday I did the following:

First I formatted all the formattable partitions to f2fs, wiped everything, clean flashed RR (which changed the system partition to ext4 again). Flashed beans mini gapps, team m8 kernel 1.3 (specific to my phone, the HTC M8). Booted into the ROM, installed everything I usually use. Install busybox and flash the booster (also specific to my phone). And finally, when I was outside without WiFi, I realized my phone stayed asleep much more % of time. So I disable WiFi during sleep (unless plugged in)... And voila
[BetterBatteryStats] JLius:
Okay, so changing to f2fs won't help battery I guess. I've disabled wifi during sleep, let's see if that helps, thank you for the tip!
[BetterBatteryStats] DB126:
Log encompasses 28+ hours of mixed use; far too involved for a meaningful analysis of any specific event. In general the bluetooth radio itself does not consume much power. Media, 'smart band' and fitness apps are another story regardless of screen state.
[BetterBatteryStats] Tayx:
Yeah, no problem! Good luck and I hope it works for you too!
[BetterBatteryStats] JLius:
I doubt it. I think I have another problem entirely. Or is it normal that the 'computed power use' does not add up to the total battery capacity?

For example the pics of my 2-days battery use (accidentely on power saver, else I wouldn't have made it to 2 days, not by a long shot).

My battery is supposed to be 4000 mAh, and that's what is says when I check with system monitoring apps. But when I add up my biggest consumers in the added pictures, I get only 1402 mAh. When I add the other ones, I get almost 1600 mAh. Is that normal? Charging my battery lasts as long as it is supposed to (over 2 hours).

Any feedback would be appreciated.
[BetterBatteryStats] JLius:
And the pics
[BetterBatteryStats] DB126:
Have no idea (nor care) how Android computes power use other than noting it is an estimate likely not far removed from magic (see Clark's third law). As for battery capacity, most packs shut down when ~85% discharged to protect the cells. Scoring ~3400 mAh out of a 4000 mAh rated battery is within expected norms.

Invest in a cheap USB charge meter (example) to check charge rate and verify usable battery capacity which will likely decline over time.
[BetterBatteryStats] xavihernandez:
Hi,

I have a weird behavior (not the 1st time it happens), I have inconsistent stats , for exemple now I open BBS and can see :

Unplugged since 7 h 41 m 17s

Deep sleep 20 h 26 m 38s

Screen On 6 h 36 m 31s

...

I cannot check my Screen on time for the period [Unplugged - Current] because Screen On time is not the correct stat.
[BetterBatteryStats] githyanki:
Do you use wireless charging? I found that it does not reset the stats, so I end up with some weird numbers all the time.
[BetterBatteryStats] xavihernandez:
Nope I use wall charger, a Dash Charger, it may be the reason why.
[BetterBatteryStats] Rated R:
i have these alarms on Oxygen, Oneplus 3T
[BetterBatteryStats] JLius:
Doesn't do anything for me. Tried this now : https://xdaforums.com/oneplus-3/how-to/guide-stop-google-play-services-t3549760/post70853146
[BetterBatteryStats] Tayx:
I actually tried that one a couple of weeks ago, but didn't solve anything. Right now I'm getting like a 1.1%/h drain, which is half than before, but still not perfect. Tried with Forze Doze and Greenify, but no luck yet.
[BetterBatteryStats] DB126:
Yep - the whole squash Google Play Services wakelock story line generally bears little fruit and often breeds side-effects. There are some exceptions, especially around location services wakelocks on older devices/ROMs.
[BetterBatteryStats] justjr:
Location alarms is what's killing me. Like wakeup activity and wakeup location. Which are the broadcast receivers, from where, I can test block without loose the location benefits?

Enviado de meu MotoG3 usando Tapatalk
[BetterBatteryStats] DB126:
Well - they probably aren't despite high counts. But you can fiddle with Amplify (Xposed module) if on MM or below. I found it to be disruptive to location services with minimal power savings. Choose your poison.
[BetterBatteryStats] paco_ramirez:
Thanks Davey. I hope this log is better (just 1h30m and a big drop) I always loose a lot of percentage just when plugging it off without using it at all.
[BetterBatteryStats] justjr:
Nham, they are the most recurring alarms, while others are like 15/h, they are 2/min. I'm on nougat, experimenting limiting location broadcasts on MAT. Having like +60% of alarms. And my drain with wake device is quite high.
[BetterBatteryStats] phillibl:
I work in a building where I get little to no cell reception all day and it kills my battery. Is there any options to reduce battery drain besides airplane mode? In running the latest Resurrection Remix.
[BetterBatteryStats] DB126:
Try disabling Google Location Services for a day (ok to keep hardware GPS active). Likely see a big reduction in location related alarms and wakelocks.

Alarms and wakelocks have no meaningful impact on drain while device is awake. Have you performed an idle (device sleeping) study with BBS? That typically is the first step to understanding drain sources.

Google Play Services will periodically reset many changes made with MAT when device reboots.
[BetterBatteryStats] justjr:
Yes, I get around 0.7% idle and I'm happy with that. I'll try use only device gps for a day and see results, thank you. Unfortunately BBS con't track my kernel wakelocks, so I think I'm missing something.
[BetterBatteryStats] DB126:
Large initial drop is symptomatic of an aging battery which isn't that surprising for a S5. Device was awake for 16½ min (~20%) which is somewhat high but not fully unexpected given short monitoring window. WhatsApp activity was a contributor. Assume Greenify is running in root mode as I didn't see evidence of Xposed Framework. Also means you can't enable 'doze-on-the-go' which is an important power saving feature for most Marshmallow ROMs. How about aggressive doze?

---------- Post added at 05:03 AM ---------- Previous post was at 04:56 AM ----------

Edit: just remembered the battery was recently replaced. Perhaps there is a problem with the phones charging circuit that does not properly top of pack. More likely the battery you purchased is old stock (although voltages seem ok).

---------- Post added at 05:09 AM ---------- Previous post was at 05:03 AM ----------

Google Location Services often responds faster than hardware GPS and works in locations that GPS can't reach (eg: inside some buildings). You will probably need to toggle it on/off as the situation demands.

---------- Post added at 05:15 AM ---------- Previous post was at 05:09 AM ----------

Not really. Toggling to 2G/3G may slow the drain but it will likely remain quite high. Radios ramp up power when trying to find/maintain a connection. Lower the power and connection will drop. Your device is behaving as intended.
[BetterBatteryStats] phillibl:
Thanks, airplane mode it is then.
[BetterBatteryStats] paco_ramirez:
Thank very much for the info. As you said, yes, battery was replaced especially because I was observing this strange behaviour; which seems present even in this new battery. I have the feeling that the new battery is ok (but it's very hard to know), but the phone is working with this new battery as it were the old one (I haven't noticed any improvement at all in general) Is it something that can be fixed? Can I try calibrating it somehow? Should I do a factory reset? In case is the circuit, can it be fixed?.

Yes, greenify is working in root mode. Aggressive doze wasn't enable. I'll give a try.
[BetterBatteryStats] JLius:
Yeah, so I noticed. Anyhow, I stick to battery saving mode (Franco kernel) then, don't notice any setbacks, performance wise, anyway. If anyone can suggest a better kernel for RN3, much obliged.

I guess my battery is just broken somehow (and always has been since I bought the damn phone).

Is there a way in BBS to differentiate between idle drain /hour and active drain /hour?
[BetterBatteryStats] DB126:
Thoughts:

- battery stats can be reset from the stock battery panel under settings

- some mfgs offer a firmware battery reset/recalibration; not sure about S5

- generally not a fan of Greenify's Aggressive Doze but certainly worth a try

- believe you will see better results running Greenify in Boost mode with 'doze on the go' enabled which requires Xposed Framework and Greenify donation

- a longer idle study (6+ hours with <1 min screen on time) will help determine if 20% wake time is the norm or just Android 6 taking it's time falling into doze mode; Greenify or a similar tool (ForceDoze; Naptime) can help with this

- can also use Greenify's Hibernate and Sleep widget to encourage faster doze

- consider temporarily adding WhatsApp to Greenify list to evaluate impact on wakes and associated drain

---------- Post added at 02:01 PM ---------- Previous post was at 01:53 PM ----------

Enabling BBS Watch Dog (under settings) will automatically generate screen off/on reference points which can then be used to distinguish between idle and active drain:

- screen off -> screen on (idle)

- screen on -> current (active)

Watch Dog does not spawn background processes or create addition loads other than the few seconds need to calculate stats after the devices wakes.
[BetterBatteryStats] ngr.hd:
Hi, [MENTION=1330150]chamonix[/MENTION] Have you transitioned to any crowd-sourced translate service? I would like to help translate it into Hindi.
[BetterBatteryStats] chamonix:
Well thanks for the offer!

Not yet but am still planning to. As the CI pipeline and hockey-app seems to work now I will focus on that next. I already have a project in place but need to see how the integration to github works and define the workflow to create pull requests automatically.

Stay tuned.
[BetterBatteryStats] justjr:
I can also update ptbr translation of needed.

Enviado de meu MotoG3 usando Tapatalk
[BetterBatteryStats] JLius:
Hi

I am going to post a dump file. Hopefully someone with more knowledge than me can have a look. I am using a battery saving profile ln Franco kernel and naptime with aggressive doze, but still my battery drain while idle is pretty high (a lot higher than I would have expected, actually).

Could it be that I just have a bad battery, or is there another culprit?
[BetterBatteryStats] githyanki:
event0 (): 17 m 27 s Cnt:(c/wc/ec)3254/68/0 7.3%

event4 (): 17 m 27 s Cnt:(c/wc/ec)3244/68/0 7.3%

event8 (): 17 m 26 s Cnt:(c/wc/ec)3250/68/0 7.3%

ipc00000295_dpmd (): 9 m 48 s Cnt:(c/wc/ec)2055/19/0 4.1%

ipc000000fc_netmgrd (): 9 m 19 s Cnt:(c/wc/ec)975/2/0 3.9%

ipc000000c2_rild (): 9 m 17 s Cnt:(c/wc/ec)972/2/0 3.9%

These all seem like system processes. You may want to try clean flash, or another rom.
[BetterBatteryStats] Rated R:
Any suggestions?
[BetterBatteryStats] DB126:
... or kernel not optimized for device. I would be tempted to go pure stock to grab a baseline with vendor certified binaries. No indication of a bad battery given high wake time and CPU utilization.

---------- Post added at 01:05 AM ---------- Previous post was at 01:01 AM ----------

Really can't work with screen shots; insufficient detail for meaningful suggestions. Better to conduct idle study (6+ hours sleeping with <1 min screen on time) and submit BBS log.
[BetterBatteryStats] JLius:
I did go pure stock 2 weeks ago, but my battery backup was still bad. I clean flashed los, and with stock kernel battery backup was equally bad. I really don't understand what the problem is. My battery has been bad for as long as I have the phone.

Also, my battery drops 3-6% a minute or so after I turn on the screen. Battery stats are always off a bit.
[BetterBatteryStats] htb2050:
Then your battery is degraded. Only option is to get a new one.
[BetterBatteryStats] JLius:
It's a none removable battery, and it has been like this since I bouht it 10 months ago.
[BetterBatteryStats] shaggyskunk:
It is possible that the battery may have been defective since you purchased the phone or something that is hardware related is causing your issue... Unless of course someone else has a better idea...
[BetterBatteryStats] JLius:
I'll grab another dump. I've installed radon kernel now.

My battery drain is very volatile, sometimes it has only drained 2% during the night, sometimes 8%. It can drop 6% in a matter of seconds. When I was on stock rom, I didn't have those drops, but still I could only squeeze +- 30 hours out of the battery with very moderate use (2 hours sot at most). I see guys with a RN3 doing 4-5 days with one load and 10hrs of sot.
[BetterBatteryStats] DB126:
Recent posts reveal long term behaviors not mentioned in your OP consistent with a bad battery or other hardware problem. I suggested a possible kernel issue in the absence of this information. Not really interested in another dump after spending a fair bit of time looking over the previous one.
[BetterBatteryStats] JLius:
Okay, fair enough, thanks anyway.
[BetterBatteryStats] justjr:
Just to see if anything is hurting it. 0.6%/h idle. I'm pretty ok with that, is wake drain that I'm not happy with, but I almost sure is the hotplug that keep all my cores always awake, soon to be addressed.

I'm using latest beta from hockey app, and still no kernel wakelocks showing [MENTION=1330150]chamonix[/MENTION], not even with API selected (not in this log).
[BetterBatteryStats] [Jaco69]:
Anyone can suggest where is my problem? com.android.phone?

Inviato dal mio LG-H815 utilizzando Tapatalk
[BetterBatteryStats] DB126:
Nothing stands out aside from WhatsApp; pretty standard activity pattern for Nougat. There are very minor items that could be addressed with MAT such as package measurement service (part of Firebase Analytics); likely won't make a meaningful difference.
[BetterBatteryStats] justjr:
So, you recommend to disable measurement broadcasts on google play store and play services? But not analytics or firebase broadcasters itself?
[BetterBatteryStats] DB126:
You will get far greater savings by allowing Nougat optimize WhatsApp. If you want to restrict FireBase analytics reporting (not necessarily recommending that) disable PackageMeasurementService within Google Play Services using MAT or equivalent. Note the service is auto-enabled at boot and other events that I have yet to fully catalog. Prior to Nougat one could use MAT Xposed to prevent this behavior. To my knowledge there is no equivalent for Android 7.x. At some point I may whip something up to auto-kill the component; still need to explore some other options that do not have an Xposed dependency.
[BetterBatteryStats] justjr:
Yes, but what about the other measurement broadcasts? Have 3, and only this one you pointed out get re-enabled automatically, the others stay disabled. Also, what about the Firebase broadcasts? They don't disable Firebase?
[BetterBatteryStats] DB126:
Disabling the service I referenced is sufficient to stop the periodic reporting that generates activity and wakelocks. I'm unconcerned about the others as there is no evidence they are significant drainers.
[BetterBatteryStats] justjr:
Too bad that's the only one that re-enable itself...
[BetterBatteryStats] Rated R:
Here
[BetterBatteryStats] DB126:
1% drop over 4 hours (~0.25%/hr) is excellent! Device was awake for 7 min at low CPU frequencies preforming normal housekeeping. There were no rogue apps. The only item of note is the Media Scanner Service which performed some routine background tasks. Suspending this might reduce awake time by 1-2 min (it shows five min of activity which almost certainly overlapped other tasks) and likely would not have an insignificant impact on battery endurance.

In a previous post you called out several wakelocks of possible concern. Ignore these; most wakelocks are either benign or necessary for the device/rom to carry out normal activities.

Recommendation: no action needed; enjoy your device.
[BetterBatteryStats] Vuska:
Is this app support Mi5 ?

Because i try with 2.2.2.0 and see CPU states, i don't see 2.1 GHz...

Only 1.59 Max.

Just don't get it why.

Mi5 with Android 7.0
[BetterBatteryStats] DB126:
- user another app to independently verify the CPU frequencies being utilized under various loads

- perform an activity that shows high CPU frequencies with another app; then see if those values are reflected in BBS

- some Mi 5 models are rate limited to 1.8 GHz although most allow full 2.15 GHz
[BetterBatteryStats] JLius:
Well, guess my battery isn't damaged after all. More info after I drained it ?
[BetterBatteryStats] DB126:
While the log looks good (normal) from both macro and detail perspectives I would be cautious drawing conclusions from a single run of relatively short duration. On a positive note, fully draining the battery can recalibrate cached data used to estimate charge level and smooth out some of the spikes/dips you were observing. Be interesting to see what happens over a few cycles.

Note: purests will call out alarms and wakelocks in the log as evidence more tuning is needed. Resist the temptation to react to red herrings unless long term data suggests there are rogue drainers that need to be tamed. Layering on power management tools breeds complexity that most regret over time. Native Android 7.x doze potentially augmented by ForceDoze appears to be doing its job.
[BetterBatteryStats] Tayx:
Interesting, how did you manage that? Did you try something new?
[BetterBatteryStats] JLius:
I returned to stock once again, did a full wipe + factory reset and installed resurrection remix. In rr, you have the option to set data to 2g when turning off the screen, I think that did the trick for me. I am mostly on 4g. I turned off the wifi too. Other than that, I run naptime on agressive doze.
[BetterBatteryStats] Tayx:
I had that setting before, but forgot to turn it on this time, thanks for reminding me! I will try to leave it on and see what happens ;)
[BetterBatteryStats] purbaboy:
alarm idle drain

Hello guys how to turn off the wifi alarm ? Anyone could please explain. Thanks in advance
[BetterBatteryStats] DB126:
Alarms in themselves don't drain; it's the actions taken (if any) that need to be considered. In this instance Connectivity Manager is necessary to maintain WiFi connections and scan for available networks. Scanning frequency can be reduced but it really won't help battery life much. If you want to tinker with scanning frequency consider the LSpeed app which has a setting to reduce the frequency in a relatively safe manner.
[BetterBatteryStats] purbaboy:
Thanks very much Sir for the explanation, so how to reduce it in the lspeed app i already installed but seems confuse to tweak it. Need your enlightment :cowboy:
[BetterBatteryStats] JLius:
Enlightenment does not come easy, one has to grab a cup of coffee and do some research. https://xdaforums.com/android/general/lspeed-app-settings-battery-stats-t3346347

---------- Post added at 07:01 AM ---------- Previous post was at 06:51 AM ----------

What really puzzles me, is that my total computed power use before was about 1500 mAh, and now it is almost 5000 mAh (still 20% left after 3 days of moderate use). My battery is only 4000 mAh, how can this be?
[BetterBatteryStats] DB126:
Battery improvement option.

---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------

Computed power use is an estimate that often bares little resemblance​ to reality. I looked at it a few times, chuckled and have since ignore it.
[BetterBatteryStats] amir.susul:
hi everyone i have a problem with partial wakelocks. i have 17% powerManagerserviceWakelocks and if im not wrong i shuold seen this 17percent in partial wakelocks. but all of them is 0. i dont have a 1% wakelock in partial wakelock. my android version is 7.1.2

sry for bad english
[BetterBatteryStats] githyanki:
Post an idle log as described in OP and someone may be able to help with that.

PowerManagerWakelock tells us that something was holding the phone awake and that the power manager was on because of that. Does not tell us why phone was on.
[BetterBatteryStats] Darayavahus:
Hello everyone,

I've bought the S7 G930F recently (used in perfect condition). First thing I did is customization, rooting and maximum debloating to suit my needs. [I chose superman ROM, with "super stock kernel", based on android nougat as most of the XDA/S7 users did]

I came to a problem with battery. I mean, I find it too weak to be true. I simply CAN'T go past 24hr use without charging, is it normal? (well, maybe if I wouldn't use the phone at all it would be better, but it's a nonesense). 4 hours of avg screen on time? Something isn't right here (or it's just me).

I've done almost all things to extend battery life on a full charge, and those efforts seems to go in vein. Maybe it's the way galaxy s7 is? i dunno, my old sony z3 lasted twice as long, and it had the same battery size [3000mAh]

The settings are as follows:

1. Screen brightness set to 40-50% without auto mode

2. No nfc/bluetooth/or any other scannig utilities beside WIFI and synchro service, which are always ON

3. Always on display switched OFF (I simply had to, cause it strenghtens the drain)

4. Black theme for whole layout (not dark, just black)

5. I have a very weak carrier signal, tends to search for it all the time [It can weaken the battery, ofc, but my previous Z3 had to struggle with the same problem and it was able to reach 2 days by avg)

6. No intensive (heat producing) apps being used - I'm talking about games etc. Apss used mostly are skype, web browser, and regular stuff like music players, msg senders. [CPU states from "better battery stats" are showing 78% deep sleep]

7. Using regular Kernel without tweaks from my side, which could cause this drain to be happening.

My question is:

Is the battery really that weak, or is should I replace the battery with the new one?

Any advice given would be much, much appreciated. I have no idea what it would be like, if I'd be using this phone as a typical consumer with all the bloat, brightness on full and bull**** like that, it would be a nightmare:/

My current average battery consumption while IDLE [phone left alone without waking up the screen] is 2% per 1 hour, based on Better battery stats info.

Below you can find a dump file taken from my device after 2.5 hour IDLE time, after being 'unplugged'.
[BetterBatteryStats] DB126:
Nothing jumps out in the log. Screen off wake time (at low cpu frequencies) was a bit high and likely reflects efforts to obtain/sustain carrier signal as evidenced by other activity/wakelocks. Might try dropping down to 2G/3G when not in active use (still ok for calls/sms) or toggling off mobile radio when connected to WiFi. There are ways to automate these actions if they prove beneficial.

To check the batteries actual capacity (don't know the device history) you will need to invest in an inexpensive USB charge meter (example). Discharge device then return to 100% with meter attached. Anything above 80% of rated capacity reflects a healthy pack.