yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] DB126:
Likely this pup is waking and/or holding your device awake - even when the screen is dark. Try reconfiguring/disabling to see if situation improves.

Also a number of minor network hits (below) that individually don't have much of an impact but collectively yield a restless siesta. Look for low hanging fruit (apps, settings) that can be quieted without lost of functionality. Don't get wrapped up in the Google stuff or trying to eliminate all network activity (fools errand). However, you might consider placing phone in Airplane/Flight mode for a few hours to see what impact that has on idle drain. Disabling WiFi will simply shift the load to the mobile radio which may or may not be more efficient.

======================

Network (requires root)

======================

10027 (Wifi) (Google Play services): 576.0 KBytes 40.4%

5018 (Wifi) (UID): 269.0 KBytes 18.9%

10087 (Wifi) (com.google.android.googlequicksearchbox.Google): 150.0 KBytes 10.5%

15010027 (Wifi) (Google Play services): 140.0 KBytes 9.9%

5010 (Wifi) (UID): 73.0 KBytes 5.1%

10244 (Wifi) (com.imgur.mobile.Imgur): 45.0 KBytes 3.2%

10129 (Wifi) (com.google.android.gm.Gmail): 28.0 KBytes 2.0%

0 (Wifi) (0): 22.0 KBytes 1.6%

10037 (Wifi) (com.samsung.klmsagent.KLMS Agent): 21.0 KBytes 1.5%

10050 (Wifi) (com.sec.spp.push.Samsung Push Service): 21.0 KBytes 1.5%

10148 (Wifi) (com.google.android.apps.maps.Maps): 18.0 KBytes 1.3%

5009 (Wifi) (com.samsung.android.scloud.Samsung Cloud): 14.0 KBytes 1.0%

1000 (Mobile) (Samsung DeX Home): 10.0 KBytes 0.8%

10280 (Wifi) (com.quoord.tapatalkpro.activity.Tapatalk): 9.0 KBytes 0.7%

15010046 (Wifi) (com.android.vending.Google Play Store): 6.0 KBytes 0.5%

10268 (Wifi) (org.thoughtcrime.securesms.Signal): 6.0 KBytes 0.4%

10357 (Wifi) (com.instagram.android.Instagram): 4.0 KBytes 0.3%

10262 (Wifi) (free.reddit.news.Relay): 3.0 KBytes 0.2%

10291 (Wifi) (com.whatsapp.WhatsApp): 2.0 KBytes 0.2%

1000 (Wifi) (Samsung DeX Home): 288.0 Bytes 0.0%

10273 (Wifi) (com.snapchat.android.Snapchat): 271.0 Bytes 0.0%

10246 (Wifi) (com.acmeaom.android.myradar.MyRadar): 239.0 Bytes 0.0%

10046 (Wifi) (com.android.vending.Google Play Store): 156.0 Bytes 0.0%

0 (Mobile) (0): 144.0 Bytes 0.0%
[BetterBatteryStats] peterlee928:
[MENTION=5950464]Haswell4200[/MENTION] 1 suggestion - if you do not use some/all of the samsung (or non-samsung) "bloatware", consider freezing or deleting them from your phone. you can use titanium backup (or similar apps) to accomplish this task. i had both the note 2 and note 3 - both phones saw noticeable battery life improvements after i removed all the samsung pre-installed apps. and unlike google-related apps and/or wakelocks, you can generally freeze/delete these samsung apps without losing overall phone functionality as there generally isnt any cross-functionality between samsung apps and non-samsung apps.
[BetterBatteryStats] DB126:
A couple of worthy (and very powerful) alternatives:

- MyAndroidTools

- SD Maid

With exceptional power comes exceptional responsibility (if unsure ask before acting; better than looking down the barrel to see if the fella is loaded). There are many other fine choices with no favoritism given to the above or those previously mentioned. Find what works best for you. :)
[BetterBatteryStats] coolvabs:
Any help on the no stats issue will be greatly appreciated. Screenshot attached for reference
[BetterBatteryStats] coolvabs:
Duplicate post..
[BetterBatteryStats] peterlee928:
search this thread. there are solutions that have been stated previously.
[BetterBatteryStats] Haswell4200:
I'm going to try again tonight with the phone facing down and see if it makes a difference. Also, where would you recommend starting with the network apps? I can't seem to change many settings. I don't have root either (s8) it seems like Google play is taking up a lot of juice doing nothing.
[BetterBatteryStats] peterlee928:
i am not familiar with how the always on display ("aod") works as i have never used an s8. but see this link for disabling aod if that is your desire:

https://www.google.com/amp/s/www.go...-disable-the-galaxy-s8-always-on-display/amp/

depends on which apps you use and what you use your phone for. personally, i never used any samsung apps when i had samsung phones. so i disabled all samsung apps.

without root, my recommendation to use titanium backup ("tibu") is irrelevant as tibu requires root. see very bottom of my post for link to root s8.

you can instead go with [MENTION=5488402]Davey126[/MENTION]'s recommendations of myandroidtools ("mat") or sd maid to disable system apps.

if you choose mat, see linked thread below on how to nullify some google play services using mat. start with op.

https://xdaforums.com/oneplus-3/how-to/guide-stop-google-play-services-t3549760/post70853146

as [MENTION=5488402]Davey126[/MENTION] said - mat is powerful but dangerous. and trust everything that [MENTION=5488402]Davey126[/MENTION] (and [MENTION=7408621]noc.jfcbs[/MENTION]) says cuz they have forgotten more about this stuff than most of us mere mortals will ever know.

i believe that, if you change settings using mat, simply deleting the mat app from your phone will not restore prior settings (someone please correct me on this if i am mistaken). so be VERY CAUTIOUS on which apps/receivers you disable and knowing which apps/services you need. it is always recommended to back up EVERYTHING prior to doing something like this so that you can restore you phone to its prior state if something goes haywire.

additional suggestions/tips that may or may not help:

-go to your location settings and make sure that wifi scanning is off

-go to your google account in settings and shut down some of the syncs if they are on and you dont need them to sync regularly

there are threads that outline how to shut down nearly all google play services functions. the caveat is that those people dont use google apps or find workarounds (eg alternative app for gmail). if you desire that, happy to share those threads with you.

however, i recommend you start with aod (and other steps previously mentioned) and see what your battery drain is thereafter. no sense in chopping off both your legs for a sprained ankle.

---------------

in case you decide to root your s8:

https://www.google.com/amp/wccftech.com/root-galaxy-s8-cf-auto-root/amp/
[BetterBatteryStats] Haswell4200:
In your opinion, is it worth doing this? How much battery will I potentially gain if I can slim everything down?
[BetterBatteryStats] peterlee928:
doing what? what is "this"?

my only recommendation (based on [MENTION=5488402]Davey126[/MENTION]s brilliant detective work to catch the "bad guy") was to disable aod and assess battery drain thereafter. all upside/no downside - if you dont like the functionality of aod being off, you can easily switch it back on with no negative repercussions to your os (based on my high-level read of this app).

not trying to be evasive or standoffish. but lets take a step back - its your phone... only you know what functionality you need/want from your device. it is difficult for me (or others) to proffer an opinion on next steps as i (nor others) dont know any specifics on what you need/want from your phone.

your dumpfile exhibits slightly above average but not unreasonably high battery drain... and very much all to the good if you are satisfied with the phones current functionality.

fair question, but i couldnt say. if you disable apps step-by-step, then you will be able to measure battery drain after each step to assess savings (if any)... assuming you maintain a static operating environment.

i will quote the main tenants of this thread - go with the 80/20 rule... and less is more.

sorry if i confused you by throwing us down a rabbit hole in referencing the disabling of system apps ☹️ bad habit that i have of providing unsolicited recommendations.
[BetterBatteryStats] Oswald Boelcke:
MyAndroidTools (Pro) and SD Maid (Pro) also require root to perform this functionality!

Without root, you simply have to live with bloatware and company induced behaviours.
[BetterBatteryStats] peterlee928:
ah thanks for the update! thought myandroidtools wasnt a root-required app. in retrospect, doesnt make much sense. :silly:
[BetterBatteryStats] Haswell4200:
Well this might help shed light on how much power aod is using. This log is for the phone being upside down all night with aod enabled.

EDIT: never mind. This log looks messed up. I think adb permissions got screwed up. I'll try again.
[BetterBatteryStats] DB126:
Yes - but not all preinstalled apps are installed in the system partition. MAT will only prompt for root permissions when needed. I believe SD Maid prompts at app start but will continue to function with limited capabilities if root access is not available. That said, [MENTION=7408621]noc.jfcbs[/MENTION] is spot on regarding the consequences of not having root access for the vast majority of preinstalled apps.
[BetterBatteryStats] j1gga84:
Sometimes I have BBS errors in the log. What could cause them?

And why are partial wakelocks not displayed correctly anymore? I am running RR 5.8.3, device is a Samsung Galaxy S5 (G900F - klte)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[BetterBatteryStats] Oswald Boelcke:
Simultaneously, you posted a MatLog screenshot in the Kernel Adiutor thread, too, with a possible issue with KA.

