yashsingh1/xdaforums huggingface dataset:
[Android General] ivy.lally:
Would you recommend adding stubborn applications to Block List in ForceDoze instead of relying upon other power saving Xposed modules in this respect, can ForceDoze suffice in controlling what happens when screen is off and make other tools redundant?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel

---------- Post added at 07:50 AM ---------- Previous post was at 06:57 AM ----------

Wow, how does ForceDoze Block List work? It's amazing how apps added to this list have been "seen" as uninstalled!

In result, e.g. Elecont eWeather widgets have been destroyed and must them build anew, and Xposed modules there added reappeared with screen ON but with error messages they must be activated in Xposed (and phone rebooted).

It looks like Block List works too effectively and the app ForceDoze is a miss, still have to look for the other solution.

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] :
You can build shortcuts with Amplify to block / unblock specific alarms, wakelocks and services. Just use any automation app to build and run those shortcuts when display is turned on and off. I use Automagic but even old school Llama will suffice (download from http://kebabapps.blogspot.kr as the Play Store version is outdated). I just block the android.appwidget.action.APPWIDGET_UPDATE all together (set to 9999999) when display is off and unblock when screen is unlocked.
[Android General] DB126:
Well that's certainly not the experience reported by other ForceDoze users that utilize numerous Xposed modules and (presumably) widgets. Your device is just full of surprises.

A half dozen tools/techniques have been mentioned over the last two dozen or so posts (self and others). You simply need to experiment and see what works.

Might also consider scheduling a series of tasks that disable/freeze/stop your weather app on screen off and restart it on screen on. Edge (Xposed module), MacroDroid and/or Tasker are three tools to consider.

Or just uninstall the offending clock/weather app.

Moving on. This conversation has gone on way too long and is heading OT ...
[Android General] ivy.lally:
And can use Tasker? How to create shortcuts in Amplify as can't see any such option in this app?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] :
Shortcuts are native to Android. If an app has shortcuts then you can access them from other apps that support this functionality. Usually launchers do, and automation apps like Automagic or Llama do too ("Run App Shortcut" in Llama). You can access Amplify shortcuts through those apps.

Tasker however does not support shortcuts (do not know why...) so you would have to use some kind of a plugin to get this functionality.
[Android General] ivy.lally:
Are you sure about tasker? ;)

And maybe other automation applications are more resources efficient, lightweight or more stable?

Please answer as really want to know into which automation application to invest intensive attention?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] Blade2014:
Hi All

Thanks to this wonderful thread, BBS, Amplify, etc I was able to achieve very good idle battery drain. Even though Awake while screen off is 1m:12s, and screen on is 36s, in the wakelock section there are multiple indication of*launch* with 15minutes. I am not able to understand this. Can anyone please have a look into my BBS dump file and guide me?

Also is it possible to achieve better?

http://cloud.tapatalk.com/s/58f98a2c831eb/BetterBatteryStats-2017-04-21_085311197.txt

Regards,

Santhosh.S
[Android General] ivy.lally:
Where is the option to add a plug-in action in Llama (can't find indeed)?

Automagic is resource hungry and cumbersome e.g. when you want to add several actions, even from the same plug-in, then you can't just make a list of them. Instead you must create flow chart consecutive nodes, every node for every single action!

In this link there are downloads available of probably every version of Llama ever released. As the newest versions there are following ones of the same date:

Llama.1.2014.11.20.2330.apk

Llama.1.2014.11.20.2330.callphone.apk

Llama.1.2014.11.20.2330.engb.apk

Llama.1.2014.11.20.2330.engb.callphone.apk

What is the difference between them?

And would you recommend to set more such shortcuts to cooperate with Amplify?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Screen off wake time and drain rate (0.1%/hr) are excellent. Don't worry about benign wakelocks that do not trigger unwanted activity. A wakelock is simply a request with associated max time parameter that the system can choose to ignore. What the receiver does with the request determines which activities, if any, takes place.

---------- Post added at 01:25 PM ---------- Previous post was at 01:18 PM ----------

Suggest MacroDroid which has solid reviews, an active developer & appears easy to use. I have no direct experience with Automatic.

Tasker & Llama are overkill for the simple tasks you are trying to accomplish; in addition the latter has not been updated in a while. Why wrestle with them when there are easier options?

I use Edge for simple macro support but I'm guessing you'll hate it as it is far from perfect.
[Android General] ivy.lally:
You know, if installed already automation application then tempt to create few further useful tasks e.g. to switch keyboards with gentle shaking phone within chosen applications group.

As Llama newest version is updated 3 years ago then maybe it means it is very resource aware because there where phones with 0.5 GB ;)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] Blade2014:
Dear Davey126,

