yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] appman1234:
Thanks for your kind response. Attached please find the BBS log for your review. Many thanks!

Edit1: Just realize that I did not strictly follow the procedure for BBS log listed in 1st post. Please let me know if I need to do it again. Thanks.

Edit2: BBS log deleted.
[BetterBatteryStats] TNSMANI:
Yes, you are right. The dump file has to be saved within seconds of unlocking the scree. In your case, it was after 4 minutes. The idle status stats would have been polluted by this.

Please try again keeping the screen on time as less as possible.
[BetterBatteryStats] scorpiuz:
Maybe this option will help.

Delete the app.

Turn off verify apps over USB in developer options.

Install the app and grant permissions over ADB again.

I have s21 ultra One UI 5.1-BBS,Gsam now work fine.
[BetterBatteryStats] appman1234:
A new BBS log created and attached for review and advice.

Thank you!
[BetterBatteryStats] TNSMANI:
Your phone was awake the entire time as you yourself stated. Dumpstate wakelock was an issue but I am not able to locate anything specific connected to it.

You have way too many apps installed, location/scanning enabled, watch connected etc all of which contribute. I am also perplexed by the entries under Network. Most of the entries are double, once via wifi and second time via mobile data. I have never seen anything like it before.

Your options seem limited. Factory reset the phone after backing up important data and do not restore any apps/app data. Save another dump file. If everything is ok, start installing apps one by one and configuring them manually. After installing a set of apps, check with another dump file and if things are ok, continue to install the apps. Check the behaviour after every set of apps are installed and when you find that the phone starts to be awake all the time, uninstall the last set of apps and install one by one, each time checking via BBS dump file.

Or go for another ROM if available.

Any further insights from others are welcome.
[BetterBatteryStats] appman1234:
Thanks for your analysis and I totally agree with them.

According to battery stats of Franco Kernel Manager, the idle drain is about 2% per hour which is not too much for me. I will wait and see if future rom update can help. Or, if idle drain is worsen further, I think I will do the steps you suggested. Thanks again!

