yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] peterlee928:
works for me

---------- Post added at 09:51 AM ---------- Previous post was at 09:43 AM ----------

set your phone down before you go to bed and let it go screen off on its own.

dont touch it while you sleep.

when you wake up (presumably >6 hours later), open bbs.

then set the "from" and "to" settings as "screen off" and "screen on".

then save the dumpfile... then submit to this thread.

as noted in the idle dump directions, screen on time must be <1 minute.

good luck :good:
[BetterBatteryStats] Unknowx:
Ok, I think I did the whole procedure correctly.

I have found two files dump that I attach to you

Thanks again.

https://mega.nz/#F!53BFjCJJ!WKziPEZWah9N9s4tmFhjJQ
[BetterBatteryStats] strongst:
Did you charged your device? Level lost [%]: Bat.: 93%(2% to 95%) [-11,3%/h]

It must be unplugged and not plugged and charging otherwise the dump won't measure the idle drain obviously.
[BetterBatteryStats] Unknowx:
I opened the app, activated the monitoring, charge the phone up to 100%, disconnected and not touched for 6 hours.

It's wrong?
[BetterBatteryStats] strongst:
There's something wrong. As seen by your dump file as it charges.

Please make sure NOT to monitor the charging process.

Monitoring is activated by default and when you unplug it starts monitoring(don't know what you did...).

You can also trigger the monitoring by setting a custom reference when unplug it immediately.
[BetterBatteryStats] Unknowx:
I simply did the steps above.

I will try to repeat the procedure without manually activating the monitoring.

But then again, it seems strange to me.
[BetterBatteryStats] peterlee928:
https://xdaforums.com/showthread.php?t=1179809&p=72467976

this post provides instructions on how to capture a proper idle dump. hopefully that helps :good:
[BetterBatteryStats] Unknowx:
Ok, new test.

Thanks a lot.

https://www97.zippyshare.com/v/UDq0yG06/file.html
[BetterBatteryStats] strongst:
Thanks for sharing, but I can't see a huge battery drain since 0.4%/h is very good.

Facebook causes some wakelocks, but it's not worth any investigation imo.
[BetterBatteryStats] Unknowx:
So the battery drain that I see in the use is simply given by the update? Since in the previous ones it was not present. And it's a very obvious thing in a lot of one plus users I exclude a battery calibration as it is not necessary. I also remember that with the verse and 5.1.9 have inserted the Sleep Standby Optimization function, it could not alter the test?

Thanks guys
[BetterBatteryStats] strongst:
Usage behavior is different than idle behavior. You cannot compare both and it's really hard for others to investigate your usage behavior, therefore idle drain behavior is what can be analyzed with a good advice what's wrong.

I'm on op5 ob16 and sleep standby optimization works very well. I get 0.4 to 0.5 idle drain per hour.
[BetterBatteryStats] muralimsir:
New to BBS

I'm new to BBS and figuring out how to read and understand the info it provides. Thanks for this.
[BetterBatteryStats] peterlee928:
this is a good place to start :good: http://asksven.github.io/BetterBatteryStats-Knowledge-Base/howto.html
[BetterBatteryStats] mrmcshagbag:
I am having issues with my proximity sensor running all the time. I have greenify with aggressive doze activated as well as disable motion sensors. I have proximity wake disabled as well as pocket mode disabled. Can't really tell what is keeping the proximity sensor awake all the time. Any help is appreciated.
[BetterBatteryStats] peterlee928:
is this causing a battery drain? just because it shows up a lot doesnt mean it is causing idle battery drain.

that said, you may want to turn off ALL gesture/display related settings (selfie gesture in camera, double tap to wake phone, phone screen automatically turning on if you lift up your phone, display settings that change when you are on the phone, etc).

other potential causes could be a health app (ive read that samsung health apps cause this), "keep screen off" function, changing display setting from adaptive to amoled (or something else), other third party apps that trigger with smart gestures.

EDIT

the smarter way of doing this would be to test one by one to see if you can isolate the culprit. more time consuming, but may be the more optimal route for your needs.
[BetterBatteryStats] gFknQ:
What rom & kernel? I may be able to help
[BetterBatteryStats] DB126:
Does it keep the device awake, trigger undesirable 'side effects' or impact idle battery consumption which typically averages 0.4-0.7%/hr on most devices? If no to all (especially the latter) enjoy your device as designed and the free time afforded by not trying trying to fix something that ain't broke.
[BetterBatteryStats] mrmcshagbag:
Havoc os 7-20 build with madys x26 kernel

---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------

Yeah it was averaging 0.2-0.6 an hour idle now it varies 1.2-3.4 at times. Just can't nail down how to keep proximity inactive when not in use. Only thing I know that uses it is my aosp dialer.

---------- Post added at 12:09 AM ---------- Previous post was at 12:08 AM ----------

Yeah it was averaging 0.2-0.6 an hour idle now it varies 1.2-3.4 at times. Just can't nail down how to keep proximity inactive when not in use. Only thing I know that uses it is my aosp dialer.
[BetterBatteryStats] DB126:
You are assuming proximity sensor activity is the culprit without supporting evidence. Proximity activity is likely a symptom of some other background processes which is the root cause of increased idle drain. Need to conduct an idle study to help ferret out the bad actor(s). See linked post for procedure.

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] vijayinvites:
Please help
[BetterBatteryStats] DB126:
Fingerprint sensor. Either dirty or not properly supported by kernel/rom.
[BetterBatteryStats] mrmcshagbag:
Delete
[BetterBatteryStats] vijayinvites:
Yeah, I don't think it's dirty. When I restart the phone, the problem is solved for some hours. It comes back again. Trying Wyeth different kernels now
[BetterBatteryStats] buffal0b1ll:
Hi. Here's an idle log. Any help with identifying culprit(s) would really be appreciated. Thank you;)
[BetterBatteryStats] strongst:
That's a really high drain per hour. Is it stock rom with custom kernel?

