yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] brchickery:
Sorry to bother guys. I tried to put a lot of time into the post on the last page with the screenshots and waited a little while but I didn't get any response. Am I an idiot and I missed something that people are just looking me over or whats going on :) ?

updated log from original post until now...

http://dl.dropbox.com/u/13108/BetterBatteryStats-2012-03-15_210726864.txt

http://dl.dropbox.com/u/13108/BetterBatteryStats_History-2012-03-15_210911725.txt
[BetterBatteryStats] jeremysherriff:
Dude can you a) not post screenies, and b) not quote all the screenies all over again?

The logs have all that info.

I'm having a look at your log now... brb.

In the meantime, can you edit this last post and take all the [ IMG]..[ /IMG] bits out, take make the page a bit more readable?

And, ideally, go back to your original post, take the [ IMG]..[ /IMG] bits out, and attach the screenies instead (if you really want to keep them)? If they are attached rather than in-line, then they show as thumbnails for people to click...

---------- Post added at 02:25 PM ---------- Previous post was at 02:16 PM ----------

OK, I think you have key sounds along with your haptic feedback, on certain touch functions like the softkeys:

Wakelocks
=========
AudioOut_1 (1013): 10 m 22 s (622 s) Count:130 5.6%

If that is true, disable the key sounds, as you can see they use a wakelock somehow to keep the phone awake.

The remainder of your dump file is incomplete:

Kernel Wakelocks
================
No reference since unplugged set yet (): (0 s) Cnt:(c/wc/ec)1/1/1 100.0%
======================
Alarms (requires root)
======================
No reference since unplugged set yet (): Wakeups: 0

I think you best reboot, then charge for a bit, unplug charger, leave the phone completely idle for a couple of hours, then take a new dump file. Make sure to use the "since unplugged" view.

I don't think the history dump file is useful for your situation, probably don't need to add that one unless someone requests it.

Your second set of dump files are also incomplete, but also contain too much "screen on" time - ie, you using your phone - to be useful.

Edit: check the dump file before you post it - if the alarm and kernel sections are empty again, there's not much point posting them. Rather post a question on why/what/how they are empty. HTH..
[BetterBatteryStats] brchickery:
Thanks for your help. I edited the previous posts. Sorry about that. I turned off the Touch sounds. Let see how that works out.

Since I started using BBS 2 days ago I have never had an alarm or kernel wakelocks.

I do have raw kernel wakelocks

"Modem usb suspend block is my highest at 48 m 54s (2934 s) 5467/0/0 5.9"

Raw alarms highest

com.android.email

wakeups: 1901
[BetterBatteryStats] Wolfcity:
Search the thread (last few pages) for Android 13. It's a known problem that BBS doesn't work correctly on A13, the developer is working on it.
[BetterBatteryStats] asripath:
Works fine for me on A13...

Version 3.3.504

Maybe an issue with some devices and

Their OS impl of A13.

Edit

Updated to 3.3.1-514...no issues
[BetterBatteryStats] RIgabula:
Hi, Happy New Year, thanks for the work, trying the app(google store) again after not using it for ages, on my Huawei P10 aince I noticed screen wakes without reason. No root, granted acces through ADB, but it seems its not working. Posting giagnostics, if any other logs are needed please let me know and I'll try to obtain them as well:

Build.VERSION.RELEASE: 9
Build.BRAND: HUAWEI
Build.DEVICE: HWVTR
Build.MANUFACTURERHUAWEI
Build.MODEL: VTR-L29
Build.VERSION.SDK_INT: 28

invoking android.os.ServiceManager.getService("batterystats")
android.os.ServiceManager.getService("batterystats") returned a service binder
invoking com.android.internal.app.IBatteryStats$Stub.asInterface
resolving getStatisticsStream(boolean)
FAILED
falling back to getStatisticsStream()
FAILURE: an unhandled exception occured

STACK TRACE
java.lang.NoSuchMethodException: getStatisticsStream []
at java.lang.Class.getMethod(Class.java:2068)
at java.lang.Class.getMethod(Class.java:1690)
at com.asksven.betterbatterystats.DiagnosticsActivity.diagGetService(DiagnosticsActivity.java:192)
at com.asksven.betterbatterystats.DiagnosticsActivity.onResume(DiagnosticsActivity.java:95)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1456)
at android.app.Activity.performResume(Activity.java:7614)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4412)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4470)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2199)
at android.os.Handler.dispatchMessage(Handler.java:112)
at android.os.Looper.loop(Looper.java:216)
at android.app.ActivityThread.main(ActivityThread.java:7625)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:524)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:987)
[BetterBatteryStats] TNSMANI:
First of all, try the latest version linked in the second post. Please note that the adb commands are different for the XDA version of the app. If you still encounter issues in running the app, please post a log with details of your device, android version etc.

