yashsingh1/xdaforums huggingface dataset:
[Android General] marcdw:
Thank you Mr. [MENTION=5488402]Davey126[/MENTION]. As always, ??☝.

I had just discovered an issue with my setup (ROM keeps changing location to device only) so on one reboot I fell asleep for real. Phone slept better than I did actually. ?

The No Data Connection thing still confuses me.

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3

---------- Post added at 14:12 ---------- Previous post was at 14:11 ----------

Thank you Mr. [MENTION=5488402]Davey126[/MENTION]. As always, ??☝.

I had just discovered an issue with my setup (ROM keeps changing location to device only) so on one reboot I fell asleep for real. Phone slept better than I did actually. ?

The No Data Connection thing still confuses me.

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
[Android General] DB126:
No confidence in last submission; boot -> current is not the best range. 0.1% per hour avg idle drain is ridiculously low even with full network isolation.

Disregard No Data Connection. Never found that metric meaningful/reliable.
[Android General] maybeme2:
Can you share the usual bad actors to target with Greenify or will that get you in trouble?
[Android General] DB126:
Those are for you to identify. What I consider a 'bad actor' may suit you just fine. Facebook app is everyone's favorite example. Eats most devices alive. Toss it in Greenify's hibernation list and notifications may be blocked or delayed. Pick your poison.
[Android General] maybeme2:
I never go to Facebook if I can help it and don't have its app.
[Android General] anon1135:
how about the Facebook lite app or other alternatives? are they just as bad?
[Android General] DB126:
Again - for you to evaluate. If there was one 'beat' there would be no need for alternatives. That said, Facebook lite is viewed by many to be Superior to the 'regular' Facebook pig.
[Android General] brian-wendrel:
Its good??
[Android General] DB126:
Looks great! Very low idle drain - especially given the app portfolio. Everything appears to be under control; no need for further action. Opinion: don't get lured into updating to Android 8/9+ unless there is specific feature/functionality of significant interest. I have yet to see a 'custom' Oreo ROM outperform Nougat; usually the opposite That will likely change in time as custodians refine kernel tunings; obviously does not apply to newer devices that came with stock Oreo.
[Android General] brian-wendrel:
Truth. I even installed a custom ROM with Android Oreo, but the battery was being drained very quickly. Then I went back to the stock version.
[Android General] Revontheus:
Hello [MENTION=5488402]Davey126[/MENTION], just a few (particularly noobish) questions here if you don't mind:

Would it be advisable to use Greenify to hibernate battery-hogging apps (Messenger, Skype, Twitter, etc) and use Naptime for the rest? Iirc, Greenify uses more resources to hibernate the apps than it saves on Android 6+

Is it a good idea to block the services listed in OP using Servicely as I am aware that the Service Blocking feature of Amplify is non-existent on Oreo Devices

For devices with 2k display, does decreasing screen resolution have a reasonable effect on battery life?

Thanks in advance! and hope you enjoy your day :)
[Android General] DB126:
The only tool I use is Greenify with Xposed framework which eliminates any performance concerns. Privileged mode would yield similar results. Greenify (generically app hibernation) is only needed for a few apps that are coded for earlier SDKs.

I do not block "services" as the maintenance effort and potential side-effects far outweigh the miniscule savings on a well tuned system.

Do yourself a favor and don't tilt to the heavy Android tweaker windmills. App selection, configuration and personal behavior (eg: heavy gaming outside in bright sunlight) is the key to outstanding battery life on most modern devices.

Good luck.
[Android General] Revontheus:
I was actually concerned since you've mentioned:

So I thought, in this case it would be better to configure Doze instead of adding every app on Greenify and enabling the auto-hibernation feature?