Old battery?

Suggest you a clean flash with stock rom to test.
[BetterBatteryStats] buffal0b1ll:
Stock ROM custom kernel, yes.

I think it's an app or sensors that's the problem but I can't back it into a corner. Just a couple weeks ago it was behaving nicely with 0.7% idle drain so I don't think the battery is bad.

Is there anything standing out in the stats that points to app(s) causing the issue? I use a lot of widgets Chronus, IP Widget, genie News & Weather I also have a lot of Tasker profiles.

Clean flash is an option, but I believe I'll just end up reinstalling whatever app is rogue and be right back where I started. So I want that to be the last resort.
[BetterBatteryStats] strongst:
There's nothing that leads to an app itself. Also the wake time while screen off is just below 10 minutes. Sensors are OK so far, only line 608 isn't clear.

That's why I thought it's the battery or the kernel.

Nevertheless, a clean installation with stock kernel can bring more light into darkness ;)
[BetterBatteryStats] buffal0b1ll:
Yeah I saw 608 too and disabled lift to wake gesture. I think before a clean flash blowout I'll try stock kernel for a couple days and monitor.
[BetterBatteryStats] strongst:
4.6%/h is higher than a sensor normally would drain from the battery when going roque.
[BetterBatteryStats] buffal0b1ll:
Actually before giving stock kernel a run, I'm just gonna switch to EX kernel, it was just one tap to switch with auto flash.
[BetterBatteryStats] DB126:
BBS reports device was awake for <10 min over a 9 hour period yet lost nearly 5%/hr while idle (supposedly in deep sleep). Something does not resonate as performance does not match metrics. Thinking BBS isn't ready for Android 9.x. Probably best to use Android's native battery monitoring tools for now.
[BetterBatteryStats] peterlee928:
for whatever its worth to other folks, the bbs beta version from google play store seems to still work ok for me. im on a pixel 2xl, stock rom, rooted via magisk unofficial beta, no custom kernels.
[BetterBatteryStats] Jess182:
Hello guys, im new here, where can i download last build? apks from second post are the last (i mean "betterbatterystats_xdaedition_debug_2.3-248.apk" is the last build ?

Thanks and Cheers
[BetterBatteryStats] RASTAVIPER:
Nope.

2.4 is the latest and u should register to download from a specific site according to the instructions
[BetterBatteryStats] murti52:
Hi I wanted to ask if there is any problem with the app in oxygen os.? I am using 3T latest stable 5.0.5 and everytime I open the app, the stats stays on unplugged.. even if I reboot, it stays on unplugged.. tried clearing and reinstalling the app. Didn't helped. Using latest beta from hockey app.

Thanks :)
[BetterBatteryStats] peterlee928:
for whatever its worth, the bbs beta version from google play store works ok for me. im on a pixel 2xl, stock rom, rooted via magisk unofficial beta, no custom kernels.
[BetterBatteryStats] strongst:
I'm using not the latest app and on oneplus-5 ob16 or whatever rom on this device before its working as expected
[BetterBatteryStats] murti52:
Which version of the app ..?

---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------

