yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] peterlee928:
post an idle dumpfile per the instructions in the linked post below

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] DB126:
You likely won't find this entry in your build.prop; simply add it to the bottom or appropriate section (eg: some files colocate radio and/or persist settings). No need to reflash factory image if it does not perform as expected; simply delete line and reboot.
[BetterBatteryStats] Oswald Boelcke:
Guess all necessary in that respect was already discussed between you and @Davey126 but a few comments from my side:

Fantastic endurance!

For modifications of build.prop, I personally always use the BuildProp Editor by JRummy Apps (actually I'm using the beta program version). However, Root Essentials has a good tool integrated, too.

I've never seen the netmgr wakelock on my device. Might be Pixel specific? Does it also occur in this amount when on WiFi? And how is the quality of your mobile data network?

Finally, I'd personally consider to disable the following services and check if you can get another .05% out of it:

com.google.android.gms.analytics.service.AnalyticsService

com.google.android.gms.chimera.PersistentBoundBrokerService

If something not working correctly, just re-enable.
[BetterBatteryStats] DB126:
As an alternative to disabling AnalyticsService I opted to block PackageMeasurementReceiver. The latter orchestrates Analytics collection while the former executes it. My choice was driven solely by idle performance vs privacy concerns. That said, I may look into your approach to see what performance and/or battery saving opportunities exist.

PersistentBoundBrokerService hasn't materiallized in my travels. What does that pup do and how does it manifest?
[BetterBatteryStats] Oswald Boelcke:
By my information, Chimera is a sort-of package management system for Google Play Services components, allowing Google to flexibly and independently upgrade each one. This is the reason why I personally try to disable it but it certainly depends on what to expect by Google.
[BetterBatteryStats] Lughnasadh:
I'm curious. What is an acceptable voltage per hour drop? On my logs its usually around 15% per hour. And what are the cures for a high voltage drop per hour?
[BetterBatteryStats] peterlee928:
wow got love from both [MENTION=5488402]Davey126[/MENTION] AND [MENTION=7408621]noc.jfcbs[/MENTION]? well sh*t n***o thats all you had to say! (pulp fiction reference... not me being racist lol).

noc - ill trying disabling those guys and see what happens. much thanks for the love! ? my data connection here is generally pretty solid... either lte or xlte. i dunno how much it occurs on wifi... will definitely look into that and provide an update.

davey - so i added that line into the build.prop, then rebooted. turns out it killed my mobile data, so i unfortunately had to delete that line. ive tried to kill packagemeasurementservice using MAT, but it always restarts itself. i havent figured out a way to kill it permanently. ☹️
[BetterBatteryStats] DB126:
Thanks - if that's the case I'm happy to leave it enabled. As you said expectation/preference driven.
[BetterBatteryStats] fossils-n-dents:
It's been my experience that 'Packagemeasurementservice', and it's broadcast brethren 'Packagemeasurementreciever', only restart upon reboot. I've had both disabled for days at a time using MAT Pro. Give that a shot, see what happens.
[BetterBatteryStats] peterlee928:
i recall my experience as similar. same with one of the analytics receivers.
[BetterBatteryStats] stuart0001:
With what? Those stats look pretty healthy.
[BetterBatteryStats] pikachu01:
You were probably sending an MMS which keeps failing thus waking up the phone at an interval.
[BetterBatteryStats] aashgaur:
i have the dialer and android system prob. !! other thn that .. evrythng is perfect !!
[BetterBatteryStats] tugler:
Well, may be you can help me too.

My awake Time is way to high and i can't find out why :(
[BetterBatteryStats] betoNL:
Well I am new at this but thanks to BBS I saw that Google services and its wake locks are avoiding phone to get into deep sleep, since that's a problem I am having no matter which kernel I try

If I freeze Google services framework and network location services ( with Titanium app), my phone is able to go into deep sleep again, but then Market becomes nonfunctional ....

Any tips?

Maybe something missing in the mod rom I am using?

Tks
[BetterBatteryStats] chamonix:
Screenshots are a bad idea, but please post a dump. A first look shows a high count on wifi but I'd like to see kernel wakelocks and alarms too before tell what the potential is
[BetterBatteryStats] chamonix:
Google Apps misbehave partly based on settings and partly on their own. Post a dump please
[BetterBatteryStats] chamonix:
That is pretty obvious looking at the partial wakelocks:

- you are using k9 with push on two accounts. You should check your k9 settings and maybe avoid syncing all folders (drafts show), think about poll or reducing the number of accounts

- your wifi is always on and causing an overhead

I suggest you take those statements and look them up in the dump in order to get used to read those. In your case everything is obvious and located in the partial wakelocks part

Fix those and repost a dump so we can check is there is more
[BetterBatteryStats] tugler:
Yes, K9 is listet on top, but the wake-time of K9 seems very low compared to the total wake time of the phone.

Turning W-Lan off seems to change nothing, i already tried, and it's usually off.

Is you can see on the screenshot of GB battery monitor, K9 is at about 2%. Beforehand i was using Gmail Push but it seems K9 is more efficient than Gmail which i turned off. K9 syncs 3 accounts and pushes only main folders like inbox. Gmail pushed all folders.

Everytime when I compare the GB battery monitor to BBS i can't see why the wake on time of the phone is 3 times the screen on time or even more as BBS shows for example K9 was on for about 6 min.

My interpretation of BBS is that my problem sits behind suspend and events/0 but i don't know what causes this high usage.

Counting all the wakelock times BBS shows me the time is << compared to GB battery monitor? May i misinterpret these times?

I'll add 3 pictures which shows what I mean.

(The jump in GB battery stats is a reboot.)
[BetterBatteryStats] betoNL:
Ok thanks

I will post a dump as soon as I am at home
[BetterBatteryStats] aashgaur:
heres a dump file !! :)
[BetterBatteryStats] betoNL:
Here you go... Thank you again....
[BetterBatteryStats] chamonix:
I must disagree. K9 sums up for for quite a few minutes, add svnet kernel wakelock to that (cause by network traffic) and you have one top cause.

