yashsingh1/xdaforums huggingface dataset:
[Android General] eng3:
I'll give that a try. I take it that by setting to 3g (or 2g) only, it doesnt waste power trying to connect to 4g?

I do get some related wake locks

GCM_CONN_ALARM

wake:com.google.android.gms/.measurement.Package...

UlrDispSvcSlowWL

CMWakeLock

*sync*/gmail-ls/com.google/eng3@gmail.com

*alarm*

ConnectivityService

Icing

FeatureconfigRefreshService

WakeLockManager
[Android General] DB126:
Those wakelocks are triggered by different processes (eg: Firebase Analytics) that are not directly related to mobile signal strength/availability. Tackle those as a separate excercise.

If the device is 'locked' to 2G/3G it will not attempt a connection to 4G/LTE. In general lower connection speeds are more battery friendly when the device is idle. The radio cranks up to high power when searching for a signal which is what you are trying to avoid.
[Android General] gooner_anirudh:
I just recently upgraded to Nougat and the fact that xposed framework isn't available for it is a bummer. I was using greenify and amplify in Marshmallow and was quite satisfied with the battery life. Can anyone suggest me apps that can be used in Nougat for improving deep sleep?
[Android General] jhunt75:
You can use Doze from the Google playstore
[Android General] DB126:
Stock doze works well in Nougat (seriously). Greenify offers some additional controls if interested. Force Doze and Naptime are other popular 'doze' apps.

Unfortunately, there are no alternatives to Amplify for limiting/blocking rogue wakelocks. You can use MyAndroidTools or SD Maid to block services and broadcast receivers. However, apps can re-enable those components at will (looking at you Google). This behavior can not be stopped without Xposed.
[Android General] gooner_anirudh:
I am gonna try using Doze and see if that helps.
[Android General] Ascenca83:
Can Servicely maybe help:

https://play.google.com/store/apps/details?id=com.franco.servicely

Identify rouge services with apos like Wake Lock Detector and then disable them with Servicely.

Br
[Android General] DB126:
FYI - Servicely is simply a subset of MyAndroidTools (same author).
[Android General] HaTrED_:
No sir, they are not from same author!
[Android General] DB126:
Yikes - my error! Was thinking of Disable Service. Gotta stop posting after 11+ hours behind the wheel. :)
[Android General] Celestial Fury:
Alarms, Wakelocks and Services are NOT the same. Servicely only stops services (which Amplify already does). However, unless you know that it's a service that you don't want like Ads/Privacy related Services (which you can find in Post #2) the recommendation is not to stop Services as some stopping some services can run wild (Post #2 under Dangerous) and drain your battery or respond with app not responding over and over again.
[Android General] ivy.lally:
Hi, just discovered Amplify, I've used DSBatterySaver with Greenify so far on my Xperia Aqua MM with STAMINA constantly on and still have energy leaks while screen off.

Would you recommend introducing Amplify instead of DSBatterySaver?

How about Greenify cooperation with Amplify, do these tools complement each other or maybe messing up and clash?

Want replacement of STAMINA, Stamina works well however it turns off vibrations in hardwired fashion, and I need vibrations e.g. to signal outgoing calls connection with Phone Vibrator Xposed module or for Download Accelerator Plus.

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
You asked a similar question in the Amplify and Power Nap threads. I responded here and directed you to this thread recommending and idle study to identify the true culprits. See post #6 in this thread for guidance on creating the appropriate logs. I'm not a fan of Amplify (due to complexity and potential side effects) but it remains the best tool for some situations. Need to see if your device falls into that category.
[Android General] ivy.lally:
Please, forgive for ample posting however feeling still confused with multitude of such similar tools and scarce information how they compare.

Amplify seems providing mechanism for blocking applications particular components like activities, services, receivers and I've had already blocked them before with the other tool (my favorite) 3C-Toolbox - I analyse every new application installed, and its components, and decode which ones serves well for user's needs, and then selectively switch some off.

In turn, there is very little to block by Amplify now :)

