yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] drezz2:
I understand but I do not see these apps in the list of processes that consume more memory, it would help me to see that wakelocks are being produced but I do not understand why they do not show them:crying:
[BetterBatteryStats] DiamondJohn:
Not sure if the file(s) will give you the info your are looking for, but if you look in the path /sys/kernel/debug/ there are a couple of files containing some wakelock details.

If you prefer a UI to get to them, then the app I built may help https://xdaforums.com/showpost.php?p=79191267&postcount=82Ther4e is also has the ability to deny an apps permission to various things (using

cmd appops set <APP> <PERMISSION> deny

), I have successfully tested it with GPS and something else, but I do notice one of the other permissions I havent tested is WAKE_LOCKS; but I am sure that is app level and not kernel level wakelocks.
[BetterBatteryStats] drezz2:
Hello, thanks for the information

I have been a bit more radical and I have installed to try the lineage version of android 9, and bbs now shows me data in the wakelock section, so I do not understand what is happening with version 7.1.2 since I am using the same version 2.3 of bbs, although it tells me "Detected problems with API compatibility (visit g.co/dev/appcompat for more info)" I thought it was no problem because it shows this message (I tried to locate version 2.4 but not is in the thread)

I'm not sure if I leave Android 9 since I think it's more unstable than 7.1.2, but at least if it shows me the information of the wakelocks (if anyone knows what the problem.)
[BetterBatteryStats] mrmcshagbag:
Having some strange battery drainage with a Pie ROM I have flashed on my OnePlus 3. This is the only thing that looks out of the ordinary:
[BetterBatteryStats] strongst:
Complete dump file according to instructions in op please...
[BetterBatteryStats] DB126:
Newer androids builds are often more power efficient than their predecessors. If apps are not the issue (probably are) then how well the build is optimized for your hardware is the determining factor. You have a 5-year old device; good chance the kernel/rom is not fully optimized for the platform. That said, 0.8%/hr avg hourly idle drain rate is on the high side but not excessive. Enjoy your device for what it is and don't get wrapped up in silly statistics.
[BetterBatteryStats] drezz2:
it is true that I have a certain "obsession" with the cost of battery when it is not used (with android 4.4.4 was around 0.4-0.5)

I tested with android 9 and the expense at night has been lower, it is also true that I have tried only with the installation + magisk + bbs nothing else, so it will be to try with all installed apps, at least I can see the wakelocks

I'll post the log when everything is ready (even if it's just out of curiosity)

true that he is 5 years old, if I can delay a little more the purchase of another one, will be fine
[BetterBatteryStats] DB126:
Keep in mind 'wakelocks' do not tell the whole story. Seen devices idle efficiently with hundreds of alarms/wakelocks per hour while others run full tilt with no WLs recorded. How receivers respond to WLs determine outcomes, not the wakelocks themselves.
[BetterBatteryStats] Sjain11:
Is something wrong with these stats?

Screen on

Screen dark

Doze interactive time

How can all be same?
[BetterBatteryStats] TNSMANI:
It is perfectly correct. You took the screenshot 2+ minutes after unplugging and using the phone. So the screen was on and it was set to dark for the same time. Doze also waited for the same time to fire the sleep settings.

Leave the phone for atleast some time to see different stats.
[BetterBatteryStats] Sjain11:
Thanks man.

You were right.

The stats changed.

Still a few questions.

1)Screen on and screen dark are still the same. What exactly is screen dark?

2)Bbs says phone was awake 6%. Fk kernel manager says 10%. Why this discrepancy? (see ss please)

3)If screen is on, how can doze be waiting to start?

Thank you.
[BetterBatteryStats] DB126:
Don't get wrapped up in gory details and comparisons between different apps. Screen on/dark means powered on/no intensity. Observe behaviors over time; you'll get the hang of the different readouts.
[BetterBatteryStats] MoveOnToWhat:
Hello. I've uploaded a dump file from my Mi A1. Screen on time is 3m. Hope that's okay.

Just a background on my problem : My Mi A1 has had really poor battery backup since October last year. I thought it may be related to software but subsequent OTA updates didn't solve my problem. The standby drain is a lot. Did some digging and found the '700000.ssusb' wakelock was hogging the battery.

Has the cold winter corrupted my USB port? There hasn't been direct contact with water that I know of though. Also, my phone doesn't charge through a powerbank when it is switched on. It works fine if it is switched off.

Any help is appreciated.