I suspect it's because of oxygen os.. I'll try the beta from the Play Store though.. to be sure of it. Thanks :)
[BetterBatteryStats] strongst:
2.3-248 but also older ones are working
[BetterBatteryStats] buffal0b1ll:
Clean flashed yesterday. Back down to 0.7% idle drain....for now. Avoiding installing any battery stats apps on Pie for now too. Gonna try to let native do it's thing.
[BetterBatteryStats] RomainD2:
Hi!

I am trying to understand why my Xiaomi Redmi 3S with Resurection Remix ROM is always awake when the screen is off!

During lunch, I start a custom reference on BetterBatteryStats and I have obtained this :

I really don't understand because under Process or Alarm, everything seems normal. I have upload the stat files here :

https://drive.google.com/file/d/13rIst52CP4H5Yapwm53WGAb41qRm4A7E/view?usp=sharing

https://drive.google.com/file/d/1e4DRolaqEDD5oZBi4Iqyx1JCHf9DE9A7/view?usp=sharing

https://drive.google.com/file/d/1DDq71yNkCejmG2jkMuChhi_Z97lQtsPm/view?usp=sharing

But I don't know how to analyse them!

Do you have an idea ?

Thanks!

---------- Post added at 07:19 PM ---------- Previous post was at 07:19 PM ----------

Hi!

I am trying to understand why my Xiaomi Redmi 3S with Resurection Remix ROM is always awake when the screen is off!

During lunch, I start a custom reference on BetterBatteryStats and I have obtained this :

I really don't understand because under Process or Alarm, everything seems normal. I have upload the stat files here :

https://drive.google.com/file/d/13rIst52CP4H5Yapwm53WGAb41qRm4A7E/view?usp=sharing

https://drive.google.com/file/d/1e4DRolaqEDD5oZBi4Iqyx1JCHf9DE9A7/view?usp=sharing

https://drive.google.com/file/d/1DDq71yNkCejmG2jkMuChhi_Z97lQtsPm/view?usp=sharing

But I don't know how to analyse them!

Do you have an idea ?

Thanks!
[BetterBatteryStats] peterlee928:
your idle dumpfile is for 1 hour and change. needs to be at least 6 hrs. see linked post below for instructions on how to do a proper idle dumpfile :good:

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] TNSMANI:
peterlee928 is right. Do as he says.

Curiosity made me look at your dump file. Wifi is your main issue as per this dump, though you may have other offenders which could be only seen with a proper dump.

The funny thing is, while your wifi is on and running all the time, all your downloads happened on mobile data and not on wifi. So wifi connectivity is the issue. This is confirmed by the kernel wakelocks related to wifi. I believe this is the wifi at your work place. So you may not have any control over it. To confirm, switch off the wifi on your phone and take a dump with mobile data on. I am sure that your drain would reduce drastically.

For the rest, follow peterlee928's instructions.
[BetterBatteryStats] RomainD2:
Well done! I didn't understand why it was always when I was at work!

I think it is trying to connect at the wifi guest.

However I am in hollydays so I can't follow peterlee928's instructions.

Is there is another way to avoid that other than tasker ?

Thanks
[BetterBatteryStats] anyone23:
Edit: Please delete this post. I will post again in a few days...

Idle drain was a bit higher than usual duo to network outage...
[BetterBatteryStats] Oswald Boelcke:
Unable to open the attachment (on two different browsers)
[BetterBatteryStats] Schroeder09:
Does anyone have this working on Android 9?
[BetterBatteryStats] strongst:
Was mentioned that it works
[BetterBatteryStats] swallowingled:
It's working for me on a stock Pixel 2XL, not rooted.
[BetterBatteryStats] Schroeder09:
I just had battery saver mode enabled. It's working fine now! Thanks guys.
[BetterBatteryStats] B00ze64:
Thanks for this, I had the same problem, 30,000 alarms daily, with 10,000 associated WakeLocks.

Opened issue on GitHub: https://github.com/iboalali/sysnotifsnooze/issues/35

I think this might be interaction between SysNotifySnooze and some other App, because SysNotifySnooze was working fine for a time, and then I started installing tons of things and suddenly the phone would not sleep...

Regards,
[BetterBatteryStats] Gamesiarz:
Hello,

Could you tell me what are these two readings at "network" tab:

0 (Wifi) and 0 (Mobile)

I have disabled every setting related to syncing but my android os is keep sending unknown data... Note 4, 910c
[BetterBatteryStats] JonasSavimbi:
Hi guys,

I need help please.

I'm on OP5 running oxygen os 5. 1.5 unrooted.

