yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] IronTechmonkey:
Not blind but perhaps not thoroughly reading the OPs. Check post #2, newest "old" version, or the test version. If I understand correctly 2.2.2 (newest old version) is the same version that is in Playstore
[BetterBatteryStats] Eversmile23:
I could not upload the screen shot.What does this 'batteryserviceupdateservices'do in the Android system? If I restrict the warlock caused by this, will there be any bad effect?

https://drive.google.com/file/d/1CAnTy4fMCPBCscn_LDxgP4krNtOIDcFg/view?usp=drivesdk
[BetterBatteryStats] One Twelve:
Question about let it run down ?

It can take many hours to reach 95% from full if i leave it there and i don't know when it will reach 95

So could i use the phone say watch youtube till it got to 95. Then close yt and let it sleep from there on ?

Otherwise could i just charge to 95 or less (ie not full) and start the test immediately after unplugging ?
[BetterBatteryStats] adm1jtg:
Fair enough....

Couldn't get the dump file for some reason... Had to use alogcat to get logcat
[BetterBatteryStats] rootSU:
Thanks for the help dude.

Yesterday night I just turned off WiFi and bluetooth scanning, and put the location under Battery Saving.

Log was disturbed from the call today morning, so couldn't upload that :(

But I got about 6% loss now in the night, on 4G, at about 1%/hr.

So I think scanning and location were wreaking havoc on mobile data.
[BetterBatteryStats] TNSMANI:
Starting from 95% is not mandatory. You can start from anywhere, preferably above 50%, if the aim is to take a dump from "screen off " to screen on". Till then what you do with the phone is your business. That will not affect the dump.

---------- Post added at 12:52 PM ---------- Previous post was at 12:48 PM ----------

Reading from your screenshot, I would say that it updates the battery stats. Restricting it may result in battery stats not displaying properly.

But should you meddle with it? After all, it kept the phone awake for hardly 4 seconds.
[BetterBatteryStats] Newtac:
Alright, so i was right :rolleyes: the only fact is that it wasnt working properly.. Ill try it out again later thank you :)
[BetterBatteryStats] ShreyanshLodha:
My kernel is not able to show Kernel wakelocks

proc/wakelocks and /sys/kernel/debug/wakeup_sources both these files exist with details of the wakelock.

just to be sure I added the lines below to my ramdisk as well.

mount debugfs debugfs /sys/kernel/debug
chmod 0755 /sys/kernel/debug

both the files have r-r-r permissions.

I saw denials in the log

01-31 18:30:40.866 21361 21361 I com.asksven.betterbatterystats_xdaedition: type=1400 audit(0.0:1259): avc: denied { read } for uid=10251 comm=4173796E635461736B202331 name="wakelocks" dev="proc" ino=4026547562 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:proc:s0 tclass=file permissive=1
01-31 18:30:40.866 21361 21361 I com.asksven.betterbatterystats_xdaedition: type=1400 audit(0.0:1260): avc: denied { open } for uid=10251 comm=4173796E635461736B202331 path="/proc/wakelocks" dev="proc" ino=4026547562 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:proc:s0 tclass=file permissive=1
01-31 18:30:40.866 21361 21361 I com.asksven.betterbatterystats_xdaedition: type=1400 audit(0.0:1261): avc: denied { getattr } for uid=10251 comm=4173796E635461736B202331 path="/proc/wakelocks" dev="proc" ino=4026547562 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:proc:s0 tclass=file permissive=1

But its a premissive build. So it shouldn't be a problem.

Can anyone suggest me what else should I check?

Or what am I missing?
[BetterBatteryStats] One Twelve:
Yes, screen off to on is the idea. Any reason for not going below 50, assuming battery saver isn't active ?

Reason i asked was because of this comment

So there is some rationale to not starting at 100 or coming off the charger too quickly.

I've tested starting from 100 and at 95, to my surprise i found the voltage lost/h higher at 20%/h compared to from 100 where it was just under 10%/h. I don't know why the difference is there or whether it matters. Battery is only three months old so age isn't a factor

With some phones its known that they take longer to drop from 100 to 99, reason being 100 isn't really hundred and trickle charging only ever stops say a good half hour or so after it says 100 and reaches real 100, if that makes sense. If you leave your phone charging unattended this is common.

