yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] Wh1t3Rose:
Upload either directly to XDA or use pastebin.
[BetterBatteryStats] PeterImmel:
here it is. but I was already told that it might be a physical problem, because there aren't problems recorded with bbs.

perhabs in this newer log....
[BetterBatteryStats] DB126:
Voltage drop is ominous; I'd say the battery has seen better days. If you still enjoy the device might be worth considering a replacement. Packs are generally inexpensive and the procedure relatively straight forward (here). Quality is another issue; be sure to purchase from a reputable source.

Otherwise no standout issues. WhatsApp was a little busy but likely not a primary contributor to drain. Not a fan of Lineage 15.1 on older hardware but it seems well behaved/matched in this instance assuming BBS readout is accurate.
[BetterBatteryStats] Wh1t3Rose:
Yea Def seems like a physical problem. Sorry man. I'd advise flashing stock if you haven't already and wiping the device. Then just install Bbs and nothing else. Leave untouched while you sleep then provide a new log.

If you are gonna return the phone anyway then I suggest you try this as a last resort before returning the phone. Quote or Mention me and I'll look at the new log.
[BetterBatteryStats] DB126:
- device is 2+ (close to 3) years young; returning wouldn't seem to be an option

- there is no evidence ROM, kernel, sensor, etc contributed to accelerated drain

- aging battery is the most likely culprit IMHO

- reflashing stock seems a waste although could certainly be used as a control point

- running a follow-up BBS study starting at 80% may be useful as failing packs generally exhibit different characteristics at different points along the discharge curve
[BetterBatteryStats] Wh1t3Rose:
Sorry missed the part about the device being so old. I agree with you on all points.

I used to be in the Nexus 5 battery troubleshooting thread daily. Was known around there and was pretty good at analyzing BBS Logs. Haven't troubleshooted battery issues since Lollipop ERA tho as I haven't had an Android Device in some time (Late 2015ish). It feels good to be back on XDA I just need to get my RC status back :).
[BetterBatteryStats] petzku:
Only 45% deep sleep time when screen is off. Can someone help me with this? I used wakelock detector root with my previous phone. It was rooted. I havent got the nerves to root my note 8 so here i am. But im confused with this app, its a bit more complicated that im used to. So if someone could point me into right direction i would very much appriciate it. Here is the dumpfile, i hope i got it out the right way.
[BetterBatteryStats] strongst:
You have nearly 4h sot. Please read op how perquisites are required for an idle log. The usage time is too high to investigate on your deep sleep behavior :)
[BetterBatteryStats] petzku:
Like this? I did like in the op. Recharged to 100 and made sure that the settings were right. Used the phone to watch youtube for some time to get battery to about 97%. And the went to sleep. Opened the phone in the morning and and toggled the sceen off unplugged and made the dump.

So something has activated PowerManagerService.WakeLocks for almost 29min... but cant identify what. Is that whats holdin the phone not going into deep sleep?
[BetterBatteryStats] githyanki:
Your screen on time needs to be less than one minute when you make your dump. Even with 27 minutes of screen on time, you still had 1% drain. The may be some things to tame once we have a proper dump to analyze, but you don't have a big problem like you seemed to think earlier.
[BetterBatteryStats] petzku:
Ok, I try again tonight after work. It seems that there is still some app or something that holds the phone from getting into deep sleep. When i had my Nexus 6p the screen off awake time was 3-5%. Now with note 8 its about 20%, thats a huge difference.
[BetterBatteryStats] Harrygsr:
Hi guys. Could you have a look at this please. I have a kernel wakelock called ohio_wake_lock that is keeping the phone awake 100% of the time. I've had this issue present in two different aosp roms and also on stock HTC software. I did this BBS dump over night with wifi, data and location turned off and still lost 20%. I would really appreciate any advice. Thanks in advance.
[BetterBatteryStats] DB126:
Try this procedure if you are having difficulty generating an idle dump.

---------- Post added at 01:34 PM ---------- Previous post was at 01:21 PM ----------

Appears related to significant motion sensor(s) which may indicate a hardware problem or kernel incompatibility. Also possible Magisk or a Magisk module is playing a role - although me thinks not. To eliminate the latter restore stock (all partitions including bootloader, kernel, recovery, etc) for a few days. If the issue persists you have likely identified the culprit.
[BetterBatteryStats] Harrygsr:
Because this problem has persisted across two different aosp roms and also stock HTC I was worried it was a hardware problem. I'm assuming the three roms have different kernels so I doubt it's kernel incompatibility. I have ruu'd back to stock already but didn't stay on it for more than a day. Do you think letting it settle over a few days might help? Thanks in advance.
[BetterBatteryStats] DB126:
Unlikely. Kernels and ROMs are different beasts. Flashing/restoring the latter doesn't necessarily change the former. If you are going to restore stock as a controlled test be sure to go all the way (previous post) and leave it unrooted.