FOr wifi I must disagree the same. If Wiki is off there is NO way that you get that high count of wifi partial wakelocks as they are cased by wifi being on.

Please take a consistent reading and post a dump, screenshots are not presenting the whole picture.

The processes that you mention are irrelevant as a cause for awake.
[BetterBatteryStats] chamonix:
===================
General Information
===================
Since 15 h 50 m 51 s
===========
Other Usage
===========
Wifi On (): 15 h 50 m 49 s (57049 s) Ratio: 100.0%
Awake (): 2 h 8 m 54 s (7734 s) Ratio: 13.6%
Screen On (): 1 h 34 m 1 s (5641 s) Ratio: 9.9%
Phone On (): 12 m 16 s (736 s) Ratio: 1.3%
=========
Wakelocks
=========
FacebookService (com.facebook.katana.Facebook): 6 m 37 s (397 s) Count:61 0.7%
WifiService (Android System): 2 m 50 s (170 s) Count:1322 0.3%
GTALK_ASYNC_CONN (Google Services): 2 m (120 s) Count:115 0.2%
AlarmManager (Android System): 45 s (45 s) Count:2248 0.1%
DhcpHandler (Android System): 42 s (42 s) Count:990 0.1%
Checkin Service (Google Services): 9 s (9 s) Count:456 0.0%
GTALK_CONN (Google Services): 7 s (7 s) Count:368 0.0%
keyguardWakeAndHandOff (Android System): 5 s (5 s) Count:1425 0.0%
ActivityManager-Sleep (Android System): 5 s (5 s) Count:2407 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:659 0.0%

I have left the important stuff so you can have a look and start understanding the dumps. Unfortunately your dump is not complete as references for kernel wakelocks and alarms are missing. Try to check that next time.

The potential we look at are 2 hours our of 15.

- Facebook is one known drainer and costs you 6 minutes

- leaving wifi on costs you a huge amount of wakelocks: 2000 wakelocks in sum: I suggest that you change your sleep policy to wifi off when screen off if the kernel wakelocks confirms rx wake

- the rest of the wakelocks are around latitude and maps. If you are using latitude you must know that it IS expensive. Not because location always is but because the implementation is poor. If your don't need latitude make sure to sign off and / or delete maps data. If you want to use latitude I suggest that you look into an alternate updater (ALTitude is one of mine) that are tuned for low energy footprint).
[BetterBatteryStats] chamonix:
This is an easy one, your phone did not sleep at all and it's amazing that you reached 15 hours with that:

Checkin Handoff (Google Services): 14 h 12 m 25 s (51145 s) Count:7 94.9%

Google checkin is the cause. That may be the product of different things:

- maps misbehaving

- you have automatic check-in enabled

- you checked in somewhere and the check-out got stuck

Whatever it is you should check maps, if you can't find the cause delete maps data from the "settings - apps".