If it runs, please save an idle dump file as detailed in the first page of this thread and post it here so that someone can help.
[BetterBatteryStats] Gandalf19:
Hi.

I'm on OnePlus 8T with root and Magisk 25.2.

BetterBatteryStats 3.3-507 from Play Store

On Summary I have this message:

Build.VERSION.RELEASE: 13

Build.BRAND: OnePlus

Build.DEVICE: OnePlus8T

Build.MANUFACTUREROnePlus

Build.MODEL: KB2003

Build.VERSION.SDK_INT: 33

invoking android.os.ServiceManager.getService("batterystats")

android.os.ServiceManager.getService("batterystats") returned a service binder

invoking com.android.internal.app.IBatteryStats$Stub.asInterface

resolving getStatisticsStream(boolean)

invoking getStatisticsStream

retrieving parcel

NullPointerException occured

batteryStatsImpl_CREATOR.createFromParcel FAILED, trying readFrmParcel with PowerProfile set

SUCCESS

How can I solve yellow error ?

Thanks
[BetterBatteryStats] DirkStorck:
Hi,

I have downloaded betterbatterystats_xdaedition_debug_3.3.1-514.apk installed it using adb and tried to grant permission

I have a Samsung S20 Ultra running Android 13.

So granting permission fails for me and without that app crashes when I try to start it.

I get a toast message 'Ausgewichen auf "Seit Systemstart" '
[BetterBatteryStats] Thebear j koss:
Don't install adb. Install as a regular app.
[BetterBatteryStats] DirkStorck:
Hi,

I uninstalled the app and installed it as regular app. Now I get
[BetterBatteryStats] Thebear j koss:
Read the last 2 pages of this thread.
[BetterBatteryStats] DirkStorck:
What do you mean exactly? I found 3 other permission. These worked and didn't give me an error. I thought I don't have to grand permissions at all because my phone is rooted

Oh I see, now I could start the app. It still asked me to grand permission for PHONE_STATE but after I did that it seams to work now.

Thank you!
[BetterBatteryStats] DirkStorck:
I have that yellow/orange error/waning that no statistics have been collected, Is that normal? Do I have to wait some time?

If I call diacritics from within settings I get

Thanks!
[BetterBatteryStats] _theluk_:
Removed: page wasn't refreshed and last comment made my response obsolete
[BetterBatteryStats] Karl_LOL:
I have the the latest xdaversion 3.3.1-522 and a Samsung Galaxy Flip 4.

I can grant every permission except READ_PRECISE_PHONE_STATE. I always get that with the following command:

adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.READ_PRECISE_PHONE_STATE
[BetterBatteryStats] Gandalf19:
Nobody ?
[BetterBatteryStats] Thebear j koss:
No idea. It's not in English.
[BetterBatteryStats] Thebear j koss:
That's not an error. Read the OP to correctly start the process.
[BetterBatteryStats] problem_child:
Hi all

Running google pixel 7 pro on January 2023 security update. Seems that due to 'deny first ' notification policy the notification toggle is broken for the 3.3.1 version of bbs installed from fdroid. Seems to work as expected but it's annoying.

Any suggestions how to fix? I've tried the obvious like uninstalled app/clear storage and cache - didn't help.
[BetterBatteryStats] Gandalf19:
I'm on rooted device and give root permission to BBS with Magisk.

In OP page I cannot find anything.

Can you be more specific?

Thank's
[BetterBatteryStats] DirkStorck:
After updating to Version 3.3.1-522 (107) and granding permissions the app doesn't crash anymore but I only get data in "Alarms" and "CPU States". All other taps show that yellow/orange notification that no data has been collected. Strange thing is. This morgen as I checked the other taps I got data.
[BetterBatteryStats] caingatcarl:
Hello everyone. I'm new to this thread. Just a quick question. So basically what this app does is to know what specific app or package is causing battery drain right? Then what to do next? Apply an adb command to prevent this "app or package" from wakelocks or wakeups? Thankyou.
[BetterBatteryStats] TNSMANI:
Not necessarily. Because alarms and walocks are beneficial for using the phone. But in some apps at some point of time, they run amuck. Usually you uninstall such an app if it is not essential. Otherwise, you try to limit the number of wakelocks and alarms. When that is not possible for some reason, you block the wakelock or alarm with consequences from unexpected behaviour to a brick.
[BetterBatteryStats] Boulder08:
I'm trying to find out the reason for my battery drain with Android 13, but BBS crashes upon start, also with the latest beta. I'm using a Samsung S20+ with BeyondROM v5.1.