Lineage builds are notorious for including kernel components that may not be ready for prime time and often stick around through rollbacks. Really depends how it was packaged by the custodian - especially unofficial builds.

Edit: Probably should continue discussion in device forum; nothing more can be done here.
[BetterBatteryStats] Harrygsr:
Thanks for your time and for your reply. Really appreciated.
[BetterBatteryStats] tomahawk5000:
May I kindly ask you to help me investigate my bbs logs. In my opinion I lost battery to fast

https://drive.google.com/file/d/1TysmkeR0ZLrXrWWQgxCPxS4oMJHAl5NK/view?usp=drivesdk
[BetterBatteryStats] strongst:
Your log isn't correct, it contains less than 6h idle time and too much sot, also a drain from 88% to 94%:rolleyes:. Please redo the log(instructions in op)
[BetterBatteryStats] tomahawk5000:
Hi,

hope now will be better.

It's 1.3%/h in my opinion should by about 0.7%/h

https://drive.google.com/file/d/1JgLP-qRAwOgxj1DTObAJWfLBSeHGVQUG/view?usp=drivesdk

https://drive.google.com/file/d/1IHRpBTSL5qhWgGp4xZ_qHc6bRZNGvU8F/view?usp=drivesdk

https://drive.google.com/file/d/1eV3qCmF58WS8CAA79z1jxIuRg2yWxX3F/view?usp=drivesdk

Thanks in advance
[BetterBatteryStats] TNSMANI:
You seem to have a huge kernel issue apart from other issues. Change to a different kernel if one is available for your device and repeat the test.
[BetterBatteryStats] Koong1:
Hello all. I'm relatively new to BBS, still trying to figure out what all the words and numbers mean. If I want to export my data and post it here to get help you guys, what format should I choose? Dumpfile, logcat or dmesg?

I'm using LG G6 still on Nougat 7.0. I have abysmal idle battery life. Overnight with WiFi turned on, location set to power-saving and Bluetooth for my Mi Band2, I get 10% drop for 8 hours of sleep. I've tried Gsam but it only shows me that *alarm* have unbelievable wakelocks. Even with WiFi and mobile data turned off overnight, I still get 7% drop in battery from 8 hours. Anyone have any suggestion/solutions?

Thanks in advance!
[BetterBatteryStats] DB126:
Gross numbers are elevated but not outrageous for a G6 given conditions. Big drainer is likely the Mi app or whatever fitness tool(s) you are using. Try killing those pups and disabling bluetooth for a day; me thinks idle consumption will drop markedly. Don't get all wrapped up with BBS terminology and high counts for alarms, wakelocks, etc. Solutions to common power issues rarely require full membership in GeeksRUs.

FWIW - a respectable average idle drain for your device is around 0.7%/hr. Tinkerers and optimizers can sometimes pull that closer to 0.5% without significant side effects. Beyond that you're into OCD territory. In the end your device is a productivity tool to make your life easier. Don't sweat the details.
[BetterBatteryStats] Wh1t3Rose:
Hey Davey, I need your Opinion. I've attached my BBS Log.

I am not getting any deep sleep on my device. I know for a fact Telegram is the cause. But if you look at my log, my idle drain is pretty good and so should I be concerned? I feel like no deep sleep is bad no matter what. FYI that 30 minutes of SOT was all at once right b4 I went to bed.

Anyways what can I do about Telegram so my phone will actually deep sleep? Thanks!

Edit: Log Attached
[BetterBatteryStats] Koong1:
Wow. Thanks for you speedy and detailed reply. Really appreciate it. I will keep a close eye on the fitness app and Bluetooth. Will test it tonight. Thank you so much for your guidance. ?
[BetterBatteryStats] DB126:
It's fine. 0.6%/hr average drain over nearly 9 hours (including 33+ min of SOT) is reasonable for this device, rom and active app portfolio. "Deep Sleep" is just a label; I prefer RVWinkle but Google disagrees. What counts is you're getting sufficient battery life make it through the day without being inconvenienced. Purists would have kittens (What?? No deep sleep!! Abandon the children; OCD calls!). Someone posted a Telegram 'fix' a few days back (here); might want to try that.
[BetterBatteryStats] Wh1t3Rose:
Thank you Davey. That fix for Telegram solved my Deep Sleep problem. Appreciate it!
[BetterBatteryStats] john yenagritis:
battery drain

