yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Lughnasadh:
Just updated to QPR2 Beta 1 (Android 13) on my Pixel 7 Pro and just wanted to report that in the app (latest version 3.1-493 from App Center) the "Summary" section is blank (it was working properly on the stable December build of Android 13). The other sections are still working properly (except for the Sensor section, which is blank but has been for me since possibly Android 12 (on my Pixels), can't really remember).

Also, seemingly related, in dump files the "Other Usage" section is blank (the one that contains deep sleep, doze, signal and a couple of other stats). The other sections (except for sensor) are working properly.

FYI, @chamonix
[BetterBatteryStats] V6-Maniac:
@chamonix Just curious, what information do you need from us to solve the issue on Samsung devices.

Not that i'm a great help as my devices (Flip4) aint rooted and not intent to do so as i have to miss a lot of apps which don't function when rooted.

I can post logcat after logcat but don't think it will help.

I would love to help you out but must admit also eager to find my drain issue while the phone is in use.

My finding for now with the 3.1-496 Play store edition.

It for now it doesn't fc but can't go into the Settings, it will fc if i tick Settings.

Also have a error message when going into RAW stats "Battery Info Service coudn't be found"

Every time i go back to the Default stats screen is says "Fall Back to stats ...."

All App permissions are set manualy by ADB.

But still the STATUS says: Failed: inconsistent tx state lenghts
[BetterBatteryStats] Schroeder09:
Is it normal for wakelocks to be this frequent and constant? My p7p is getting 6-9 hr SOT, but it seems like this is bad with wakelocks. There is a lot of Google play services BS.
[BetterBatteryStats] V6-Maniac:
If I where you i would look for anything you use that uses your location.

To me it looks like Playservices is called due to the nlpcollector which is called by apps to get your location.
[BetterBatteryStats] Schroeder09:
I don't have a lot set with the location permission. Tasker only monitors location 2x daily for about an hour. If I try to revoke it from Google or android intelligence services it tells me my device may lose functionality. Will a bunch of stuff break if I set these two to "allow only while in use"?
[BetterBatteryStats] V6-Maniac:
What android version do run?

Android system intelligence is compatible anymore on Android 13, at least PL says so if i search the app there.

I disabled the app.

Google app love to wake your phone to seek nearby devices and your location.

I disabled it as i dont use it on my phone.

Dont know about the vr service but i also disabled it.

Edit:

Tasker looking for location a whole hour?

Why if i may ask?

Thats also a drainer, my Tasker only watches if I'm home or not but my location mode is off.

I have set an ip where Tasker should look for so no location mode needed
[BetterBatteryStats] Schroeder09:
I'm on a13 on a p7p. I didn't install this app so idk how it would have got on here if it weren't included- and compatible - from Google. What does it even do?

I disabled the Vr one prior to you posting this. I assumed it is for gaming. I don't, have never, and never will game on my phone.

I suppose this is a different discussion. I did have a task set up to start autolocation's geofence monitor when a specific cell tower was determined to be near. This would allow for a narrower location monitoring window. It's so wide though because I arrive at work at those different times.
[BetterBatteryStats] Schroeder09:
I'm trying to provide usable analysis data, but I don't seem to have the options described in the directions. Here are the directions from the OP

1.- enable watchdog processing in BBS settings

2.- verify from/to references is checked under custom views

3.- full charge device then let it run down to ~95%

4.- put device to sleep for at least 6 hours (no touchy!)

5.- wake device and launch BBS

6.- adjust from/to references to 'screen off' and 'screen on'

7.- save dumpfile from share menu

8.- post resulting log to this thread (or provide cloud link)

What is step 2 talking about? See my attached pic for this. Do I just need to click this at step 2? There is no "from/to" reference anywhere in the app. Step 6 is similar.
[BetterBatteryStats] V6-Maniac:
Android System Inteligence is a Google component.

Link will tell you more: https://www.pcguide.com/android/guide/android-system-intelligence/

VR has something to do with VR headsets, i don't use one.

But i think your Tasker and specific Autolocation is the culprit if your story is indeed as you described and no other apps are using your location.

I won't go in depth about battery save location options for tasker.

I have it to expect autolocation and Tasker is doing to it's running tasks on specific locations.

But running gps or nearby services as you describe for such a long time is a battery drainer.

But also in de background your location is asked for many, many times by apps/system apps without you even knowing it.

Some are nearby services, weather but also google components asking for it.

I use tasker cell based and WiFi based on static IP (not wifi near) which doesn't need to have the location mode to be ON.

I do use a Watch4 which also (even disabled) is asking a lot of location queries.

Narrowed my battery drain to two possible suspects.

My battery only drains when i'm on the move or outside.

At home (idle) my Flip 4 uses 1% per 3 hours thats overnight with wifi/data on in DND mode.

But didn't disabled any features to make it a dumb phone.

While on the move (train driver) and very light usage i always got home after 12hr work with 50 till 60% left.

When i use the phone little i was glad i could make it home with 10% left just because location mode is ON while nothing is using my location.

Since a couple of days with the same scenario but tasker set to disable location when not driving my car i get home with 70 to 80% left

There for i have now two possible suspects for which i need BBS to prove i'm right.

1. Something is using/asking location while on the move while i don't use the phone.

2. Poor cell reception but can't imagine it has that big of a impact because my previous phone S20FE didn't had this issue.
[BetterBatteryStats] Lughnasadh:
This morning after taking an idle dump I checked and the problem still persisted. However, just now I checked the app and took an idle dump and both the "Summary" section in the app and the "Other Usage" section in the dump were populated. Gremlins, maybe....

I'll keep on eye out...
[BetterBatteryStats] Schroeder09:
Here's my dump file. I did my best to follow the instructions. Is there any indication what's causing all of the wakelocks from play services all of a sudden?
[BetterBatteryStats] TNSMANI:
Your dump file failed to attach (it sometimes happens on XDA). If it fails again, zip it and attach it or upload it somewhere and provide the link.
[BetterBatteryStats] Schroeder09:
There we go. .zip file method seems to work.
[BetterBatteryStats] TNSMANI:
Sorry, you have used the device for about 30 minutes before saving the dump file. Plus the dump file is from 'Unplugged' to 'Screen On'. The instructions are (as available in the first page of this thread), the file has to be saved within seconds of unlocking the screen (the screen on time should be as less as possible, in seconds). The start time should be from about 85%, not from Unplugged. Either set a custom reference for the start time or choose Screen Off as the start point.
[BetterBatteryStats] Schroeder09:
Thank you for the reply I most certainly did not use the phone for 30 minutes after waking. I woke it and exported the dump as quick as I could. I do not believe this took over 5 minutes.

I do appreciate the help, but must admit this is frustrating. A few posts above (#38,713) I asked for specifics on the instructions. No one replied. I'm not saying it's incumbent on you specifically to have replied, but no one did. The "instructions" on the OP are wrong to put it bluntly. I'll explain. Here are the OP dump-file-collection instructions for reference.

1.- enable watchdog processing in BBS settings

2.- verify from/to references is checked under custom views

3.- full charge device then let it run down to ~95%

4.- put device to sleep for at least 6 hours (no touchy!)

5.- wake device and launch BBS

6.- adjust from/to references to 'screen off' and 'screen on'

7.- save dumpfile from share menu

8.- post resulting log to this thread (or provide cloud link)

1.) Enable watchdog processing- I go to BBS settings via the 3-dot menu in the upper RH corner of the app, scroll down and click "settings", scroll down and click "watchdog", and there is no "enable" button. There is an "enable" button under "active monitoring" which is directly under "" watchdog" in the BBS settings menu. For my dump file I assumed this is what the poorly written instructions in the OP meant. If active monitoring is what needs to be enabled, this very first step in the process is wrong in the instructions.

Instruction steps 2-5.) Straightforward and completed without issues.