After that is fixed post another dump so we can look at the stuff showing after your phone got healthy
[BetterBatteryStats] betoNL:
Well....I will remove MAPS completely as I always did on my sgs, since I use only ONBOARD GPS progs like Aura and iGo and NEVER Maps

But I have no idea what this check-in feature is...it belongs to which service/settings?

Grtz
[BetterBatteryStats] stuart0001:
I frequently get this error pop up for a split second and no stats appear until I reboot
[BetterBatteryStats] chamonix:
Well I can't exclude it's a side effect of freezing too much of the google stuff. Check-in is used by maps but also by google places.
[BetterBatteryStats] chamonix:
What ROM are you using?
[BetterBatteryStats] stuart0001:
Latest insertcoin ICS
[BetterBatteryStats] DB126:
Yep - many (but not all) Play Service receivers are started on reboot, Play Services auto-update and occasionally on other event(s) that I have yet to identify. MAT's Xposed module can block the restarts but is only certified to work on Android 6.x and below. I have yet to test it with Nougat+ using one of the framework forks.

---------- Post added at 07:07 PM ---------- Previous post was at 07:03 PM ----------

Thanks for the feedback; not surprising given the lack of sources (I only found two) and consistent with my original caveat. I normally wouldn't suggest such a change but felt confident you could recover if needed.
[BetterBatteryStats] peterlee928:
ahhhh xposed. miss that lil guy lol.
[BetterBatteryStats] charirma:
I have lenovo zuk z2 running resurrection remix 5.8.3 and in the past couple of weeks i experienced masive battery drain. according GSAM battery monitor it was because Kernel (Android OS) takes up 35% resources and according to BBS it was because android (i think its the same as Kernel (Android OS) on GSAM) wakelock takes up 40%, in the detail shows up Intent: *job.delay* and Intent: *job.deadline*, any solution this problem?? Thanks :)
[BetterBatteryStats] DB126:
The wakelocks presented are not problematic. Nor have you demonstrated any "massive" drain. Prepare and submit an idle log for analysis (guidance). Go from there.
[BetterBatteryStats] fossils-n-dents:
No Auto Update or Sync for me, I update apps manually. I'm on Play Services 11.0.3.8, and haven't noticed any reason to update the apk. I'm running Nougat, and MAT withstands reboot for 10 disabled 'Services', and 14 disabled 'Broadcasts' constantly in my device, with the exception of the two aforementioned services.

Life post-Xposed was rough at first, but the lack of Xposed for Nougat forced me to learn a little (A good thing), as opposed to simply loading a module. But, I do miss what appears to be pure genius by Rovo.
[BetterBatteryStats] DB126:
As you are likely aware there are forks of [MENTION=3283196]rovo[/MENTION]'s work available for Android 7+. Not a fan of such franken-frameworks but some have reported 'success' (roughly defined as working extensions on a stable device for an undefined period of time) with a limited suite of relatively simple modules. Only those fully comfortable recovering their device from boot hangs/loops and other unexplained weirdness should take the plunge. That said, fork maturities are improving; probably worth monitoring until an official variant becomes available.
[BetterBatteryStats] fossils-n-dents:
Desparation sometimes springs forth innovation, even in haste. However, I haven't the time for a possible device malfunction as I move about the world. My device hanging when I need it most is a very scary proposition. With my luck, it would be the issue that hasn't a solution yet.

I'll wait for Rovo, or at the least, give a large time span for these 'Forks' (Excellent term) to mature within their perspective forum(s) before I can experiment. Stability (Or at least a heavily stocked forum) is a must for me.

It took me one day to root/ debloat/ choose a rom/ kernel...and three months to get my device to idle drain at 0.3% h. That was enough nail-biting obsession for a while. Gonna enjoy my device as is...For now.:fingers-crossed:
[BetterBatteryStats] m0han:
i played around with the rom's alarm blocker and wakelock blocker. but....

https://pastebin.com/dSKQ8DJr. guys, please take a look. should there be such drain in flight mode?
[BetterBatteryStats] peterlee928:
pastebin site cant be reach for me.
[BetterBatteryStats] m0han:
this ok? http://www57.zippyshare.com/v/5pt7fceP/file.html
[BetterBatteryStats] peterlee928:
good to see the proxycontroller issue is no longer ?

overall, 0.5%/hr average idle drain rate isnt bad at all. if you did nothing from here on out, then no issue.

that said - whatsapp appears to driving your accelerometer crazy. some potential solutions:

1) go to settings, scroll down to accounts, tap on whatsapp. there you can turn off contacts synchronization, which may be causing the wakelocks. it should not interfere with your messages as this only syncs your contacts.
do check once in a while if it stays off as it may sometimes turn back on automatically. and you can sync contacts every once in awhile manually.

2) there is a setting in whatsapp that backs up messages daily. turn that off, and back up manually whenever you would like.

3) make sure you have the latest whatsapp installed.

i ended up deleting whatsapp - was a big battery drainer for me. and with so many phone plans offering unlimited texting, whats the point? but i understand some people need it for work or various other reasons (eg international contacts).

hope that helps. im sure others will provide more thoughtful insight.

---------

EDIT

i said there were wakelocks caused by whatsapp. not correct. the goal of my suggestions is to hopefully reduce some of the sensors caused by whatsapp. im not convinced they will as whatsapp will still keep running constantly in the background, but...
[BetterBatteryStats] githyanki:
.5%/hr is not bad, especially if you can achieve that in normal mode. There was nothing that stood out to me in your dump.
[BetterBatteryStats] m0han:
that's the problem; in normal mode it is >1% per hr. will keep checking. thanks.
[BetterBatteryStats] kevindd992002:
I'm very new to BBS and I'm confused with this article:

http://better.asksven.org/bbs-systemapp/

It says there's already a way to make BBS have the correct permissions for Android 4.4 and above without being rooted. But then there's this statement:

*** To circumvent this limitation I have implemented a helper system app that - when installed to /system/priv-app - gives BetterBatteryStats back the missing permissions. Unfortunately that means that root is a requirement starting from 4.4. ***

The last sentence of that statement contradicts the idea that you can run BBS with the correct permissions without being rooted. Can you explain more?

Thanks.
[BetterBatteryStats] DB126:
BBS is a mature app with many incremental releases over 5+ years. I have not kept track of non-root workarounds and their effectiveness. There is copious information from the author in the first half dozen posts with emphasis on #4 for devices without root permissions.

It's possible (perhaps likely) there is contradictory information floating around. That said, the developer does a pretty good job keeping the main posts up to date. Life changes; sometimes doc archives do not reflect the latest thinking... especially those penned years ago.
[BetterBatteryStats] githyanki:
Then your test south airplane mode indicates what is the best you can achieve without some serious tweaks.
[BetterBatteryStats] kevindd992002:
That's what I thought. I just wanted confirmation, is all :)
[BetterBatteryStats] chamonix:
Just to let you know that the distribution of BBS using HockeyApp is now out of its test-phase. You can register to participate in the test programme here:	https://rink.hockeyapp.net/recruit/e8a901e5d6a04e73a95c53b0fa21ab1a

Please note that this is a fast ring containing all builds that pass tests (I try to not go more than one build per day). You will automatically be notified when new builds are available.

And of course please let me know your feedback!
[BetterBatteryStats] peterlee928:
so i did another idle dumpfile last night with wifi on the entire time. granted it wasnt for 6 hours, but the netmgr wakelock did occur, albeit for much less time. oddly enough (or perhaps not), the idle drain rate was double that of when i was on mobile data. ?
[BetterBatteryStats] loginsvarios:
Phone never goes deep sleep

Hi, someone can help me?

My battery drains extremely high as the phone never goes deep sleep.

The weird thing is that it don't happens always, maybe 70% of the times after reboot.

-Extra Info-

• Phone: Mlais M7 Plus (MTK6753 64bit)