hey guys im new to better battery stats

i installed it recently an done all the adb commands

now i see that im getting 684 wakeups from google play services and 589 from android..

what are these and how can i stop them?

thanks

ps i cant post screenshot for some reason

---------- Post added at 07:52 PM ---------- Previous post was at 07:47 PM ----------

google play services and android are waking my device what can i do?

---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------

how can i know what is draining my battery i have bbs installed and adb commands.
[BetterBatteryStats] strongst:
Welcome! Well, android is the system itself, the operating system. If it's not there, it won't drain the battery but you won't have an operating system ;)

Google play services are the middle ware for all Google related apps like Gmail, YouTube, calendar, accounts, contacts etc. Without them those mentioned apps/services won't be usable.

You should record and provide a dump file(idle drain) according to the instructions in the first post and upload the file itself here.

In general: Idle drains up to 1% per hour are OK(depending on your device etc.) if it's more, then there is maybe something going roque and we can investigate your dump file.
[BetterBatteryStats] john yenagritis:
ok thanks.. i cant post links here it wont let me

how can i send the dump file?
[BetterBatteryStats] strongst:
You can attach the file to the post itself or post a link. But since you are a new user, there are restrictions. Please read the "new user guide" in my signature.
[BetterBatteryStats] richtofen_13:
Hello guys,

I have an idle drain on my Mi6, it uses more than 2.5% battery per hour with everything turned off, so i struggle to get one day of battery. I installed BBS and since i don't have my phone rooted i gave root permissions through adb, but still i cant send logs or dumpfiles, it just send emails without attachments. Can anybody help me get those so i can attach here for some help with my drain?

Thank you
[BetterBatteryStats] TNSMANI:
Simply save the dump file. It should be saved in /storage/emulated/o. Then attach it here.

Which version are you running? The PlayStore version and XDA version have different adb commands since the package names are different. Check.
[BetterBatteryStats] richtofen_13:
Version 2.3.217, I installed from a apk a friend sent me, and i ran the adb commands specified on the app and they say " GRANTED". As for the storage, i cant find any folders like that, the strange thing is that after i try to save them it says " files were writen" but i cant find anything. Can someone help? this is the first time i use the app.
[BetterBatteryStats] TNSMANI:
Always install apps from the Store or a trusted place. These are the commands required:

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 (needed starting on Lolipop)

If the app is from the PlayStore, omit the "_xdaedition" from each command. The dump may be in /sdcard saved as a .txt file or else go into Settings of BBS and set the location manually.

If nothing works, uninstall, reboot and then reinstall BBS and grant the permissions via adb again.
[BetterBatteryStats] richtofen_13:
I had ran those commands on it and in the app says Granted on each one of them. I will try to reinstall the app and try to get the logs again. I'll let you know if i succeed. Thank you for your help
[BetterBatteryStats] crixley:
This doesn't work with Android P I'm assuming? It never gets any stats, I've left it a couple days.
[BetterBatteryStats] richtofen_13:
Like i said,

I have an idle drain on my Mi6, it uses more than 2.5% battery per hour with everything turned off, so i struggle to get one day of battery. I installed BBS and since i don't have my phone rooted i gave root permissions through adb, the logs are attached. Thanks in advance for the help.
[BetterBatteryStats] strongst:
[MENTION=5978836]Blaster30[/MENTION] deep sleep drain(idle) is OK, you have screen on time too but doesn't impact really as it's only 0,8%/h.
[BetterBatteryStats] TNSMANI:
Two things.

Did you switch off wifi and data? If so, enable both and take another dump.

You had used the phone for nearly 9 minutes before saving the dump. So strictly speaking, this is not an idle dump. Save the dump as soon as you unlock the phone. The screen on time should be less than one minute.
[BetterBatteryStats] richtofen_13:
i will enable wifi and data and recharge it, then i will wait for some hours and as soon as unlock save the dump correct?
[BetterBatteryStats] Artieza:
I have issues while initial mark cannot be loaded on Lineage 14.1. It means empty view at startup and toast «Fallback to "Since boot"». Periodically it works properly after plugged / unplugged.
[BetterBatteryStats] richtofen_13:
Here are the logs after charging and not using anything, also i didn't switch on the wifi and data. If you could check this logs i would appreciate it. If logs with wifi and data on are needed then i will provide them. Thank again
[BetterBatteryStats] Mikulec:
Looks like it is not working.
[BetterBatteryStats] k1bu:
Kernel: RedPillKernel_Rev1.3 :)
[BetterBatteryStats] jeremysherriff:
Hi dude. As you mentioned, the overnight sleep/activity seems to be good, yes svnet_dormancy is the highest for time, but by my reckoning it's not high on the "count" and the time isn't really all that long. So maybe not something to be concerned with too much right now?

