yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Utini:
Hey hey, I actually even have better reception here in Austria than I had in Germany (atleast according to the BBS stats in regards to "poor/good signal".

Hmm I can make another dump this weekend while being here in Austria and the weekend after in Germany.

I already posted dumps here but it seems like no one found anything suspicious besides Fairmail.

I was in touch with the fairmail developer and everything seems fine with my 2 mail accounts that I use.

Also fairmail is configured the same way in Germany as it is in Austria.

Dump post #1: https://xdaforums.com/t/app-2-2-05-oct-v2-4-betterbatterystats.1179809/post-86044903

Dump post #2: https://xdaforums.com/t/app-2-2-05-oct-v2-4-betterbatterystats.1179809/post-86048699

Both dumps were during the night in which deep sleep works fine. But in general usage during the day I can see the differences as described between Germany/Austria.

The basebands are the same but my phone identifies with my carrier somehow?

E.g. there is a mbn file on my phone which is known by the German carriers (thus allowing me to use VoWiFi there) while it it not known by the Austrian carriers. Maybe with "unknown" mbn file (or any other file that there might be) the carrier tries to "Ping" my phone more often or maybe the connection to my carrier is less optimized then?
[BetterBatteryStats] mrjuniork:
What carrier are you using in Austria and which one in Germany? Are you using 2 diff SIM cards?

From what I read about Multi-bearer networks, your working theory might actually be one of the reasons.

Since you are basically using the same setup and you have the same usage in both countries, it must be connected to a reciprocal carrier/signal/mbn scenario.

But bear in mind, that a usage during the day has so many factors weighing in, which are influencing the power consumption. Mostly various apps tinkering with the already very well implemented Android power saving mechanisms.

Maybe those dumps taken at both locations give a little more insight.
[BetterBatteryStats] Utini:
Good morning :)

so first things first:

I use a dual-sim setup (physical SIM and E-SIM).

E-SIM in Austria: Drei.at

Physical SIM in Austria: Vodafone

E-SIM in Germany: o2 (but it is set to choose any carrier automatically, I could e.g. also use Vodafone)

Physical SIM in Germany: Telekom (but it is set to choose any carrier automatically)

So I am not using different SIM cards in Austria or Germany. It is always the same two SIM cards, no matter in which country I am, both get used.

Yes the usage during a day really has a lot of factors and maybe I just used my phone less while being in Germany.

I will wait until the december update can be flashed with root (the update has ~100 fixed) and then create a dump for Germany and Austria during the night (no usage) as well as during the day (maybe this can compare the usage case during the day). Any ideas how I can monitor in which frequency the screen has been on during the day? Because maybe I am reeally simply waking my device less often while being in Germany due to a different day routine.

Also: If the issue is connected to reciprocal carrier/signal/mbn scenario, then there is probably nothing I can do to fix it?
[BetterBatteryStats] mrjuniork:
Interesting, that you are using Vodafone while being in Austria. Since there is no official Vodafone carrier here in Austria, I wonder what carrier is being used for roaming? Could be a reason for less deep sleep in Austria.

Regarding a way to monitor what screen refresh rate was being used, I can't help you with. But who knows? Maybe there are ways to do that and I'm sure you will find it 😉
[BetterBatteryStats] Utini:
Ah sorry its not Vodafone in Austria, it is Magenta. My fault.

Are you from Austria btw? :P
[BetterBatteryStats] mrjuniork:
Yeah I wasn't sure either if maybe Vodafone has entered the Austrian market overnight, so I had to double check it 😅

So once you post another dump(s), me or one of my fellow peers will have another crack at it. Meanwhile you can analyze your usage pattern while in Austria and then compare it to the one in Germany. Could be really just that as a possible culprit.

Happy findings 😉