Thank you
[BetterBatteryStats] MoveOnToWhat:
Hello! I tried using the method suggested in the URL. Didn't work for me. I've also posted a new dump file in the forum thread. Can you please look into it once?
[BetterBatteryStats] Javier0515:
Hi.

I am using version 2.3-248, in my angler with Pixel Experience Pie and I get this error.
[BetterBatteryStats] gritts:
Hello!

Thank you to the developers and regular posters who make this app and help available. I feel I am losing excess battery life on my un-rooted Pixel 3, running un-modded Pie. I have attached a no-touchy dump from screen off to screen on as of last night. Can anyone see any red flags in my data?

Thank you again!
[BetterBatteryStats] strongst:
The ssusb wakelock is still persist and with your observation, regarding charging.

An possible explanation that suits your observation:

Well, if the device is powered on it consumes battery, current flows to your main circuit as usual and also current to the resistance towards your USB port which may be corrupted. So if you charge your device when it's powered on you need more power/current than normal when you don't have an additional consumer like your resistance in the usb port.

---------- Post added at 07:22 AM ---------- Previous post was at 07:11 AM ----------

The file contains only 2h22m of recorded stats, not 6+ hours. Can you please make a new one according to instructions?
[BetterBatteryStats] MoveOnToWhat:
So what it means is that the corrupted USB port is offering a higher than usual resistance and hence the powerbank is not able to supply current to the phone?
[BetterBatteryStats] strongst:
Exactly, but this is a possible explanation to your observation ;)
[BetterBatteryStats] gritts:
Hmm, I followed these instructions:

Any idea why my dump file is only recording 2 hours of activity? I literally went to sleep and left the device untouched in another room for 8 hours.
[BetterBatteryStats] githyanki:
You choose screen off to screen on, the screen must have come on for a short time in the night. Perhaps a notification or you checked the time.
[BetterBatteryStats] MoveOnToWhat:
I think either way, I have a corrupted USB port. Thank you for the suggestion.
[BetterBatteryStats] drezz2:
after finishing installing everything I had in lineage 19, I made a new test (I left a few hours in airplane mode) perhaps the main problem is with "es.ibercaja.ibercajaapp"? it's a banking application, although I do not understand what it must be doing to run during that time without being in use / without connectivity the device

Is everything okay or something that should change?

thanks
[BetterBatteryStats] DiamondJohn:
My phone is old (2013), and the thing that got me from high standby battery consumption to low was doze. Have you checked if your phone is getting into deep-idle quickly and staying there?

Doze also limits which/when wakelocks will occur.
[BetterBatteryStats] DB126:
Seriously? <15m wake time over a nearly 12 hr sampling window on a 5 year old device? Your config is fine.

============ Battery Info ============

Level lost [%]: Bat.: -6%(100% to 94%) [0,5%/h]

Voltage lost [mV]: (4302-4190) [9,4%/h]

=========== Other Usage ===========

Deep Sleep (): 11 h 40 m 44 s 97,6%

Awake (Screen Off) (): 14 m 39 s 2,0%

Screen On (): 2 m 30 s 0,4%

Doze Interactive Time (): 2 m 27 s 0,3%

Doze Idle Mode Time (): 11 h 25 m 33 s 95,5%

No Data Connection (): 11 h 57 m 55 s 100,0%

No or Unknown Signal (): 2 s 0,0%

Moderate Signal (): 5 s 0,0%

Screen dark (): 2 m 30 s 0,4%
[BetterBatteryStats] curiousrom:
Most Recent BetterBatteryStats & Proper Dump Settings

Check the post #2 in this thread, the "Get release candidates here" link or the big QR Code under CLICK TO SHOW CONTENT. I have BBS v2.5-302 @ the present.

Note: LineageOS 16.0 & Android Pie 9.0 users will get an error notification once in a while that says:

"Detected problems with API compatibility (visit g.co/dev/appcompat for more info)"

You can just disregard that message & use BBS normally or get rid of it permanently by using these commands in adb and hitting Enter after each line:

adb shell settings put global hidden_api_policy_pre_p_apps 0

adb shell settings put global hidden_api_policy_p_apps 0

Explanations & more info by the BBS dev chamonix in this post.

***

Unless you can travel in the future I guess that you are talking about LineageOS 16.0, right?

Your dump says: "Level lost [%]: Bat.: -6%(100% to 94%)" and Li-ion batteries drop faster from 100% to 95 compared to afterwards so that's why it says in post #1 to discharge @ 95% before testing. I prefer 92% or less:

***

It also says adjust from/to references to 'screen off' and 'screen on' and in your dump I can see "Unplugged to Current" and also "Screen On (): 2 m 30 s" and you are supposed to capture the dump immediately after turning the screen on and not turn the screen on during the test so I give you 2/10 for your test & 8/10 for the effort. ;)

In the attached screenshot you can see:

Screen Off to Current

Since 13 h 4 m 7 s

Level lost [%]: Bat.: -2%(86% to 84%) [0.2%/h]

That's with Wifi, Data & Sync enabled on a Galaxy S5 G900M LineageOS 16.0 klte build 2019-03-27 + Open GApps Pico + LineageOS Addonsu.

I applied the optimization tips described here including using LineageOS's Privacy Guard Advanced: Remove Animations UI Speedup Test - Taming Google & Apps.

***
[BetterBatteryStats] drezz2:
good morning

Sorry I do not understand what you mean by "Have you checked if your phone is getting into deep-idle quickly and staying there?"

hanks, it's been a while since I used the program and I do not finish understanding any of the information very well, do you know if there is any guide?

In the options where "boot" "chargued" "unplugged" "screen off" appears, which shows "screen off"? I do not get to understand from when he is counting. "screen on" there are times that it appears and sometimes it does not, I feel if it is a basic question,

today is being somewhat higher and the process appears "es.ibercaja.ibercajaapp" I guess the application should not be well done

true, I do not have a delorean :), I wanted to say android 9 and I put lineage 9: /

I tried version 2.5 in lineage 15 and the app itself came out in the section of wakelocks with high values, so I went back to an earlier version, the 2.3 shows me a message of "api compatibility" but I thought it read that there is no problem , more than the annoyance of the message, is it like that?

ok I will consider 92% for future cases

this is the part that I do not understand "It also says adjust from / to references to 'screen off' and 'screen on'" refers to the start of the app, leave this adjustment and do not close the app and after the time make the dump ?

I have done a test putting "screen off" I left half an hour, but when I return to the app, the time has reset and marks 1 second, that's why I said I do not understand how it works, in the same way that screen on Sometimes it does not appear

2% with the active data in 13h is very little
[BetterBatteryStats] DiamondJohn:
https://developer.android.com/training/monitoring-device-state/doze-standby

You can basically get the data from a

dumpsys deviceidle;

but to see it graphed see https://xdaforums.com/android/apps-...rehensive-documentation-t3806260/post79135309

As you can see on the graphs, one goes from "normal" (ie fully awake) and very quickly into a deep-idle (a lower power state) while the other sits in a light-idle (not as low power drain as a deep-idle) for a while before finally going into a deep-idle. Also, in the graph you can see the phone stays in a deep-idle (with timed maintenance periods) except when I physically turn the screen on. ie its not being woken up apart from when I explicitly wake it up. NB: I was constantly turning the screen on and off, but it now gets back to a deep idle very quickly.
[BetterBatteryStats] lukaszsas12:
There is a chance that someday this application will work on Samsung s 10 plus ??

Wysłane z mojego SM-G975F przy użyciu Tapatalka
[BetterBatteryStats] gritts:
Thanks for the tip—I made sure ambient notifications were turned off and generated this new 8-hour dump. Attached. Thanks in advance to anyone who can take a look. Mike.
[BetterBatteryStats] mrQQ:
Hello,

I have used BBS on all my devices, but I have problem getting it to properly work on my Huawei P20. I have enabled required permissions via adb and disable Huawei battery optimization for it, to allow it run in the background. However, I sometimes get message about API compatibility, and it does not automatically record fully charged reference. Any ideas how to fix it?

---------- Post added at 10:32 AM ---------- Previous post was at 10:32 AM ----------

Hello,

I have used BBS on all my devices, but I have problem getting it to properly work on my Huawei P20. I have enabled required permissions via adb and disable Huawei battery optimization for it, to allow it run in the background. However, I sometimes get message about API compatibility, and it does not automatically record fully charged reference. Any ideas how to fix it?
[BetterBatteryStats] TNSMANI:
You have a mobile signal issue, it is not great where the phone was kept during the taking of the dump. Is there any other location where it is better? Otherwise you will have to live with the drain.

Wifi connection also looks dicey. Reset the wifi router. Also did you have any other device connected to the wifi, especially something like a printer? If so switch it off for the next dump.

