yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] DB126:
Device slept for ~1 hour (20%) during 5 hour monitoring window; should be 95% or better. No obvious red flags in dump. Observations/thoughts:

- unfamiliar device, kernel and ROM; not a lot of historical data

- try clearing Google Play Services cache/data followed by a reboot

- noticed bet365 app was active; possibly blocking sleep (long shot)

- same for bluetooth

- suggest consulting device forum/thread to see if others have experienced similar problems: https://xdaforums.com/le-pro3

- can only react to what's shown in log; possible BBS isn't seeing everything
[BetterBatteryStats] prosnz:
thanks. As I can see here you get nothing out of your work? Is there anyway to donate?
[BetterBatteryStats] fastguy:
A note about disabling "high accuracy" location provider. I take pictures and when I do, I set the camera app to insert the location info in the Metadata. This I'm using in the future when I'm looking for pictures on a specific place (I don't need that much accuracy, village level would be enough).

If we limit to GPS, and since GPS won't provide a location in a few secs that I'm taking the picture, that would mean I'd lose the location info, right?

Any ideas?
[BetterBatteryStats] DB126:
Na - but thanks for the kind words. :)

---------- Post added at 05:18 AM ---------- Previous post was at 05:15 AM ----------

One of many examples where high accuracy (ie: leveraging Google's location services) is appropriate despite the modest increase in battery drain. All else being equal never sacrifice functionality for a few extra mins of run time. The device is there to serve you.
[BetterBatteryStats] House_of_Ka-el:
Thanks for your time.

I followed your suggestion and went a bit more.

I entered my recovery and wiped Dalvik & Cache and I also cleared Google Play services data & Cache as well and rebooted my device.

The results were better this time around.
[BetterBatteryStats] DB126:
Typical results for an Android 7.x based ROM. Device idled at low frequencies for most of the 6m wake time. Common background drainers are present but not worth reigning in IMO. Enjoy your devices full functionality and reasonable idle battery life.
[BetterBatteryStats] peterlee928:
hi all. would it be possible to provide any feedback on the idle log in the link below? from my novice review, nothing jumps out as problematic. but figured it couldnt hurt to get the expert opinions. much thanks in advance.

https://www.androidfilehost.com/?fid=673368273298968713

note: idle log was prepared in accordance with the directions in this link:

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] j1gga84:
In my opinion there is still a lot to do for LOS because android still holds the device awake alot.

When I go to battery statistics it says that OS System is on second place, about 10-12% after one day which is, compared to MM, a bit high for my taste.

I think it must have something to do with wifi because when I check the alarms in Better Battery Stats 'android' is on first position with a high percentage.

There are a lot of entries regarding wifi, such as SupplicantWifiScannerImpl Background Scan Period, WifiConnectivitiyManager Schedule Periodic Scan Timer, WifiConnectivityManager Restart Scan, WifiConnectivityManager Schedule Watchdog Timer and something like DeviceIdleController.light (I think this is the Doze feature, is this really good for a better battery lifetime?)

What can I do to improve/reduce the wifi wakelocks?

thanks & regards
[BetterBatteryStats] DB126:
You will need to submit an idle log for an analysis of your individual situation. Reported wakelocks and small amounts of wake time are less important on modern devices that idle efficiently while performing routine background tasks. Big drainers can usually be tracked down and squelched using native tools. Trying to manipulate Android's power management at a detailed level usually bares little fruit and is considerable more difficult on Nougat given lack of Xposed framework.

As for WiFi wakelocks:

- disable scanning

- toggle location services to 'device only'

- try setting a fixed IP address (on device)

- insure AP/router is not broadcasting on a congested channel

---------- Post added at 11:16 AM ---------- Previous post was at 11:00 AM ----------

Well prepared dump. :)

Pretty standard Nougat log; no red flags. 2% mid-cycle loss over 6 hours (~0.3%/hr) is respectable for this device. Wake time could be reduced by disabling PackageMeasurementService within Google Play Services which is a collection and reporting component of Firebase Analystics. However, it will automatically reenable itself on boot and periodically between restarts. Such behaviors could be blocked with Xposed; obviously not an option on Android 7. That said, actually battery consumption is trivial. Wake time does not always equate to high power draw depending on device, kernel and rom; this is one of those examples. You'd probably see the exact same loss rate 9 runs out of 10. My advice: leave it alone.