Amplify has the advantage over 'my method' it allows blocked components to wake up in defined times.

Also, using tool Titanium Backup, I've had created widgets freezing/defrosting cumbersome applications with one tap and only defrost an app when really needed.

How do you think, can the Amplify provide better solution or can add anything more than I already have?

And how does Amplify behave while screen is on, does it wake up components defined as blocked before, or keeps them constantly dormant until any of them is deliberately launched by user? (Question if need stamina when relevant components have been blocked by Amplify)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
As noted create an BBS idle log and submit for analysis. That will indicate if there is significant benefit to further alarm/wakelock limiting. If you are looking for a therotical discussion in absence of hard data you probably won't get it. Amplify is no longer being developed as there are better ways to constain excess (operative word) wake time and associated battery drain on modern devices. The whole idea of aggressively limiting wakelocks is getting long in the tooth IMHO - although there are still situations where it can prove quite benefical.

I'll stand down and let other voices chime in. Obviously one opinion does not make a concensus.
[Android General] ivy.lally:
Hello again, however BetterBatteryStat appears missing these options described in the post #6, please review:

is what I have, as you can see there is no item "others" on the list, maybe some special settings is required?

And otherwise, the following stats has been recorded in 5 hours idling after full charge:

as we can see, it drains around 2.4 mA. How do you think is this good record?

(However it went with WiFi and data 'off',' as it has been automatically switched off by Smart Network Xposed module, next time will take care of it to have WiFi & data on during reads)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
I don't see an attached BBS log for the monitoring period; screen shots do not provide any meaningful information. Be sure to capture and post a .txt log for the next run. Keep radios configured as you would normally have them when the device is not in use.
[Android General] ivy.lally:
After uninstalling and installing anew BetterBatteryStat on first run it created the unplugged profile, now I can follow the instructions from the post #6

Please, again specify precisely what conditions are required during this measuring:

- WiFi, data and sync ON,

- what about stamina?

- Xposed modules: Greenify, DSBatterySaver, SmartNetwork?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Don't change the configuration of your device; just capture a 6+ hour idle log with minimal screen on time (ideally <1 min) and post the result.
[Android General] Celestial Fury:
Seems odd to be linking instructions from another thread when such instructions are already in the thread.
[Android General] DB126:
Agreed; got sloppy/lazy. So I get it right you are referencing post #3 in this thread, correct?
[Android General] ivy.lally:
Hello again, please review the BetterBatteryStat dump file of 30 hours after fully charged been idle. Just one exception how for 15 minutes there had been an incoming phone call picked up, and except this the phone has been in perfect idle state untouched.

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
The following details from your log says it all:

============ Battery Info ============

Level lost [%]: Bat.: 5%(81% to 86%) [-0.1%/h]

Voltage lost [mV]: (4028-4091) [-1.2%/h]

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

Didn't look any further as the numbers are excellent. Any further optimizations border on obsessive. ;)
[Android General] Celestial Fury:
Level lost [%]: Bat.: 5%(81% to 86%) [-0.1%/h]

The drain is in reverse (negative) probably from charging the phone at some point meaning this log has been compromised. See Post #3 on where you went wrong.
[Android General] DB126:
Nice catch; overlooked that (d'uh).
[Android General] ivy.lally:
Had it to reset before starting massiv measure?

However to clarify:

where phone had been woken just after 15:00

It looks like drain over 10% per 30h with data and WiFi on.

Has Amplify the potential to improve it?

And I'll repeat BetterBatteryStat session.

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
If accurate works out to 0.3-0.4% per hour which remains quite good. Can you do better? Possibly - but is it worth the effort and potential side effects? Would be another matter if your phone needed to survive (sleep) 7+ days w/o charging. In that case you'd probably flip off radios or the device itself.

Not a fan of Amplify but it does have the potential to squash some unruly wakelocks if your device suffers from that type of problem. It's often better to go after the source of the 'problem' vs limiting the symptom(s).
[Android General] ivy.lally:
Indeed, better to alter troubled applications' components.

However Amplify does better in these respects:

- can limit some system activities normally out of reach to control them,

- can limit every activity but services with time parameters when they are allowed to occur,

- probably better to have one good Xposed module (and possibly Greenify additionally?) than several ones of dubious effectiveness (DSBatterySaver, SmartNetwork), how do you think?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] ivy.lally:
Please, review again BetterBatteryStat dump file, this time after 8h has 5% drain, maybe because just Greenify active and other Xposed modules frozen: Amplify, DSBatterySaver, SmartNetwork.

And thanks to it maybe finding troubled wakelocks, alarms turns out easier? Please identify which activities worth to limit and in what time frames allow them to wake?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] Celestial Fury:
Level lost [%]: Bat.: -5%(100% to 95%) [0.6%/h]