(And yes, I'm from Austria)
[BetterBatteryStats] Utini:
Thanks a lot!

Will post the dumps when I got them.

In the meantime I will try to figure out how to get VoWiFi to work. Might be easier on the P6P than on previous Pixel devices :P
[BetterBatteryStats] norman00037:
Hi sir, please kindly have a look at my Dump file.

Scenario:

Device: Pixel 6 with latest software (December update)

Using Acca to automatically stop charging at 78% (5:26), and lost 7% to 71% when at 8:05 only within 2.5h

Time screen off: 100% with AoD.

I have quick check and doze_time_tick wakes 141 times.

Normally (before update) the one that causes more wakeup is WifiConnectivityManager Schedule Periodic Scan Timer. (222 times)

I attached files in order:

1. Before updating December patch

2. After updating for WifiConnectivityManager

3. doze_time_tick

4. Dump file

( Updated image)
[BetterBatteryStats] TNSMANI:
There are two issues with your dump. One is that it is for too little time. It should be for 6+ hours whereas yours is for 2+ hours.

Second is that the dump was not saved immediately on unlocking the phone. The phone was used for 9+ minutes before saving the dump. The screen-on time should be in seconds, not in minutes.

Please obtain another dump and post it here. In case of any doubt, please read the first page of this thread on how to produce a proper idle dump.
[BetterBatteryStats] Virus1x:
I'm sorry maybe I'm completely dumb, I see that they removed BBS from the Google play store is there a place I can download the already compiled apk?
[BetterBatteryStats] Lughnasadh:
You will find the answer you seek if you read the OP, particularly Post #2.
[BetterBatteryStats] Virus1x:
Is the work around posted above the only way to get it to work with android 12 without root?

the adb shell settings put global hidden_api_policy 1

Edit: did it before giving perms and works disregard question.
[BetterBatteryStats] norman00037:
@TNSMANI

Sorry here is the new dump file.

Sum up:

Device: Pixel 6 December update. Rooted. Enable Adaptive battery.

Using Acca to stop charging at 79%.

Battery 78% (11:39 PM) - 66% (07:32). Drop 12%

Awake 100%, deep sleep: 0%.

Most Alarms: doze_tick_time
[BetterBatteryStats] vlubosh:
are you using e-sim?
[BetterBatteryStats] norman00037:
No I only use 1 sim.

And Wifi will be disabled between 1AM and 7AM by Tasker
[BetterBatteryStats] vlubosh:
in phones battery stats is network standby higher than display screen on?
[BetterBatteryStats] norman00037:
Mine shows Mobile network instead of Network standby.

And yes, it consumed a lot of battery
[BetterBatteryStats] vlubosh:
which version of update you have? A1, A4 or US?
[BetterBatteryStats] vlubosh:
and at first, turn off AOD and execute this command with ADB:

adb shell settings put secure doze_quick_pickup_gesture 0

then measure again.
[BetterBatteryStats] norman00037:
It's A1. I'm using Japan carrier (Yahoo mobile)
[BetterBatteryStats] TNSMANI:
As you noticed, the whole time the phone was awake. May be because of AOD, I am not sure. The others are below.

Wakelocks:

Alarms:

Location/scanning being on caused a lot of alarms and drain.

Tasker again:

Sensor stats and kernel wakelocks not registered in BBS.

Apart from these, there doesn't seem to be anything to warrant the high drain. May be a factory reset may help.
[BetterBatteryStats] bosox284:
I'm having similar drain and thinking it's due to the AOD as well. It's only about 1% per hour, but I deliberately put the phone face down to shut it down overnight. I have a few different things I'm going to try, because I like the AOD on.

Looks like this is just an adb command to turn off the 'Lift to check phone' gesture in settings? I'll try that tomorrow night. Tonight I'm trying to turn off adaptive connectivity. I believe that caused an issue in last month's firmware, but maybe it's not fully fixed.
[BetterBatteryStats] vlubosh:
Yeah, it's command for lif to... But it caused in my phone heavy batt.drain. I have also disabled ad.connectivity and kirisakura kernel for now
[BetterBatteryStats] KedarWolf:
My phone is rooted. Pixel 6 Pro. Has superuser permission, checked in Magisk.

When I open the three dot dropdown menu and click on Raw Stats, it says BatteryInfo Service could not be contacted.

Edit: I thought the below was only needed on phones not rooted.

Android 12 workaround

adb shell settings put global hidden_api_policy 1

https://stackoverflow.com/questions/55970137/bypass-androids-hidden-api-restrictions
[BetterBatteryStats] swieder711:
Similar set up and similar problem. Rooted Pixel 6P

I ran "adb shell settings put global hidden_api_policy 1" from my PC. No errors reported. Same message "BatteryInfo Service could not be contacted." Do I need to reboot after issuing the command?

EDIT: Working after a reboot. Thanks!
[BetterBatteryStats] KedarWolf:
Thank you, working now. :)
[BetterBatteryStats] andrerebucci:
Hi, good morning. How are you? Sorry to bother you.