I was able to get the app launched once, but no stats were available. IIRC the error message in permissions was "inconsistent tx state lengths" for status.
[BetterBatteryStats] _theluk_:
This is a known issue. Please look at the last few pages of the thread. Keep checking for updates here. It will hopefully be possible for the developer to fix the issue
[BetterBatteryStats] chamonix:
An update on the Samsung A13 nightmare:

1. I have a S20 lender on A13, thanks to my brother in law. I will probably end-up having to buy one because I am under the impression that this issue can only be fixed by Samsung, and it may take a while

2. I am able to reproduce the error

3. Samsung is not running the core/java/com/android/internal/os/BatteryStatsImpl.java implementation from any android 13 branches or tags I could find on https://android.googlesource.com/platform/frameworks/base.git (I am not judging)

4. From all the call stacks I could parse the issue is related to accessing the modem counters that do not align. My unproven theory here is that the error is caused by some missing permissions that are not visible since the code does not throw any SecurityException.

Here is the complete call-stack. Please let me know if you have an idea:

Spoiler content hidden.

Call to action:

- if you know where to find the Samsung Android source tree please let me know

- if you know someone who has access to Samsung's Android source tree please try to connect me
[BetterBatteryStats] chamonix:
Unfortunately I do not maintain the F-Droid BBS entry: it has been added there without my consent, without takling to me or even asking. The most annoying is that the entry is a 1:1 copy of the google play entry, that names me as the supported.

If anyone knows who owns the F-Droid entry I would be very happy if this person could contact me. I am not going to sue (even if that entry breaches the license) but I am really fed-up having unhappy people reaching-out to me and not being able to do anything about it!

If you want my support please use the g-play version or the (always free) version distributed through XDA
[BetterBatteryStats] problem_child:
Oooooh

Sorry, I wasn't aware of this. I kinda assumed the f droid one is the same as xda as it can bypass possible google play restrictions...

I'll use the xda one instead then
[BetterBatteryStats] Schroeder09:
Ok. Now I'm getting the dreaded *job.deadline* alarm from Android. The occurrence ranges from 1-2x / minute with it being two times more often than not. This started about 2 days ago. I've installed Nova launcher and its nova google companion app which enabled the Google feed when swiped to the left of the home screen. I've restricted some items via xprivacy Lua too.

Since then I've locked some apps down with app ops through the app "app manager" but the changes have no effect. What do I do to determine what is causing this alarm? Do I need to do a BBS dump? Do i need to use a log viewer? Battery historian? What will tell the actual cause in Android or the app working through android that's driving this alarm?

Yes, I have done searches. Yes, there are past XDA threads about this vary alarm. No, there was never a resolution in the threads I found. Multiple people wiped their phones over it and still had the wakelock. I'm working with:

Google pixel 7 pro

Kirisakura kernel 1.2.3

January update

Magisk 25.4

Lsposed 1.8.5
[BetterBatteryStats] jbonilla51:
I have no idea about this power suspend lockout wake lock. Tried googling with no luck. Running Crdroid on OnePlus 5 with root. Any insight is greatly appreciated. Edit: trying to upload dump via mobile but unsure if working. I'll check on laptop shortly
[BetterBatteryStats] Schroeder09:
Will battery historian give much better and thorough data than the log reports from the BBS app? I'm using a p7p. When I start a bug report I'm given the option to generate an interactive or full report. The description for the "full" report makes it sound like it actually gives less info tho. Which one do I select for Battey historian?
[BetterBatteryStats] Oswald Boelcke:
I suggest to discuss this in a "Battery Historian" wherever it might exist as this would be off-topic in the BBS thread.

Regards

Oswald Boelcke

Senior Moderator
[BetterBatteryStats] chamonix:
Deleting bbs' should solve the crash issue so that can confirm the other error that unfortunately is still unfixed. You can read all about what we know in my previous post
[BetterBatteryStats] chamonix:
Can you reproduce will the version from XDA? I do not maintain nor endorse l the version that is distributed through fdroid
[BetterBatteryStats] problem_child:
Hi

