yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] DB126:
Classic symptoms of battery (likely given age) or other hardware problem. Nothing going on with Android, kernel, radio, etc which you could have ascertained through stock battery readout, GSAM or other tools currently installed. Verify fingerprint sensor and power button are in good working order. Then consider whether replacing the battery, or anything else, is economically reasonable given age of device. Good luck.
[BetterBatteryStats] krzylew:
Forgot to mention that she replaced the battery for a new one so the battery age is not the reason. I did verify in GSAM and BBS but I consider myself a noob in terms of these issues so I wanted to consult more experienced users. Thank you for you answer, If you have any other advice, please give it to me ;)
[BetterBatteryStats] DB126:
Replacement batteries from third parties are notoriously crappy. That said, if there was little/no change in drain behavior after battery was swapped then it is likely a hardware issue. Clean up exterior buttons, headphone jack and USB port with compressed air. Make sure fingerprint sensor is glick free. Might go back to stock firmware as a final test.
[BetterBatteryStats] DiamondJohn:
Have you checked that the phone is entering deep-idle (ie doze)?
[BetterBatteryStats] krzylew:
From what I understand, yes, it does. But even if it didn't, it wouldn't explain the Power Off drain, right?
[BetterBatteryStats] Oswald Boelcke:
This happened to me once on a Samsung Galaxy S5 LTE (SM-G901F - kccat6) when I migrated from RR-N-v5.8.5-20180413-kccat6-Unofficial to RR-O-v6.1.0. I returned to RR-N, and the issue was solved; the device is still on RR-N and in daily use without any issues. As I wasn't really interested in Oreo anyway, I didn't dig further into the problem.
[BetterBatteryStats] DiamondJohn:
Sorry, did not read that part:o