I have a samsung note 20 ultra (exynos) with latest software (One ui 3.1 - Android 11).

For me it's absolutely perfect, except for his bad stand by battery drain. -26%(95% to 69%) [3.3%/h]

I Came to this forum after a Suggestion of another note 20 ultra user. A lot of them can reach near to 1~1,5% (even on exynos) hour stand by battery drain after an unbloat. I Did it, No AOD, only 60hz display with his poorest resolution and still getting this high drains..

I have it since may and when I set up it in the first time i did a Clean install, no backups. The only backup that I did was download the same apps from play store that was on previous phone.

It Would be perfect for me to improve it without needing a factory reset.

Could you please analise my dumpfile?

Hopefully,
[BetterBatteryStats] TNSMANI:
You don't seem to have a great mobile signal where you kept the phone for the dump. Check whether any other area nearby has a better signal.

Your wifi router seems to be having some issues. Switch it off and after >10 seconds switch it back on. If you have any other devices connected to the router, especially like printers, switch them off or disconnect them for the duration of the next dump.

Your BT seems connected, may be a watch? Switch it off for the next dump.

Wakelocks:

Instant Messaging Service seems to be the greatest drainer going by this and and the one below.

Alarms:

I don't know what this is.

This is all I could spot. If you are able to control any of the above things, please do so and then post a fresh dump.
[BetterBatteryStats] Oswald Boelcke:
Looks like a tracking app i.e. consuming lot of "Fuel" if badly coded. No own experience with it.

Life360: Standort teilen – Apps bei Google Play

Mit dem Familienorter haben Sie die Sicherheit Ihrer Familie überall im Blick.

play.google.com
[BetterBatteryStats] andrerebucci:
Thanks for fast reply!

Ok. Will check a bether signal area, reset the router, and turn off bluetooth (yes, it's a watch!).

I will uninstall life 360, it's a family tracker indeed.

Do you know anything that I could do to improve the instant messaging service? I Only need WhatsApp! :)

ImsService (Sistema Android): 20 m 49 s Count:475 4.4%

Alarms: 126, Intent: com.sec.internal.ims.imsservice.alarmmanager

I have done a thread search and find this:

'ImsService' (Android System) Turn off messaging sync in your device, then clear the cache in 'Messaging' app in your device. turn sync back on. Do not disable ImsService- possible dialer/ freezing related issues.

When you say messasing it's about SMS, right? Anything else except those tips above? Thanks a lot!!!
[BetterBatteryStats] TNSMANI:
I never owned a Samsung so no idea about IMS except that for some users, it creates issues. This too I learned from this thread having been regularly posting here. May be the clearing cache idea will work out.
[BetterBatteryStats] It_ler:
IMS should be "IP Multimedia SubSystem".

I found some articles that it has something to do with messages app. And other were talking about LTE and VoiceOverLTE.

Clearing cache of those apps might be s good idea to try first. Then you can disable somee of the related system options.

Good luck 🤞
[BetterBatteryStats] kenny_eazy:
Hi guys, help me please.

I have -14% per night.

It's normal usage, or no?
[BetterBatteryStats] TNSMANI:
The dump is not an idle dump. The screen on time is nearly two minutes while it should be as low as possible, in seconds. So please redo the dump taking care to save the dump as soon as you unlock the screen.

However, I am able to see that your mobile signal strength is poor and not consistent which usually is a huge drainer. If possible, locate the phone where the signal is better while taking the next dump.
[BetterBatteryStats] TNSMANI:
@EldigoR

BBS is not fully compatible with Android 12. Read a few pages back and use the recommended adb command to see whether it resolves your issue.
[BetterBatteryStats] EldigoR:
Thanks

I already ran

adb shell settings put global hidden_api_policy 1

and rebooted

I do see partial wakelocks and others. Only kernel wake lock are missing/faling
[BetterBatteryStats] Utini:
Just curious: Does anyone know if BBS still get developed? @chamonix was last seen half a year ago :S
[BetterBatteryStats] chamonix:
yes it is. My day-job and family are my priorities and unfortunately the gap for android 12 is pretty big so this is not something that can be solved in a few hours. I have done the refactoring though, bumping MINSDK so that I can deploy to google play as well (the app was taken down for silly reasons).
[BetterBatteryStats] mrjuniork:
Thx for the info mate, this is really appreciated.