6.) I guess this step means to simply toggle from "screen off" and then " screen on"? What's this so? As my pics note, there are two unlabeled menus next to each other that each have a " screen off" and " screen on" option in the drop-down menu. I've been using BBS for 5 years and have never known what thes two unlabeled drop-downs do or mean. The picture with the red and yellow doodles addresses this step in the instructions.

Steps 7-8) straightforward. Not sure whats causing time to be logged after the dumpfile was collected though because I most certainly did not use the phone for 30 minutes before collecting and saving the dump file.

Please do excuse my frustration with the shoddy instructions with no included screenshots. I do hope answering these questions helps others in the future too.
[BetterBatteryStats] TheJuve:
Hi, Samsung S21 Ultra here, Android 13 with One UI 5 and latest GSam version (3.45?).

FWIW, Although the first day after the OS upgrade was full of GSam crashes, it seems to have been resolved of its own.

However, I noticed that the "adb shell settings put global hidden_api_policy 1" hack seems to have no effect anymore (I verified it's still "1" after the OS upgrade) - e.g. I can no longer see my work profile's apps in the battery suckers list - is this a known issue?
[BetterBatteryStats] DaOldMan:
Same thing on Samsung S22 Android 13 stable. Any solution to this problem? Better battery stats, latest xda version 3.1.
[BetterBatteryStats] TNSMANI:
In Watchdog, there is an option to be checked and that is 'Reference on unlock'. It may be checked by default, if not you check it. That was what the OP meant.

'Active Monitoring' is definitely not what the OP meant. As the warning says, it is likely to increase the drain, if enabled.

The 'from/to' reference: The so-called unlabeled menu (as you refer to them) on the left is the 'from' and the one on the right is the 'to'. You make the selection there by opening the drop down menus and choosing 'screen off' (or 'custom' if you created a custom reference before you started the dump file) on the left and 'screen on' or 'current' on the right. These are the start and end points of the dump file.

I am not here to defend or support the OP but this is the first time in my about 8 years on this thread that I come across someone saying that he didn't know what the 'unlabeled drop-downs' meant, for five years. In my earlier post I also said to read the first page of this thread, not the first post, since some useful info is available in posts subsequent to the OP.

Whether you used your phone or not before saving the file, that is what BBS is saying. From your attachment:

And we need a file that is saved within seconds of unlocking the phone to give you some useful advice.

One thing I can say for sure from the file that you already attached (irrespective of whether it was saved after 30 minutes of usage or not) is that your mobile signal strength is very poor and that is a huge drainer.

If you are interested in finding out additional info about the drain, please attach a fresh dump file taken according to instructions.
[BetterBatteryStats] TNSMANI:
In this thread we discuss BBS, not GSam. Or did you mean BBS?
[BetterBatteryStats] TheJuve:
Sorry, I thought BBS is just the legacy name for GSam. Is there a more appropriate forum?
[BetterBatteryStats] TNSMANI:
AFAIK there is no dedicated thread for GSam on XDA. Users have been posting about it in the relevant device forum. You may either post in your device forum or post in the Android Q&A forum.
[BetterBatteryStats] the_naturat_com:
Hello. Is there any version that works on S22 Ultra Android 13?
[BetterBatteryStats] DaOldMan:
No one seems to answer. The problem was reported twice. Maybe your third time is the charm 😀?
[BetterBatteryStats] Schroeder09:
Again, I definitely did not use the phone 28 minutes after having let is sit for 6hrs during a day when I would otherwise be using it for the expressed purpose of collecting this file. Could it be that this 28 minutes was from before the dump file was collected? The OP instructions say to charge fully and then drain the phone down to ~95%. That's exactly what I did. I used it for that 100% - 95% window in the morning before starting this file collection process.

Ok. This was checked for the dump file.

Understood. However since the instructions are wrong and there is no "enable" (only the reference check you mentioned) I thought this was it and was required to get the accurate dump. I will disable active monitoring for the next attempt.

See my above thoughts in response to another member here. Could it be the 28 mins of use are from the 100%-95% battery window that the OP instructs users to do before collecting the dump file?

thank you for the detailed explanation of the critical, yet poorly written instructions in the OP. I sincerely appreciate it, and I will attempt once more to get a dump. If the 28mins of use is a problem should I start the file collection immediately after unplugging the phone at 100% and disregard the steps of the instructions that tell us to let it discharge to 95%?

also, can anyone seeing battery life that they're happy with show a screenshot of what the BBS wakelock graph should look like? Mine is basically a solid blue box. Lol. Constant wakelocks.
[BetterBatteryStats] _theluk_:
The problem was reported more than twice and the developer has already acknowledged the issue. He has received log files with error information and wants to try and reproduce/fix.
[BetterBatteryStats] DaOldMan:
Excellent ! Thanks to the developer for his long time support!
[BetterBatteryStats] chamonix:
Unfortunately the only thing I need is time: google is nagging me and I have consumed all my time chasing solutions to avoid BBS (yet again) to be taken down. A release to gplay is on its way and fortunately x-mas is coming and I will take my S8 with me in the holidays, hoping to reproduce the issue. Worst case: I will need to get hands on a device that has the issue if mine fails...
[BetterBatteryStats] V6-Maniac:
I understand but don't let this issue screwing your holidays.

Take your time and take care of your self...
[BetterBatteryStats] the_naturat_com:
The problem is Android 13. On A12, the program worked very well on the S22 Ultra. On Beta A13 it stopped working and now it doesn't work on stable A13.
[BetterBatteryStats] shaggyskunk:
Thanks for the update to BBS 🙇🏼

Take your time & enjoy the Holidays with your family! - Family FIRST! 🎄🕊️

Android & Unfortunately Google Play Zealots will still be there after the Holidays.

Ignore the screen shots until your return, should you be inclined to deal with Google's silliness. ☺️

It's been less than 8 hours since I last Rebooted my S20 Ultra Snapdragon variant running One UI V5.0

Thank You for your PATIENCE & continued Time & Efforts 🙇🏼
[BetterBatteryStats] Wolfcity:
This is my wakelock graph after 12 hours of normal use (no mobile signal today).

Not to be confounded with the usage that is needed for a dumpfile.

(Debloated Xiaomi Mi 9T running Xiaomi.eu A11)
[BetterBatteryStats] Schroeder09:
Thank you.
[BetterBatteryStats] TNSMANI:
So that is your issue. After using it for some time, you let the phone sleep and then saved the dump file. But you chose 'Unplugged' as the 'from' point instead of 'screen off'. Since you used the phone after unplugging, BBS is correctly showing the result (usage of 28+ minutes). It is not an idle dump file. I have noted the wrong start point now in the file you attached earlier.

Do not start either at 100% or 95%. Use your phone after charging upto 100% and start the dump at around 85% or even lower. You can also charge it upto some value between 50% and 85% and start the dump. The point here is not usage after charging but the starting point. This is also stated in one of the posts in the first page.

It is also better to set a custom reference by using the three dot drop-down menu when you are ready to let the phone sleep. Then choose 'custom' from the left menu when you save the file. You can also use 'screen off' in the left menu instead of 'custom'. I always set a custom reference in order to avoid incorrect stats due to screen being switched on for some reason or the other during the night.
[BetterBatteryStats] Schroeder09:
Great. Thanks for the explanation. So here's the modified instructions with what I need to do on this attempt. Correct me where I'm wrong.

1.) enable watchdog processing in BBS settings no such option. Press "watchdog processing" in settings and then check "reference on unlock."