Couldn't it now more being on issue with your ROM or kernel. Did you already try to just dirty re-flash your ROM to check if both issues persist?

Affirmative, without root both applications provide limited functionalities and services. I believe they are both "must have" even on non-rooted devices.

And I see the marketing and operations strategy by moth companies to try to void a warrenty in case of a rooted device. This strategy seems to work pretty good as many people owning new and especially expensive devices fear to root and to trigger a counter. And what are you going to do when the boatloader is locked - and can't be unlocked?
[BetterBatteryStats] DB126:
I only own one device (Fire 7) with a locked bootloader as the ability to openly unlock the bootloader is a purchase prerequisite. The Fire 7 was an exception given ridiculous price point and disposibility should something go wrong. I've deployed several in 'high risk' environments. The locked bootloader restricts the choice of ROMs but does not block kernel tweaks or full root access. Not much of an impediment given use case. Can even boot (but not install) a custom recovery from fastboot on some early firmware builds.
[BetterBatteryStats] Oswald Boelcke:
@Davey126, @peterlee928: Friends, may I politely ask for your expertise if time permits.

Please have a look into these BBS dumps in this post. I'd really appreciate an answer in this thread.
[BetterBatteryStats] DB126:
Yikes - second dump (idle w/network connectivity) shows a number of anomalies with elevated wake time, CPU use and overall drain rate. Some of this is likely due to age of hardware and component/kernel capabilities. But you should be seeing better. Suggest a cold star and resample of this device configured in the same mode to obtain a clearer picture of what may be causing the drain.

First dump (idle; no network connectivity) looked fine; I didn't open the in use dump for reasons noted above.

Curious, are you capping CPU frequencies during sleep, either via aggressive governor tunings or hard limit?
[BetterBatteryStats] Haswell4200:
Okay here's a log with the screen down. It seems like it was less active. What do you guys think?
[BetterBatteryStats] Oswald Boelcke:
Thanks very much in deed for your insight. Affirmative, the device is pretty mature but overall running very smoothly with RR. The built-in kernel doesn't offer too many capabilities but that's acceptable. Governor is zzmoove, profile battery yank extreme. Max freq is set by me to 1,000 MHz, min = 200. No specific settings for sleep.

I'll have a look on it, maybe I first try a different governor profile.
[BetterBatteryStats] DB126:
Looks good for an unrooted Samsung device running Android 7.0. 0.4%/hr idle drain is respectable for any device, especially stock. Enjoy your S8 as-is assuming you can disable the active screen functionality; nice phone.

---------- Post added at 02:44 PM ---------- Previous post was at 02:29 PM ----------

Never been big on governor "profiles" as most overmanage CPU states leading to unnecessary overhead/drain rapidly switching frequencies, especially with older hardware. But I understand their appeal - albeit probably oversold. I stick with the lowly interactive governor, sometimes with modest tweaks, depending on the device and how it is utilized.

I also find capping CPU frequencies counterproductive to performance and battery endurance unless heating or other factors come into play. That said, I'm not familiar with the voltage curve/tiers for your device. If there is a significant spike over 1GHz then it *may* make sense to cap. Limiting frequencies at the low end is a fool's errand as the voltage curve is often flat for the first few CPU levels.

You might want to consider a different scheduler if lag is an issue; I like the simplicity and low overhead of deadline. A small write delay can be beneficial in some use cases although I typically don't recommend that (over tweaking).
[BetterBatteryStats] Amcray_86:
I didnt decide my problem connected with kernel wakelock (7000000.ssusb). I have tried to reflash, wipe dalvick cache , wipe data.

I have find in dmesg wk:dwc3_otg_sm. Do you know how decide it?

dmesg: dropbox.com/s/2w7zxp0ua9s7lgg/dmesg-2017-07-26_230459010.txt?dl=0
[BetterBatteryStats] peterlee928:
dump 1 thoughts:

1)overall looks very solid at 0.2%/hr

2) one thing i noticed is that several (seemingly unrelated) wakelocks/alarms all ran for almost exactly the same time... what might be the cause of that?

3)very nitpicky (and likely not meaningful): perhaps using my android tools to shut off wearable service (assuming you dont use a wearable... if so, of course disregard) and google analytics service

dump 2 thoughts:

1) microg services core - https://www.google.com/amp/s/xdafor...core-floss-play-services-t3217616/page76/amp/

this person also experienced alarm issues with microg (albeit different rom). of note:

"Seem to me that "microG Services Core" is affected by the Mobile radio active bug that causes a big battery drain in Android ≥ 5.x and for this motive I switched back to cm11 in which microg works without problems."

makes me wonder if rr rom and/or kernel is the root cause...

2) alarm_rtc kernel wakelock - https://www.google.com/amp/s/xdaforums.com/galaxy-nexus/help/kernel-wakelocks-t1558292/amp/

has general instructions on how to find the cause

3) wlan kernel wakelocks - https://androidforums.com/threads/battery-saving-tip-really-works.563008/

4) mdm_hsic_pm0 kernel wakelock

one potential charging-related solution here: https://xdaforums.com/showthread.php?t=2574255&page=3

one potential kernel-related solution here: https://xdaforums.com/showthread.php?t=2221395&page=2

generally speaking, my research on this concludes that: (a) there arent any definitive solutions to this; and (b) it is somewhat of a necessary evil short of leaving your phone in airplane mode... which doesnt make much sense.

5) taking a step back - there were a ton of *alarm* and *launch* wakelocks. v7 (forum moderator for one of these battery-saving threads) stated that they appear in all custom roms >5.x and they do not drain battery.

that said, see post from yever on a possible solution:

https://xdaforums.com/redmi-note-3/help/od-alarm-launch-wakelock-t3470264

---------- Post added at 01:09 AM ---------- Previous post was at 01:02 AM ----------

i mean this sincerely and in no way trying to be offensive... but i do not understand your question. can you please reword?
[BetterBatteryStats] Oswald Boelcke:
WOW! Speechless and thankful. I'm very grateful for all the time you took to have a look into the dumps and the advices you gave. I'm definitely going to walk through them step by step.

Meanwhile I decreased the drainage by 0.1%/h and Awake (Screen off) by 1.3% by simply greenifying Conversations and taking it back into battery optimisation. It was just a try because as expected Conversations wasn't anylonger connected to the jabber-server while screen off. I just wanted to know how much Conversations affects the battery. As I require Conversations 24/7, it's back again non-greenified and non-battery-optimised.

I'm now talking all your and @Davey126's advices to see if and how I can achieve more. Started already by setting the max-CPU-freq back to 1400, I've never changed the min freq anyway. I'll certainly keep you informed; maybe others can benefit from these test flights.

Yes, but this is in all the dumps of both i9305. I'm pretty much convinced it's Resurrection Remix and/or kernel related. It first occured after an upgrade of a RR-MM-version and hasn't changed since then, also not with RR-N. I know I've to live with it, and that these lines not really provide good information.

No, not using any wearable. But I'm going to step through MAT again. I'm nearly convinced I disable all analytics services already but need to check the wearables.

Thanks very much again for your efforts!:D:good:
[BetterBatteryStats] Amcray_86:
Sorry for my english) What can you say about the log(dmesg) : dropbox.com/s/2w7zxp0ua9s7lgg/dmesg-2017-07-26_230459010.txt?dl=0 ?
[BetterBatteryStats] peterlee928:
no apologies necessary.

cant say much, unfortunately. if you are still experiencing elevated battery drain and are trying to find the reason(s), please post a proper idle dumpfile. see the linked post that i sent you previously for instructions.
[BetterBatteryStats] BARGORESC:
Lgg3 battery drain

https:// ibb.co/cBJJLQ

https:// ibb.co/kwpfZk

https:// ibb.co/ga0XfQ

https:// ibb.co/h1eQ0Q

https:// ibb.co/fr6G75

https:// ibb.co/fHQyLQ

https:// ibb.co/mwEfZk

Better battery stats

uploadfile.pl/pokaz/1167902---golg.html
[BetterBatteryStats] peterlee928:
your screen on time was 23 minutes. please submit a proper IDLE dumpfile per these instructions:

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] facemob:
i have a question. Hopefully the answer is simple. I can charge my phone to 100%. I take it off the charger and start using it and with in 10 minutes the phone shuts off. The battery will read anywhere from 98 to 95 percent. Then i have to plug it in to the charger to turn it on and the battery will read 88%. So does this sound like a bad battery?
[BetterBatteryStats] DB126:
Yep - classic symptoms.
[BetterBatteryStats] facemob:
Awww man... thanks man. i was hoping it was software related but i guess my nexus 6p has bit the big one.
[BetterBatteryStats] DB126:
https://m.youtube.com/watch?v=spz9S5aIiJg
[BetterBatteryStats] facemob:
Also another thing is if i leave the screen off the battery will drain but the phone wont shut off. it only shuts off if the screen is on.

---------- Post added at 09:18 AM ---------- Previous post was at 09:13 AM ----------