Thank you so much for your kind response.

Regards,

Santhosh.S
[Android General] Celestial Fury:
Yes, it's possible.

*launch* seems to encompass a multitude of things so I wouldn't touch it. All in *launch* seem to be stuck at 15 m 7 s Count:3 3.4%. You should get clarification from the BBS thread if it's working as intended.

This is in Post #2

Alarms: 6, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_192644

These are probably MM analytics (so aren't in Post #2) but analytics have so far been safe to be limited in LP

Alarms: 1, Intent: com.google.android.gms/com.google.android.location.internal.AnalyticsSamplerReceiver

Alarms: 0, Intent: com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS

Alarms: 0, Intent: com.google.android.gms/.analytics.internal.PlayLogReportingService

I see a few more possible tweaks but you can go with these first and see what your drain looks like.
[Android General] Blade2014:
Dear Celestial Fury,

Thank you so much for your guidance. I shall do as you have guided me and will revert back.

Regards,

Santhosh.S
[Android General] ivy.lally:
Yet about automation applications, e.g. Automagic, please. In fact automation apps have their wakelocks and alarms themselves. How to treat them in respect of limiting these activities?

- put Automagic into "exclusions" in Android Battery Optimization settings? (if "battery optimized" then Accessibility rights keep resetting)

- insist on Greenifying it?

- in Amplify, limit Automagic''s wakelocks and alarms? ;)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] Wilmerin:
Thanks for reply. Actually, the screen wasn't on during the test. Just the few seconds taking the dump file.

Also, I took a look on maps settings and there was many things using data conection. I already disabled almost all of it.

Please see new stats on attached file. Now, there is a kernel wakelock named

"ste-gps-interface" (): 5 h 29 m 37 s Cnt:(c/wc/ec)84/0/0 64,4%

On the next test I'll disable the gps and see what happens.

Thanks for your time.
[Android General] DB126:
Do none of these things unless behavior suggests action is required. Since you are looking for actions to take place just before the device sleeps and immediatlely after it wakes there seems no reason to mess with default optimization and Greenify settings. Wakelocks are not evil unless they yield unwanted drain. That will show up in BBS if more than trivial.
[Android General] Celestial Fury:
10026 (Mobile) (com.handmark.tweetcaster.premium.TweetCaster Pro): 5.0 MBytes 48,9%

10072 (Mobile) (Servicios de Google Play): 3.0 MBytes 34,6%

Have you turned off Play Store auto-updates? Is there a setting to control your background tweets?

Seems like there's a fix for your Android JB ste-gps-interface.
[Android General] DB126:
[MENTION=7837559]ivy.lally[/MENTION] - this is another app you may want to try to tame your unruly weather clock/widget. I have NO directly experience with Servicely but others speak highly of it. FYI Only.
[Android General] ivy.lally:
Yet another tweak tool, is it reliable enough to replace Automagic with Amplify, Greenify, SmartNetwork together? :)

And maybe to run it as additional one together with them? :)

Please, review my BetterBatteryStat dump file this time after 6h of sleeping with Automagic & Amplify and Greenify http://cloud.tapatalk.com/s/58fc4ea1af70d/BetterBatteryStats-2017-04-23_080559031.txt

Which activities are the culprits this time to limit them? ;)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
You have to decide that. If the existing tool(s) are working fine no reason to change. Not a fan of running multiple tools concurrently unless each offers a distinct advantage that can not be achieved by the others.