This kind of behaviour will skew the level% lost/h. From 100 the average drop rate is lower rate than from 95. Things may appear better than they are when starting from 100 :)

i will test at lower levels to see whether the voltage levels change. The watchdog feature is very handy here. Makes idle testing feasible as i can use the phone this way and run an idle test when i want
[BetterBatteryStats] DB126:
There is a ton of rational. I have worked with a few dozen devices of varying design and capability. Discharge behavior is highly individualized within and across device types regardless of battery age, especially for 'economy' packs. More often than not rates under constant load are not linear at the upper and lower quintiles regardless of manufacture. Differences may not be radical but definitely measurable/repeatable. But it's hard to convince others of that when the only data point they hold is in their hands.
[BetterBatteryStats] IronTechmonkey:
+1 each, from almost every device I've ever used.
[BetterBatteryStats] kventura:
can someone for the love of god tell me what is wifioffdelayifnotused ? That thing is draining my battery like mad
[BetterBatteryStats] TNSMANI:
Isn't it obvious - "wifi off delay if not used"?

Without any further info, this is the best I could do.
[BetterBatteryStats] Oswald Boelcke:
Is "WiFi Search" enabled under ROM settings => Location => menu button top right corner => Search? If affirmative then disable.
[BetterBatteryStats] kventura:
Its already off but still getting high usage.
[BetterBatteryStats] adm1jtg:
[MENTION=1330150]chamonix[/MENTION] anything in here that helps?
[BetterBatteryStats] jukyO:
[MENTION=1330150]chamonix[/MENTION]

Bump, help needed.

---------- Post added at 05:04 PM ---------- Previous post was at 05:03 PM ----------

[MENTION=1330150]chamonix[/MENTION]

Bump, help needed.

---------- Post added at 05:04 PM ---------- Previous post was at 05:04 PM ----------

[MENTION=1330150]chamonix[/MENTION]

Can you help here?
[BetterBatteryStats] suvishalreddy9:
BBS DUMP

Firstly any suggestions to improve my battery life are appreciated [MENTION=1330150]chamonix[/MENTION]

✓ followed #1 post rules and created dump file from ~95% (left device ideal for 8-9hrs)

WiFi and mobile data turned on

Got .7% ideal drain

✓Screenshot of my setup is attached [will be using Francisco kernel and OnePlus open beta for 5T for couple of months atleast]

✓Battery saving app's used only Naptime!!

Planning to get Greenify ....

Dunno if Amplify will work perfectly on Android 8.0.0

(As xposed oreo is still in beta) ??

Should I attach logcat also ? Or only dump is needed

I don't want to break Gmail & WhatsApp push notification

Thanks in advance
[BetterBatteryStats] TNSMANI:
0.6% per hour drain is reasonably good considering that the screen was on for 9+ minutes before the dump was taken.

An idle dump should have 6+ hours of idle statistics in addition to less than one minute of screen on. In other words, the dump should be saved within seconds of unlocking the screen. So please generate another dump and attach so that someone can help you.
[BetterBatteryStats] peterlee928:
fyi please avoid posting the same message in multiple threads.

https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884/post75441100
[BetterBatteryStats] adm1jtg:
Well this is why I don't bother posting logs. I don't expect an immediate resolution but a simple response either saying you think you found the culprit or asking for more logs would be appreciated
[BetterBatteryStats] DB126:
Sorry about that. Must be all XDA developers/volunteers servicing this thread were out celebrating huge bonuses.
[BetterBatteryStats] steigerth:
Battery Drain in Nougat 7.1.2

Hello,

First of all, thank you very much for the excellent App "BetterBatteryStats". It is really helpful!

My phone seems to have a problem with the following kernel wakelocks:

suspend_backoff

qcom_rx_wakelock

I have a Sony Xperia Z1 compact with a custom ROM: LineagesOS 14.1; Android 7.1.2

As mentioned in the introduction of this thread I fully charged my phone and left it on my desk for a bit more than six hours without touching it. How can I resolve the battery drain? How could I find out the reason for the suspend_backoff and qcom_rx_wakelock.

Attached are the log files from BBS:

BetterBatteryStats

dmesg

logcat

I would highly appreciated any hints.
[BetterBatteryStats] Zotho:
Hi altogether,

I also need some help please, as I am getting insane with this battery drain topic. :eek::crying:

Trying several ROMs based on 7.1.2 on my Samsung Galaxy S5 / klte since one month now, and no matter which options I try, I never get better idle or deep sleep drain than min. 0.8%/h up to 1.2%/h.

At the moment I got AICP, already tried AOKP, crdroid and blank LOS.

I started with no helper apps, then changed between ForceDoze, L.Speed, Amplify, Greenify and so on.

At this moment I have Amplify and Greenify active, and additonally got some apps stopped background usage using the LineAgeOS Privacy Guard. Tried with and without also...

Settings is energy saving.

I cannot really find the reason for the battery loss overnight, please give advice, really appreciated. I really can´t read the logs as good as you to find the culprit. ;)

Maybe I really have to step back to MM, which had less drain even though I didn´t reduce so many things.

The logs are taken in 8.5 hrs overnight, immediately switching phone off after setting bbs custom reference.

Thanks in advance,

Zotho
[BetterBatteryStats] jukyO:
[MENTION=1330150]chamonix[/MENTION]

Bump, help needed.

[MENTION=1330150]chamonix[/MENTION]

Bump, help needed.

---------- Post added at 05:04 PM ---------- Previous post was at 05:03 PM ----------

[MENTION=1330150]chamonix[/MENTION]

Bump, help needed.

---------- Post added at 05:04 PM ---------- Previous post was at 05:04 PM ----------

[MENTION=1330150]chamonix[/MENTION]

Can you help here?
[BetterBatteryStats] TNSMANI:
Suspend_backoff - read this

qcom_rx_wakelock - related to your wifi. Frequent connection/disconnection attempts will trigger this. Check whether you have any other device connected to the wifi, like a printer for instance. That will also interfere. Assigning a static IP for your phone may lower this number.

BT - you seem to have a wear device connected to the phone which is contributing to the drain. If not needed during sleep, disconnect. If not, learn to live with extra drain.

com.sonymobile.lifelog (): Wakeups: 75 (11,9 / h) - a major contributor for the drain. Looks like a health app. Disable or uninstall for better battery.

0 (Wifi) (0): 6.0 MBytes 77,9%

10037 (Wifi) (Google-Dienste): 1.0 MBytes 14,7% - in addition to all the above, background downloads also contributed to the drain.

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

You seem to have taken the dump with airplane mode on ie. no wifi or data. So the dump's usefulness is very limited. For a proper dump, both these have to be on.

Though your phone was in deep sleep for 8 hrs and 26 odd minutes - 99.4% ( awake screen off was only about 2 minutes - 0.5%), you had a drain of 1.1% per hour. This is high considering there was no wifi or data connection. How old is your battery?
[BetterBatteryStats] Zotho:
Thank you for the fast answer [MENTION=5656100]tnsmani[/MENTION]

Yes, I really tried to find out why it drains so much battery during airplane mode, with everything off. I do this usually by an app (Timed Toggles) overnight.

I used to have very little drain doing it like that, but I can´t get to good results anymore.

You´re right about the battery, it is still the first since end of 2014, so it´s about 3+ years old now. This could be also an issue, but I am able to use blank ROMs without many apps and have almost no battery loss in airplane mode. I only install about 20 apps, mainly Google stuff.

Maybe I really should try another battery, but I think there´s room for improvement still by changing software behaviour.

Btw. is there a difference in installing Gapps (openGapps) pico vs. some larger package and installing the wanted apps through the play store? I mean other than having it not in system? Does this affect anything else?

Thanks again
[BetterBatteryStats] nospherato:
Hi all,

does anyone of you perhaps has any idea why my xperia xz1 compact uses lot more battery when Wifi is enabled?

These are pics with Wifi on.

(Battery consume is same on 2,4ghz and 5ghz. Signal strength is not weak as the router+repeater [bridged mode via lan; doing the wifi] are just like 3-4m away.)
[BetterBatteryStats] TNSMANI:
The reason why you have less drain with less Google apps is obvious. It is the expected behaviour whether on MM, Nougat or Oreo.

I don't think there is any difference between Gapps in ROM and from PlayStore.. They will drain equally badly. Have as less Gapps as absolutely required. Or be Gappless.

Three+ years old battery is definitely due for replacement.
[BetterBatteryStats] nospherato:
And these pics are with wifi off and using LTE.