Getting really out there, have you tried removing the battery overnight to check how much it drains when not in the phone?
[BetterBatteryStats] DB126:
Log shows "deep sleep" for 95% of sampling window. If accurate (no reason to believe it isn't) doze state is largely irrelevant.
[BetterBatteryStats] TNSMANI:
First of all, this is not an idle dump. Phone was used for sometime before saving the dump. See the OP on how to take an idle dump.

Battery replaced at OnePlus or outside?

Your mobile signal was very poor the whole time which will drain battery hugely.

I see that location or scanning seems to be on. Switch it off.

Since there was no data connection/wifi, the apps might have kept on trying to connect. So if possible, I would say switch on airplane mode, connect wifi and take another test.

The drain during the phone off period might be a one off event. Take another dump as stated above.
[BetterBatteryStats] DiamondJohn:
I havent used battery stats for a while, but is it showing "deep sleep" or deep-idle times?
[BetterBatteryStats] Oswald Boelcke:
Forget about my values. Just grabbed a dump on the go as an example. That's what shown to me...
[BetterBatteryStats] Lughnasadh:
I'm pretty sure the deep sleep stats include both deep idle and light idle doze times combined. It doesn't separate them out. I came to this conclusion because the Pie roms for my device don't go into deep idle doze, only light idle doze as reported by GSAM Battery Stats, which does separate out deep vs light idle doze times. But BBS and other battery monitoring apps seem to combine deep and light idle doze times into 1 stat=deep sleep.
[BetterBatteryStats] krzylew:
Thank you all so much for trying to help me.

The dump was produced by my sister according to instructions from OP, I think she tried to do it right, log shows 21s Screen On which is about what would take to produce the dump after waking the phone in the morning. Could you explain what do you mean?

Anyway, soon I will have that phone in my hands so I'll be able to provide everything you need by myself.

The device is Samsung so why would the battery be replaced at OnePlus? I don't get this one at all. I believe it was a 3rd party battery but I'll verify that.

Once I get my hands on the phone, I'll try your other suggestions.

Cheers!
[BetterBatteryStats] TNSMANI:
Sorry, must have been sleepy or something :eek:. The dump is good as an idle dump. Somehow it got into my head that you were talking about an OP3.:D

All other observations hold good.
[BetterBatteryStats] doggie13_:
Any help will be highly appreciated... OnePlus 6
[BetterBatteryStats] mrjuniork:
https://xdaforums.com/showthread.php?t=1179809&p=80455431
[BetterBatteryStats] DiamondJohn:
I obviously wasn't clear, the differentiation I was making was, between your CPU in a state of "deep sleep" and your phone in doze's "deep-idle" state. Not between the two different doze states of light--idle and deep-idle.

I have never used GSAM (nor heard of it till now) so don't know where or what it is reporting or if it is simplifying things by aggregating both into one stat. I would try running the following to get closer to the raw data

dumpsys deviceidle;

and check what it returns.
[BetterBatteryStats] Lughnasadh:
Yeah, I've run that before. Its not GSAM that's aggregating both into one stat. It's BBS and others that are doing that. GSAM separates out those 2 doze idle modes. The reason that I mentioned that is because BBS and others don't tell you which or if both light and deep idle doze are occurring. They only report it going into deep sleep, which could be either deep, light or both doze states.

I know you weren't trying to make the distinction between deep and light idle doze stats. I was just trying to point out that if BBS or other apps besides GSAM report a phone going into deep sleep it doesn't necessarily mean that its going into deep idle doze. It could be just going into light idle doze, as is the case for Pie roms on my device (unless you use Greenify, Naptime, etc, which, in my case, will put the phone into deep idle doze on my device when on Pie roms). And since deep idle doze blocks wake-up timers and light idle doze doesn't, it may be important for some to know when analyzing battery stats.
[BetterBatteryStats] DB126:
I think you may have been viewing the wrong dump (or perhaps it's me). Saw your later revision on idle state but don't agree with the other conclusions. While scanning and lack of connectivity can produce high drain rates there is nothing in the log to suggest these were the primary culprits. In fact, quite the opposite. Running a test with better connectivity is reasonable but is unlikely to yield significantly different results.

My views remain unchanged...although I will toss in the slight possibility of a corrupt kernel that is producing drains not being detected by BBS.

IDK - maybe the old phuck (not you, old friend!) has lost too many brain cells. I'll just go back to knitting the worlds largest afghan. :)
[BetterBatteryStats] X46X:
Hi, will you add Android Q support?
[BetterBatteryStats] strongst:
Works on Android Q already :svetius:
[BetterBatteryStats] DiamondJohn:
But have you actually compared that with the results that you are speaking about?

And this is where I think we are getting crossed paths. "deep sleep" is a term associated with your CPU state NOT the doze state. ie "deep sleep" != "deep-idle"

I am running Oreo on my daily, but have tested Pie ROM's, and these Pie ROMs have entered doze's deep-idle without any other coaxing from apps like naptime or greenify. And I would say even more aggressively than Oreo.
[BetterBatteryStats] Lughnasadh:
1. Yes

2. Yes, I was just stating that you can't tell if you are going into deep idle doze from the deep sleep stats. So yeah, are paths are crossed on that one.

3. I 'm speaking specifically about custom Pie roms on the Nexus 6P. None enter deep idle doze. Its a bug with these roms. Its fine on any Oreo custom rom on the Nexus 6P and fine on Oreo and Pie roms for the Nexus 5. I am only talking about the Nexus 6P custom Pie roms.
[BetterBatteryStats] DiamondJohn:
===========
Other Usage
===========
[COLOR="Blue"][b]Deep Sleep (): 16 d 2 h 34 m 34 s 89.7%[/b][/COLOR]
Awake (Screen Off) (): 1 h 28 m 52 s 0.3%
Screen On (): 44 m 55 s 0.2%
Phone On (): 6 m 50 s 0.0%
Wifi On (): 20 h 32 m 23 s 4.8%
Wifi Running (): 20 h 32 m 23 s 4.8%
[COLOR="blue"][b]Doze Interactive Time (): 51 m 8 s 0.2%[/b]
[b]Doze Idle Mode Time (): 18 h 55 m 4 s 4.4%[/b][/COLOR]

Looking very quickly at your log, the first thing that jumped out at me is that it is explicitly separating "Deep Sleep" from the two "Doze" measurements. I know doze resets itself on a reboot (at the least), and that would make sense with your "Deep Sleep" is at 16 DAYS! while your idle states are in hours. I would guess that "Doze Interactive Time" are the maintenance periods of doze.

This also highlights my point to [MENTION=6530865]Lughnasadh[/MENTION], if these are the values he is speaking of?

PS: I also noticed after I posted, that your log has "Phone On (): 6 m 50 s 0.0%":confused: which further highlights just how little I understand about BBS logs ;)
[BetterBatteryStats] Lughnasadh:
I wasn't really speaking of doze interactive time (when the device leaves doze mode for during maintenance windows, I believe). I was talking about the doze idle mode time. The only point I was really trying to make is that the doze idle mode time doesn't separate out light vs deep idle mode time.
[BetterBatteryStats] Oswald Boelcke:
As I initially stated "forget about the values", any value show is just rubbish due to the way I took the dump. I just wanted to present what status line are/can be provided in my dumps. Don't even think about or try to analyse the values. I guess it might lead you onto the wrong track.
[BetterBatteryStats] X46X:
Hi, latest version is still VERSION 2.5-337?
[BetterBatteryStats] NickosD:
Yeap
[BetterBatteryStats] pidl:
Hey guys! I am getting terrible battery life on my op7 pro, dont know why that is. I almost always got 4G Connection, so i dont know why these stats are so weird ..
[BetterBatteryStats] strongst:
Hello, if you want help, please post a dump file according to the last ones provided here(6h+ recording time, less than a minute sot).

Also read OP for further information :good:
[BetterBatteryStats] pidl:
I did that now, surprisingly for that 7 hours my drain was pretty much nonexisting. I didnt have wifi during that time, maybe thats why.
[BetterBatteryStats] githyanki:
You can test again with WiFi on and see. Based on this, it is most likely that your problem is usage based, so it has to do with using it too much, or what your doing is too intensive.

Unless you notice a big drop at some point that may indicate a battery problem. Such as it losses 10% in a few minutes right around 40% (for example)
[BetterBatteryStats] pidl:
I literally only browse reddit/instagram/YouTube and some snap, that shouldnt be too intense for my op7 pro imho. I dont ever play games on the phone.
[BetterBatteryStats] curiousrom:
Analyzing Apps Battery Usage - Freezing Apps

A good troubleshooting tool when using some apps: GSam Battery Monitor.

There is a GSam user guide which is a little bit dated but informative.

As you can see in the screenshot attachment in the > triangle (Delta) menu there is a Since Now reference point option so the stats will not be reset by turning the screen off/on if you want to check the battery usage of a given app or several apps while using the device instead of just the battery usage @ idle.

This said analyzing the battery usage @ idle for at least 6 hours with BetterBatteryStats (or GSam with the no file dump caveat) is the first troubleshooting step to spot rogue apps or settings problems but one could have low battery usage @ idle but high consumption when using the device.

For example I am a New York Times subscriber. I was using the NYT app & noticed a huge %/hour of battery consumption by this app in Gsam & in my LineageOS battery stats. Now I am using a browser instead to login & surf NYT and it's consuming only 1/3 of the app's %/hour battery usage.

Instagram was an other big battery eater. Since I use it only occasionally I disable it when not needed.

If rooted there are a number of third-party apps that can disable (they call it freezing) apps & System apps when in Settings > Apps > 3-dots > Show system the Disable button is greyed out like SD Maid which I use for lots of stuff but I use also App Freezer because you can add some apps to it's Favorite panel to enable/disable quickly on the fly & when pressing on the name of the apps you get infos like path, services, etc

***

Don't blindly disable system and/or stock apps without researching them otherwise you may have some problems like not receiving notifications, device freezing, boot loops, etc.

If you have the TWRP custom recovery I suggest you do a full backup in TWRP (if you don't have a recent one) before enabling/disabling system apps which is good practice anyway.

For those without root see this XDA article: How to disable any pre-installed system app bloatware on Android without root.

***

Dying Battery?

Users tend to resist the idea that their battery needs replacement & often keep on trying to find some software or ROM or settings explanations to their poor battery life. ;)

A battery could have a seriously reduced real capacity without having a telltale symptom like a huge % drop in a short time frame. Thanks for the "around 40%" tip while obviously that may vary depending on the battery & device.

***
[BetterBatteryStats] snarl16:
Can someone please look at my log? It appears there is something holding my phone awake but I have no clue what it is. I have deleted pretty much all the apps from my phone. Alarm Manager seems to be running a lot though. I would really appreciate it if someone could help me track this down. Thanks
[BetterBatteryStats] jeremysherriff:
Looking at your usage, and all the things you are syncing in the background (twitter, facebook, whatsapp, gmail, google talk etc etc etc) then 14 hours on battery seems fair.

Can you please take another dump using "since unplugged" and cover a period where your phone is idle? It's hard to tell what is you using your phone, and what is background activity.

Best way to do that is: charge for a while before you go to bed. unplug. go to bed. Create a dump file in the morning.

---------- Post added at 09:14 AM ---------- Previous post was at 09:05 AM ----------

Hi. I think you have poor cell reception.

Your wakelocks (both user and kernel) seem OK. I would like someone else's opinion on that though, i'm not familiar with ICS kernel stuff.

Re: AlarmManager, this:

Wakelocks
=========
AlarmManager (Android System): 34 m 17 s (2057 s) Count:204 28.1%

translates into these alarms here:

Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 14
android (): Wakeups: 4
com.google.android.apps.maps (): Wakeups: 5
com.android.settings (): Wakeups: 3

None of these are terrible, GSF is a little higher than I would expect, but I wonder if every time the cell data (your 4G LTE) is used, the poor reception means that it takes several attempts to connect and has dropped packets.

Try switching down to 2g or 3g and see if you battery life improves - do it overnight, it'll be pretty obvious in a 6-8 hour overnight period if it fixes the problem.

---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------

Sorry dude, you have to change kernels. You cn reboot after you charge each time, but it's a kernel problem.

---------- Post added at 09:23 AM ---------- Previous post was at 09:15 AM ----------

Hi, sorry we missed you out :)