Awake (Screen Off) (): 1 m 47 s

Alarms: 63, Intent: com.android.internal.telephony.data-stall

Mobile data ON will drain more than WiFi.

Alarms: 14, Intent: android.appwidget.action.APPWIDGET_UPDATE

Widgets drain.
[Android General] ivy.lally:
What then, limit alarm of widgets with Amplify, but with what frequency: 3600s?

And are other wakelocks, alarms, services safe for battery drain?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] rocky78:
hi there, i'm on aosp 7.1.2 (ya i know),

i know there's some pro's here in reading BBS.

i just need a hand on the log file to help me understand

what is keeping my phone awake.

now i already saw something with my wifi in the log...

but still need some experience over here.

hope you all in a good mood :o
[Android General] DB126:
See first few posts in this thread for further guidance. Great resource - OP put a lot of work into that (whack the 'thanks' button while you're there). I'm not a personal fan of Amplify and for some the benefits do not offset the work and potential side effects. That said, many have followed and profited nicely from this guide. YMMV. Just an opinion, not a Rx.
[Android General] Celestial Fury:
Depends on what widgets you have, what they do, and how often you need them to do it. Limit them accordingly. See recommendations for android.appwidget.action.APPWIDGET_UPDATE in Post #2.

Once you've done this take another log with WiFi on BUT data OFF. BBS can tell you what alarms/wakelocks have triggered but it can't measure the amount of battery each individual alarm/wakelock consumed. Alarms/wakelocks occur in tandem and to ascertain the drain for each individual alarm/wakelock would necessitate isolation of said alarm/wakelock which does not seem practical nor really possible. All that remains is experience in limiting these alarms/wakelocks and observing the drain. Hence, the guide.

What's keeping your phone awake? According to your level lost - nothing. [0.0%/h] Which does not seem likely according to the rest of your log. Do you see all these alarms/wakelocks enclosed with asterisks like *job*? I don't know how it is with the latest BBS version or if you're using the root or no root version or if it's how Nougat displays alarms/wakelocks but it's most likely you're using API in BBS. See Post #3 In BBS Settings - Advanced.
[Android General] rocky78:
I'm using v2.2.2 xda version and yes the rooted.

do you mean on the app itself? no I'm not seeing *...*

no. my api isn't ticked in setting's.

did you see in the log the wifi thing? (attached pic.)
[Android General] ivy.lally:
And how about Amplify stats information, how to use it, does it provide any basis for limiting activities this reported:

just straightforward from here?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Follow the guide my friend; also search thread which itself is a great resource.
[Android General] Celestial Fury:
It can have a thousand alarms but if your drain is [0.0%/h] then what does it matter? More important is how fast does the battery drop once you start using it? That is, to me your log and your [0.0%/h] drain does not tally. If it drains naturally in use then you've got a great battery, ROM and kernel and have nothing to worry about. Did you even limit anything in Amplify?
[Android General] rocky78:
i can't use amplify (no xposed for nougat yet), but thank you for your patient and the time you took to have a look at my log. :good:
[Android General] Oswald Boelcke:
At least when connected to your home WiFi did you try to disable DHCP and to assign a fixed IP to your device?
[Android General] TNSMANI:
Firstly, do what the post above states. Your data connection was off and on since your WiFi was not properly connected. That itself will drain battery.

Your wakelocks all have the same times, 2 minute 29 seconds. It is not right. BBS doesn't seem to be working alright. Uninstall and reinstall BBS and take another dump and see whether the report is ok.
[Android General] Wilmerin:
New stats, please check it.

Can you please check my new stats.

There are two files: one is in idle mode (network and wifi are on). The second one is in airplane mode.

Thank you!
[Android General] Celestial Fury:
Level lost [%]: Bat.: 0%(100% to 100%) [0,0%/h]

Airplane mode - all is as it should be but . . .

Screen On (): 34 m 32 s

Screen dimmed (): 34 m 32 s

Was your screen actually ON? If it wasn't (and it doesn't appear to be from the exact same figures above) then I don't know what's going on with BBS these days. If it WAS on, then there's no way you could have gotten [0,0%/h] and the same previous comment on BBS applies.