Both settings are with location service disabled (also wifi+bt scanning), bt on, and just 2-3 checks for e-mail (little usage).

As you can see in the same timeframe wifi on uses 7% vs not even 1% using LTE only.

This is the wifi off post for the wifi on post:

https://xdaforums.com/showpost.php?p=75489280&postcount=33663
[BetterBatteryStats] TNSMANI:
Enabling data or wifi will result in battery drain since all the apps will start using the internet. Between the two, wifi is better.

For any further advice, please take an idle dump and attach it here. Screenshots have only a limited use.
[BetterBatteryStats] nospherato:
Sorry, I'm new to BBS, is this the dump you are talking about?

(I know wifi on and enabling data usses more battery, but normally shouldn't wifi use less than LTE and not 6 times more battery?)

Ah one little more:

I use adguard to block ads (also tried with uninstalling it, but same battery consume..) and there are not really and apps (you can check traffic there) using a lot of bandwith.
[BetterBatteryStats] TNSMANI:
For a comparison, an identical scenario is an absolute must. The phone might have been in deep sleep before wifi was enabled, in which case all the net hungry apps which were under control, will start using the wifi simultaneously, draining it faster. If after sometime, the wifi is switched off and data is enabled, there will not be much internet traffic since all the apps had just then finished using the net.

So please post a couple of idle dumps (1) with wifi on and data off and (2) with data on and wifi off. Then we will see.
[BetterBatteryStats] nospherato:
[MENTION=5656100]tnsmani[/MENTION]

Will do it, thanks for now :)
[BetterBatteryStats] TNSMANI:
Idle dump: charge the phone to 100% or atleast 90%+, disconnect power and leave the phone idle for atleast 6 hours. Then unlock the screen and immediately save the dump from ''disconnected' to 'current'. The phone should be idle for 6+ hours and the time between screen unlock and saving the dump should be less than a minute.
[BetterBatteryStats] DB126:
No unusual activity; in fact quite the opposite. Slept like a baby on Benadryl.

Two possibilities:

- old device, old battery with diminishing capacity

- kernel incompatibility disallowing hardware/sensor 'deep sleep'

Really boils down to characteristics of an aging device. Replacing the battery may be cost effective; otherwise consider rolling back to MM which still may not yield tangible benefits if the battery is crapping out.

Could also doink around with custom kernels if you are into that sort of thing (oi - I prefer dipping my head into a pot of boiling oil).

Oh yea - loose the Amplify/Forcedoze/L-Speed/Naptime/etc. plecebo farm - none of which are needed on Nougat+. Greenify and similar hibernation tools offer a method for reining in 'bad actors' if/when needed and can be helpful dealing with screen-off motion detection (aka Doze on the Go) on Android 6.x based ROMs. Good luck.
[BetterBatteryStats] Zotho:
Thanks for your thoughts, Davey

Well, first of your mentioned possibilities is definitely true, the battery is getting older and older... Thinking of buying a new one, just not sure which one, as there´s an 'upgrade' from 2800 to 3500 mAh possible with original Samsung batteries.

In fact when I was using the crdroid 3.8.4 version in beginning of January I used different kernels and tried to tweak them for battery lasting. Didn´t really help for standby time, just for SOT.

About the 'placebo farm' you´re calling it: Which of those tools do you think help beginning from Nougat onwards? I think any kind of aggressive doze can be helpful to get the device to sleep faster. This would be Greenify, Force Doze, L.Speed and Naptime. Amplify is the only different tool there to stop wakelocks and alarms. And I think this really is helpful if some apps or services try to be active too many times, don´t you think too?

However, I will try a little longer and if nothing succeeds I will buy a new battery and revert to MM stock ROM. Seems Samsung did a good job on this, keeping Google under control :p
[BetterBatteryStats] DB126:
None, unless you have a highly specialized situation that demands a surgical solution. Even then there are usually better responses than blocking wakelocks (which are a misnomer and have little to do with actual wake time) or munging doze parameters.

Android engineers are not fools. While early builds were focused on increasing functionality at the expense of performance and battery life Google quickly recognized future growth was in regions where users could/would not buy into more powerful hardware. In some areas nightly charging is a luxury; devices are expected to run untethered for days. The results can be seen in the progressive resource management improvements in Android M/N/O and recent builds of Google Play Services which are far less taxing. Improvements emerging in 'Android Go' will likely be folded into future mainstream ROMs and apps.