Thanks!
[Android General] DB126:
Doze works w/o configuration for most (nearly all) modern apps. You don't need to do anything to enable or tune on Android 7+ (Android 6 may need a tweak to calm the significant motion sensor). Greenify is a fallback for the occasional 'bad actor'.
[Android General] Revontheus:
Thanks for clarifying things! I've read your previous posts both here and on other threads :) and have decided to remove Amplify, Servicely and stick to Naptime + Greenify. Hopefully this would yield better results.
[Android General] DB126:
Good choice - at least at a starting point. Be sure to grab a baseline w/o any tools installed so you have something to measure against. Naptime is hardly needed but many enjoy the placebo effect. Most of the 'regular' tweaks are incorporated into doze on Android 7+. Advance settings expose knobs/dials that are of little benefit in the real world. Akin to installing a full set of drive train monitoring and tuning controls in the humble family van. Keeps dad occupied while mpg remains largely unchanged. Enjoy your travels.
[Android General] Revontheus:
Loving your analogies, it might be akin to putting gel on ones hair :). However, is there any other way to enable Aggressive Doze w/o using 3rd-party apps? Also, I've always wondered on what's the difference of an app in Doze and app hibernated by Greenify?

Thanks!
[Android General] DB126:
Actually not a fan of aggressive doze as 'normal' doze is well balanced. That said, using a 3rd party tool is the best approach if afflicted with power mgmt OCD. Greenify and/or Naptime are as good as any other hack kit.

While doze and hibernation share many outward characteristics the most striking difference is the former is only effective when the device is inactive (ie: idle, screen off, mostly motionless). In contrast an app/service placed in hibernation says in hibernation unless explicitly/implicitly woken. You can choose which apps to hibernate; doze is global unless an app/service is excluded from "battery optimization". There are a bunch of other differences; discussion is beyond the scope of this thread (and my immediate recall).
[Android General] Ganapatya:
is still useful to amplify in android 8.1 or is it useless?
[Android General] DB126:
Usefull/useless characterzation is in the eye of the beholder. That said, I see few benefits and numerous fallbacks employing any form of broadscale alarm or wakelock blocking on Android 6+.
[Android General] habylab:
Yes to all of those.
[Android General] DB126:
LOL - not really (thoughts) but people just love to turn 'dem knobs and dials!
[Android General] habylab:
The resolution comment is true though. Naptime also saves a lot of battery, as does greenifying/using servicely for apps like Facebook. I prefer to just uninstall them though!
[Android General] Imnotquitesure:
Is AlpmModeManager something that needs limiting? It's time active is 10+ hours out of 16.
[Android General] DB126:
Naptime is benign on a well tuned system as Android is perfectly capable of entering/exiting doze (deep sleep if you like) without a 3rd party background service orchestrating its efforts. On suboptimal config Naptime and similar tools may offer a marginal benefit on restless devices. Personally I'd rather fix the problem at its source vs covering it up.

Resolution tweak is crap. While it's true 'faking' a lower resolution will trigger some apps to process content (especially video) differently but the same effect can be achieved by simply choosing a lower playback resolution which may yield other benefits. Simply lowering panel brightness by 5-10% will yield far greater savings.

Reining in 'abusive' apps like Facebook with Greenify/Servicely/Brevent/etc is certainly effective. But why use those pigs when lite options exist? Greenify is the preferred choice IMHO based on approach, track record and user support. Or use web based alternatives such as Hermit.

Urban legends love non-specificity. "xxx saves a lot of battery" is meaningless unless supported by data collected in a well controlled environment.

---------- Post added at 02:10 PM ---------- Previous post was at 02:06 PM ----------

Nope - unless you can correlate that specific event with elevated wake time or battery drain. Neither of which are likely.
[Android General] Imnotquitesure:
I'm having trouble pinpointing my battery drain. I'll lose 10%+ overnight. Kernel (Android OS) and Android System are always at the top of the list of battery usage. Where do I want to go from here to diagnose the cause?
[Android General] DB126:
Prepare and submit a BBS idle study in this thread for community review/comment.
[Android General] J4jks:
I'm getting more than 10% drain overnight,but stats show Android Os and phone idle, Android system are top

Redmi note 3 ,AEX N with custom kernel AGNI + microG+magisk+xposed systemless

Disabled keep awake in AppOps for microG core and few other apps too to check drain but same

One day it seems fine around .5% drain overnight with wireguard on, other day it is more worse without wireguard too

I'm not using any apps like greenify

Can anybody find the cause o the idle drain from logs attached ?

Thanks

BBS stats

https://hastebin.com/jikugakodo.swift

dmeg

https://hastebin.com/edilujofaf.vbs

logcat

https://hastebin.com/uyohejogip.vbs
[Android General] strongst:
[MENTION=6697942]J4jks[/MENTION] I can't find a real issue.

Minor things are:

- one hour poor/moderate signal

-the cpu isn't going to the lowest frequency before falling into deep sleep

Therefore I would recommend to try another kernel and/or if you made kernel settings reset to default.
[Android General] J4jks:
Well thank you for reviewing

I'll try changing things today

Today battery is draining like hell

I've disabled SIM toolkit app yesterday, will it cause this much drain
[Android General] Jrhotrod:
On a daily basis, Cell Standby drains more battery than anything else on my phone. This, as far as I know, is due to poor service (which is definite where I live). Is there anything I can do to combat this? I think toggling to 2G when on WiFi can help, but I'm unsure of how.

I appreciate any help I can get. :)
[Android General] strongst:
Definitely yes. You can toggle to 2G in settings - sim/network on most roms.
[Android General] mattie_49:
Tagging
[Android General] Victorman86:
Two logs: with WiFi enabled and disabled. Any comments please.
[Android General] strongst:
There's no big difference between both. What do you need to figure out between both?
[Android General] Victorman86:
Oh no) There are two day logs.

I need to know battery drain reasons for my Xperia from signature.
[Android General] strongst:
This is exposed: LocWeather (com.xiaomi.hm.health.Mi Fit):
[Android General] Victorman86:
Installed My Android Tools. There is HMWeatherSettingActivity only. No more *weather* components.
[Android General] strongst:
I don't know what you want to say, but this is the wakelock from bbs what I discovered and is known from your Xiaomi app,do you have a mi band?
[Android General] Victorman86:
I have Mi Band 1s. No display, no weather forecast. How kill this wakelock?
[Android General] strongst:
It's the Xiaomi app that I posted, not the band itself(sure, it's using blue which causes wakelocks too).
[Android General] lazostat:
I have one question according to greenify. If I enable aggressive doze is there any reason to have also hibernated apps or not? I mean to press the "Zzz" button once in a while.
[Android General] DB126:
Doze and app hibernation are different things that often (but not always) yield similar benefits. Doze only works when the device is NOT is use. Hibernation can be invoked anytime and remains in effect until the app is restarted.

Greenify will automatically hibernate selective apps shortly after screen off. However, you can manually induce hibernation of one or more apps via UI, widget or Greenify notification. Normally there is no reason to do this unless you suspect an app is consuming resources while not in the foreground.

tl;dr: No.
[Android General] lazostat:
I have lg g4 with custom android nougat. So i enable aggressive doze and what else? Doze on the go?
[Android General] DB126:
Sure. But really you need do nothing; Android 7+ pretty much takes care of itself. That's the easy answer you're looking for.
[Android General] lazostat:
But i cant see doze settings on developer options..
[Android General] DB126:
Nothing to see; if you really want "aggressive doze" set it in Greenify or some other tool and call it a day.
[Android General] macschwag14:
Did you ever figure this out? I'm having it too and trying to figure it out. By any chance do you use Podcast Addict?
[Android General] k54k54k54:
more than one person told me that the continually trying to stop wakelock, services etc. etc. and force the doze etc. etc.

it can have the opposite effect and that is to consume more battery

can it be true ???

thanks by k54
[Android General] strongst:
Yes. Cause apps are programmed to communicate(those who intended to be and others that not) and communication obviously causes wakelocks(the app needs to be become active).

Messaging apps for example can only receive notifications in time when they are active(within communication windows for example).

When you suspend/block those wakelocks the app can be more active to hold the communication active. That's the opposite effect.

Therefore it's better to change an app to a better programmed, use other alternatives or leave it as it is ;)
[Android General] k54k54k54:
I followed that rules without disable location things (because that I use location with life360)

https://xdaforums.com/showpost.php?p=60429417&postcount=4

and You are saying me that could be worse , so there isn't solution :crying: :crying: :crying:

In general I don't notice improvements but if it gets worse, I'll remove amplify :crying: :crying: :crying:

thanks by k54
[Android General] DB126:
In addition most recorded wakelocks are benign, do NOT wake the device and cause NO meaningful battery drain. Receiver actions are what matters. If no receiver is listening (or chooses not to respond) no action is taken. In general it is best to leave alarms, wakelocks and core services alone on Android 6+.
[Android General] mattie_49:
Not sure why you continue saying this on all threads. I have an HTC 10. If I leave services wakelocks and alarms alone. I get approximately 12 hours of battery and maybe 2 hours on screen time. This is on Stock Oreo. If I adjust wakelocks, alarms and services as per guides I get 24-30 hours off charger probably more and 5+ hours on screen. So the information you are speaking of on Android 6+ is incorrect in my case. I must be one of the special cases I guess.
[Android General] DB126:
Reread the post that triggered your response. Nothing inaccurate or untrue. Assuming the opposite position suggests Google and HTC knowingly produce products can't go more than a half day on standby and struggle to get two hours of run time.

You haven't identified the root cause and prefer to deal with the symptoms. That's ok if side-effects are negligible (rare) and the effort to apply the various fixes does not exceed the perceived benefit. Akin to living with an analgesic; works for some. There is ample evidence to support the hypothesis that good device/ROM/app hygiene is the key to achieving the intended battery endurance.

If this thread works for you, great! There are always outliers. Also worth noting many devices that upgrade to Oreo through whatever means seem to experience higher drains than those that were designed with Android 8+ in mind. Especially custom ROMs that are rarely optimized for the hardware platform.
[Android General] pbigband:
Nope, haven't figured that out either LOL and Nope, not using the Podcast Addict
[Android General] k54k54k54:
which is the truth ? :confused::confused::confused:
[Android General] DB126:
"Truth" is what you believe. I don't think anyone on this forum is intentionally spewing lies despite the different experiences and perspectives. That said, there are different approaches to deriving 'the truth' (empirical; scientific; often some hybrid). Up to the reader to separate wheat from chaff.
[Android General] peterlee928:
seriously [MENTION=5488402]Davey126[/MENTION] can you PLEASE stop with the FAKE NEWS! seriously we are trying to build a BEAUTIFUL WALL to keep out wakelocks, but you and the FAKE NEWS senior xda leaders are getting in the way! :laugh: :laugh: (obviously jk)
[Android General] Jrhotrod:
sigh...

Joking aside, I was formerly a big user of Amplify on my old Samsung on Lollipop. It worked like a charm on there, since Doze is non-existent on SDK 22 and below. I moved to the Moto G5 Plus a year later and continued to use it on the stock ROM and LineageOS 14.1. But at the recommendation of Davey126, I stopped my usage of it and haven't noticed a difference in battery life.

The only battery mod I use is Greenify's Aggressive Doze, which has actually shown a marked improvement on my battery life (simply eyeballing the graph shows that the line is less steep with Aggressive Doze).
[Android General] maybeme2:
So Greenify's Aggressive Doze improves battery life on lineageos 14.1? I thought I read Aggressive Doze was not a good idea (but that may have been on 6.0.1).
[Android General] DB126:
Nothing is binary. Depends on app portfolio, usage patterns, environmental factors (motion, signal strength, etc), notifications, location services settings and many other factors. In some cases the rush of activity after exiting prolonged doze windows (which can delay some notifications) induces lag and offsets any power savings. I generally find normal doze yields the best results on *most* devices. YMMV.
[Android General] Jrhotrod:
Precisely. I have really bad cell service at home so I use Aggressive Doze to counteract the drain. I also have a Tasker profile where it will switch to 2G when I'm on home WiFi, and that has helped... Eh. A little.

I also carry my phone with me even when I'm at home, so I figured the motion would prevent it from Dozing.

At any rate, I'm actually pretty happy I gave up wakelock blocking. I have pretty much no reason to install Xposed now, and even though I love the framework, modern Android doesn't really exhibit a need for a lot of the modifications that are possible with it (especially Android P-ify... who would actually want that filth on their phone?).
[Android General] maybeme2:
I use xposed in lineageos 14.1 mainly for xprivacylua, gravitybox, and minminguard. Perhaps there are alternatives that don't need xposed.