• Clean stock ROM (rooted with Chainfire's last stable SuperSU) with only some basic apps installed

• Sync and location services disabled

• Tried with 2 different batteries, same results

The manufacturer only released this rom and, as far as a know, there's no other kernel available to try.
[BetterBatteryStats] tslnox:
Hello guys,

I've got this weird problem where stats don't make sense - they don't correspond to nothing - and I can't figure out what's keeping the phone up.

For example now I have Awake (screen off) 20 minutes, 18%.

In Kernel wakelocks, apart from Display wakelock, I have PowerManagerService.WakeLocks 16 minutes,15%

qcom_rx_wakelock 10 minutes, 10%

But in Partial Wakelocks, there is a truckload of apps with exactly 1m 15s, 1%, and then another truckload of apps with 0%.

When I set the app to retrieve alarms and wakelocks using API, the stuff gets weirder. Summary shows Awake (screen off) 20 minutes, but in kernel wakelocks there is NETLINK 1 hour 11 minutes and some more - which don't even add up (I counted 202% of Kernel Wakelocks, what?!) Partial wakelocks are still this all 1% nonsense.

BTW, does anyone have any idea what is NETLINK wakelock? Google offers no info on that...
[BetterBatteryStats] DB126:
Try disabling (turn off) WiFi radio. Any better?

---------- Post added at 10:39 PM ---------- Previous post was at 10:34 PM ----------

Prepare and submit an idle dump consistent with this guidance. Go from there.
[BetterBatteryStats] fossils-n-dents:
Greetings Chamonix, I'm a big fan of your work!

All good so far. I have the paid version, but couldn't pass up the opportunity to try a new BBS. However, I could not locate the option to 'Install as System App'. It's probably not needed as an option anymore, but I just wanted to ask.
[BetterBatteryStats] DB126:
There is no longer a benefit to installing BBS as a 'system app' is noted in response to FAQ #3: https://xdaforums.com/showthread.php?t=1179809&p=15869904
[BetterBatteryStats] fossils-n-dents:
I didn't think so. My previous install was loaded as 'System'.

Thanks so much Davey126...Again.:good:
[BetterBatteryStats] loginsvarios:
What do you mean by "WiFi radio"?

I tried disabling WiFi connection (i.e. phone completely offline) but the issue persist.

If I can't solve this issue, my phone battery goes away doing nothing instead of going to deep sleep.

Please, any help will be welcome!
[BetterBatteryStats] DB126:
BBS dump exposes an EINT wakelock which typically occurs when the WiFi radio can not enter a low power mode (ie: sleep). There is also a prolonged spi_wakelock which has similar origins. The latest dump indicates with WiFi radio was enabled and active during the 4+ hour sampling window despite stating WiFi was disabled ("phone completely offline").

Does the phone behave the same way with airplane/flight mode engaged?

These are kernel (low level) wakelocks that typically can not be fixed via simple app tweak or ROM update. Possible indication of a corrupt kernel or hardware problem.
[BetterBatteryStats] loginsvarios:
No, no, that dumpfile is the original (with WiFi on).

Give some hours and I'll take another one with WiFi off.

Thanks for your help!
[BetterBatteryStats] TNSMANI:
Your phone was at an elevated frequency (1.04 GHZ) for most of the time instead of being at 299 MHZ. I could not find any reason for that in the dump, except what is stated by Davey126 above.

So, if your dump with wifi off is also going to be like the previous one, you may be stuck without any way out.

Anyway, I will wait to see your next dump before jumping to conclusions.
[BetterBatteryStats] loginsvarios:
Hello again.

Sorry for the delay, but this time I wanted to collect dumpfiles of my cell in all possible situations to provide more useful information.

Specifically I attach the following logs:

· WiFi On, with Deep Sleep

· Wifi On, without Deep Sleep

· Wifi Off, with Deep Sleep

· Wifi Off, without Deep Sleep

As you can see, the problem is intermittent.

Thanks again for continuing to help me with this.
[BetterBatteryStats] TNSMANI:
I think that you are stuck with 1% per hour whatever you do. While some alarms can be controlled with Greenify/Amplify, it is not worth the effort since that may not bring you any significant relief. On the other hand, you may have to deal with the ramifications of having these battery savers.

One thing that you may try is to limit the time that your wifi is running with the help of something like LeanDroid which may help to some extent.

I leave the field to the experts to comment further.
[BetterBatteryStats] loginsvarios:
The problem is that isn't 1% per hour. When the phone don't go deep sleep, it's more like 4%~...

So the battery lasts four times less that when it works as expected going to deep sleep (i.e. from a few days to not last one single day without it been used).

Also the problem sometimes appear when WiFi is ON, others when it's OFF... and sometimes the phone works OK either with WiFi ON/OFF as could be seen in the attached logs.
[BetterBatteryStats] DB126:
I tend to agree with [MENTION=5656100]tnsmani[/MENTION] whether it be 1% or 4%. This is not a well known device (at least on XDA) released in mid-2015 with few/no kernel and/or ROM updates from the manufacturer or 3rd parties.

Sleep is being blocked by EINT kernel wakelock which is almost certainly due to a hardware component not responding or failing to fall into a lower power mode. Spi-wakelock is also active during these sleepless periods.

WiFi radio has been identified as one potential culprit; fingerprint sensor has been mentioned elsewhere. You're going to have to experiment, tinker and use a bit of good old intuition until the offending component is identified. It then becomes a question of whether you can control/disable that component. You might also give some considering to rebuilding your device with a factory image. I tend to think that won't help but it may be your best option short of purchasing a new device.