2.) verify from/to references is checked under custom views

3.) full charge device then let it run down to ~95%

5.) Re-ordered here** put device to sleep for at least 6 hours (no touchy!)

6.) Re-ordered here** wake device and launch BBS

4.) Re-ordered here** adjust from/to references to 'screen off' and 'screen on' press 3-dot settings menu and press "set custom ref." Set "from" reference ( LH in-app drop-down menu) to "custom." Set "to" reference (RH in-app drop-down menu) to "screen on"

7.) save dumpfile from share menu

8.) post resulting log to this thread (or provide cloud link)

Is this right? I re-ordered some of the middle steps. If that doesn't need done and the from/to points are to be selected afterward as listed in the OP I can do that. Thanks.
[BetterBatteryStats] TNSMANI:
1 & 2 are ok.

3. Run down to 85% or less.

4 ok but has to be done as step 4 ie. you choose the from to references before letting the phone sleep, if you are going to choose custom.

5 ok but put phone to sleep immediately. 6 ok.

7 ok but before saving, check the from to refrences to ensure they remain at custom & screen on.

8 ok.
[BetterBatteryStats] Roki_100:
A52s running One UI 5/A13, can confirm BBS doesn't work anymore, seems like google changed something
[BetterBatteryStats] paulr24:
I can't seem to get permissions working on my unrooted Pixel 7. I have run the following and get no errors:

adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS

adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP

adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.PACKAGE_USAGE_STATS

When I open BBS I still get:

BATTERY_STATS not granted

STATUS: Failed: Neither user ##### nor current process has android.permission. BATTERY_STATS.

DUMP not granted

PACKAGE_USAGE_STATS not granted

Any ideas?
[BetterBatteryStats] Wolfcity:
Which version of BBS have you installed?

If it's the one from playstore you have to use different commands (without "xdaedition") because it has a different name .
[BetterBatteryStats] Schroeder09:
Here's attempt #2. I'm a little shy of the recommended 6hr logging time, but it's still 5hrs 15mins collected without touching the phone. I've been studying the results for the past 20 minutes. I see lots of android.gms wakelocks, lots of android system alarms, watch of gms alarms, and lots of these seeming to pertain to activity detection based off the wakelocks' names. I've already cleared the data and cache on Google play services, the Google play store, the Google app, and android system intelligence. There has been no change in behavior.

What do I do? I have the app manager app for managing app ops. Do I need to start blocking receivers and senders for Android system and Google play services? Do I need to block receivers as outlined in these links? I still am not crazy about that and don't understand why either the installation of the Pixelfy magisk module or the December update triggered this.

Post in thread '[APP][2.2+][11 Dec. 2022 - V3.1] BetterBatteryStats' https://xdaforums.com/t/app-2-2-11-dec-2022-v3-1-betterbatterystats.1179809/post-35755907