What's your beef with Android P-if?
[Android General] DB126:
Excellent. Sounds like your device is well optimized for your needs using mainstream tools/techniques applying the minimum number of 'tweaks' needed to get the job done. There is a elegance to simplicity that pays back with reliability, stability and less time in the 'maintenance shed' fixing fickle fluff that only addresses symptoms vs root cause. I prefer to use/enjoy my devices vs manage them.
[Android General] mattie_49:
Davey126 you may be onto something. Scenario. HTC 10 Verizon. Lee droid Oreo rom. Been setting up with amplify and xposed. I'm actually finding source of problem like you suggested. Big battery drainers. Well here at my apartment my 4g/lte signal is well. Pretty bad : just barely connecting. Seems like a problem as far as battery drain. So tried something different. On home Wi-Fi which is really strong. And I have Wi-Fi calling. Through rom I found network switcher. Long story short while on home Wi-Fi , I switch to 2g only and am getting better screen on time that I was (mucking with Alarms and wakelocks) as you put it, no amplify installed and no xposed framework. So I'm starting to lean towards your theory of its definitely not needed for android 6+. Thanks buddy
[Android General] Jrhotrod:
The UI of Android P looks like crap. Too bubbly and way too white. The white is so counterproductive to good battery life (especially on AMOLED displays) that it looks like the Adaptive Battery feature introduced is just going to offset the extra drain caused by such bright colors.

I mean, seriously. It looks like TouchWiz and iOS had a baby.
[Android General] DB126:
While beauty is in the eyes of the beholder the additional battery drain should be negligible on most modern AMOLED panels except on the highest brightness settings. Guidance for those with 1st/2nd gen panels: don't upgrade if concerned about drain. Your device probably wouldn't be a good canidate for 'p' anyway.
[Android General] mrjuniork:
Won't be a problem with substratum etc.. :)
[Android General] Portgas D. Ace:
As long as you are rooted. Starting from Android P, rootless Substratum won't work anymore.
[Android General] wogooo:
Should i enable both Shallow Hib and Agressive Doze in Greenify?
[Android General] DB126:
Neither; defaults are fine for most.
[Android General] ksa_android:
[MENTION=5488402]Davey126[/MENTION] hello , please can you guide me where to go ? this thread is present since 3 years , I'm using 8.1 Resurrection remix with Magisk v16.0
[Android General] strongst:
Unless you have no problems it's not necessarily to adapt something from here except the general recommendations.

But not greenify or amplify.
[Android General] wogooo:
So this whole topic is now practically pointless for most Android 6 and above users?
[Android General] strongst:
https://xdaforums.com/android/general/guide-extreme-battery-life-t3095884/post74140616 the basic stuff is still adoptable in particular.
[Android General] DB126:
Basic power management guidance is still relevant but there is little to be gained (other than migraines) using the suggested suite of tools for tasks other than monitoring. Alarm/wakelock/service limiting and blocking is generally a fool's errand that often yields no power savings in exchange for side effects of varying severity. Pick your poison wisely.

tl;dr: Android 6/7/8+ manage power effectively without all the black magic.
[Android General] k54k54k54:
thousands and thousands of suites to save energy like the one in question and in the end they are practically useless ... nervous and absurd :crying::crying::crying:

thanks !!!

by k54 from italy
[Android General] strongst:
It's an evolution, not everything here(like guides) are suitable for the newest technology.

Best example is the invention of DOZE or Magisk.
[Android General] k54k54k54:
doze ok , even if in somewhere I read that it's not sure al 100% that do a lot to improve battery :eek:

but magisk to improve the battery ???

thanks

by k54 from italy
[Android General] strongst:
Magisk was just an example, as written before, to explain the evolution of something(magisk is the preferred root method and the predecessor supersu will be more and more neglected).

Nothing to do with battery optimization :o
[Android General] DB126:
There are many historical examples of once useful things that are no longer needed due to various advancements. Android and the underlying hardware have improved; app developers are also more sensitive to power issues.
[Android General] f.a.tonmoy:
Should I do all this blocking wakelocks, alarms on Nougat??

or on Oreo??
[Android General] DB126:
Absolutely not. Which you would know browsing recent thread history. Android 7+ takes care of itself and most apps that contribute to excessive battery drain or exhibit other undesirable background behaviors. Of course, if you're looking for something to do and love chasing down weird alarm/wakelock side-effects the guide serves as a ready source of perpetual entertainment.
[Android General] f.a.tonmoy:
So, should I uninstall Amplify and powernap??

or what apps I should use for a better battery life??
[Android General] maybeme2:
Thank you Davey for all your advice. I'm curious, how does android 7+ handle misbehaving apps and how does one discover which apps are particularly battery intensive?