My recommendation is to look at resource management holistically versus through whatever pinhole happens to be in focus. Objectively measure outcomes over an extended period vs reacting to single data points or conceptual claims from enthusiasts based largely on empirical evidence without accompanying (scientific) analysis. Improving 'reasonable' idle drain rates may not, and probably will not, yield improved battery endurance over the course of a day as most forcibly deferred tasks will run at some point and/or yield undesirable side effects, often when you least want it. I could go on but have long since learned that the power of the placebo playground usurps hard data. People just love to turn knobs & dials then attach meaning to each movement.

Good luck. I'm sure you'll find your personal zen in some cocktail of Android tools.
[BetterBatteryStats] Zotho:
Davey, again thanks for your interesting statements. :)

I also believe that the Google devs improve things from version to version. However, the progress they make by having their system as performant and at the same time less battery consuming can be minimal.

And don´t forget about the app developers, who still have freedom to choose, how active the app will be in the background. No matter how hard Android tries to stop the App, if this tool always tries to force activity in the background, it will be hard to improve things.

Another thing is that especially the apps by Google themselves tend to eat up battery like no other. Look at Maps or Google App, which I really love to have because of voice recognition. But if one looks at the real battery drainers in the statistic, it´s always led by Google stuff. No matter if you really used it actively or not.

Agreed on your second point, interferring with the tasks may result in having negative side effects. You know, that´s like with medicine. If you take it and you´re getting better, it for sure was the medicine. :p

Will try to reduce as many apps that I don´t need. I think that´s the only Zen I´ll find out there :laugh:
[BetterBatteryStats] JCARLOS123:
Hello,

Any adjustments I can make to improve battery life? I have attached a dump file from BBS.

Thank You,
[BetterBatteryStats] DB126:
A few quick comments:

- Random apps no longer have the ability to drive sustained background activity on Android 8; MM/Nougat also impose some restrictions. Developers are responding by redesigning apps to behave more responsibly which benefits everyone.

- Google's own apps *can* be drainers depending on how they are configured and used. On some devices I hibernate Maps which tends to self start and pop up annoying notifications. I use to fuss over the Google app but found it does not consume much juice if not using Assist which I personally don't care for. Interestingly, Gboard can be a heavy hitter depending on configuration. Bottom line: Google apps can be resource pigs but can also be configured to be less aggressive.

- Those who demand control over everything will find Android increasingly frustrating as Google increases its sustained presence similar to Amazon and Apple (microG or going commando are options but carry their own burdens). Pull the lens back and the impacts typically are not that egregious. I'm comfortable giving up 3-5% of battery endurance over 24 hours (~0.2% per hour) in exchange for the services provided. More importantly, I can spend time using my device vs managing it.

- None of the above address privacy concerns which some find bothersome. I don't tilt to that windmill but do take reasonable precautions both behaviorally and technically.

Edit: let direct observation and hard data drive actions vs. the worrisome presentation of some apps, forums and boards (not to mention the media when it come to security drama). Technical social media is great but also trends to be an echo chamber where the same old claims are endlessly repeated without accompanying data collected in a manner that minimizes 'placebos'. Then again, that's all rather boring. :)
[BetterBatteryStats] Zotho:
I know we´ve gone OT now, but it´s pretty interesting :D

So your suggestion for me would be: wait for a stable running Android Oreo for my old device, replace battery and stay without any additional 'helper' tools. Tried an AICP early build of 8.1 as well as an blank LOS, but both still are in early state. :)

I always triy to configure the Google apps as little intrusive as possible, as I like to use them, but only if I actively do it. I don´t like thousand syncs a minute.

Regarding the topic that Google more and more becomes like Apple, that´s true unfortunately. This is one of the reasons that I still want root, because I want to have Airplane Mode automatically set overnight. This was no issue pre Lollipop but then they decided to drop this option. Same goes for the Oreo option to disable Wifi while not active and charging. I can´t understand these decisions, as this will definitely lead to more battery consumption.

I hope they won´t restrict everything, like the Apple´s golden cage, because this would really frustrate me. This was always a reason for me and many others not to buy anything of the fruit company. I got an iP 6s as work phone, and it´s awful to use. Even Windows Phone was better use experience. But the battery lasts :p