Would you mind taking a dump file that shows your working day usage, for comparison? I wonder if there's something happening over the course of the day that's draining the crap out of your battery. Either plug it in to the charger for a few minutes before you head off for the day, and then give us the dump file for "since unplugged", or set a custom reference from the menu and use that view to dump the stats.

Does your email app use peak times, so that you're only getting email during the day? Or any other app, configured in a similar way?

PS - can you post a screenshot of your battery usage, covering like 24 hours? With you not having root, can you get a screenshot?
[BetterBatteryStats] ybres:
Uninstalled BetterBatteryStats, went to Android Market and bought the app ;)

Keep up the good work :cool:
[BetterBatteryStats] chamonix:
Looking at the alarms you have battery monitor widget waking op your phone every minute for storing a sample.

That is over-monitoring imho and the main reason for wakeup in this log. Turn down BMW and take another reading
[BetterBatteryStats] chamonix:
Could you provide a logcat and the output of 'dumpsys alarm'?
[BetterBatteryStats] chamonix:
This reading shows 30 minutes of potential out of 7 hours. Most of the wakelocks are caused but wakeups and network traffic.

There's nothing really obvious but I thing if you got through your account and check the update frequencies you will be able to reduce both traffic and wakeups a bit. The other thing you may want to consider is replacing the cloud backup by a scheduled local one to avoid the overhead and traffic

This is a good baseline to start looking at a dump during normal use
[BetterBatteryStats] coder_for_life22:
Thanks

Nice informative
[BetterBatteryStats] BonySoft:
I'm on 2G only since the beginning. Will try different radio and see how it goes, thanks for the hint.

Thanks, will try that too. Could someone please advice another battery monitoring app without so intensive wakeups?
[BetterBatteryStats] jeremysherriff:
Nothing wrong with BMW. Just set the frequency of data collection to 5 or 10 minutes.
[BetterBatteryStats] BonySoft:
The only frequency setting I've found is "History update rate", which set to 10 min while ago. Is there another one?
[BetterBatteryStats] jeremysherriff:
Yeah that's the one.

The stats definitely are updating every minute - 152 count in 152 minutes.

Maybe try setting it back to 5m (the default) and see if BBS shows more or less collections:

======================
Alarms (requires root)
======================
ccc71.bmw.pro (): Wakeups: 152
net.dinglisch.android.tasker (): Wakeups: 75

Are you running a widget, or just the background collection mode?

Edit - what are you doing with Tasker that it wakes up every 2minutes?

Edit 2: @Chamonix, did you see these kernel wakes?

Kernel Wakelocks
================
"SMD_RPCCALL" (): 19 s (19 s) Cnt:(c/wc/ec)314003/43936/0 0,2%
"rpc_read" (): 8 s (8 s) Cnt:(c/wc/ec)264034/0/0 0,1%

Any idea on source? I googled but I don't understand kernel stuff, all the search results just confuse me..
[BetterBatteryStats] BonySoft:
widget (percentage and consumption), and status icon in notification bar (percentage); shouldn't it be inactive when screen is off?

I have 3 profiles depending on week days and time periods to switch sound/air modes, like that:

Day profile: Mon-Fri, 9-22 (time), Air mode off, Silent mode off

Night profile: 22-9, Air mode on, Silent mode on

Weekend: Sun/Sat, Silent mode on

Simple profiles, long terms, don't have an idea why Tasker wakes so badly.

Yeah, I wonder too :)
[BetterBatteryStats] Karpfenhai:
hmmm, maybe you should get rid of tasker, i made good experience with lama, it can do pretty much the same and much more. for me it consumes almost no battery, give it a shot.

Swyped from my GT-I9100 using XDA App.
[BetterBatteryStats] sohebq:
https://market.android.com/details?...mNvbS5XYXphQmUuYW5kcm9pZC5CYXR0ZXJ5RHJhaW4iXQ..

Is there any app similar to this one which tells what app drained the battery in a particular hour?
[BetterBatteryStats] edison218:
Hi Bonysoft, I happen to use the tasker program for the same reason. For day and time profile, like in your case I will set time context from 2200 to 2200, airplane mode on and silent mode on. Then set another for 0900 to 0900 so the context don't need to stay active all the time.