Location/scanning seems to be on. Switch it off when it is no longer required.

Major downloads of more than 15 MB happened during the sleep period mostly by PlayStore and PlayServices about which you can't do anything. But it will not happen everyday.

Proximity sensor was awake the whole time. Anything related to it switched on?

Take suitable action for the above and then get another dump.
[BetterBatteryStats] DiamondJohn:
I have not tested it, mostly because I have my updates set to not be automatic. However, I recently noticed the command:

cmd opps set <APP_NAME> RUN_IN_BACKGROUND deny;

I am thinking that removing this permission against certain apps (such as Vending), maybe the download will only occur when the screen is on, and not in standby. That is of course if you want such behavior broken.
[BetterBatteryStats] dominicstg2:
non rooted s10 plus used adb

hi all, i have a non rooted s10 plus and folowed the adb commands but i am curious as to if it has activated correctly as i am getting this message.
[BetterBatteryStats] strongst:
Page 3557 will inform you:)
[BetterBatteryStats] dominicstg2:
I looked and didn't see anything
[BetterBatteryStats] m0han:
https://xdaforums.com/showpost.php?p=79207901&postcount=35625
[BetterBatteryStats] bradical711:
[MENTION=5139398]dominicstg2[/MENTION]
[BetterBatteryStats] lm089:
Think I've seen that before but can't find it right now,so I post it again:

Sometimes mostly when opening BBS from notification I'm prompted with some error message, see screenshot. Clicking OK BBS appears to resume normally.

Version is 2.5-302,device is OnePlus 6 w/ open bootloader and stock OOS 9.0.4
[BetterBatteryStats] lm089:
Not sure whether this thread is the right place to post something like this, please let me know if not.

Version 2.5-302: link to Help is pointing to a non-existant page "https://better.asksven.io/bbs-help", see screenshot.
[BetterBatteryStats] learnyee:
I had the same issue as well...nothing is being displayed.
[BetterBatteryStats] trinidude4:
Entering the code in this post fixed that for me:

https://xdaforums.com/showthread.php?t=1179809&p=78962706

I don't think it affects functionality so you can just hit OK and move on.
[BetterBatteryStats] bradical711:
If someone could take a look at my dump when they get a moment, I would greatly appreciate it. Thank you!
[BetterBatteryStats] strongst:
Youtube keeps your device some minutes awake. Also try to turn off wifi and location scanning if enabled and repeat the test with similar sleep time and see if it gets below 0.7%/h.

Otherwise 0.7%/h isn't too high, just a little exposed.
[BetterBatteryStats] gritts:
Thanks for taking a look! For the second (BetterBatteryStats-2019-04-05_080023708) dump, I placed the phone near a window at the front of my house. Hopefully that promotes better mobile signal.

I reset my WiFi router last night before going to bed (and starting the dump).

I turned off automatic updates in the Google Play Store.

WiFi Scanning in Android options is turned off, which was also the case for dump #1. I'd like to leave Location services on for regular increased app functionality.

Proximity sensor should be clear this time around, as the phone is just laying about a few feet away from a window on a flat surface. I've also taken off my screen protector.

I have also attached dump #1 (BetterBatteryStats-2019-04-02_083105347) to this post to make comparisons easy. Thanks again!
[BetterBatteryStats] TNSMANI:
Thanks for attaching both dumps together!:good:

The drain has come down marginally from 0.8% to 0.7% per hour.

As you can see there was no 'good' signal earlier, only 'moderate'. Now you get 'good' signal most of the time. If you are able to get 'great' signal, the drain will come down further. I know that it is not in your hands. If you can switch the provider to another who has a better signal at your place, it would be great (pun intended).

Instagram fired a few alarms more this time. Facebook which was quiet last time also fired some alarms. Whatsapp became quieter.

Proximity sensor was again active the entire time. Anything like Pocket mode etc which uses that sensor enabled?

With location enabled and signal 'moderate' to 'good' and proximity sensor acting up, I think that this is the best that you can get.
[BetterBatteryStats] DiamondJohn:
Although it is simply a choice, and your battery drain is pretty low, but do you need "Location services on for regular increased app functionality" when the phone is in standby?
[BetterBatteryStats] gritts:
Short answer, no. Long answer, it's annoying to go a few menus into the settings to toggle this option regularly. Unless there's a shorter route I'm unaware of?

---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------

Thanks for the heads up on the signal strength. I'll consider switching providers. Project Fi is definitely a nice plan, though.