Footnote: There are other threads that promote a more aggressive approach to blocking Firebase Analytics. Makes no difference; nailing the above service stops 95% of battery draining activity...which is still trivial in the grand scheme of things that can tap power as previously noted.
[BetterBatteryStats] fossils-n-dents:
I agree wholeheartedly with you Davey126, peterlee928s' idle log was a joy to read. No need for him to go a step further while running Nougat.

I too had given in to the more 'Aggressive' threads and disabled multiple Google Play Services services. Ultimately, they provided no more relief to my battery than avenues I previously explored. I found no matter what configuration I concocted, I could never get my devices' battery to drain lower than 0.3 h. I think 0.3 h is as good as it gets without Xposed.
[BetterBatteryStats] 'Akira:
So, after about 12 days, I still cannot get my kernel wakelocks stats. I even tried to enable the "Kernel wakelock using API" option in "Advanced", but had no success.

After analysing my logcats, I identified a process that constantly pops this warnings/errors:

07-03 21:11:05.695 E/QCOM PowerHAL(1241): Failed to acquire lock

07-03 21:11:06.233 E/BatteryStatsService(1241): no controller energy info supplied

07-03 21:11:06.242 E/KernelWakelockReader(1241): neither /proc/wakelocks nor /d/wakeup_sources exists

07-03 21:11:06.244 W/BatteryStatsImpl(1241): Couldn't get kernel wake lock stats

Can anyone help me diagnose this?
[BetterBatteryStats] peterlee928:
much thanks ?

yes i tried disabling packagemeasurementservice. but as you noted, it automatically re-enables itself. i wonder why that happens with this specific receiver...

i agree with your approach - less is more. the more i screw around with disabling receivers and the like, the more my phone seems to run into issues. i now try to take a pretty minimal approach. and if you say im in a decent zone... boom.

this is all i do to my phone... gives me the battery life from my earlier dumplog.

https://www.androidfilehost.com/?fid=673368273298967963
[BetterBatteryStats] DB126:
Interesting to observe the dozens of receivers and internal services enabled by Google Play Services shortly shortly after boot (and periodically thereafter). Guessing these are Google's bread and butter. A far greater number are left alone.

Thanks for sharing your action list. I do even less blocking. An app or service pretty much has to demonstrate it's a bad actor before it receives 'special' attention. Of course, I have a short list of stuff that gets impulsively whacked regardless of behavior because there is no reason they should auto-start or remain in memory (eg: media and content consumption apps). Trick is not to get obsessed with micro-managing every app/service.
[BetterBatteryStats] iamnotkurtcobain:
This isn't normal right? The Chronus wakelocks...
[BetterBatteryStats] DB126:
Well...you have one of these installed so yeah...expect associated wakelock activity. Presence doesn't mean good or bad. The app is simply doing it's job. Don't like it? Uninstall.
[BetterBatteryStats] fossils-n-dents:
Ha! Funny how two different approaches (The common thread being the OnePlus 3 OP), yielded similar results.

My actions were borne of 3 months of late night, after work fanaticism (As evident by the overkill in my action list), and yours is a calmer, gentler attack. 'Minimal' is also a common theme between us. Careful app selection is a must. One false move, and Andriod OS, or Google Play Services will crush you.

For my setup, Greenify 'Aggressive Doze' was not aggressive enough. I used only Shallow Hibernation/ Automated Hibernation as one layer, and let ForceDoze handle the Doze mode and sensor killing layer. Very unscientific, but effective. Greenify alone yielded unpredictable results for me. You made it work.

I do not 'Optimize' Greenify, ForceDoze, nor MyAndroidTools, as I could not be sure if Doze mode weakened their effectiveness. I noticed my disabled apps do not hold wakelock, but they get updates...grrrrrr. I also used to re-enable 'Packagemeasurementservice' every day on principal alone. Ultimately pointless, I gave up.

https://www.dropbox.com/s/mcx2e7d2afl21qj/Untitled 1.pdf?dl=0

Well played peterlee...well played indeed. You're making me rethink my long-winded process. Cheers!:good:

"Less...is...more" -Davey126
[BetterBatteryStats] peterlee928:
i think youre spot on regarding app selection. especially with the efficiency apps eg forcedoze, naptime, lspeed, etc. my main issue was that these apps were doing too good of a job. mainly i stopped getting notifications (eg email) despite "unoptimizing" those specific apps and setting notification levels to max importance.

so i went the opposite direction and minimized the efficiency app settings. just to test whether doing so would yield similar/better battery life while not killing apps that i wanted to do their job.