Nothing agregious stands out; I'm sure there a little things that purests will point out. BUT...the device was on charge during a portion of the monitoring window as evidenced by the BBS reference point and positive net voltage. Therefore the information is partially invalid. You will need to create another log that is purely battery based.
[Android General] ivy.lally:
In fact, the measure has started when battery was half full ;) but I've reset (cleared) BBS data before the measure and log should be clear.

What do you mean "the device was on charge": was it used, or was connected to charger?

It was purely on battery power and only navigated for few seconds to dump log file.

And about Servicely, has anybody any experience with it? As in description it is so perfect, pure and simple and yet powerful, it should suffice entirely to resolve DeepSleep wakelocks and alarms problem, and why need anything else?

What do you think of replacing Amplify and Automagic together with this Servicely?

And Greenify may stay as needed to limit power use also when screen is ON (hibernate just unused processes).

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
From BBS log:

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

Level lost [%]: Bat.: -2%(51% to 49%) [0.3%/h]

Voltage lost [mV]: (3776-3839) [-9.6%/h]

================== Reference overview ===============

ref_unplugged: Reference ref_unplugged created 2 h 49 m 12 s

Note net gain in battery voltage (rather unusual) and unplug reference during ~6-½ hour monitoring window. Possible I am misinterpreting data; if so can't immediatlely explain discrepancies.
[Android General] ivy.lally:
How does exactly program Servicely works?

Just had tried how it does, as for now just run BBS with idle phone for 1.5h and the battery drain is 0% (ZERO%)!!!

It needs confirmation with full charged battery and a long test, it's just 100 minutes however it seems the best result so far!

And the utilities run in the test together concurrently were:

- Servicely

- Greenify

- SmartNetwork

Just them, and have frozen Amplify and Automagic and others to isolate the result.

What do you think: is this Servicely so brilliant indeed? ;)

And maybe rather the combination of the three listed above utilities was what yielded such promising outcome?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] :
I am sure because shortcuts and plugins are not the same thing :) but it seems that in case of Amplify there is no difference so you can use it like that with Tasker too.

Llama is extremely lightweight and has unique location tracking abilities such as always on cell location tracking (and WiFi too but has to be turned on manually) that does not drain battery at all. I have tried Tasker out several times but did not like it. I finally switched from Llama to Automagic as I wanted to use more advanced features which Llama simply does not offer. Also, Llama is no longer actively developed. It does still work though and I would still recommend it for a low end device.

It is called "Locale plugin" but really works with any plugin, i.e. there is no difference in functionality between Llama, Automagic and Tasker here.

I find Automagic extremely efficient when it comes to battery drain thanks to its triggers / conditions system which gives a lot of control on when specific actions are triggered and actually executed. It does have its shortcomings (requires extreme specificality, no end actions, etc.) but for me the battery savings are worth it. Llama and Tasker are more flexible in this aspect. When it comes to the Amplify's plugin and shortcuts though, I do not think you can add more actions in one shot in any of these automation apps. This is just this specific plugin's limitation.

It is all explained on the Llama's website (right side menu). I use(d) the standard version (Llama.1.2014.11.20.2330.apk).

This is my setup:

I unblock everything on screen unclock (the "User Present" trigger) .
[Android General] ivy.lally:
It's nice of you, thank you very much, since this my question I've already studied Automagic quite a bit, and also can see many possibilities. However most of them fall into other topic than power saving. Indeed, built several flows similar to yours, however as far as I see now the utility Servicely yields better results. Yet to confirm it, and if the results repeat than Servicely is on the top in curbing services with their wakelocks and alarms during DeepSleep :)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel

---------- Post added at 04:19 PM ---------- Previous post was at 03:39 PM ----------

I already know about the Servicely disadvantage. As I set many suspected services to submit Servicely blocking when screen is OFF, just after waking up the phone and the screen processor goes high - as restored services do some initial job to settle for stable functioning afterwards.

In turn, the battery energy saved during DeepSleep on waking up is wasted!

How to overcome this?

And maybe the better still is automation with Amplify, there are processes still running there just wakelocks and alarms are blocked?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
As the old saying goes 'pay me now or pay me later'. Services exist to do work and consume power doing their assigned function. If you don't benefit from the tasks performed then disable the service.