I'm not sure what's going on with the proximity sensor. I downloaded an app (Androsensor) that tells me when the proximity sensor is picking up a "close" reading, which it is not. I don't think there's a pocket mode on the Pixel 3. Any other ideas? Thanks!
[BetterBatteryStats] DiamondJohn:
Depending on your ROM, you may be able to set up a quick shortcut in your pull down status bar. I also have a widget on my home screen that allows me to turn off/on GPS.
[BetterBatteryStats] TNSMANI:
Location: apart from the quick setting tile to manually trigger it, there are apps to automate it. Search.

Proximity: how about Ambient Display? Is it on? Screen protector not properly set? Sensor dirty?
[BetterBatteryStats] prorokrak:
Hi,

could anybody with experience help me with finding out what causes my battery draining rather quickly and why my phone is awake some 75% of time when the screen is off?

My setup: Oneplus 3, HavocOS 2.2 ROM (1st logfile) and SkyDragon ROM [9.x][03.15] (second logfile).

After going from an Oreo 8.1 based ROM to Pie-based ROMs I have experienced much worse battery life. At first I thought it could be a problem with the HavocOS ROM so I tried to switch the ROM to SkyDragon but the situation is very similar. (As a side note, I have made clean flash of the SkyDragon but I have used Migrate to restore some 66% of my apps on the new ROM - which means some 40 apps).

Additional notes: I usually charge the battery only to some 80%. It is the biggest deviation from the instructions given in the OP about creating the dump file. Also, first log was made during the night when there was daylight saving time change. That means there is one hour seemingly missing in the log.

I would appreciate your help very much. Hopefully I have not missed anything important about creating logs.
[BetterBatteryStats] DB126:
Too many variables. Flash stock Pie w/no app and observe drain. If crappy find another ROM. Otherwise, add gapps and apps in small measures until offender identified.

Gut feel suggests rom/kernel compatibility issue with platform. Device idled at low frequency during most of sampling period. Probably not an app.
[BetterBatteryStats] prorokrak:
Thank you for looking into it. I hoped it would be less complicated process. This sounds like quite a lot hassle to have the device working normally again. But maybe there will be no other way.

Anyway, I really appreciate your help.
[BetterBatteryStats] bradical711:
[MENTION=613506]strongst[/MENTION] I did another test last night and my drain got a lot better. I have no idea why in the previous dump YouTube kept my device awake but YouTube didn't this time around and I didn't change any settings within the app since then etc.
[BetterBatteryStats] DiamondJohn:
If you are running Havoc, then you will have the ability to set the doze config. After making a nandroid, try flashing the zip at https://xdaforums.com/showpost.php?p=78537752&postcount=2 then go into Settings/Havoc Settings/Battery Savings/Doze settings select the Menu in the top right, select "DiamondJohnDroid-Comatosed", press the Save/disk icon.

I use this setup to force it to doze soon after the screen is off. NB: I do not have any wakelock issues.

You can also see a graph of the doze states by using https://xdaforums.com/showpost.php?p=79135309&postcount=74

If you do the graph before, I will guess you are not getting into Doze quickly or staying there for extended periods.
[BetterBatteryStats] prorokrak:
Thank you for another tip. Currently I am running SkyDragon. But it seems that SkyDragon ROM also enables a user to tinker with DOZE settings. On the attached screenshots are my current settings (I think these are default). I am not sure if I could use the app with my current ROM but maybe I give it a try. But before trying, I would appreciate a word on how it affects apps running in background. For example I rely on WhatsApp and e-mail (Gmail, Exchange) quite a lot. Sometimes I also use an app to record my hiking routes using GPS. And also I rely on my phone to wake me up using a 3rd-party app. Any idea how severely would these functions be affected when using the above-mentioned tools?
[BetterBatteryStats] strongst:
Statistical variance ;) sometimes apps going roque...

Now you got 0.2%/h which is absolutely amazing
[BetterBatteryStats] DiamondJohn:
Those settings seem VERY relaxed (ie slow) about going into doze.

Most ROM's repo pick features from other ROMs. ie the code for a specific feature is commonly the same, so I would be surprised if it did not work. However, a nandroid is always recommended.:fingers-crossed:

Way OT for this thread. If you also had read the link, I explicitly said I do not use social media apps; "alarms" work differently to social media apps under doze. This is where a web search is your friend. Search, Read and learn; or backup and try;)