and as always, davey126 was spot on. nougat is pretty efficient on its own. and less work for me to tweak settings. win-win. ?

sounds like you have a good setup also though. ??
[BetterBatteryStats] Andiii:
in the past (Android 5.x) i did things like this with tasker/LLama/Locale - to switch on location services and turn on High Accuracy profile for the time the camera is active.... Don't know if its still working with Android 7.x (since 6.0 came all the rights management etc.) but you might give it a try.
[BetterBatteryStats] Danilo-Sanchez:
Could someone please take a look at this dump file to see if it is in the right format and if yes please tell me what is causing battery drain here.
[BetterBatteryStats] peterlee928:
unfortunately your dumpfile is not in a useable format.

see link below for step-by-step directions on how to make a proper dumpfile:

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] Danilo-Sanchez:
Thank you for your reply!

I'll see the instructions and make another dumpfile tomorrow ;)
[BetterBatteryStats] m0han:
... please take a look at this dump file and tell me what, apart from rank bad cell signal, is causing battery drain here. no gapps. any way i can improve 'battery times'? thanks, everyone.

http://cloud.tapatalk.com/s/595dd77248da9/BetterBatteryStats-2017-07-06_063334167.txt
[BetterBatteryStats] peterlee928:
This is not the required idle dump. See:

Screen On (): 2 h 24 m 14 s

Suggest to take a dump in accordance with the link below.

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] m0han:
you're right. my bad. although i'd set custom ref., i forgot to save dump as custom to current.
[BetterBatteryStats] Danilo-Sanchez:
Could you please take a look at this dumpfile to see what is draining my battery?
[BetterBatteryStats] peterlee928:
lol ok not to sound like a huge ahole... but seriously - 22 seconds??? i mean f**k if you even read 2 posts above, you would see that i linked a post that has detailed instructions from the master davey126 on how to do a proper dumplog. lol try again homey. :)
[BetterBatteryStats] Danilo-Sanchez:
I did what was in the instructions, the problem is that I didn't open BBS as soon as I woke up in the morning. I used the phone for a while and later I remembered to save the dumpfile lol.

I know that this isn't the right dumpfile, but I have one of 21 hours.
[BetterBatteryStats] peterlee928:
please read the post from davey126 that i linked above and submit a dumpfile according to those instructions. the main issue with the second dumpfile is that the screen was on for over 52 minutes. you must leave the phone alone. full stop.
[BetterBatteryStats] Danilo-Sanchez:
[MENTION=6089972]peterlee928[/MENTION] I think this time I got it right. Could you please take a look at it?
[BetterBatteryStats] peterlee928:
:good: i will leave it to the smart folks to analyze your dumpfile
[BetterBatteryStats] m0han:
'screen off to screen on' didn't come out well. signal continues to be bad. please take a look and suggest remedies. thanks.

[MENTION=5488402]Davey126[/MENTION]. http://cloud.tapatalk.com/s/595f4324af334/BetterBatteryStats-2017-07-07_060144858.txt

http://cloud.tapatalk.com/s/595f43411fb92/BetterBatteryStats-2017-07-07_060036378.txt
[BetterBatteryStats] peterlee928:
the second dumpfile is irrelevant.

the first dumpfile is also no good:

Screen On (): 20 m 28 s 4.7%

screen on time must be less than 1 minute.

please re-submit a proper dumpfile according to the directions in davey126's post that i linked.
[BetterBatteryStats] birdie:
-- delete --
[BetterBatteryStats] peterlee928:
your dumpfile cannot be opened in its current format. change it to a .txt format.
[BetterBatteryStats] birdie:
Both WinRAR 5.4 and 7-zip 17.00 open it just fine.
[BetterBatteryStats] pjadec:
Sorry but your log is wrong

Screen On (): 1 h 46 m 1 s 7.3% this should be under 1min, better below 30 seconds

read op again and do as instructed
[BetterBatteryStats] TNSMANI:
Firstly, your wifi was on and running the entire time. Tame it. Also ensure that wifi and BT scanning are disabled in Settings>Location>Three Dots Menu. The phone was awake for nearly 2 hours which is too high.

You also have some wifi connection issues. If your router has not been restarted for quite some time, do it now. If not, try assigning a static IP for the phone.

Though you also have some alarms, on Nougat, there is no way to control them, to my knowledge.

