yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] peterlee928:
hi all

quick q

i have a rooted vzn pixel xl

lost 1% over ~5.5 hrs

on a 100% charge

generally speaking

thats solid?

dont wanna waste yall time

with my log

much thx in advance :)
[BetterBatteryStats] Darayavahus:
Thank you sir for your involvement. Greatly appreciated. 24 hr battery time for a smartphone isn't great though. Gotta check battery capacity as you've mentioned
[BetterBatteryStats] DB126:
Think I mentioned a few options including validating battery actual/current battery capacity. That said, daily recharging is not unusual on Galaxy series phones even with your usage pattern compounded by weak carrier signal strength. Good luck.
[BetterBatteryStats] Darayavahus:
Yeah I saw them, but I'm not using mobile data for testing purposes. Just wi fi in home, which is always on. So I don't concern it as an issue for the battery life. If wakelocks are OK, then it must be battery, or something I have to get used to the z3 battery spoiled me too much I guess...
[BetterBatteryStats] DB126:
A fair chunk of wake time seems to be radio related. Might want to validate WiFi signal strength and channels (look for conflicts/overlaps) in common locations. Also try setting a fixed IP on the router and/or phone.

There was other screen off activity including Google's intrusive, no configurable FireBase analytics reporting. But that was likely happening on your Z3 as well.

---------- Post added at 05:53 PM ---------- Previous post was at 05:47 PM ----------

It's fine; enjoy your device.
[BetterBatteryStats] Darayavahus:
Well, I had no issues with wifi on z3 whatsoever. If you confirm my thoughts, that wakelocks are OK, then it must be battery related issue, or it's just something what GS7 have in common and I gotta get used to it. thanks m8t.
[BetterBatteryStats] DB126:
ROMs, kernels and devices respond differently to congestion and/or weak signals. While your Z3 may have locked on to a specific WiFi channel despite the presence of other nearby WiFi broadcasting on the same channel the S7 may constantly hunt for alternatives keeping the device awake and radio power high. Same for dynamically assigned DHCP addresses. Those are easy things for fix if you have access to your AP.
[BetterBatteryStats] Darayavahus:
I C , but there is no way for it to access any other wifi channel, I live outside urban area, and only way to access the signal is from my router. (there's nothing in my area to catch on, IF that actually changes anything). And most of all, I can't modify my router settings - I have no access to it.

Might try my luck with different ROM, like LineageOS. At this point it could be anything, or nothing.
[BetterBatteryStats] paco_ramirez:
Thanks for all suggestions. I have made some changes but honestly I haven't seen any visible improvement:

1)I haven't found an official way to calibrate the battery so I did using the app battery calibration... I know people say it's not very useful, but it was the only way I found to do it. No visible improvement here.

2) I used aggressive doze and didn't see any improvement