I don't see anything wrong with your stats, you could maybe try turning off the auto backup feature of Titanium but I don't think it will help much. Other than that, see my comments above about cell reception - you also have poor reception (you can see from the signal bars) and its likely that your phone is chewing up battery whenever there's any data connection at all. It may also be scanning for better networks quite frequently. Change to 2g data for a day or two and see if that helps.
[BetterBatteryStats] snarl16:
---------- Post added at 09:14 AM ---------- Previous post was at 09:05 AM ----------

[/COLOR]

Hi. I think you have poor cell reception.

Your wakelocks (both user and kernel) seem OK. I would like someone else's opinion on that though, i'm not familiar with ICS kernel stuff.

Re: AlarmManager, this:

Wakelocks
=========
AlarmManager (Android System): 34 m 17 s (2057 s) Count:204 28.1%

translates into these alarms here:

Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 14
android (): Wakeups: 4
com.google.android.apps.maps (): Wakeups: 5
com.android.settings (): Wakeups: 3

None of these are terrible, GSF is a little higher than I would expect, but I wonder if every time the cell data (your 4G LTE) is used, the poor reception means that it takes several attempts to connect and has dropped packets.

Try switching down to 2g or 3g and see if you battery life improves - do it overnight, it'll be pretty obvious in a 6-8 hour overnight period if it fixes the problem.