So your issue mainly rests on wifi.
[BetterBatteryStats] m0han:
what i did:

due to power outage, i could charge only till 97%. then used phone till 94%. thereafter, no touchy! seeing my first save was no good, i saved unplugged to current. maybe i should've saved dump for custom to current.
[BetterBatteryStats] DB126:
Should have saved 'screen off' -> 'screen on' assuming device was not in use while being charged. You can do this anytime prior to the next screen off event.
[BetterBatteryStats] Javi22:
If someone is so nice to analice mi stats... I'm running Resurrection remix on mi5s and I get much worse battery than the others...

https://www.dropbox.com/s/59zo4oxbs5u8lvv/BetterBatteryStats-2017-07-07_192149359.txt?dl=0

Enviado desde mi MI 5s mediante Tapatalk
[BetterBatteryStats] peterlee928:
this is an invalid dumpfile:

Screen On (): 1 h 38 m 27 s 15,1%

screen on time must be less than 1 minute.

see link below for step-by-step directions on how to make a proper dumpfile:

https://xdaforums.com/showthread.php?t=1179809&p=72467976
[BetterBatteryStats] Javi22:
Thanks mate, I forgot that, sorry

Enviado desde mi MI 5s mediante Tapatalk
[BetterBatteryStats] peterlee928:
noob questions:

1) "... your wifi was on and running the entire time..." - how does this run down the battery? i thought battery drain with respect to wifi connectivity (or lack thereof, as it were) occurs when the wifi is on but isnt able to connect, so the phone continues to do work trying to connect to a wifi network that isnt there.

2) understand about the scanning issues. been a victim of it myself.

3) how can you tell that there are wifi connectivity issues from reading the dumpfile?

much thanks in advance :)
[BetterBatteryStats] Danilo-Sanchez:
1) Wifi never had so much impact on battery life for me before on the same SSID.

2) I always disable wifi scanning

3) Good question. I also want to know about that.

I want to know if there is some "best config" to do in the router to make wifi work better.
[BetterBatteryStats] Cozmos23:
Hey guys I have a big problem my phone doesn't enter deep sleep and is going crazy with wakelocks.

I would call myself an advanced user but this time In out of ideas.

I have wiped everything 2 times and even installed factory image but the problem persists. In getting around 5000-10000 wakelocks per minute! but only when the screen is off.

Maybe its a hardware fault but everything is working and I get no freezes crashes and so on.

I did an dump with bbs I hope I did it right.
[BetterBatteryStats] DB126:
BBS log is fine. Appears data connection (mobile and/or WiFi) is absent with device spinning its wheels trying to reestablish. Try placing in airplane mode for an hour or so (screen off) to see if behavior subsides. If so try disabling WiFi first then mobile data to further isolate problem.

This problem has been reported by other HTC 10 users in various forums. Reported fixes are all over the map but typically involve going with a custom kernel (eg: ElementalX) and/or ROM (Lineage 14.1 was cited a few times).
[BetterBatteryStats] Cozmos23:
Thx for the info, it looks like after 3 days of "wheel spinning" the device starts to enter deep sleep which didn't happen before. Was 99.9% active while idling before.

Was curious because even an flashing of an factory image didn't resolve the problem.

Was researching alot but didn't know what to search for.

And searching for wakelocks or battery drain overall is a pain as you can imagine.

If it appears again I will check out the wifi, mobile flightmode solution you suggested and give an hint here.

I already tried the cleanslate Kernel but will check out the elemental X or install LOS.

Another possible fix could be an downgrade to marshmallow.

And fyi I will post your answer in the htc10 forum maybe it helps someone with similar problems.
[BetterBatteryStats] DB126:
Possible your device received an OTA update that addressed a known issue in the 'base' kernel/ROM. Also assume you rebooted a few times after flashing the new ROM which is sometimes needed to complete initiation. In absence of those events it seems doubtful your device will resume normal sleep patterns after such a prolonged period of insomnia without further intervention. Post a new log if more help is needed.
[BetterBatteryStats] m0han:
should i put phone in airplane mode for the 6+ hrs of 'no touchy!' screen off? i mean with wi-fi and data disabled.
[BetterBatteryStats] DB126:
Na - configure the phone as you normally would for an overnight siesta. Make sure you have enabled BBS Watchdog processing in advance so both 'screen off' and 'screen on' references are available after waking device.
[BetterBatteryStats] m0han:
thanks. yeah, done all that. i wanna grab a proper dump while at my workplace. will post dump later.
[BetterBatteryStats] TNSMANI:
1. If all the apps behave properly, then keeping wifi on may not be an issue. But in cases where the behaviour is cranky, there will be apps and processes trying to connect to the cloud while the device is asleep. So in