The normal log

RILJ (TelÃ©fono): 22 m 45 s

Commonly drains in Android ICS. You could try this.

10072 (Mobile) (Servicios de Google): 4.0 MBytes

Active downloads will cause many other wakelocks/alarms. Turn off your auto-updates and get another log.

Also, see Post #2 FIX for suspend_backoff (kernel wakelock). Clearing recent apps should also limit alarms/wakelocks with a connection to those apps. That is, have a clear plate for testing an idle log.
[Android General] cristixperia:
I can limit this process in amplify: "com.android.server.device_idle.STEP_IDLE_STATE"

? :confused:

So, what exactly make this process?
[Android General] Celestial Fury:
Search [Ctrl-F] for com.android.server.device_idle.STEP_IDLE_STATE here.
[Android General] ivy.lally:
And what about such alarm (of the third party app eWeather so the general guidance from first posts can't know about it):

Full Name:

com.Elecont.WeatherClock/.WakeUpReceiver

It has many alarms count after every night despite setting it to update just when screen on (and the alarm checks very frequently when screen already comes ON so its crazy). It has time indication on its widgets in very graphical fashion so it takes care to show it accurately and that's why it constantly checks if screen is awaken.

It seems just Xposed module DSBatterySaver can take care of such cases, it works simple: when screen off it hibernates every process without discussion,

when screen ON it wakes up.

And Greenify should work in this fashion too, however it doesn't hibernate the eWeather - why?

Probably because eWeather has two major components: widgets associated background service and GUI main interface, and Greenify is so stupid it keeps just GUI part hibernated, even after screen comes ON.

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] Celestial Fury:
First sentence in reply.
[Android General] ivy.lally:
Yes, we know: "Weather widgets are notorious battery drainers", however to tame them just hibernate them with screen off, and unhibernate when screen ON. Question which Xposed module can do it, just DSBatterySaver?

Probably just Nougat Android version can control it, can't it?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
- if DSBatterySaver works for you then use it

- Greenify is far more intelligent than you may think; does what you tell it

- add both components to hibernate list and profit; requires paid version
[Android General] ivy.lally:
I used to use DSBatterySaver, Greenify and SmartNetwork Xposed modules together and still got small energy leaks during sleep state. And so interested in Amplify, but there're too many modules to run simultaneously now and Amplify reports wakelocks of other modules, there's the mess ;)

I have got paid version of Greenify.

However where is the service of eWeather on the Greenify list of apps to add?

As you can see they're is just one eWeather component possible to add:
[Android General] DB126:
Wow, that's one heavy app. The offending service is ElecontWeatherUpdateService (com.elcont.weatherclock) along with a bunch of broadcast receivers to update various widgets and perform other periodic functions. The reason the service doesn't show up in Greenify is it auto stops after performing whatever task is asked of it. I acknowledge not exposing this type of service when idle is a short coming of Greenify.