---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------

Thanks for looking at this. My reception is showing as -77dbm. What is a good level to look for?
[BetterBatteryStats] saebafr:
Hello, thanks for your answer. I will try to switch 2g. Thank you

Envoyé depuis mon Galaxy S Cm9 avec Tapatalk
[BetterBatteryStats] bendirkss:
Ya but only being able to get 2h max screen time is what bothers me. I'm on wifi all night with **** reception and my idle battery isn't to good. Let it sit over night anyhow?
[BetterBatteryStats] gtizon:
I have a question. I see partial wakeclocks just fine. When I check kernel wakeclocks, it just says No reference point since charge. What do I do check this? Is there something wrong I'm doin? Thanks!
[BetterBatteryStats] jeremysherriff:
Try it anyway, because there is two possibilities:

a) Poor cell reception causes network scanning

b) Poor 3g/4g data causes network problems/dropped packets etc

This test will check for "a".
[BetterBatteryStats] bendirkss:
K I guess I'll try it tonight. Report back tomorrow morning. I'll charge to 100% before I let it sit
[BetterBatteryStats] ballmead:
I have a similar screen on my Samsung Galaxy S2 running Redpill V1.3 kernel and BBS V1.6.1

My battery drain is massive and the phone is awake 100% of the time, even when the screen is off.

There are no significant partial wakelocks but the kernel wakelocks look like the above pic.

It seems to be a compatibility issue between BBS V1.6.1 and RedPill kernel V1.3 as the problem goes away when I revert back to an older version of BBS (V1.4.2)

EDIT: The same thing happens with BBS V1.5.1 too
[BetterBatteryStats] Miracle_Man:
My kernel wakelock thing looks like this too. What the hell does this mean?
[BetterBatteryStats] noke955:
No, I don't believe that, I have no issues with Redpill v1.3 and BBS v1.6.1
[BetterBatteryStats] ballmead:
Ok that's good to know.

What else could it be? I'm now running BBS 1.4.2 with no issues whatsoever??
[BetterBatteryStats] noke955:
Did you check your settings in Preferences?

Default stat type -> since unplugged

Maybe clearing data of BBS helps?
[BetterBatteryStats] ballmead:
Danke Schoen noke955