my

opinion, it is better to keep the wifi in check since I don't know which app's update is going to kick up a storm.

3. There are wakelocks relating to wifi running riot in the dump. That is how I can tell.
[BetterBatteryStats] peterlee928:
much thanks for the background ?

would it be too much to ask which ones indicate this?

would the mere presence of these wakelocks always/generally suggest a haywire wifi? or are there other things that you see in conjunction with those wakelocks that indicate the haywire wifi?

thanks again ?
[BetterBatteryStats] pjadec:
Probably this.

Kernel Wakelocks

qcom_rx_wakelock (): 13 m 4 s Cnt:(c/wc/ec)15744/1299/15744 3.1%
[BetterBatteryStats] Cozmos23:
I found it!!!!!! :cowboy:

It was a hardware related problem.

I could reproduce the nasty wakelock by moving the middle metal part of the usb c charging port up and down.

Thats why it even happened when installing a factory image.

Something must be loose there.

Too bad the repair videos on youtube call my device the medusa of smartphones as its glued everywhere.

But the good thing is now I know my 16 digits wifi password .-.
[BetterBatteryStats] DB126:
Nice detective work, mate!! Intermittent hardware problems are often hard to diagnose as tolerances are small with the real issue buried deep inside the case. Returning to stock and requesting a warranty repair may be one path. Another is semi-permanently sealing a stubby adapter/cable into the charging port as the problem will likely get worse in time without a reinforcing structure. Obviously not ideal but better than the alternative (no connection, no charge or potentially shorting out on mainboard). Good luck!
[BetterBatteryStats] birdie:
My phone (LeMax2) eats up to 1% of battery during idle, I'm curious why.

Could anyone please take a good look?

By Idle I mean:

Wi-Fi is disabled

Mobile data is disabled

Mobile type is set to GSM/2G (100% signal)

GPS/Location services are disabled

That's when running stock unrooted LineageOS 7.1. Also I'm curious why this app has never been updated for better compatibility with Android 7/Nougat.
[BetterBatteryStats] DB126:
Nothing jumps out. Device was awake for 3 min (at low frequencies) over 7½ hours which is quite good. Battery decay seems a bit high at 4% (~0.5%/hr) but that may be skewed 1-2% as monitoring began at 100% charge. Some packs give up the first couple percent fairly quickly before settling into a more linear drain under steady load. Good chance there is parasitic sensor drain that BBS isn't seeing. Likely taxing the modest battery a bit more than some run-of-the-mill devices. Also, Lineage isn't known to be the most power efficient ROM in its default configuration and likely isn't optimized for the stock kernel.

All that said, device is idling pretty much as expected for Android 7. You might be able to shave a few dozen seconds off wake time via an 'aggressive doze' tweak but the battery savings will be very minimal at best and likely offset by a burst of activity when the device wakes. I wouldn't take any action.

As for your final question, BBS developer is a volunteer contributor who likely has an active life outside of XDA. Be happy for what we have and hopeful the dev (at some point) will have extra cycles to make BBS even better.
[BetterBatteryStats] Clandaries:
Hi,

what is the newest version here? Long time since i was here last time.

Regards
[BetterBatteryStats] peterlee928:
see post #2 in this thread ?
[BetterBatteryStats] DB126:
- BBS log is well done; thanks for that

- please do not embed lengthy content in posts as the XDA 'hide' function only works with desktop browsers; huge log overwhelms small screens

- device remains awake due to a kernel wakelock which can not be eliminated via direct action (short of replacing the kernel...not likely for your device)

- make sure BlueTooth and WiFi scanning are disabled (Google for more info)

- see if leaving BlueTooth enabled after use helps; BT radio generally does not draw much juice when idle

- if still no joy check for solutions in your device forum

- otherwise, you'll need to consider other options such as avoiding BlueTooth or rebooting after use.
[BetterBatteryStats] rtk217:
In the network tab I encounter a value called: 0 (Mobile) 0 which downloaded 47.0 MBytes which are 10% of my total network usage since recharge.

Can anyone tell me anything about this PID 0? is it a legitimate process that simply disappeared? is it network overhead which is not related to a specific process?

Thanks!