Bbs isn't working as expected as you can see from the screenshot... Not refreshing when unplugged and showing some weird wakelock descriptions.
[BetterBatteryStats] Oswald Boelcke:
The "0" in front of "WiFi" or "Mobile" is usually the UID of the connected process. Even if synchronisation is disabled doesn't mean that your device is not transmitting or "calling home". To avoid latter (if avoidable at all) that requires other actions, and by utilisation of tools like Network Log (from Google PS; halted for 3 years now) or Net Monitor (on F-Droid; seems to be in active development at the University of Darmstadt, Germany) you can examine what is calling where.

Did you comply with the procedure as described in post #4 ("Running BBS on non-rooted devices")?
[BetterBatteryStats] JonasSavimbi:
Yes I did, and it worked fine on the first usage... But since I've charged the phone this happened :\
[BetterBatteryStats] Oswald Boelcke:
Then I suggest you provide an dumpfile and a logcat. A screenshot of the advanced settings if the required permissions are granted might be useful, too. Is BBS not battery optimised? Which version of BBS are we talking about?
[BetterBatteryStats] JonasSavimbi:
I've forced close the app and restarted. Aparently it has worked so far.

I'll check when I recharge to 100% again if the stats reset. The version of BBS is 2.3-247.
[BetterBatteryStats] Oswald Boelcke:
In any case, I suggest to at least update to BBS_xdaedition_debug_2.3-248 available at post #2, or to join the beta programme here (link also taken from post #2). At least to me personally it doesn't make any sense to use an outdated version and to report then something as a bug or missing feature etc.

BTW: It's good tradition to hit the Thanks button (always at lower right corner, or :good:if on XDA labs) of the OP and the following posts by the OP in order to salute the dev for a great job well done.
[BetterBatteryStats] JonasSavimbi:
I've bought the app from the Google Playstore and it shows me as up to date... I'll test the beta version you advise me to. Will I have to do some adb commands or the ones that I've did previously will be enough?

Thanks a lot for your help and sorry for not having thanked before.
[BetterBatteryStats] Oswald Boelcke:
I personally don't mind about the thanks i.e. you can retrieve the one you dedicated to me if you're running out of your daily eight ones. For me, the thanks to the developer was most important...

I don't know how often Sven updates the Google repo or his policy when to upload a specific version there. Anyhow, the one from post #2 is running very well - at least for me; however rooted device. And in this thread I read that guys using the betas from the linked location are also very happy.

And I apologise not to know if the adb commands must again be executed. I've never been on an unrooted device - no own experiences.
[BetterBatteryStats] JonasSavimbi:
No need to be sarcastic ;) At least it wasn't my intention when I thanked you, because I do appreciate the help. I'm sorry if I haven't explained myself correctly.
[BetterBatteryStats] Oswald Boelcke:
I apologise very much and sincerely. I wasn't sarcastic and never intended that it has obviously sounded that way. Usually, I try my very best to express myself in the best manner using English, a foreign language. I'm regularly at XDA to help as much as possible and within my personal limitations - and I never offend anybody or try to sound sarcastic. Please accept my serious apology. And you certainly expressed yourself absolutely correctly. It was and it is my bad.

EDIT: Whoever the moderator was (maybe even @

Wood Man

) thanks very much for cleaning the thread and the respective posts. I wasn't sure if I should report but as the thread was cleaned, I assume that my understanding of American English (or let's call it slang) wasn't too wrong. Good to see that mods always have a permanent look into their dedicated area of responsibility.
[BetterBatteryStats] MrRob0t:
Mind sharing your 'prefer a 'lite' touch on Android 6+ which yields roughly the same battery endurance profile'?
[BetterBatteryStats] DB126:
In general means not messing with obscure crap that isn't accessible via the normal Android UI. Select your app portfolio wisely, let native doze do its thing and enjoy your device instead of over managing it. Occasionally stronger actions are needed to rein in a misbehaving app for which no suitable alternative exists. Those situations are best handled on a case by case basis.
[BetterBatteryStats] nola mike:
After a while (not sure what triggers it), the phone doesn't want to sleep. Hopefully this is the correct dump file. Looks like pretty good battery drain (0.4%/hr) despite not going into deep sleep. Only thing that jumped out at me was the "significant motion" sensor. The phone was sitting on a table for the duration of the measurement. Any suggestions?
[BetterBatteryStats] DB126:
For what? 0.4%/hr average idle battery drain is excellent. Deep Sleep is simply a label someone decided to apply when a selected suite of dials are aligned in a particular way. One of your 'dials' missed role call. Meh. The true litmus test is power consumption and device stability.