this video is intense.
[BetterBatteryStats] DB126:
Screens draw a lot of power - far exceeding any other component.
[BetterBatteryStats] facemob:
Thanks. I understand better now
[BetterBatteryStats] githyanki:
Does it happen on stock also?

Probably a bad battery, but a bad rom / kernel compatability could cause weird things to happen.
[BetterBatteryStats] facemob:
I haven't tried stock yet. But I'm running the pure Nexus rom with the elemental x kernel. From what I've read it's compatible
[BetterBatteryStats] peterlee928:
thats a pretty common combo. you may want to pose the question on the purenexus or elementalx thread as well if you havent already. just to double check. (i know its taboo to do multiple posts of the same question, but...)

but [MENTION=1631192]githyanki[/MENTION] brings up a great point - cant hurt to see if the issue persists on stock. if it does and your phone is under warranty, you may be able to relock your bootloader, unroot the phone, and exchange for a new one. (this assumes that you havent tripped knox on your phone, if that is relevant)
[BetterBatteryStats] facemob:
I haven't tried looking thru the elemental x forum. But in the pure Nexus forum it states that rarely do ROMs effect battery life in such a manner. But I will look thru the elemental forums tho just to see.
[BetterBatteryStats] peterlee928:
cant hurt!
[BetterBatteryStats] DB126:
Chasing your tail my friend; ROMs and kernels don't exhibit the behaviors you describe (details matter). Take a peek at voltage drop in BBS dump just before phone shuts down. Suspect it will be rather dramatic. But hey, if battery replacement is not an option flashing another ROM and/or kernel can't hurt. Be sure to keep the sucker plugged in to a high output power brick during the install so you don't end up with a corrupted device. Most USB ports on laptops/PCs can not deliver enough juice to maintain the battery during screen on/high intensity operations.

Outside chance there is another hardware fault (eg: erratic/overheating voltage regulator) but that seems highly unlikely.
[BetterBatteryStats] facemob:
Yeah that's what I believe. But since I haven't looked I will for personal knowledge. But as you said I'm chasing my tail. And I agree.
[BetterBatteryStats] githyanki:
I do have issues with my phone shutting off at lower levels with any other kernel than stock. I guess their governors are more aggressive or something I never really tried to get it right, I just stay on PN stock kernel. It is at least than 30% though, not nearly full like your experiencing. It should be easy enough to try out PN stock kernel for awhile to test that if you want.
[BetterBatteryStats] ajamxar:
"To" reference not showing up

Hey!

In the "from" reference, I can see Screen off, but in "to", only "Current" is shown. Is this normal and sufficient for creating the dump file?:confused:

PS: I know the time is not enough, but I just wanted to be sure I'm doing it right.
[BetterBatteryStats] githyanki:
Will be fine, just make sure screen on time is less than 1 minute.
[BetterBatteryStats] BARGORESC:
uploadfile.pl/pokaz/1169029---6dhd.html
[BetterBatteryStats] DB126:
While fine better (and ultimately easier) to use procedure in this post. Results will be more accurate and no worries about screen on time.

Direct link:

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] Sam Nakamura:
Maybe it's just an issue on my end but opening the link you posted results in this...

PS: coincidentally reading this with interest in what you actually meant :) even deleting the "http://xn--https-nw3b//" part gives no results
[BetterBatteryStats] DB126:
Wow - have no idea why XDA labs app (or XDA back end) is munging the imbedded reference. I amended my post with a direct URL link.
[BetterBatteryStats] ajamxar:
So, I let my phone down yesterday night, and woke up after around 9 hours without touching the phone. Yet, when I checked, it shows 20 mins SOT.

Also, the standby drain is pretty bad, and I'm not able to figure out what the issue is... :(

Attaching the dump file. Could someone pls help? :crying:
[BetterBatteryStats] peterlee928:
your main culprit is this:

ssr (wcnss): 5 hr 58 min 24 sec 100%

unfortunately, i do not know what the cause of this bad guy is. hopefully one of the smarter folks here will provide some helpful insights.

----------

also:

bam dmux - this thread provides some background on this wakelock along with potential solutions to reduce its occurrence: https://xdaforums.com/showthread.php?t=1811365

i noticed the radio interface wakelock was high but dont think this is an issue. but others may have more insight on this.

sorry i couldnt be of more help.
[BetterBatteryStats] DB126:
Too much going on to isolate root cause(s); looks more like an active dump... which it was. Reboot and see if it reoccurs. If pure idle drain is greater than 1%/hr submit another dump for further analysis.