Another for tasker >menu > preferences scroll down under monitor for display off timing, you can change it. Also i untick run in foreground at the top of the list. Hope this help. Just my 2 cents :)
[BetterBatteryStats] iovaniorgovan:
Great news people,

I found the problem

. Please see the attachment for a better view of the problem.

In my investigation, I reinstalled Omega v1.0 where this wake lock had no or very little presence.

Omega v3.0 or XXLPH came with some default access points (APN) for my network. I don’t know how it figures it out what APN to install, but 3G data was working out of the box. The ROM had this APN used as default:

Orange WAP, APN wap,

Proxy 62.217.247.252

, mcc 226, mnc 10, apy type default, apn protocol IPv4.

This APN was the source of my massive wakelocks for GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint

Then I made the analogy with Omega v1.1 where there was no pre-defined/built in APN. So I made a new APN, like I would have did in Omega v1.1, where I setup only the Name bla_bla and APN: net. Et voila, the wakelock went down from 20-28% to 1-2%.

There is also an existing APN in Omega v3.0, called Orange Internet, which is the same as APN Wap, but without the proxy server. When I tested this APN, the wake lock for AndroidEndpoint went down to 0.7%.

So

the predefined proxy server made this wake locks

and made me loose this huge amount of time troubleshooting it.
[BetterBatteryStats] Settembrini:
Hi Chamonix,

there is no result (Galaxy Tab 7.7) when I use "More" "raw alarm". It computes for a while, but nothing is shown?

When I do the same on my Galaxy Tab 7.0 plus, there is an immediate result.

Any ideas?

Thanks!

S.

I don't know how to get "dumpsys alarm".

Still no "raw alarm" on the Galaxy Tab 7.7.

If you can see any unusual battery draining, grateful for a tip.

Thanks!

S.
[BetterBatteryStats] chamonix:
BMW is just great, you just have to pick the right frequency (settings)
[BetterBatteryStats] chamonix:
I don't know those specifically but rpc tells me it's kernel internal stuff. Especially the first one with high wake count would be worth a closer look if persisting.

For analyzing that kind of stuff I recommend studying the sources, checking dmesg and contacting the dev. Certainly an interesting exercise.
[BetterBatteryStats] DB126:
No ROM/app anomalies; stats are excellent. Me thinks you have a hardware problem or possibly corrupt firmware (kernel/bootloader) install. Beyond any assistance that can be provided in this thread. Consider engaging carrier or manufacturer if still under warranty.

Alternatively, since device appears to be running Lineage 15.1 it suggests an unlocked BL or other means for installing/modifying system components. If accurate consider rolling back to last ROM/kernel combination that worked, possibly stock.

================== General Information =================== BetterBatteryStats version: 2.3-217

Creation Date: 2018-05-11 08:30:20

Statistic Type: Unplugged to Current

Since 9 h 14 m 32 s

Root perms: false

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

Level lost [%]: Bat.: -20%(100% to 80%) [2,2%/h]

Voltage lost [mV]: (4344-4103) [26,1%/h]

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

Deep Sleep (): 9 h 9 m 47 s 99,1%

Awake (Screen Off) (): 4 m 21 s 0,8%

Screen On (): 23 s 0,1%

Doze Interactive Time (): 22 s 0,1%

Doze Idle Mode Time (): 8 h 56 m 9 s 96,7%

No Data Connection (): 9 h 14 m 32 s 100,0%

No or Unknown Signal (): 9 h 14 m 32 s 100,0%

Screen dark (): 23 s 0,1%
[BetterBatteryStats] Edwrib:
About that:

com.asksven.betterbatterystats_xdaedition android.permission.PACKAGE_USAGE_STATS

Isn't the same as that in attached screenshot?
[BetterBatteryStats] richtofen_13:
Already tried every stock ROM before going to LineageOS but ever since the Oreo update from MIUI 9 that i have this issue with the battery.
[BetterBatteryStats] DB126:
More likely than not the initial Oreo install altered some low level partitions. You'd need to do a complete reinstall via fastboot or an equivalent vendor tool (eg: RSD Lite for Moto devices) to remedy that. Simply flashing a ROM and kernel image via TWRP or other recovery won't do it. Your device forum is the best place to secure the appropriate tools and procedures.
[BetterBatteryStats] richtofen_13:
Could you elaborate on that? I could even tip someone if my issue is resolved, cant take it anymore, already reinstalled some many times different ROMS