Modern devices, kernels and ROMs idle efficiently at low frequencies while maintaining connectivity and responsiveness. Enjoy the benefits; don't sweat the details.
[BetterBatteryStats] anyone23:
I have very high idle drain (3.x% - 5.x%/hour) despite having a very clean system without even Gapps installed.

Can someone look at my idle file and tell me what's wrong with my device?

It's an OP3 with LineageOS 15.1 and latest firmware and aside from stuff like Adaway the system isn't modified.

(The files are in 2 parts as I was quickly checking the phone for a minute)
[BetterBatteryStats] DB126:
Device sleep/wake ratio is reasonable for Android 8.x in both logs; something else is wrong. Dirty/failing hardware sensors, unoptimized kernel, bad battery.

"the system isn't modified."

Huh? LOS 15, no GAaps, potentially a tweaked kernel that came along for the ride. Yep - sounds unmodified to me.

Restore stock and benchmark. Me thinks your problem will go away.
[BetterBatteryStats] anyone23:
Thank you for your help.

I have also noticed that if I use my Vodafone sim card (3G only) despite only a average - good connection I have only 1.x% battery drain. As soon as I add a t-mobile sim card (be it a 3G only or 4G card) with great connection and data disabled I have 3.x% - 5.x% battery drain but I just can't figure out why. As you can see in the logs the connection quality is always close to perfect.

I will try it again with a clean installation of LineageOS.
[BetterBatteryStats] DB126:
Think you have identified the culprit. Suggest restoring stock to benchmark vs a custom ROM. If you go the latter route check your device forum for similar issues. Really depends how well the ROM maintainer packaged and optimized core Lineage for your device. Good luck.
[BetterBatteryStats] DiamondJohn:
I have taken a log after about 5hrs, and although the CPU sits in DeepSleep nearly all the time, the device does not appear to be in Doze mode. The battery just goes down at 3.8% / hour :mad:

Another confusing thing is that when the battery level drops below about 50 or 40%, the device will enter doze mode and the battery stats go flat. I tried turning on extreme power saving manually (I am running crDroid Oreo) and that didnt help. The battery just goes down.

My log thus far can be found at https://www.hastebin.com/elusenohex.cpp, and I am hoping someone will be able to tell me what/why my battery is being drained.
[BetterBatteryStats] TNSMANI:
K9 mail is a drainer for you. Disable that and take a dump to check. If confirmed, try to change its settings or go for another mail client.

Network statistics is not populated in both the dumps. Despite having a great signal, I have a doubt that your wifi and data alternate (this can be confirmed by the Network stats) increasing consumption. The kernel wakelocks is consistent with this scenario. Are there any other devices connected to the same router? Switch them off and take a dump to check.

These observations are independent of Davey126's and I have a suspicion that they will ultimately prevail:fingers-crossed::mad:

---------- Post added at 02:38 PM ---------- Previous post was at 02:21 PM ----------

Don't go for a log in BBS. Save the Dumpfile and attach it here. It has to be an idle dump for atleast 6+ hours. To know how to do it, search this thread.
[BetterBatteryStats] MrRob0t:
Heh, yep, to each their own.

Unfortunately for me, I don't get the solid results by not "messing with obscure crap that isn't accessible via the normal Android UI". This is half the fun of a rooted device as well.. taking 5 minutes to "over managing" the device isn't that big of a deal. Also, this is what backups are for. :cool:

Doze is still doing its thing, but for me, I prefer to get the best out of my phone, and deeper actions are needed to get under 0.5% idle. Otherwise I'm draining around 1%.

Thanks. :good:
[BetterBatteryStats] DB126:
Ok - I'll bite. Outline the steps needed to drop idle consumption to miserly levels in 5 minutes. I must have missed that chapter.

Let's assume your device is idle 14 hrs/day:

- 6 hrs charging (eg: overnight)

- 4 hrs active use (screen on)

- 14 hr idle (untethered; screen off)

Let's further assume you can actually drive idle drain down from 1.0%/hr to 0.5%/hr (avg) without compromising device stability or functionality. Net savings: ~7% of overall battery capacity or roughly 30 min of screen on time. That would be worth considering if the effort was low. I suspect far more extensive tweaking is involved to get those results.

Granted, those who have copious unstructured time and an elevated geek coefficient love this stuff. In my simple world hand held gizmos serve a functional purpose. Consuming scarce resources for marginal benefits (not to mention unwanted side effects) doesn't rank. I will invest time to quell a bad actor when no other options exist ... and usually win that game. Those situations are few and far between when "wants" and "needs" are appropriately segregated.

As you said, to each their own. Enjoy your gizmo.