Actually I already had the bought version from playstore. I probably completely forgot about it. Works like a charm so no can't reproduce it. Seems that's it was related to fdroid but that's another ball game...
[BetterBatteryStats] krkhaha:
Hi. My problem is because is not possible to grant permissions for notifications. Even manually from settings of phone. Is not possible to tap on this

Screenshot-20230123-175958 hosted at ImgBB

Image Screenshot-20230123-175958 hosted in ImgBB

ibb.co
[BetterBatteryStats] problem_child:
Hey

That's the same problem I had with the version from the f droid store. Which one are you using?

I solved mine by using the app version from google play instead
[BetterBatteryStats] krkhaha:
I use it from here https://install.appcenter.ms/users/...stats-xda-edition/distribution_groups/testers
[BetterBatteryStats] krkhaha:
This is last version what can work without that issue

betterbatterystats_xdaedition_debug_3.0-485. Even if I updated on top is same problems so I think is bug.
[BetterBatteryStats] xn0live:
Hi, can anyone know/explained what for wakelock and how to fixed?

Its called:

CMWakeLock (Google Play-Dienste): 7 h 23 m 24 s Count:28 50,3%
[BetterBatteryStats] sandry24:
Hey any updates on the no stats have been collected error?

I have a samsung S20+ 5G android 13 and the status says: FAILED:Inconsistent tx lengths
[BetterBatteryStats] Ok_Kaleidoscope5109:
Confirmed, I have no persistent notification either. I think this disappeared at some point when I updated and thanks to your factfinding, it pretty much aligns with my observations that older versions were fine.

I'm wondering if I should downgrade or just wait til the problem gets fixed.
[BetterBatteryStats] ace2nutzer:
No stats on rooted Android 9 stock ROM? How to fix?
[BetterBatteryStats] Oswald Boelcke:
No issues on SM-G955F with LOS 16.0
[BetterBatteryStats] ace2nutzer:
Could you please post the same screenshots for comparison?
[BetterBatteryStats] Oswald Boelcke:
Here you go...

Spoiler content hidden.
[BetterBatteryStats] Thebear j koss:
It's something with Samsung devices. Read back the past few pages. It's being looked at.
[BetterBatteryStats] fatspirit:
Original unrooted S22, Android 13. 3.0.45 is crashing, 3.3.1-522 (107) is crashing. Not immediately. It works after giving adb permissions in the evening, and at the morning it doesn't work.
[BetterBatteryStats] asripath:
The global hidden API policy seems to trigger

Restrictions on non-sdk interfaces failure.

Is it still needed to be turned on globally or Is there a workaround (rooted)
[BetterBatteryStats] 努力的咸鱼:
my phone is

Korean version of Samsung S20

System: oneui5.1

Have root privileges (magisk-alpha).

After downloading bbt in the Google store, give root permission and run normally,

At that time, only the wake lock page had data, and other pages had no data.

After running bbs, after three hours, bbs crashed and could not be started.

(After testing, it can be started without root permission, and it will crash if adb gives permission)

Delete the Google version, download the latest test version on xda, open it and give root permission, the display is normal and each page has data

Restart the phone, open bbs again, the software crashes

After uninstalling the software and installing it again, the software crashes

(no root privileges, works fine, no data)

Then test another software

Install gsam battery, it works normally, but after giving root permission, the software crashes

These are my test results

Is this a problem with my phone?

I can still use gsam in the past, and I can have root authority
[BetterBatteryStats] Schroeder09:
Anyone ever see these? Is the only way to determine which app is using these with battery historian?

1.) BugleFirebaseMessagingService.onMessageReceived -> PrewarmTickleHandler:: onTickleReceived -> TickleHandlerHelper::backgroundService

2.) BugleFirebaseMessagingService.onMessageReceived -> PhoneTachyonTickleHandler:: onTickleReceived -> TickleHandlerHelper::backgroundService

**Note: in each of the 2 wakelocks above I added a space between "::" and "on" because an emoji was in the middlle of the wakelock otherwise.

I'm on BBS 3.3-504. I have a pixel 7 pro on Android 13 with the latest February security patch. I have magisk 25.2. In terms of messenging I use telegram for techy groups that run parallel to XDA. I use the stock Google messages app. I mention those two apps because they seem like two that might be using this wakelock.
[BetterBatteryStats] jimmylui:
cant use the app

