So you're recommending selecting individual services in Servicely - do you know which ones are safe to stop?
Or, in other words, which ones are the biggest causes of wakelocks - I've got a Samsung Lollipop device so I have no Xposed, and therefore no Amplify. I would love to be able to stop the NetworkLocationProvider services.
Theres really no need to run Greenify + Amplify + Servicely as well, why use 3 programs which all have parts that do what the other 2 do? To me thats madness, your actually adding cycles and memory use and raising the possibility of less battery time by doing so.
I run Amplify and Servicely, but i use AutoStarts to tweak things before i even touch Amplify or Servicely...if it doesnt run at startup or triggered by an intent, then theres no need to touch it with Amplify or Servicely. I only use Amplify and Servicely to handle the apps that i run manually or have to have their intents left alone for interactivity with other apps.
Just the way i do it. I got rid of Greenify weeks ago as it became obvious it was no longer necessary with Amplify & Servicely running.
In the case of Servicely,the GCM push is a hit or miss.Blocking the apps having GCM push may stop the push notifications.So can't rely completely on Servicely.With Servicely we can't block alarms or Wakelocks.Its required that we use Amplify for that.
I won't recommend to remove Greenify.I've asked in the thread to Greenify only the apps having GCM push.This keeps the Push Messaging alive.
The fact is that Servicely runs a small service in background.It doesn't even show up in battery stats.So no need to worry about battery loss.
And using Greenify+Servicely is because of the fact that Greenify doesn't actually stops the service.It hibernates it.That's why I've asked to Hit-List the apps that you don't want to run without starting it manually.
So that's my point.
Tapped from my furious Dogo
|android, battery life, drain, fix, saver|
|Thread Tools||Search this Thread|