A few hours is indeed not realistic, but maybe you can manage it in a few days 😜

Jokes aside, as you already stated, RL comes definitely first.

Looking forward to seeing what you come up with and the mod family wishes you a happy new year, especially a healthy one for you and your family.

Cheers 🥂
[BetterBatteryStats] Utini:
I can relate to your priorities.

Thanks for the update and all the best!
[BetterBatteryStats] ltcdata:
Hi! I Always used bbs to diagnose errand wakelocks from apps... since gingerbread days!

I migrated a few days ago from an S8 to an S21 Ultra, exynos.

Installed BBS, gave the correct permissions using adb but still says "no stats have been collected yet"

If i check the apk permissions, they are all ok.

I tried with gsam battery monitor (i used it ocassionally on my S8), gabe the adb permissions... same problem, no detailed stats, nothing.

Anybody can give me a little insight if i'm doing something wrong?

S21 Ultra, exynos, Android 11, november patch.

Digging a litle more: if i go to raw stats, it says "service batteryinfo can not be contacted"
[BetterBatteryStats] TNSMANI:
Which version of the BBS did you install? Please read a few pages back to find a compatible version.
[BetterBatteryStats] ltcdata:
Hi!

As always i went for the latest version, i installed 2.6-382.

I searched the thread but couldn't find anything :(

I saw a few pages back that there are problems with android 12. But i'm still with android 11.

Edit: found it: 2.5 341 works good on Android 11
[BetterBatteryStats] Utini:
I am still investigating what is causing the wake ups on my device (Pixel 6 Pro - Android 12).

Attached is a dump of 44min from "Screen Off" to "Screen On".

It has about 50% deep sleeep and 50% awake while screen off.

I was driving to my office during that time.

Maybe someone can find the cause in this dump?

Sensors, movement, wifi, radio signal,...?

It doesn't seem like it is an app.

WiFi-Scanning and Bluetooth-Scanning are both off.

Stuff that is wrongly reported:

No Data Connection (): 46 m 12 s 100.0%

Bluetooth On (): 0.0%

Data was always available and bluetooth was on and connected to my car

Update: I have internet disabled in AFWall+.. maybe thats why BBS shows no data?

Thanks!
[BetterBatteryStats] Oswald Boelcke:
Impossible to provide any analysis or recommendation from this 46' dump. Please refer to the OP; the idle dump should (at least) be 6 hours with Screen-on-time less than one minute (better just a few seconds like yours).
[BetterBatteryStats] Utini:
The idle dump will show 99% deep sleep. I already did that and it is no use for me.

During a 6h idle of not touching the phone, everything will be fine.

How ever, during a normal day where I simply move the phone around, I get only about 50% deep sleep.

And I would like to figure out why since this is the most important part of the phones "daylife".
[BetterBatteryStats] DiamondJohn:
BBS is all about idle drain. When you are driving around and/or using your phone, its not idle drain, and hence your BBS dumps wont help others help you in this thread.

To investigate running drain, I have built an App TeMeFI. This app has (among 500+ other methods) the following, which may help you diagnose your battery issues.

Doze Cycle Graphs

Battery History. Including drain rate in addition to the battery values. (some examples)

Wake Locks (Battery History Extra's), Signal strength, WiFi strength ....and much more

On a side, a quick rash diagnosis is that your doze profile keeps your phone out of deep-idle too much ;)
[BetterBatteryStats] Utini:
Oh thank you very much. I will check out your app!

What do you mean with doze profile? is there any way I can "fix" that? :o
[BetterBatteryStats] DiamondJohn:
Yes, read the thread. Its OT here. And maybe do some web searches and reading regarding Doze. Its what android uses to save battery. Very important.
[BetterBatteryStats] Virus1x:
Strangely it was working yesterday now it says no stats collected and I did do the..

adb shell settings put global hidden_api_policy 1
[BetterBatteryStats] jackwang050203:
Hi guys,

Im on android 11 and tried to run adb via wireless debug, but when I tried to grant permission. It showed error: no device found

Any tips?

Thanks
[BetterBatteryStats] Virus1x:
If you type adb devices in the cmd prompt do you see your device? if not make sure USB DEBUG is on, and you've set to always allow access.
[BetterBatteryStats] jackwang050203:
Yes, I can see my device.