On my Android 6+ devices I simply allow native doze to manage such services, waking occationally to perform required/desired services during pre-defined maintenance windows. My primary phone rocks 0.1%-0.2% per hour idle drain with all radios active and full location services. I use Greenify w/Xposed to rein in 2-3 apps that like to wake the device. I also block Google Firebase Analytics. That's it.
[Android General] ivy.lally:
And maybe the solution will be to let Greenify hibernate services it agrees it can, and those Greenify can't hibernate (it warns plainly about them) let Servicely block (stop during screen OFF? How does it work?)

It was probably big mistake to put too many services on the Servicely list, especially those already greenified.

Hibernating means afterwards waking up cost very little energy, unlike starting a service anew, doesn't it? ;)

And do you block Google Firebase Analytics in every application installed (as I used to do using 3C-Toolbox)?

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
- how about block nothing until an app/service is demonstrated to trigger excess (operative word) drain?

- hibernating typically avoids the overhead of reloading and reinitializing (but not always...depends on memory load)

- I disable the firebase analytic reporting service within Google Play Services and keep it disabled with MyAndroidTools Xposed; otherwise Google Play Services automatically restarts stopped services at boot an periodic intervals

- I never mass tune/tweak at the application/service level; rather deal with the source of the 'problem'
[Android General] ivy.lally:
I can see Servicely has priority over Greenify, if a service is both greenified and Servicelied than then Greenify does nothing with it, just Servicely stops it on screen OFF and starts when screen ON.

And I have Servicelied just these services Greenify can't Greenify them, e.g. eWeather, Ampere, NovaLauncher, Swype keyboard,

and it improved (re)start energy drain and still have 0% in DeepSleep :)

It seems Automagic, Amplify render redundant now, even already miss them, these programs are so elegant and smart would like to do something with them ;)

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] :
What controls sync?

android.content.syncmanager.SYNC_ALARM (Alarm)

SyncLoopWakeLock (Wake)

or is there anything else i am missing that affects sync?

Any issue limiting NetworkStats (Wakelock: 600); com.android.server.action.NETWORK_STATS_POLL (Alarm: 7200) RILJ (Wakelock: 600) ?
[Android General] cristixperia:
Can someone take a look on my BBS log? :)
[Android General] rocky78:
showoff :p
[Android General] cristixperia:
No :(
[Android General] rocky78:
dont know what you want. your phone was a sleep for 99.3% for 9.23 hours. what more do you want?
[Android General] cristixperia:
Awake time is pretty high.
[Android General] rocky78:
i think your stats is great. leave it and be happy!
[Android General] pawwaap:
You know, if someone pampers this settings for a week or so then gains idealistic attitude ;)

However maybe it's well founded: problems often lurks beneath and strike when least expected and desired, so no surprise people think in advance!
[Android General] Celestial Fury:
So as no misinformation is spread in this thread, Servicely only works on services. Many other apps can also disable services including Amplify. However, services have a negligible drain on battery compared to alarms and wakelocks. You can see for yourself in any BBS log - services can run for hours with low drain. Any claim that just stopping services produces [0.0%/h] after just 1 hour should post the log in the Servicely thread. Its dev has recently started re-posting in the thread and would surely welcome such accolade. For those who consider my words, I'm telling you it doesn't and the proof is in the logs - and no, 1 hour isn't enough if you're talking about idle drain. More to the point, unlike alarms and wakelocks, services CAN'T be regulated. They can either be allowed or disabled and if they're disabled whatever app that needs it to work simply won't work unless the service is restarted (if the app includes that functionality). Then consider how many times a day you turn on your screen.
[Android General] DB126:
I concur that stopping services for the sake of power savings is a fool's errand except if you do not want the actions performed by that service. I intentionally (and intelligently) stop several Google Play Services sub-components yielding significant, demonstrable and repeatable power savings with no ill effects. Of course, I do not receive the 'benefits' offered by those stopped components which is exactly as desired.