You are a scholar and a gentleman.

That worked a treat, the phone now goes into deep sleep.
[BetterBatteryStats] iovaniorgovan:
As a reminder, this is about sec-battery-monitor wakelock described in this post.

chamonix, I attached the dump file. I'm not sure what you meant by "52" in the quote above.

Thanks.
[BetterBatteryStats] noke955:
/OT

Bikers should help each other :)

/OT OFF
[BetterBatteryStats] cloney:
I'm getting the exact same problem, using AOKP 27 and Franco M1. Dropping about 1% every 4 minutes from BBStats. Thought it was going from Franco 18 to M1 without wiping cache and dalvik but did that and the same thing happens.

Anyone with similar issue or know a solution?? Is it the Franco Kernal issue?
[BetterBatteryStats] chamonix:
That simply means that you have not charged your battery completely since you installed BBS or rebooted. "Since charged" is an event that triggers BBS to save a reference used for later calculations and without this reference the message you mentioned is displayed.
[BetterBatteryStats] chamonix:
That is normal since version of BBS prior to 1.6.1 did not show any kernel wakelocks for a given period but only totals. The message just tells you that BBS did not detect any "battery charged" event since your phone was booted and thus can not display any data "since charged". Switching to "since unplugged" or charging your phone and letting BBS store that reference should do
[BetterBatteryStats] chamonix:
52 was the time awake, 12 minutes that specific wakelock.
[BetterBatteryStats] NickosD:
I don't know if it's reported by someone, but in beta Android 10 for s10 the issue were after going below 70% and not being able to see stats, is gone. (rebooted at 94%, so android has stats from there and not 100%)

[MENTION=1330150]chamonix[/MENTION]
[BetterBatteryStats] chamonix:
Am I understanding it right, that the flakiness due to the battery info service stops delivering stats is gone? If that is correct can you please go to the advanced settings where the permissions are shown and post a screenshot? What I would like to check is if bbs still uses the workaround code to retrieve stats or if Samsung have fixed the bug completely.
[BetterBatteryStats] NickosD:
Yeap, I can see the stats from 100 to 0 now.

But don't get your hopes up. It's the beta. A lot of things can brake until stable?
[BetterBatteryStats] chamonix:
Interesting: the beta build now exposes the right spot for the stats, avoid bbs to use the "old" way of getting stats. I did not implement a completely different code path for the S10 but only a fallback the the old method if the new fails. It does not fail at the moment so fingers crossed that Samsung does not "fix" it.
[BetterBatteryStats] chamonix:
I have updated the gplay beta channel with the latest build (same as hockeyapp) and started the production staged rollout.

From November 1st Google will bump up the minimum required SDK and from there on there will be lots of things breaking so I may have to provide different builds for golay and xda. I have no clear picture yet but it may be a while until I can deliver a rootless build on gplay. The xda build will not be affected by that as the change is only to prevent another chunk of private API from being used by gplay apps:

I can understand the rationale to keep apps fresh but do not understand why Google does not provide public API to apps like bbs, but do everything to kill the segment instead

Edit:typos
[BetterBatteryStats] skivnit:
I keep having these RILJ_ACK_WL and mmc0 wakelocks even after removing the sd cardView attachment BetterBatteryStats-2019-10-18_070822842.txt
[BetterBatteryStats] strongst:
I would more worry about the wifi related wakelocks which compared to your mentioned ones higher than usual. How about your battery? The device is quite old?!
[BetterBatteryStats] skivnit:
It's a s9+ so almost 2 years old in February :) skipped yearly upgrade this year. As for wifi wakelocks, I tried different settings but looks like I have a lot of connected devices at home which keep pinging my phone, that's my assumption
[BetterBatteryStats] vojopd:
Does it finally work on galaxy s10?
[BetterBatteryStats] NickosD:
Did you read the last posts?
[BetterBatteryStats] vojopd:
Yes I did, beta works, any bugs?
[BetterBatteryStats] DB126:
Best/latest information on device compatibility comes from reading posts in this thread. Use the search function to narrow results.
[BetterBatteryStats] dr4go:
Just one question: were / are you using #337? Thanks in advance
[BetterBatteryStats] vojopd:
I paid for the app, and it isn't updated on playstore since 2018. So I guess it isnt working.
[BetterBatteryStats] NickosD:
Beta Channel or from the op. Search a bit

Join beta channel. BTW buying an app doesn't mean it's gonna provide with updates for ever. You are just supporting the dev