BTW I installed more than 220 apps :LOL:
[BetterBatteryStats] nortuzar:
wow that easy is the solution? Will try and inform. Thanks
[BetterBatteryStats] aadeshiscool:
Uh weird it crashes for me. can you tell which version are you using?
[BetterBatteryStats] scorpiuz:
Yes, after a few reboots it crashes again(
[BetterBatteryStats] aadeshiscool:
Does gsam work in recording the wakelocks? Or does it also crash or doesn't record the wakelocks?
[BetterBatteryStats] scorpiuz:
No, it doesn’t work (. I install bbs and Gsam, everything works great, but if I do a few reboots, the application doesn’t work, it crashes at startup. I still don’t understand how to win it (
[BetterBatteryStats] Watanabe_You:
Can someone help check if anything's put of the ordinary here?
[BetterBatteryStats] TNSMANI:
The following stand out:

Location/scanning is on and resulted in these Alarms:

Heart Monitor caused these Alarms:

Instagram Alarms:

Apart from these, your mobile signal was patchy and not stable or great. Usually patchy mobile signal consumes a lot of battery.
[BetterBatteryStats] Dave^:
Does anyone else get occasional "poll_reboot_readiness" alarm wakelocks?

I've had 90 of them in the past 8hrs, battery has dropped 0.9% an hour overnight as opposed to the usual 0.5%.

Rebooting stops them happening for a few days/weeks.

Google shows 0 search results, but I've been getting them for quite a while.

I'm not rooted and I use Tasker quite extensively, so each time I reboot I have to hook my phone up to my laptop to enable adb over WiFi.
[BetterBatteryStats] kelltech:
My device suddenly drains battery, typical recently to lose 20%-30% overnight while not using it when it would lose maybe 6% before.

I'm unsure if it's an app or system error or battery failing and I would appreciate any help looking at the dumpfile.
[BetterBatteryStats] TNSMANI:
As I said in the other thread, please read the first page of this thread on how to generate an idle dump file and post it here. Simply saying your phone drains more doesn't give any insight to such behaviour. You also will have to specify your device, model, ROM, kernel (if custom), version etc.
[BetterBatteryStats] kelltech:
Hello,

After following the instructions to ask for help with a dumpfile, I am prepared to share that file and my situation.

Device:

Oneplus 6

LineageOS+MicroG, (LineageOS version 20-20230308)

Rooted, Magisk

Issue:

After updating my phone from LineageOS 19 Android 12 to LOS 20 Android 13, I experienced a sudden and very noticeable decline in battery life. The phone would typically only need a charge every 1-1.5 days before the update, currently my device needs a charge twice a day on average.

I am trying to determine if my phone has a dying battery or if it's an app problem, or perhaps an OS issue.

I have so far allowed the phone to sit overnight in safemode. In this case, I only lost a few percent of battery. In normal mode, it loses 20% overnight. I also uninstalled all apps that I don't use on a regular basis. Lastly, I followed the instructions in this post step by step to generate a useful dumpfile that may hopefully point me in the right direction of whether to try a system wipe, revert to LOS19, or if I need a new phone.

Thank you for any assistance.
[BetterBatteryStats] TNSMANI:
@kelltech

It is better if the dump doesn't start from 100%. If you have already charged it to the max, use it till it reaches ~85% and then start the dump. You can even start from a still lower level. I think that this is in one of the other posts on page 1.

While saving the dump, please ensure that you save it immediately on unlocking the screen ie. within seconds before doing anything else on the phone. Then please post the dump file here or if you have difficulty in attaching it here, please post it elsewhere and provide a link.
[BetterBatteryStats] kelltech:
Very sorry that I can't seem to get it right. This is what I did:

Right now my phone is ~35%. Should I then charge to 100%, use until ~85% instead of the ~95%, let it sleep for 6+ hours, then immediately pull the dump?
[BetterBatteryStats] Oswald Boelcke:
I usually start around 95%. Attached are two recent idle dumps as examples (sorry, I'd to zip them. They didn't upload as txt-files as usual).
[BetterBatteryStats] kelltech:
I wonder if I completely missed somethig...did my dumpfile not upload? I don't see it now that I'm looking at my post.
[BetterBatteryStats] Oswald Boelcke:
Might be. Did you try to upload as txt? It was already quite often reported in this thread that some dumps as txt look like they uploaded but they didn't "stick". Nobody really knows why. We had the administrators engaged but the issue could be solved. There're must be some "content" in some dumps that the filter prevents them to be actually uploaded. If you experience that your txt file didn't upload, just zip. That always works.
[BetterBatteryStats] kelltech:
Trying again with the dump as zip. 🙏
[BetterBatteryStats] Oswald Boelcke:
First, that's a good idle dump.

Second, I've no clue about LOS 19/Android 12 or LOS 20/Android 13 (or Oneplus). I'm a Samsung user and my device is still on LOS 16.0 and I will never "upgrade" to anything above.

But what catches my eyes are Signal and Telegram in these lines:

org.telegram.messenger (org.telegram.messenger.Telegram FOSS): Uid: 10224 Sys: 6 h 30 m 49 s Us: 4 h 48 m 43 s Starts: 0

org.thoughtcrime.securesms (): Wakeups: 590 (1.4 / min)

Like you I'm also using both applications, and I'm also GApps-free and with µG. But if you look at my dumps, both applications behave differently.

Maybe somebody else has more insight into an OP with your OS?
[BetterBatteryStats] Schroeder09:
I've been wishing there was a line item that explicitly listed "idle drain." I think I've come to the realization that idle drain is simply just called something else in BBS: "awake." The awake percentage is what is often colloquially called "idle drain." As an example, 15% "awake" time is 15% loss in battery while the phone was not in use? Will playing audio with the screen off fall into this "awake" category?

If I am wrong, how *do* I determine idle drain in BBS?

Phone idle in my phone native battery tracker is listing 20% drain on the battery with the time of idle basically (not perfectly) equalling the BBS (time off charger)-(awake time). The times are the same but the percentage of drain is not. BBS is 4% less. The native phone settings battery usage lists the phone using 16% for mobile network drain. The screen usage is listed as having drained the battery 11% over 1hr 50 minutes while BBS says SOT is 2hr 30 minutes with 23.4% drain. Are the BBS figures % of time versus % of battery? I want to see % of battery. Am I interpreting this correctly? Why doesn't the native pixel battery tracker jive more closely with BBS? I'd expect to only see a 1-2% difference in battery usage stats and similar discrepancies in time used.
[BetterBatteryStats] TNSMANI:
Yes, this is the first time I am seeing the BBS file on your post and as my colleague said, the file is ok.

You have mobile signal issues having only moderate and good signal, never great signal:

Usually, this drains a lot of battery. How old is the battery? Next time while recording a dump file, choose a place where you have a better signal, if possible.

Kernel Wakelocks:

Please check THIS thread as to what it is and also search on Google.

Then as my colleague said above,

This is huge. I don't know how to control this. May be uninstall and reinstall? Please search on Google too. Signal also has issues..

Do you have many widgets?

Either reduce the number of widgets or the number of times they refresh.

And you were on mobile data, not wifi. So all background uploads and downloads happened on mobile data. Coupled with the weak signal, this is sure to drain battery fast. Enable wifi next time.

Sensors:

Disable this feature when you next check with a dump file.

That is all I could see.
[BetterBatteryStats] TNSMANI:
I have taken the following from an idle dump file provided by another user:

This is the idle drain.
[BetterBatteryStats] kelltech:
Thank you, I shall remember to only upload zip files. :)

Unless there's an underlying problem with the hardware, I'm on T-Mobile near a city and this is probably as good as I'm going to get at home unfortunately.

I bought the device used and could only speculate the battery is up to 5 years old, based on OnePlus 6 released in 2018.

After searching for Signal issues, I can only find that there are indeed issues. I can submit a bug to Signal, then uninstall/reinstall and see if something improves.

I don't use many widgets, only 3. Clock, open tasks, and search in Mull browser. I removed open tasks to see if any improvement.

It seems like giving attention to Signal app is a good place to start, remain on wifi at home/work, and if there aren't noticeable improvements then I could factory reset or adb wipe and fresh install LineageOS.

And if it still isn't good then a new device 😂
[BetterBatteryStats] TNSMANI:
Mobile signal issues can't be wished away unless you are prepared to switch providers.

Five years is a very reasonable time for the battery. Usually it is about 3 years.

That looks like a plan. I am sure a factory reset or clean flash coupled with wifi will definitely help. How much it will help, I don't know.

Best wishes on your endeavours!
[BetterBatteryStats] Zergrinch:
I'm having issues with this app. Specifically, it's not gathering any data. All it would say is "BatteryInfo Service could not be contacted." I have checked the app permissions, and granted permissions for everything: "Files", "Music and audio", "Nearby devices", "Network", "Photos and videos", "Sensors", "Notifications", and "Phones". I have also rebooted a few times, but so far no dice.

I'm running the custom SparkOS ROM (Android 13) on a Xiaomi Mi A3.
[BetterBatteryStats] redhonker:
Hi,

I'm probably reporting something already reported. Search result is a bit difficult find relevant posts.

Samsung Galaxy S21 with Android 13

BBB will do either

Say "no stats have been collected yet"

Or

Crash (after a flash of the screen with the above message).

All permission has been granted via ADB

What could be done?

Thanks
[BetterBatteryStats] lee99:
Hi all.

I am using on my redmi 7a (pine) lineage os 20 (lineage-20.0-20230320-UNOFFICIAL-0xCAFEBABE-Mi439) and i have from time to time some draining problems.

Thanks in advance.
[BetterBatteryStats] TNSMANI:
Did you switch off both mobile data and wifi? There is something wrong with the dump file. Your phone is identified both as a Redmi 7A as well as a OnePlus 7A Pro. Though the battery drain is shown as 3.3% per hour, nothing shows up in the dump file that can be a reason for that kind of drain. The entire time was spent by the CPU on a very high 2.02 GHZ but there are no clues in the dump file for this high rate.

May be you can attempt to save another idle dump file after going into recovery and clearing cache and Dalvik cache and after enabling both mobile data and wifi. But if we don't get any details (as in the present case), you may have to factory reset or clean flash the same ROM. Please remember to backup before attempting this.
[BetterBatteryStats] Oswald Boelcke:
@lee99 Besides what my esteemed team mate said, are you using this file manager?

X-plore File Manager – Apps bei Google Play

X-Plore ist ein Dateimanager mit zwei Fenstern mit Strukturansicht, LAN / Root / Clouds und mehr.

play.google.com

In your idle dump, line 81 scares me slightly:

com.lonelycatgames.Xplore (com.lonelycatgames.Xplore.X-plore): Uid: 10175 Sys: 4 d 4 h 9 m 32 s Us: Starts: 0

It seems to me that this file manager keeps your device awake and let the CPU run at high level:

If you don't depend on that file manager, consider to uninstall it and e.g. to use MiXplorer, which I use with full satisfaction for several years. And check your battery drainage again after uninstallation.

[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)

[APP][2.2+] MiXplorer (full-featured file manager) Hello everyone! My name is Hootan. I work on XDA in my free time and this file explorer is my favorite Android project! MiXplorer mix of explorers (SD, FTP, Lan, Cloud and other storage...

xdaforums.com
[BetterBatteryStats] lee99:
Hi. Yes I was using airplane mode. Yesterday I updated lineage os 20 unofficial to newer version (01.04.2023).

On dump file i attached check sensors section. I wonder that sensor this is? Maybe it is a light sensor what causing this draining issues? I don't know... I am guessing.
[BetterBatteryStats] lee99:
Hi. Yes I am using Xplore and I must say i have/had problems with draining issues on my Redmi note 10 pro with MIUI 14. I don't remember this issue on MIUI 13 with android 12 so I think this must be android 13 related.

Xplore file manager sometimes don't start at all but after full reboot it is working just fine.

I have also solid and root explorer pro on this phone.
[BetterBatteryStats] illetyus:
I am very disappointed of this App's support on S23 Ultra.

Although i did all the ADB permissions, i am not getting any readings..

What is "Fall Back to Since Boot"?

On the other hand, my Android 12 Galaxy M51 device seems to be working perfectly.
[BetterBatteryStats] shaggyskunk:
If you are unhappy - Blame Google not the Dev!

@chamonix has been trying everything to get it working on Android 13 / One UI V5.0/5.1.

Google has imposed additional restrictions on how apps can access your device.
[BetterBatteryStats] guhvanoh:
Isn't the blame more Samsung's than Google's since BBS works fine on other manufacturer's fones than on Samsung's?
[BetterBatteryStats] TNSMANI:
The only sensor showing some drain is this:

This does not relate to light sensor. This is waiting to detect motion. I don't think that this will cause such a huge drain. If in doubt, disable the sensors using the native setting or, if not available natively, using some app from the Play Store. Or, disable motion sensing ie. disable whatever you have enabled in Settings like Pickup etc.
[BetterBatteryStats] lee99:
I made another dump but I made a mistake and instead of exporting uplugged I copied from the last reboot. The file was generated on lineage-20.0-20230401-UNOFFICIAL-0xCAFEBABE-Mi439.

Which specific app(s) do you recommend?
[BetterBatteryStats] TNSMANI:
The stats are not ok. It doesn't show the screen off time or the screen on time. Again you seem to be on airplane mode. Please follow my earlier post and save an idle dump.

If you are talking about an app to disable sensors, I have no idea since I have the ability in the ROM itself.
[BetterBatteryStats] illetyus:
So you are saying i paid for not working app? Okay...
[BetterBatteryStats] shaggyskunk:
XDA version is free - I'm not sure if it's even a paid app on the Play Store.

When did you install it on your device anyway?
[BetterBatteryStats] illetyus:
I installed it 2 days ago on my S23 Ultra. Got all the ADB permissions.. No luck. (Android 13, ONEUI 5.1)

... Otherside my Galaxy M51 works fine from the 1st moment with ADB permissions. (Android 12, ONEUI 5.0)
[BetterBatteryStats] shaggyskunk:
So you're saying that you might have paid for the app - and it's working on one of your devices - Yet you are complaining that it isn't working properly on another device.. I see....
[BetterBatteryStats] h4lik:
Thank you, @chamonix for your great app.
[BetterBatteryStats] IronTechmonkey:
That's a good point to which I can testify from my Motorola devices but... although there are OEM variations in implementation and in the timing of implementation, it is usually Google who is foisting these permissions and other restrictions upon us. Additionally the OEM implementations can vary across similar devices on the same Android version so, IMO yes the OEMs may be culpable in some situations but Google makes that so.
[BetterBatteryStats] steve197635:
I installed it on my S23 Ultra. Got all the ADB permissions.. i not works :(
[BetterBatteryStats] shaggyskunk:
Yeah - There seems to be an issue with One UI V5.0/5.1.

The Dev has tried to resolve the issue - But Google has imposed new restrictions on what apps can access on your device.

It may or may not be fixable?

Definitely NOT @chamonix's fault!
[BetterBatteryStats] WhoIsJohnGalt1979:
I think I took a data dump right after I woke up to measure idle. Any one care to take a dig at the stars and share some observations. Would appreciate.
[BetterBatteryStats] Morpheus68:
Colleagues, good day!

I have 2 almost identical Xiaomi Redmi Note 11 devices on hand - black with 6GB of RAM and blue with 4GB of RAM.

There are the same firmware and approximately the same composition of applications.

But there are battery drain issues:

Blue 4GB behaves well - the battery discharge after fast charging from the native PSU is normal, during the night when all consumers are turned off, except for cellular communications, it gives ~ 0.1% per hour.

But with black 6GB there are anomalies. If you charge with a weak PSU that does not include fast charging, the behavior is similar to the blue model - low consumption ~ 0.1% per hour..

If the black one is charged with a powerful PSU (for example, stock), which includes fast charging, then there is a very fast battery discharge after charging ~ 1% per hour, also with all services disabled.

If the black one is rebooted after fast charging, then the discharge returns to normal and corresponds to ~ 0.1% per hour.

The problem is repeated on several devices - in the profile topic on 4PDA, users complain a lot about the problem and solve everything by rebooting the device after fast charging.

I briefly looked at the conclusions from the BBS - there is a suspicion of 2 processes that appear after fast charging:

irq/205-type_c_ (0): Uid: 0 Sys: 2 h 20 m 26 s Us: Starts: 0
tcpc_timer_type (0): Uid: 0 Sys: 1 h 9 m 32 s Us: Starts: 0

Who can tell me what can be done about it?
[BetterBatteryStats] TNSMANI:
File not attached. Try zipping it before attaching.
[BetterBatteryStats] TNSMANI:
USB Type-C Port Controller (TCPC) is what I get from a Google search. I don't know what it is. May be a search will help you understand. You can check this too:
[BetterBatteryStats] WhoIsJohnGalt1979:
Thank you! I did that now, appreciate the tip.
[BetterBatteryStats] TNSMANI:
BT seems to be creating issues. If you have enabled it or scanning, please disable and check. Likewise for Location and scanning.

Please switch off your wifi router for a minute and then restart it.

A lot of background uploads and downloads happened and it might have increased the drain. But it is not likely to happen always. May be the next dump file will show a different result.

A lot of sensor activity took place via various apps. If the ROM has an option to disable sensors, try that during the next dump file or else look for an app in the Play Store.
[BetterBatteryStats] WhoIsJohnGalt1979:
Thank you for the analysis. I have my pixel watch connected by Bluetooth all the time . It helps me get useful information about my sleep pattern. Sensors could be the ones which detects oxygen saturation, heart rate, snoring etc as I didn't touch the phone at all for the duration of the test. Thank you again, this is good. From what I can see there are no rogue drainers, all expected ones. Oh another device connected through Bluetooth would be my blood sugar monitor which is also connected all the time to my phone. Attached is tonight's logs.
[BetterBatteryStats] steve197635:
i love this app. but can u fix it for the S23 Ultra? :-)))
[BetterBatteryStats] orifori:
App is not working correctly on rooted Android 13 (Noble rom). Stats are shown only for Alarms and CPU states (for everything else - No stats have been collected yet). All root permission granted but the app crashes frequently. Same results described above with app versions 2.5-314, 3.3-504 and 3.3.1-522.

Some advice of how to make it work please?
[BetterBatteryStats] skiely666:
Getting this on Android 14 beta1.
[BetterBatteryStats] TNSMANI:
You haven't specified your device. If it is Samsung, even on Android 13 BBS doesn't run correctly in most devices. To expect it to rum on Android 14 is premature for any device.

Blame Samsung & Google :mad:
[BetterBatteryStats] skiely666:
A14 beta is only for pixels. P6.

Did I post on the wrong site by accident or is this xda?
[BetterBatteryStats] Oswald Boelcke:
Mam, Sir! What do you mean by this? This is indeed XDA, and it might be worth to occasionally review the XDA Forum Rules! Thanks for your cooperation and efforts.

Respectfully

Oswald Boelcke

Senior Moderator
[BetterBatteryStats] skiely666:
What I mean by this is you would think being XDA and being in an Android app thread that a person replying to a post asking for information would know this well known information. I didn't ask a question in my op I was just bringing it to the developers attention.

My reply was sarcastic. I don't think sarcasm is against forum rules is it?
[BetterBatteryStats] V0latyle:
As long as you aren't being rude.

XDA has members from the world over, so not everyone may grasp the more subtle nuances of the English language.
[BetterBatteryStats] kleoxy:
Hello everyone,

can someone help me please analyse the dump file?

I have a battery drain while in sleep mode and I can't check myself what processes should I switch off through ADB. The phone is showing me the drain in "Battery saver" setting as "Other", so I can't see exactly what proccess is draining the battery...

Thanks in advance!
[BetterBatteryStats] TNSMANI:
You seem to be on airplane mode with BT on for your watch:

Location/scanning also seems to be on. These alone jump out. As a test, disconnect your watch, disable BT, Location/scanning for a night and save another idle dump.

Apart from these, various sensors like sar_sensor, pickup etc are also causing drain but I think once your watch and its associated elements are taken care of, the sensors also will quieten down.