I do NOT use Servicely and do not endore its use or the developer. Especially if the latter cross/re-posting as a faux endoresement to drive sales. However, it is a tool some find useful (like Amplify - which I also do not use) and has been mentioned in that context. Appreciate the heads-up on some potentially shady behavior. Will be watching for that.
[Android General] justjr:
Can you share the services you stopped, the 'benefits' you are 'loosing' in doing so, and the app you are using to do it, please? Thank you in advance.
[Android General] Celestial Fury:
No, by re-posting I meant that I've used Servicely when it first came out then the dev stopped posting in the Servicely thread for some time but now I see that he's active again and re-posting (by 're' I mean posting again) in his own thread. As far as I know, he's a fine dev with several fine applications including the popular Franco Kernel.
[Android General] DB126:
Greenify and MyAndroidTools both complemented with their related Xposed components. Among others I opt to stop (block) Firebase Analytics using techniques documented elsewhere on XDA. In my case stopping a single service in Google Play services prevents data collection and reporting to Google which often delayed sleep/doze. I loose nothing in exchange but do blind developers on potentially useful information on how I use their apps.

My intent is not to write alternative prescriptions or hijack this thread. Please see the extensive, excellent work performed by the OP (@Celestial Fury), especially the first several posts. Each person must find their own personal 'zen' with the device they own, apps used and level of effort applied.
[Android General] Celestial Fury:
For pure sync it's whatever has 'sync' in its name. There's also ContentSyncService. However, sync and push notifications work in tandem so look for the cloud icon in Post #2. For network stats, IIRC there's no issue but they weren't extensively tested since they didn't really drain.

MM equivalent of the one in Post #2 (LP) so probably no issues limiting it

Alarms: 6, Intent: com.google.android.gms/.checkin.EventLogServiceReceiver

In Post #2

Alarms: 6, Intent: CONTEXT_MANAGER_ALARM_WAKEUP_245480

What's this? Charging by draining is an oxymoron.

Alarms: 57, Intent: com.sonymobile.smartcharger/.chargingintelligentservice.ChargeStateLogger
[Android General] justjr:
I follow this post long time, and also find it excellent. I also know I must find my own 'zen', problem is I'm on Nougat so I can't use Amplify anymore. And to find my own zen I usually look at what other people are doing (like yours config), it really help me figure out what I can try to do with mine, rest assured I don't copy blindly this things.

I am also using Greenify and MyAndroidTools, unfortunately without Xposed too... just wanted to see what you are blocking.

I don't want to hijack this topic either, sorry if I gone off-topic! I found some other topics and proceeding to devore them.
[Android General] cristixperia:
"com.sonymobile.smartcharger/.chargingintelligentservice.ChargeStateLogger" is from "Battery Care" function implemented on Sony devices ;)

"Charging by draining"? :confused:
[Android General] DB126:
On Nougat try stopping PackageMeasurementService within Play Services. Unfortunately, without Xposed service will peroretically restart including on reboot. Wouldn't be surprised if Google makes this a 'mandatory' component in a future update.
[Android General] Bewildered Wolf:
Bro, battery care check for your charging cycle so whenever you put your phone on charger or even when you are not charging,the battery care app checks for the battery cycle so this specific wakelock is always running I don't think it drains your battery.

---------- Post added at 04:32 PM ---------- Previous post was at 04:30 PM ----------

Stopping Package measurement service using Myandroidtools ?
[Android General] DB126:
Sure.
[Android General] ivy.lally:
Please review this BetterBatteryStat log:

http://cloud.tapatalk.com/s/58fe238297f6c/BetterBatteryStats-2017-04-24_175926287.txt

It is weird:

===============
Kernel Wakelocks !!! wakeup_sources !!!
================
PMS^15496^BBS_WAKELOCK_WHILE_SAVING_REF (): 3 h 11 m 53 s Cnt:(c/wc/ec)0/0/0 100.0%
PowerManagerService.WakeLocks (): 1 m 35 s Cnt:(c/wc/ec)60/0/0 0.8%
radio-interface (): 7 s Cnt:(c/wc/ec)31/0/0 0.1%

What does it mean, BetterBatteryStat prevents DeepSleep??

Aqua-M4 E2303, modded MarshMallow, SkyMelon kernel
[Android General] DB126:
Looks like a glitch, possibly introduced by other mods on your system. Reboot and see if it repeats. If yes uninstall BBS, reboot, reinstall and make sure all permissions are properly granted.