Post in thread '[APP][2.2+][11 Dec. 2022 - V3.1] BetterBatteryStats' https://xdaforums.com/t/app-2-2-11-dec-2022-v3-1-betterbatterystats.1179809/post-54328941
[BetterBatteryStats] Oswald Boelcke:
Personally, I think 0.8%/h is not bad considering that you had a poor signal for more than 4 hours (81.6%) and the remaining time only a moderate signal. I'm convinced your battery would drain so much if you were in a "better signal environment".

Just a few dumps by me from the beginning of the month in order to support my statement. I've usually around 0.2% - 0.4% per hour but it went up to 0.5%/h with more moderate signal time (due to weather conditions by the way).

Just a remark but without a dump for 07 Dec.: That night my idle drainage went up to incredible 1.0%/h for a simple reason. The evening before, I've checked my (modified) Google Play Store but simply forgot to freeze it afterwards what I usually do. And sure like hell: 1.0%/h!

And unbelievable: It seems I didn't have to zip the dumps!?
[BetterBatteryStats] Schroeder09:
Thanks for the reply. I am after ~.4%/hr idle drain and this is what I had before the December update and install/removal of the Pixelfy magisk module. Last night at home while sleeping the phone had 2%/hr idle drain with all sorts of the Google play services alarms and location based wakelocks.

How are you freezing apps? Are you doing that with titanium backup?
[BetterBatteryStats] Oswald Boelcke:
Affirmative, Mam, Sir! TB but alternatively I can use SD Maid by @Dark3n.
[BetterBatteryStats] the_naturat_com:
Is there any hope of working BBS on Samsung One UI 5.0?
[BetterBatteryStats] Thebear j koss:
Be patient , it is being worked on. Samsung handles things different than stock android. Certain root privileges need a work around to gain access. If and when it is solved, I'm sure it will be posted by the dev. Read back or search for Samsung one UI 5.0 in the thread instead of just posting.
[BetterBatteryStats] shaggyskunk:
Exactly! The Dev has already posted some of the challenges that he's dealing with - In no small part are the "hand-tying" demands from Google.

Although no Dev ever needs to @chamonix has asked for feedback on possible solutions.

Just an FYI - BBS is not the only Battery monitoring app that is facing issues on One UI V5.0 - So we all appreciate the Time & Date going into BBS! 🙇🏼

This isn't the time of year for anything about Android - But it IS the time of year - For EVERYTHING about Family 🎄🕊️
[BetterBatteryStats] Schroeder09:
Anyone had time to look through this dump file and make any analysis of the wakelocks. I seem to have a bunch of wakelocks from Android trying to detect motion, and those are new. Why is the activity detection so high? Is this truly android or is another app actually calling on Android to use activity detection? How do I determine that and can I do it with this dump file?
[BetterBatteryStats] chamonix:
Unfortunately after reviving my s10 I had to discover that it will not get updated to A13. I brought it to A12 and will test if I can reproduce. If not I will have to look for someone who can lend me a S20+ device with A13 for a few days.