I would tackle this problem by blocking receivers (and possibly core services) using a utility like MyAndroidTools or SD Maid. However, that adds yet another tool to your portfolio (which you're trying to simplify) and doesn't fully address the requirement of 'off while sleeping, fully functional while awake'.

As previously noted if DSBatterySaver is working to your satisfaction then go with it. Might consider a different/lighter weather app but I suspect you have considered and rejected that idea.

Good luck.
[Android General] ivy.lally:
Which receivers do you mean, Elecont eWeather's ones?

And in fact what Amplify reports:

com.Elecont.WeatherClock/.WakeUpReceiver

is a receiver itself. Amplify can limit it in timely fashion however when I set this alarm to activate e.g. everyhalf an hour then the main big analog clock widget of Elecont updates every half an hour too, what is absurd. And setting more frequent updates results in bigger energy leaks during phone sleep.

Why is the DSBatterySaver unique in this job? It's simple, it has wake interval the same for every process, coalescing them, and beside of it phone is in deep sleep no matter how many wakelocks are designed to occur.

And after screen turning on it unhibernates everything.

Is DSBatterySaver better working than Greenify, is it possible? Author hasn't updated DSBatterySaver for >3 years.

And what about Amplify, can it hold on while screen is ON i.e. work exclusively during phone sleep (preferably if settable this behavior per app)?

Probably Nougat version Android has inbuilt mechanism to tackle it, I've Nougat on other telephone with eWeather installed and zero energy leaks during phone sleep, would you agree? Price for it is the lack of Xposed for Nougat so far.

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
- install MyAndroidTools to see the full suite of services and receivers

- DSBatterySaver is heavy handed and can lead to missed notifications and/or device lag on wake as everything becomes active at once

- if on Android 6 (MM) consider ForceDoze as an alternative to Greenify if not satisfied with other solutions

- Amplify is purely time based blocks with no regard for sleep/wake state(s)

- Doze in Marshmallow/Nougat may very well address issue as all background activity is suspended unless whitelisted (excluding maintenance windows)

- could also consider a software firewall to block selected app activity when screen is off; I use AdGuard which has an integrated VPN based firewall
[Android General] ivy.lally:
Why does Nougat perform better than MarshMallow in empowering doze?

Where to set maintenance windows frequency in MarshMallow? (White list is the same as for Battery Optimization settings, right?)

Has the system inbuilt mechanism of doze potentials to render Xposed modules like Amplify, Greenify etc useless, unless they are set for doing their job just in screen ON state?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel

---------- Post added at 04:31 AM ---------- Previous post was at 04:13 AM ----------

What is ForceDoze, among Xposed modules you can't find it?

Maybe do you mean BetterBatterySaver?
[Android General] DB126:
- didn't say Nougat was better than Marshmallow in "empowering doze"

- doze in Android 7 has certain refinements especially around motion sensing

- you can find ForceDoze in the Play Store

- ForceDoze has knobs and dials for tuning native doze (best left alone)

- doze and Xposed modules mentioned are full compatible/complementary

- whitelist and battery optimization refer to the same thing (wrt doze)
[Android General] ivy.lally:
How to tackle power saving Xposed modules with native doze settings:

- whitelist modules like Amplify, Greenify to let them do their job while phone sleeps,

or

- let them doze and configure them for regulating processes exclusively when screen is ON (as many processes behave wastefully)?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
- Greenify and ForceDoze add themselves to the whitelist ("not optimized")

- don't try to over-think this; allow the apps do their job without turning a bunch of knobs and dials

- avoid redundancies; don't need 23 power management apps ...

- as previously stated not a fan of Amplify unless there is a specific situation that warrants its use
[Android General] ivy.lally:
Why can't doze make some services (e.g.eWeather) with their wakelocks sleep if it is so trustworthy?

And ForceDoze has possibility to add applications to the Block List to make them doze, it means some of them require enforcing to doze. Why and which (what kind of) applications don't want to submit to native doze?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Dude - time to stop whining and accept the world as it is. If not satisfied with the available solutions dump the weather app and solve your problem. There are many other choices.