It says list of device attached.
[BetterBatteryStats] DiamondJohn:
I use ADB over wireless almost exclusively.

1. Can you ping the device?

2. Have you connected to the device? adb connect 192.168.1.19; until you connect, it wont have any idea of the existence of your device.

3. Have you turned on ADB Over WiFI on in the device?
[BetterBatteryStats] jackwang050203:
Hi, thanks for the reply

I'm new to whole adb thing.

1. Sorry, how do I ping the device?

2.I entered the command to connect and it says already connected.

3. I'm connected to wifi and usb debug and wireless is on. Connected and paired to LADB to enter the command.
[BetterBatteryStats] DiamondJohn:
The ping is a test before / pre connecting. ie if you can connect, then being able to ping is a redundant test.

knowing and changing to your specific device IP, copy and paste in your shell/client output when running the following two commands.

eg:

adb connect 192.168.1.3;
adb shell;
[BetterBatteryStats] jackwang050203:
I used adb connect and says I'm already connected

Then I ran adb shell; it shows error:more than one device /emulator.

The adb devices showed two ips. The one I'm in and the other one

Eg.

192.168.1.5:4529

192.168.1.5:5862
[BetterBatteryStats] DiamondJohn:
try adb kill-server and then do a new connect.
[BetterBatteryStats] jackwang050203:
I restarted and only on ip appear and I'm connected as well. But when I ran the grant permission command it still says no device found. What am I doing wrong?

Thanks
[BetterBatteryStats] DiamondJohn:
first run adb shell aand get why it wont connect.

That will connect to your device. The connection has to be debugged before you can run any commands. You are convoluting the issue by trying to do two things at once.
[BetterBatteryStats] ppell:
Hi.

I have little problem with idle drain. My device uses around 1% per hour over night. Sometimes even more.

I think that is too high. What is the main category to look at for checking out the culprit? process? alarms? dont know much about this.

Have dumpfile here. Maybe some of u can check?

seems that signal strengh is not the case (1 file with poor and 1 with good signal?!)
[BetterBatteryStats] pol-der:
Hello. I can see attached devices with adb devices but when i entered below command i am getting error.

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

The error:

Exception occurred while executing 'grant':

java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

at android.app.ContextImpl.enforce(ContextImpl.java:2028)

at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:2056)

at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(PermissionManagerService.java:1445)

at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1426)

at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2300)

at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:251)

at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98)

at android.os.ShellCommand.exec(ShellCommand.java:44)

at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:22170)

at android.os.Binder.shellCommand(Binder.java:929)

at android.os.Binder.onTransact(Binder.java:813)

at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4687)

at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4409)

at android.os.Binder.execTransactInternal(Binder.java:1159)

at android.os.Binder.execTransact(Binder.java:1123)

Could you please help me about this issue? I have unrooted phone and app version is 2.6.382
[BetterBatteryStats] pol-der:
Also tried 2.3.248 version, same error :/
[BetterBatteryStats] pol-der:
I found the fix. I enabled USB Debugging Security on MIUI and worked!
[BetterBatteryStats] jeremysherriff:
Your dump file is incomplete, sorry. No kernel or alarm info.

Set the default display to "since unplugged" in the preferences, and always use that view if possible.

Reboot, then charge your phone briefly, before leaving it unplugged and idle for a few hours.
[BetterBatteryStats] sohebq:
RILJ is related to phone or dialler. This could be due to skype, latitude, or any other phone finding service.

I am not really sure about "connectivity service". See the running apps, and may be this connectivity service is present there.

Also, why don'y you remove Juice defender, may be one of the above two culprits arrived due to JD.
[BetterBatteryStats] nixie2121:
I am an idiot when it comes to things like this.. i think I have something draining the battery.. i don't understand how to use this app to figure this out.. any help would be appreciated.. Thanks
[BetterBatteryStats] chamonix:
In the dump from 5 hours awake most of it was because you were listening to music. The biggest reason for awake are:

- deleted_wakelocks: kernel issue

- location
[BetterBatteryStats] chamonix:
I am trying to chase down the problem since over one week but unhatfortunately no one sent me logs. My assumption about the "since charged" is no being saved on phones with a kernel preventing 100% battery charge. The logic for saving the "since charged" is happening when unplugging AND the battery level is 100%. If I could have had this confirmed till 1.7 release I would have added a threshold.

I can still make a maintenance relese for that but I need your guys help as I can not reproduce