also when i enter raw stats it pops out batteryinfo could not be contaced

using the s23ultra
[BetterBatteryStats] swapyworld:
Hi Guys, i am experiencing 2.5% per hour and above idle drain on Siberia rom for K20 Pro. Just wanted to know the reason if i could do anything about it.

Would appreciate if anyone can read the long and help me. Its for about 11+ hrs duration with 8.5+ hrs as idle time over night.
[BetterBatteryStats] Oswald Boelcke:
This is not an idle dump; screen was on for one hour and 18 minutes. Screen on time should be less than one minute. Consider to review the instructions in the OP.
[BetterBatteryStats] swapyworld:
I read, it said run down battery to 95% or so, so i used it more. But i guess 'adjust from/to references to 'screen off' and 'screen on'' is more important, so wake up screen is not seen in the log.

Could u tell me how or rather where to set it?
[BetterBatteryStats] TNSMANI:
On the left drop down menu when you are on the 'Summary' screen, you get 'Unplugged' by default. Click it and choose 'screen off' and on the right dropdown menu click 'Current' and choose 'screen on'. Then save the file.
[BetterBatteryStats] nortuzar:
Any news regarding Samsung on One UI 5.1? I really need to check what is going on with my s22 ultra battery.

Thanks for the great app
[BetterBatteryStats] RomainD2:
Hi,

My phone doesn't go into deep sleep and I can't find the application which keep my phone awake when the screen is off :

I have attached a dump file, how can I solve this problem ?

Thanks
[BetterBatteryStats] Oswald Boelcke:
There's no file attached to your post. And just due to your screenshot, please remember that in accordance with the opening post an idle dump should be over a period of at least six hours with less than one minute screen-on-time.

Regards

Oswald Boelcke
[BetterBatteryStats] swapyworld:
Can anyone help read the log? Seems only gms is causing the delay on this rom. But just wanted to be sure.
[BetterBatteryStats] TNSMANI:
Instagram held wakelocks for about 22 minutes.

PowerManager Service kernel wakelocks for about 26 minutes, though I see no reason for the same and the screen was not on.

Symantec seems to be running in the background for about 8 minutes.

The alarms under android gms are usually required for proper running of the device and it is the Heartbeat alarm which is high. This is used to keep in touch with the mobile tower periodically and may be because you don't have a great mobile signal, it is topping the list. In addition, Location/scanning is on and that has its own drain. You also don't have wifi on and all things are done on mobile data which will contribute to this situation. Try enabling wifi for a night and take a fresh dump.

Instagram figures in Alarms too.

In Sensors these three

top the list, I don't know why. The first one is stated to relate to charging. May be the next two are linked and disabling DT2W may give some respite.

For more than 2 hours your phone was awake with the screen off as a result of all the above.

Since I don't know your usages and the other apps installed and since you are the best one to understand your device better, see if any of my observations help.
[BetterBatteryStats] aadeshiscool:
Were you able to find anything? Seems like the issue is with oneui 5.1 mostly. My s23u too has the same issue
[BetterBatteryStats] RomainD2:
Thanks,

I made a an idle dump file this night according to the opening post attached to this post.

Thanks for your help
[BetterBatteryStats] appman1234:
Hi all,

BBS showed that the dumpstate_wakelock is always 100% and Deep Sleep is 0%. Tried to google it but nothing helpful.

I want to ask: What is "dumpstate_wakelock"? How can I reduce/eliminate it? I tried switching kernel but it didn't help.

Thanks
[BetterBatteryStats] TNSMANI:
I think that it relates to apps which trigger the dumpstate to be recorded. May be an app you have has an improper implementation of it. If this issue suddenly cropped up, find out which apps you installed just before the issue started and see whether uninstalling those apps solves the issue. Since you haven't attached any idle dump of BBS, at this time, this is all I can say.

Otherwise, please post an idle dump from BBS as enumerated in the first post of this thread and we will try to help.
[BetterBatteryStats] TNSMANI:
Your mobile signal is not great and that drains battery fast. Since the phone continuously searches for a better signal, the phone is likely to be kept awake longer.

Location/scanning is on and that too will drain battery. Do you require it to be on while you sleep?

Sensors also seem to be keeping the phone awake. Disable DT2W when you save another dump file. And while doing so, ensure that your phone is at a place where the signal is better.

Also reset your wifi router by switching it off for sometime and then restart it since wifi was not used for background downloads/uploads resulting in mobile data being used whose signal is already bad.