3) I removed greenify and battery performance seems exactly the same (so it wasn't helping to improve it in fact....)

This weekend I'll try to go for a 4+ hours statistics from 100% and sot of less than 1 minute to see if we can find something out. My feelings are that phone is not recognizing well the battery capacity.

Thanks again.
[BetterBatteryStats] DB126:
Sure, worth a shot. My suggestions reflected what logged by BBS. In short a fair (but not excessive) number of network related wakelocks that typically indicate difficulty obtaining and/or maintaining connections. But it could be something else. Be sure to backup your existing config before jumping to another ROM in case it doesn't work out. Good luck!
[BetterBatteryStats] DB126:
You can also run an extended idle test mid-discharge which offers a slightly better representation of power usage as it avoids the drop-off that's often occur at charge kevel extremes. Also eliminates a bit if personal stress trying to capture a log with <1 min screen in time.

- enable Watchdog service in BBS

- also insure 'From/To References' option is enabled under customize views

- fully charge device

- use it normally for a bit

- begin the study (by putting device to sleep) somewhere between 60-80%

- after waking device launch BBS and adjust start/end spinners to 'screen off' and 'screen on', respectively

- capture and submit resulting log
[BetterBatteryStats] StephenMSmith:
I just re-rooted my phone to see in bbs what started keeping my phone from deep sleeping. It's otg_default kernel lock, which I think usb on the go. I've never plugged in a otg cable or external drive. What would cause otg_default to keep my phone awake permanently?
[BetterBatteryStats] DB126:
It pops up occasionally when device is unplugged from charger. Likely a misread on what's actually attached (or being detached). Replug charger, disconnect cleanly and reboot. Should go away. If that fails repeat above but disconnect power cord from charge brick before removing from device.

KitKat based ROM...possibly on a Moto device?
[BetterBatteryStats] StephenMSmith:
No, it's a Nexus 6P on Nougat. Just started a few days ago so I'll try your suggestions. Yeah, all the XDA posts about otg_default wakelocks are for older phone back then. Hopefully, this resolves by applying your recommendations.
[BetterBatteryStats] antimatter.web:
I'm sorry if this has been asked before. I did search the thread for this particular wakeup and found a couple of mentions, but the wakelock seems to be far less frequent for those replies than for me. Basically com.google.android.googlequicksearchbox wakes the phone dozens of times per minute. I'm using Google Beta 7.3.16.21. Is it possible to prevent these frequent wakelocks while retaining ok Google functionality? Where should I start to fix these/make them less frequent. BTW, I'm using Nova launcher and am using the Google now widget, but not the quick search widget.
[BetterBatteryStats] githyanki:
Try removing the widget and turning off OK Google detection. If it still happens then post an idle log.
[BetterBatteryStats] DB126:
Typically this wakelock neither wakes the device nor delays doze/sleep during screen off operations. A wakelock is simply a request with an associated max time value that is often ignored if no action is required. I do suspect there is a small penality for keeping the Google Now and/or OK Google detection active. Personally don't use either as I prefer Google to 'listen' only when summoned.
[BetterBatteryStats] takis:
Deleted (app didn't work even though permissions were granted, after charging the phone it magically worked... Weird stuff)
[BetterBatteryStats] magarto:
Hi,

I have around 1 wakelock per minute of job.deadline and job.delay

How can I fix it? I was using MIUI and now I installed Lineage OS

Enviado desde mi MI 5 mediante Tapatalk
[BetterBatteryStats] christantoan:
I think I have a bug, my stats for No Data Connection and No or Unknown Signal always shows as 100% even though my signal level and Internet connection are normal.

Thanks.
[BetterBatteryStats] DB126:
These wakelocks are harmless and reflect normal operations; they do not wake your device or consume excess power. Nothing to fix.

---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------

WiFi connection takes presidence on most devices; mobile radio likely in a low power state. Disable WiFi for a while to see if things change.
[BetterBatteryStats] JLius:
Battery still going strong, lasts at least 3 days of moderate use.

---------- Post added at 09:37 PM ---------- Previous post was at 09:36 PM ----------

And, what happened?
[BetterBatteryStats] thomasck:
Well, finally I could try to find what's draining battery overnight. But I'm not understanding what would be draining all this when the phone was idle. Can anyone help me?

1 - battery was 100% charged

2 - mobile was set to extreme power saver

Running xenonhd nougat..

Any explanations? Battery is 4 months old..

Here's a screenshot
[BetterBatteryStats] DB126:
Need an idle log to see what is keeping device awake:

- enable watchdog processing in BBS settings

- verify from/to references is checked under custom views

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

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

- wake device and launch BBS

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

- save dumpfile from share menu

- post resulting log to this thread (or provide cloud link)
[BetterBatteryStats] Oswald Boelcke:
Samsung GT-i9305 with Resurrection Rexix-N-v5.8.3-20170510-i9305-Official and boeffla-kernel-6.1-boeffla-stratonz-beta3-Linaro6-LOS14.1-i9305

Despite it not being a "real" idle dump in accordance with the OP, please allow me to post as the behaviour of my device, I discovered this morning, is somehow strange. Actually it's the first time it occured, and I haven't recently made any change to the settings of my ROM or kernel, no new applications installed but had applied an update to the (substratum) theme I use ("PitchBlack│Origins│Substratum") and reverted my launcher Nova from a beta-release to the latest official version (v5.1.1). Anyhow, I don't know yet if this is really connected to the issue. When I woke up this morning, I not only realised the below mentioned problem but also that WiFi was on but not connected to the home network; maybe that contributed to the issue.

Statistic Type: Unplugged to Current

Since 7 h 15 m 21 s

Level lost [%]: Bat.: -54%(96% to 42%) [7,4%/h]

Voltage lost [mV]: (4273-3741) [73,4%/h]

Awake (Screen Off) (): 7 h 3 m 1 s 97,2%

Screen On (): 12 m 20 s 2,8%

Phone On (): 2 m 10 s 0,5%

Wifi On (): 7 h 15 m 21 s 100,0%

Wifi Running (): 7 h 15 m 21 s 100,0%

Doze Interactive Time (): 14 m 24 s 3,3%

Screen dark (): 6 s 0,0%

Screen dimmed (): 12 m 13 s 2,8%

"mdm_hsic_pm0" (): 7 h 2 m 58 s Cnt:(c/wc/ec)0/0/0 97,2%

The phone (and the CPU) never went to deep sleep during the entire period!

Since I took the log about 5 hours ago, I'm monitoring the device besides using it, and I realise that it still doesn't switch into deep sleep at all.

I'm going to take a Nandroid backup of the current, trouble making system in order to be able to probably reproduce the issue pending on the suggestions and recommendations I probably get as replies to this post. However, I'm reverting now to my last Nandroid backup.

And to reiterate I haven't observed that issue yet so far.

Dump as well as the BBS dmesg and logcat attached.

I appreciate any comments, recommendations, suggestions or even assumptions. Thanks in advance.
[BetterBatteryStats] thomasck:
I'm about to update the ROM, as soon as I do it, I will provide those information. Thanks for your prompt answer.
[BetterBatteryStats] Tayx:
Honestly? No change :/

I've given up on this issue after one month of testing different stuff. I'll just have to get used to activating airplane mode when I'm running low on battery at the end of the day. If by some miracle this fixes itself sometime, that would be awesome, but it doesn't matter what I try, nothing seems to affect Nougat idle drain on my m8.
[BetterBatteryStats] JLius:
Okay, then maybe this didn't solve my drain, will try to deactivate it and see if it makes a difference. If not, it's a mystery what did. I uninstalled naptime, since it did nothing for me. Battery backup remains awesome.
[BetterBatteryStats] bryanjay420:
can someone examine my dump? deep sleep is ok but i think i can still get more :laugh: tia
[BetterBatteryStats] Oswald Boelcke:
That dump was taken for even less than one minute; really no examination possible.

Please refer to the OP how to provide a suitable log.
[BetterBatteryStats] bryanjay420:
yeah my mistake. im making dump when i sleep when my alarm rings. it wakes the device and that makes error :( I'll try again later after bedtime
[BetterBatteryStats] DB126:
Follow guidance here and you may be able to avoid this problem.
[BetterBatteryStats] Oswald Boelcke:
There a problem with the link. This is under it:

http://"https://xdaforums.com/showthread.php?t=1179809&p=72467976”

Even one connected with your screenshot wouldn't be ok as it has more than one minute screen on time.
[BetterBatteryStats] bryanjay420:
the screenshot i made is as of now i will try again later at bedtime
[BetterBatteryStats] bryanjay420:
here is after the alarm
[BetterBatteryStats] DB126:
Standard guidance this type of hang: reboot device (better yet: power down, wait 5 sec and restart). ROMs, kernels and hardware signaling is imperfect; occational glitches are to be expected on consumer grade components. A robust, redundant, hardened, semi-mission critical (99.99 SLA) data server operating in a controlled environment will still glitch 1-2X/year. Happens.

If the problem persists after nandroid restore to a known good state (and a suitable period of network isolation) your device likely suffered a hardware failure. The component may still function but exhibit unexpected behaviors.

Good luck. Post findings as they solidify (possible community learning opportunity).
[BetterBatteryStats] bryanjay420:
can't open link
[BetterBatteryStats] DB126:
Screenshots are meaningless; need an idle log.

Edit: retry link; appears there was a garbage in the original reference.
[BetterBatteryStats] bryanjay420:
is this settings correct when making dump?
[BetterBatteryStats] DB126:
Linked post stated 'screen off' and 'screen on'. Seems like that would be what you want to use...no?
[BetterBatteryStats] bryanjay420:
that is what im asking sir i dont understand :D or is it unplugged to current?
[BetterBatteryStats] JLius:
I disable this setting and left the phone idle for an hour. Had 2% drain. With 2g I have 0,3-0,5% drain, so I guess it is what solved my problem.
[BetterBatteryStats] Oswald Boelcke:
Thanks very much. You supported my assumptions.

The Nandroid backup is running (and draining) as advertised. Drainage and mdm_hsic_pm0 fully back to normal; device is entering deep sleep again.
[BetterBatteryStats] DB126:
Guess I don't understand the point of confusion. Reference points are 'screen off' and 'screen on', respectfully. If you don't see those it's likely watchdog processing has not be enabled -or- the device wasn't in a screen-off state for the minimum period specified in the watchdog option panel.
[BetterBatteryStats] bryanjay420:
check which of this is correct. thanks
[BetterBatteryStats] Tayx:
I'm glad you managed to solve it ;)
[BetterBatteryStats] DB126:
- first log (ending in 4448) is fine; didn't look at the others

- your device is dozing/sleeping fine; no action needed

- you may see some small improvements hibernating Facebook and XDA labs

- IMO leave things the way they are; enjoy your device

Purists will note the 7+ min 'vfsspi_sigwake_lock' kernel wakelock which could likely be squashed by placing device in airplane mode during sleep. However, impact on overall battery live would be minimal given low CPU usage and drain rate during screen-off wake time.
[BetterBatteryStats] atifnr:
No matter what I do it doesn't work for my op3 A3000 , i am currently on Lineage OS and still not working , i never flashed as a system app though . .
[BetterBatteryStats] bryanjay420:
you don't have to flash it. using any file explorer with root push the apk in system app and give 644 permission or rwrr
[BetterBatteryStats] DB126:
...or use one of the numerous freebie apps in the Play Store (example) to migrate apps to the system partition.
[BetterBatteryStats] Finijumper:
My better battery stats app is showing that, I'm getting very poor battery life, I wish someone could help me.
[BetterBatteryStats] DB126:
Screen shots are useless. Why not take a picture if your car and ask why it's not running well. At minimum an idle log is needed to identify the culprits; see below for guidance. You should also consult the battery panel under settings. Pretty good chance one or more big power hogs are listed near the top.

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] :
redacted
[BetterBatteryStats] shaggyskunk:
How is that "an issue"?

You powered off your device and rebooted.... Where did you think that Battery Stats would be saved & relevant??
[BetterBatteryStats] IronTechmonkey:
You are bypassing one of the key points of the post to which you replied. After reboot the stats are no longer relevant to the focused observations that would flush out a particular cause of battery drain, the testing of which is typically done in one extended session with the device in a given state between power cycles (a process described many places in this thread).

You might also consider dispensing with the obnoxious tone of statements such as "I can't be babying this app all the time. Also, in the 3 years that "it's been an issue" perhaps you could have come up with more constructive feedback to support your case.

Although I can understand the desire for longer term record keeping that is not the way most people use BBS but you could still use the share feature to save "dump files" and keep your own archive of them.
[BetterBatteryStats] Idiosyncratinom:
[IMG="BBS Stats bug"]http://m.imgur.com/gallery/hMiJL0A[/IMG]

Does anyone know why my partial wakelocks do not display correctly?
[BetterBatteryStats] olivercervera:
Hi, I have the same bug. All other stats are shown correctly.

Xiaomi Mi5 running custom ROM (Android 7.1.2 AospExtended).
[BetterBatteryStats] Oswald Boelcke:
Slightly to little information. I suggest to take an idle dump following this procedure by @Davey126.

Only in exceptional cases screenshots are useful to augment a report. I suggest to follow above linked procedure.

---------- Post added at 15:12 ---------- Previous post was at 14:58 ----------

Please allow me a question: What is the meaning respectively the difference between the counts c/wc/ec?

I unsuccessfully searched the web and XDA. Only within this thread, I was very partially successful to find an interesting discussion between @Tungstwenty and @chamonix here, here and here; however, it didn't answer my question.
[BetterBatteryStats] DB126:
c - event count

w - wake count

e - expire count

First is largely unconcerning (although a favorite target), second obvious, last suggests a serious issue that is rarely observed on modern devices. Mostly informational as little can be done about kernel wakelocks short of flashing a new/updated kernel or disabling the offending component - typically not an option.
[BetterBatteryStats] fossils-n-dents:
Try my method. I hope it helps.

https://xdaforums.com/general/help/guide-how-resolved-battery-drain-htc-10-t3619461
[BetterBatteryStats] bigknowz:
No Sleep

For the past few weeks, 6 or 7 days after flashing a new ROM, phone wouldn't deep sleep. Now it happened after 2 days, can't tell what is causing the problem, any thoughts appreciated. I know its only a few minutes off charger, plugged in so PowerManagerService would show 100%, still 0% deep sleep after 20 minutes off charger.
[BetterBatteryStats] pjadec:
Read OP again how to get battery information, those pictures are no good at all. Plus screentime is too much. Again, read OP again carefully with thought. Thanks.
[BetterBatteryStats] bigknowz:
[MENTION=3851273]pjadec[/MENTION] sorry about that, here's the dump.
[BetterBatteryStats] DB126:
Log is only 44 min with 17+ min of screen on time; useless. Return to OP for guidance on capturing a 6+ hour IDLE log with <1 min screen on time.
[BetterBatteryStats] M@31:
Just want to say thanks to everyone for the advice and comments.

I know I dont have battery "problems" per say, but just wanted to get the most out of the battery of course.

I use Kakao talk because I live in Korea and it is the most popular IM service here, and most people use it.....Ill keep the gmail stock app, since I really dont care about my hotmail account....

Thanks again for all the help, hopefully I can help you out somehow!
[BetterBatteryStats] It_ler:
There seems to be something wrong with latest version 1.6.0.0 ... at least on my phone.

Custom reference does not work properly for me, and after 8 hours of phone running on battery, BBS says that the time since charged is about a few minutes only.

If I am the only one having this issues, what am I doing wrong?

Running my SGS2 (GT-I9100) with XWLA4 Frankenstein ROM, N.E.A.K. v1.3.3x kernel and XXKL1 modem.

Cache and Dalvik cache are already wiped.

Now I am back on BBS 1.5.1.0 and everything is fine. It shows the correct 8 hours since charged.
[BetterBatteryStats] betoNL:
subscribing :)
[BetterBatteryStats] longfeng:
Yeah, buddy. Use your battery in something useful like kaokao talk. Life is beautiful and phone should not be in airplane mode everyday.
[BetterBatteryStats] desean:
I just updated to version 1.6.0.0 (xda edition) and BBS is requesting for root access while only viewing, no dumping of alarm/file/whatever.

Changelog for 1.6 did not indicate any changes that requires root access. Is there any reason why root was requested?

Thanks in advance.
[BetterBatteryStats] chamonix:
Have you read the release note that popped up (accessible also from the help menu)

Alarms are dumped when displayed but also when references are saved; that means on "charged", "unlugged", when saving dumps.
[BetterBatteryStats] desean:
Apologies. I read but I guess I read too fast on point 3 and miss the point on su request. Thanks for clarifying.
[BetterBatteryStats] chamonix:
Could anyone else confirm. I am holding back the release to market because of this feedback, can't reproduce myself though.
[BetterBatteryStats] yhrn:
I'm also having problems with BBS 1.6 not automatically refreshing. If I don't hit refresh in the menu manually BBS never updates the stats. Did not see this in 1.6 RC1/RC2 or in previous versions.

After manual refresh I seem to get reasonable stats.

Attaching a logcat of me opening BBS and getting no auto refresh (not sure if it helps).
[BetterBatteryStats] mrrogers1:
I actually notice that BBS is calling for SU access every minute in this new build which I have NEVER seen in the earlier builds. I think I'm going to roll back and see if I can reproduce just to make sure I'm not losing it.

We'll post screens later today. 200 entries in my SU logs and all are BBS UPDATE: So after looking closer, I think it was calling for SU access every minute WHILE plugged in. Still not something I had ever noticed before but I'll see if it keeps it up. My phone was plugged in from 3AM - 8AM and that's the time that the every minute calls for access were made which would explain the over 10% CPU utilization I saw overnight as opposed to the less then 1% I saw the night before with my phone unplugged overnight (for testing purposes on Virus's Eternity R97 build).

---------- Post added at 09:46 AM ---------- Previous post was at 09:42 AM ----------

Will check this now before rolling back to the earlier revision. :) UPDATE: I set a timer for 15min and I can see that BBS is showing the correct time awake and such. I can't reproduce this one either.
[BetterBatteryStats] :
Custom Ref works for me SGS2 on CM9 (ICS).

I mentioned a few pages ago that my phone would reboot the UI when I pressed the power button to wake up the screen, I later observed the same behaviour after unplugging the phone from power, both AC and USB. I didn't have this issue with the latest iteration; I think selecting alarms first and being prompted for SU rights may have "fixed" it (?). I wasn't prompted for su rights prior to selecting alarms.

Presently working flawlessly.
[BetterBatteryStats] shinew:
I had a similar glitch caused when I unplugged and saved a custom reference point at the same(not sure what I was trying to do :P).

It went back to normal after uninstall -> resintall.

---------- Post added at 06:41 PM ---------- Previous post was at 06:11 PM ----------

Just downloaded 1.6 & tested this issue, no problem for me.