I already posted about this in the NRG ROM because that's the ROM I'm using, but I am so impressed with the battery improvement after using this app for a week that I had to cross post to a larger audience. I know the battery is the one major drawback on the Amaze. This is just not a problem for me anymore since I started using Greenify.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
I've been getting over 24 hours regularly with 3-4 hours screen time. I'm using NRG with stock kernel, but I see no reason why this app wouldn't offer improvement for any configuration. It enables effective hibernation of apps without freezing them. They'll run but only in the foreground. It cuts out all background processes of the apps you select.
You have total control over which apps you want running in the background and allows you to keep the aggressive battery hogs at bay. You select which apps should hibernate. For instance, now Google maps will really stay asleep when it's not being used, no constant wake locks, but unlike with freezing it, you can conveniently launch it when needed. However any apps with background processes that are actually useful are free to do their thing, eg, widgets you want to auto update. It's taming the beast that is android.
And not only is my battery improved, but my phone is more responsive too. Highly recommended. Here's the xda thread:
http://forum.xda-developers.com/showthread.php?t=2155737
thanks a lot for sharing this, will try it out, always wanted an app like this, the maps kill the battery for no good reason.
My pleasure. I hope your experience is as satisfying mine.
dosnt kill maps most apps remain in idle, pending hibernation mode.
EDIT, opened my eyes and read the FAQ. - maps not gonna die :|
Q: Some of my greenified apps (e.g. Google Maps) seems not hibernating.
A: In short, don't worry about frequently awake apps. It will still hibernate in minutes after screen goes off, thus hardly add observable battery consumption. Use battery statistics in settings or "BetterBatteryStats" to confirm that.
While most greenified apps will stay in hibernation quietly, some apps do break hibernation, due to being waken up by others. Some known cases include enabled account sync, backup agent, and explicit launch by other app.
Since version 1.45, Greenify will now automatically turn off directly involved account sync of greenified apps when going to hibernate, to avoid the periodic account sync wake them up. For backup agents, Greenify will NOT disable them, to ensure your backup of app data is always up-to-date. As backup usually does not perform often, they are thus unlikely to be waken up often.
Google Maps is a typical example of explicit launch by other app. Some Google apps, including Google Now (a.k.a Google Search), will start the NetworkLocationProvider of Google Maps for its proprietary implementation instead of the public Android one if Google Maps is installed.
Since Greenify is designed to not break any explicit usage of greenified apps, these behaviors are considered "normal", and will NOT be "fixed". To clear out your unease, Greenify will still put them into hibernation when standby to protect your battery consumption.
Click to expand...
Click to collapse
bilaliz said:
dosnt kill maps most apps remain in idle, pending hibernation mode.
EDIT, opened my eyes and read the FAQ. - maps not gonna die :|
Click to expand...
Click to collapse
You can manually put them into hibernation mode by selecting them, and hitting the pause button at the top of the screen. To help control maps make sure you don't have Google Now running or have it on in a very limited mode. (Google Now sucker punches battery. Honestly, I just presume that anyone interested in battery preservation has abandoned Google Now.) The other anti-maps tactic I use is to go to System Settings>>Location and disable "GPS satellites" and "Location & Google search." I can easily re-enable these through a widget I have set up when I need Maps capability, but it keeps the program quiet for the most part and Greenify does the rest.
The proof is in the screenshots. I never got any battery life like this before Greenify.
Shabidoo said:
The proof is in the screenshots. I never got any battery life like this before Greenify.
Click to expand...
Click to collapse
but in those pics i also see juice defender running, so that may be playing a part too. also there are no phone calls, phone calls take a lot of juice.
regarless of that i have witnessed significant battery improvement with this app, i think i'll be giving a donation to this guy. he deserves it.
bilaliz said:
but in those pics i also see juice defender running, so that may be playing a part too. also there are no phone calls, phone calls take a lot of juice.
regarless of that i have witnessed significant battery improvement with this app, i think i'll be giving a donation to this guy. he deserves it.
Click to expand...
Click to collapse
Lol yea juice defender
Sent from my Amaze 4G using xda app-developers app
I've had Juice Defender going as long as I've had my phone. I use the customization in ultimate, but before Greenify, I was getting around 17 hours battery life. So JD has not been a variable for me in evaluating the app.
I'm not a big phone call maker, but I do use bluetooth for music streaming a lot. I think it was so minor in comparison to the screen usage that day that it probably didn't even register 1% battery usage.
So I'm giving it a try. This a pretty much a light app that kills the app you select when you aren't using it.
Sent from my Amaze 4G using xda app-developers app
Trying this out now but just thought I'd pass along some info that really helped me with maps. Using Autorun manager (free on playstore) I killed any process under map that had the word friend in it and it has made a big difference even though Latitude has been disabled since day 1. There are lots of other battery saving and wake lock preventing things you can do with this app.
Justin
Sent from my Amaze 4G using xda app-developers app
mestguy182 said:
Trying this out now but just thought I'd pass along some info that really helped me with maps. Using Autorun manager (free on playstore) I killed any process under map that had the word friend in it and it has made a big difference even though Latitude has been disabled since day 1. There are lots of other battery saving and wake lock preventing things you can do with this app.
Justin
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
I did the same and it helped my battery life dramatically.
Sent from my HTC_Amaze_4G using xda app-developers app
mestguy182 said:
Trying this out now but just thought I'd pass along some info that really helped me with maps. Using Autorun manager (free on playstore) I killed any process under map that had the word friend in it and it has made a big difference even though Latitude has been disabled since day 1. There are lots of other battery saving and wake lock preventing things you can do with this app.
Justin
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. I am trying this out as well and after 2 days, my battery life has doubled. :good: Even works very well on my wife's GNex, where the battery life is worse than the Amaze
Hello @oasisfeng
Ive been using of greenify since the beggining ive rooted my device and now that MM is out which im also using since it was released on my nexus 5 device i still used greenify
Right now i have to uninstall it for one particular reason. It doesnt sync in notifications anymore.
I do know that "doze" limits notifications but opens background sync up in a short time for every minute or hours of interval. I do know greenify forces apps to go to "app standby" mode or forces apps to defer background process without exiting them on 6.0+ this means that the general "wait time" for push notifications are also deffered.
I do know there is a "wake up service" for greenify that intends to wake up device services again when hibernated from time to time but to be honest i think it is inefficient.
So haveyou tried creating an alarm that cuts the hibernation off for a small second to quickly sync in background process and push notifications from apps such as xda labs or messenger? You can do it by creating an alarm with a code of setandallowwhileidle()
Hope you read this and ill be waiting for your feedback, in the meantime ill be uninstalling greenify also its donate package and wait for further improvements
Cheers!
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
oasisfeng said:
Instant messaging apps should generally be excluded from Greenify unless it supports GCM "high priority" push on Android 6.0+. This is the recommended solution mentioned in the app description and FAQ.
Do you mean the Greenify did sync in notifications in the past but not now? Can you give me a specific version number of Greenify that worked for you?
If I understand correctly, you want to wake-up apps periodically. It has been discussed actively in the early time. That derived a large set of functionality requirements, such as interval settings, settings per app, black-out duration, conditional wake-up, and etc. Even the worse, the longer interval, the less timely notification while the shorter interval, the more battery consumption. It is hard to balance, compared to the real right solution - GCM push. In summary, this idea introduced too much complexity.
As always, if you want to achieve that purpose, I'd suggest using Tasker together with the "wake-up" plug-in function provided by Greenify. Why do you think it is inefficient?
BTW, the solution of setAndAllowWhileIdle() is not the answer you may expect. If you are a developer and have read the documents, you should know this API is strictly limited and it also defeats the purpose of Greenify.
Click to expand...
Click to collapse
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
phantom146 said:
I havent tried testing whileidle() to be honest i just read it multiple times on google sources and the likes.
For your suggestion on tasker i would not recommend it. There has been an endless discussion on tasker if it was battery friendly or not and i know for a fact that it is not. The problem with tasker is its constant background monitoring which depends on your "trigger" and "event" so yep i wouldnt use tasker to automate things anytime soon.
And yes. Waking up apps periodically is the thing that i would like to propose though it might contradict M's doze mode. So overall just now im with you that its not a good solution for messaging apps.
I dont remember it was years ago way back when im using kitkat and a non-famous brand phone locally made here in our country, but as far as i remember messenger really still doesnt tickle a notification update.
So bottomline right now theres no solution for messaging apps other than leaving it as it is right? The problem is that those messaging apps have the highest background drain so i guess i had to adjust myself using messenger lol
Click to expand...
Click to collapse
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
oasisfeng said:
IM app without GCM push is such a pain, since it usually tries its best to improve the real-time notifications, at the cost of power consumption. In my experience, even a 5 minutes interval wake-up is far from enough for a IM app, but already increases the power consumption a bit.
Click to expand...
Click to collapse
Agreed and again facebook and messenger is to blame for the poorly written codes and the messy services they all have.
Right now my issue is solved and im glad for such a quick and concise response. Ill be waiting for the future beta releases and in the meantime if you need my help for an upcoming feature on M count me in, and ill also throw down "possible suggestions" for you and maybe give you some codes for it
Cheers bud
I included a screenshot of all the options I'm given on the Greenify Settings tab. I've always avoided using Greenify because it seems very difficult to use; however, I keep hearing about all the miracles it does as far as battery life so I want to give it a chance.
My confusion comes from the fact that out of all the Tutorials, Reviews, Articles, etc. I've seen and read on YouTube & Google, everyone either has an older version of Greenify than me, or the options are a little different. Some versions have more options than mine, and some fewer. Some have specific settings enabled, some disabled.
For example, some tutorials said to enable Aggressive Doze and Automatic Hibernation, some said to disable them.
I would appreciate it very much if someone with more knowledge on the subject could explain to me what some of these settings do, and which would be better.
Merazomo said:
I included a screenshot of all the options I'm given on the Greenify Settings tab. I've always avoided using Greenify because it seems very difficult to use; however, I keep hearing about all the miracles it does as far as battery life so I want to give it a chance.
My confusion comes from the fact that out of all the Tutorials, Reviews, Articles, etc. I've seen and read on YouTube & Google, everyone either has an older version of Greenify than me, or the options are a little different. Some versions have more options than mine, and some fewer. Some have specific settings enabled, some disabled.
For example, some tutorials said to enable Aggressive Doze and Automatic Hibernation, some said to disable them.
I would appreciate it very much if someone with more knowledge on the subject could explain to me what some of these settings do, and which would be better.
Click to expand...
Click to collapse
Which version of Android are you running? If 7,8 or 9, most likely you will not need Greenify since Android itself handles the apps very well. Only apps which could not be controlled by Android and which drain battery excessively need control through Greenify or some similar app. Doze in these versions of Android is very capable.
If you want to know something more about this, search for posts from member Davey126 in https://forum.xda-developers.com/apps/greenify/beta-greenify-3-1-build-1-1-23-2017-t3544311 thread.
tnsmani said:
Which version of Android are you running? If 7,8 or 9, most likely you will not need Greenify since Android itself handles the apps very well. Only apps which could not be controlled by Android and which drain battery excessively need control through Greenify or some similar app. Doze in these versions of Android is very capable.
If you want to know something more about this, search for posts from member Davey126 in https://forum.xda-developers.com/apps/greenify/beta-greenify-3-1-build-1-1-23-2017-t3544311 thread.
Click to expand...
Click to collapse
@tnsmani obviously received my check ...
Kidding aside, his guidance is spot on. If you decide to experiment further ignore all the options. They are largely refinements; defaults are fine for most. Simply respond to initial setup prompts (including the all important 'root' query), add 'offending' apps to the watch list and observe whether Greenify helps to reduce background activity.
Wait...you don't have any "offending" apps, do not know how to identify bad actors have no idea if you actually have a problem with excessive (operative word) battery consumption?? If so Greenify will only work as well as your perception of good/evil/impotent which is often an inaccurate measure of reality.
Sadly, Greenify does not have magical powers. That said, It is an effective tool to address a specific type of 'problem': reining in undisciplined app driven background activity...plus a few other gems outside the scope of this discussion. If your device is rocking Android 6/7/8/9/27 native doze does a fine job managing cranky apps that want to eat your battery any small children within a 10 foot radius. Best part: no confusing knobs and dials! It just works.
Enjoy your device.
tnsmani said:
Which version of Android are you running? If 7,8 or 9, most likely you will not need Greenify since Android itself handles the apps very well. Only apps which could not be controlled by Android and which drain battery excessively need control through Greenify or some similar app. Doze in these versions of Android is very capable.
If you want to know something more about this, search for posts from member Davey126 in https://forum.xda-developers.com/apps/greenify/beta-greenify-3-1-build-1-1-23-2017-t3544311 thread.
Click to expand...
Click to collapse
I'll definitely give that post by Davey126 a read, thanks.
I'm using a Galaxy Note 4 with Android Marshmallow 6.0.1. The phone is not officially supported anymore obviously, but with ROOT, it's still a great phone even today.
My only issue that made me consider Greenify; I don't know if this is typical of Android, is that I charge my phone to 100% before I go to sleep, and when I wake up it's at 86%. The battery is brand new and the phone has been restored to factory settings to start fresh.
Davey126 said:
@tnsmani obviously received my check ...
Kidding aside, his guidance is spot on. If you decide to experiment further ignore all the options. They are largely refinements; defaults are fine for most. Simply respond to initial setup prompts (including the all important 'root' query), add 'offending' apps to the watch list and observe whether Greenify helps to reduce background activity.
Wait...you don't have any "offending" apps, do not know how to identify bad actors have no idea if you actually have a problem with excessive (operative word) battery consumption?? If so Greenify will only work as well as your perception of good/evil/impotent which is often an inaccurate measure of reality.
Sadly, Greenify does not have magical powers. That said, It is an effective tool to address a specific type of 'problem': reining in undisciplined app driven background activity...plus a few other gems outside the scope of this discussion. If your device is rocking Android 6/7/8/9/27 native doze does a fine job managing cranky apps that want to eat your battery any small children within a 10 foot radius. Best part: no confusing knobs and dials! It just works.
Enjoy your device.
Click to expand...
Click to collapse
The screenshot I posted are the default settings as of now for my version of 4.3.2.0 of Greenify on my Galaxy Note 4. Would it be okay to assume that if I leave "these" settings on default without changing anything, and all I do is start choosing application to hibernate that I don't use often or don't need push notifications from, it's a good start?
I do have to choose applications manually for Greenify to start working right? I keep looking at all these "Smart Hibernation" & "Automatic Hibernation" settings and my brain goes back to regular applications like the old App Managers that would start working in the background without me settings anything up or choosing applications.
I'll give your post a read as well, and see if I can learn something from it. For once, I wish I had an Android phone with good battery life like my last iPhone; it wouldn't loose any charge overnight. Loosing 14% battery life overnight without doing anything is a little annoying, but now that I've tried Android with ROOT, it's practically imposible to go back to IOS; specially with all the customizing I can do on my Note 4.
Merazomo said:
I'll definitely give that post by Davey126 a read, thanks.
I'm using a Galaxy Note 4 with Android Marshmallow 6.0.1. The phone is not officially supported anymore obviously, but with ROOT, it's still a great phone even today.
My only issue that made me consider Greenify; I don't know if this is typical of Android, is that I charge my phone to 100% before I go to sleep, and when I wake up it's at 86%. The battery is brand new and the phone has been restored to factory settings to start fresh.
Click to expand...
Click to collapse
On 6, you may require the help of Greenify but only after you identify the rogue app/s. Unless you sleep for 24 hours a day, your idle drain is high (14% during sleep).
Visit the BBS thread, learn how to create an idle dump, install latest BBS beta from the PlayStore, take an idle dump and post it in the BBS thread and ask for help.
Merazomo said:
The screenshot I posted are the default settings as of now for my version of 4.3.2.0 of Greenify on my Galaxy Note 4. Would it be okay to assume that if I leave "these" settings on default without changing anything, and all I do is start choosing application to hibernate that I don't use often or don't need push notifications from, it's a good start?
I do have to choose applications manually for Greenify to start working right? I keep looking at all these "Smart Hibernation" & "Automatic Hibernation" settings and my brain goes back to regular applications like the old App Managers that would start working in the background without me settings anything up or choosing applications.
I'll give your post a read as well, and see if I can learn something from it. For once, I wish I had an Android phone with good battery life like my last iPhone; it wouldn't loose any charge overnight. Loosing 14% battery life overnight without doing anything is a little annoying, but now that I've tried Android with ROOT, it's practically imposible to go back to IOS; specially with all the customizing I can do on my Note 4.
Click to expand...
Click to collapse
Reread previous post. Your first task is to identify which app(s), if any, are draining your battery while the device is idle. Adding apps to Greenify w/o justification is a fools errand and will likely increase overall power consumption vs reduce it. Let's keep it simple. What apps regularly appear near the top of the list in Android's battery page in settings?
There are very few "new" batteries for 4 year old devices. While you many have purchased it recently there is a very good chance it sat on the shelf for several years. Or was 'loaded' with substandard cells with less than stated capacity.
Davey126 said:
Reread previous post. Your first task is to identify which app(s), if any, are draining your battery while the device is idle. Adding apps to Greenify w/o justification is a fools errand and will likely increase overall power consumption vs reduce it. Let's keep it simple. What apps regularly appear near the top of the list in Android's battery page in settings?
There are very few "new" batteries for 4 year old devices. While you many have purchased it recently there is a very good chance it sat on the shelf for several years. Or was 'loaded' with substandard cells with less than stated capacity.
Click to expand...
Click to collapse
The battery is good since I was still using Lollipop LOL not that long on my Note 4, and I felt it ran a lot cooler and battery would last longer than on Marshmallow, but app permissions were horrible in Lollipop; I had no control of my privacy whatsoever with apps.
The only top app on my battery apps list with 20% of the battery used overnight was ESPN. I don't even have push notifications enabled for this app, and I used it hours before I went to sleep and before I charged the phone. That might be the app that is harming my battery life. All the other apps are at 0.04% or less.
Merazomo said:
The battery is good since I was still using Lollipop LOL not that long on my Note 4, and I felt it ran a lot cooler and battery would last longer than on Marshmallow, but app permissions were horrible in Lollipop; I had no control of my privacy whatsoever with apps.
The only top app on my battery apps list with 20% of the battery used overnight was ESPN. I don't even have push notifications enabled for this app, and I used it hours before I went to sleep and before I charged the phone. That might be the app that is harming my battery life. All the other apps are at 0.04% or less.
Click to expand...
Click to collapse
ESPN app would be an excellent candidate to Greenify. Add it to the 'watch' list and observe device behavior over 24-48 hours.
Davey126 said:
ESPN app would be an excellent candidate to Greenify. Add it to the 'watch' list and observe device behavior over 24-48 hours.
Click to expand...
Click to collapse
Everything is as you said. Greenify's default settings are more than satisfying, specially since all I wanted to do was to find the culprit that was killing my battery.
After using BetterBatteryStats & Greenify, it turns out "ESPN" and "Samsung Peel Remote Control" are both using more battery life overnight as I sleep, than the "System" itself.
ESPN behaves as it should when I hibernate it; however, Samsung's Peel Remote wakes up overnight; it won't stay hibernated.
I've been trying to use the scissor's icon to prevent other apps from waking the Peel Remote, but it gives me a failed message.
At least now I know that my problem is not the battery or the phone.
Merazomo said:
... however, Samsung's Peel Remote wakes up overnight; it won't stay hibernated.
I've been trying to use the scissor's icon to prevent other apps from waking the Peel Remote, but it gives me a failed message.
At least now I know that my problem is not the battery or the phone.
Click to expand...
Click to collapse
Me thinks you should consider another app:
https://fossbytes.com/peel-remote-use-remove-smart-remote/
There are ways to tame the monster using perfectly legal advanced tools (MAT, SD Maid, etc.) but such discussion is beyond the scope of this thread.
Davey126 said:
Me thinks you should consider another app:
https://fossbytes.com/peel-remote-use-remove-smart-remote/
There are ways to tame the monster using perfectly legal advanced tools (MAT, SD Maid, etc.) but such discussion is beyond the scope of this thread.
Click to expand...
Click to collapse
I though I was the only one struggling with these apps. I installed an app that called AFWall+ though, that blocks Internet/Data access to the Peel Remote. I no longer get that annoying TV Guide, Ads, or VOD recommendations; just the ability to use it as a normal remote.
The last 3 days, I've only lost 5% battery life overnight with the Greenify & AFWall+ combination. If that keeps up, it's as good as it is going to get for me. If it changes back to 14%, I'm just going to uninstall Peel.
Merazomo said:
I though I was the only one struggling with these apps. I installed an app that called AFWall+ though, that blocks Internet/Data access to the Peel Remote. I no longer get that annoying TV Guide, Ads, or VOD recommendations; just the ability to use it as a normal remote.
The last 3 days, I've only lost 5% battery life overnight with the Greenify & AFWall+ combination. If that keeps up, it's as good as it is going to get for me. If it changes back to 14%, I'm just going to uninstall Peel.
Click to expand...
Click to collapse
A software firewall (preferably VPN based) is an excellent way to block unwanted content and network communications including ads, tracking uploads and/or malicious downloads. I run some type of software firewall on every device I own. As for idle drain rates, I average 0.15-0.25%/hr on WiFi only tablets; 0.4-0.6%/hr on phones. Pretty consistent range regardless of brand, ROM or other variables. Greenify, which I use sparingly, is the only non-native power management tool in my arsenal. No silly alarm/wakelock squashing, doze tuners, etc. Mind your settings, behaviors and app portfolio. Pretty simple stuff. Depressing news for budding geeks with too much time on their hands.
Merazomo said:
I though I was the only one struggling with these apps. I installed an app that called AFWall+ though, that blocks Internet/Data access to the Peel Remote. I no longer get that annoying TV Guide, Ads, or VOD recommendations; just the ability to use it as a normal remote.
The last 3 days, I've only lost 5% battery life overnight with the Greenify & AFWall+ combination. If that keeps up, it's as good as it is going to get for me. If it changes back to 14%, I'm just going to uninstall Peel.
Click to expand...
Click to collapse
First and most important, it's exactly as @Davey126 stated directly above. Second in order to support your decision: For many years now, I use Greenify and AFWall+ Pro, and I confirm your observation. All of our telephones (we don't own an Android tablet etc.) achieve overnight battery drainages between 0.5 - 0.7%/h including network connection and some non-greenified apps. In airplane mode the drainage decreases to 0.2 - 0.3%/h. For quite some time till about a year ago, I also used tools like Amplify, PowerNap etc. until I realised it makes no sense to try to turn on these knobs i.e. to fight effects but not the causes - and more important I didn't gain any battery life by their utilisation.
BTW: If you're interested in trying a different firewall, NetGuard by M66B, very well known among all users interested in privacy, is an interesting alternative. Based on VPN and no-root required. The only reason why I stay with AFWall+ Pro and don't switch to NetGuard is Android's inherent limitation to only allow one VPN tunnel at a time. And as I always enable my own secure VPN connection with my RaspberryPi in our home network before I connect to mobile data or a foreign WiFi, I can't use NetGuard.
Oswald Boelcke said:
First and most important, it's exactly as @Davey126 stated directly above. Second in order to support your decision: For many years now, I use Greenify and AFWall+ Pro, and I confirm your observation. All of our telephones (we don't own an Android tablet etc.) achieve overnight battery drainages between 0.5 - 0.7%/h including network connection and some non-greenified apps. In airplane mode the drainage decreases to 0.2 - 0.3%/h. For quite some time till about a year ago, I also used tools like Amplify, PowerNap etc. until I realised it makes no sense to try to turn on these knobs i.e. to fight effects but not the causes - and more important I didn't gain any battery life by their utilisation.
BTW: If you're interested in trying a different firewall, NetGuard by M66B, very well known among all users interested in privacy, is an interesting alternative. Based on VPN and no-root required. The only reason why I stay with AFWall+ Pro and don't switch to NetGuard is Android's inherent limitation to only allow one VPN tunnel at a time. And as I always enable my own secure VPN connection with my RaspberryPi in our home network before I connect to mobile data or a foreign WiFi, I can't use NetGuard.
Click to expand...
Click to collapse
Yeah, after doing much research online, it came down to NetGuard - NoRoot Firewall - Droidwall(now Avast) - Afwall+.
I chose Afwall+ because it seemed easier to use. The other apps seem more customizable if you know what you're doing, but for what I needed Afwall+ is more of a "click and save" type of app.
Davey126 said:
A software firewall (preferably VPN based) is an excellent way to block unwanted content and network communications including ads, tracking uploads and/or malicious downloads. I run some type of software firewall on every device I own. As for idle drain rates, I average 0.15-0.25%/hr on WiFi only tablets; 0.4-0.6%/hr on phones. Pretty consistent range regardless of brand, ROM or other variables. Greenify, which I use sparingly, is the only non-native power management tool in my arsenal. No silly alarm/wakelock squashing, doze tuners, etc. Mind your settings, behaviors and app portfolio. Pretty simple stuff. Depressing news for budding geeks with too much time on their hands.
Click to expand...
Click to collapse
Curiosity bricked a few of my phones over the years LOL. I guess it's human nature.
Reading through a bunch of threads when I still didn't know what Greenify was, there were a few discussions about being able to get "push notifications" when an app was still in hibernation.
How much truth is there to those statements? I have Instagram, Messenger, Facebook, etc. installed on my phone not because I use them constantly, but because it's the easier/cheaper way for my family to contact me.
It would be great to be able to hibernate all those apps, and still know when my family is trying to contact me, even if I have to manually hibernate the apps again afterwards.
Or did I read too much into it and mixed things up?
Merazomo said:
Curiosity bricked a few of my phones over the years LOL. I guess it's human nature.
Reading through a bunch of threads when I still didn't know what Greenify was, there were a few discussions about being able to get "push notifications" when an app was still in hibernation.
How much truth is there to those statements? I have Instagram, Messenger, Facebook, etc. installed on my phone not because I use them constantly, but because it's the easier/cheaper way for my family to contact me.
It would be great to be able to hibernate all those apps, and still know when my family is trying to contact me, even if I have to manually hibernate the apps again afterwards.
Or did I read too much into it and mixed things up?
Click to expand...
Click to collapse
Push notifications work with some Greenifed apps (must be GCM capable) but may be delayed by minutes/hours depending on Greenify settings, app design, GCM capabilities, availability of Xposed framework, timing of doze maintenance windows and a bunch of other variables. Best way to assess with your app portfolio is to try.
i was wondering..... some apps like greenify or superfreezZ use accessibility usage to track the app behaviour and auto hibernate them, but since android 9 there is a new command to restrict the background activity of an app and it is RUN_ANY_IN_BACKGROUND
you can simply enable in app info>battery>background restriction set to RESTRICT.
is it a "better" way to hibernate an app and stop all trackers, alarms and services that DRAIN the phone battery? or maybe it's is less powerfull than "force stop" the app?
how does compare DOZE to RUN_ANY_IN_BACKGROUND ? i suppose 1st is a generall switch off for all apps, BUT only on screen off. when you use the phone the "bad" app could continue to do what he wants, wakelocks, call some strange domains to receive or updload datas.... BUT WHAT IF it is restricted by RUN_ANY_IN_BACKGROUND? the app is not force stopped but should be something like hibernated when it's not foreground....?
i found some info here
App Power Management | Android Open Source Project
source.android.com
realista87 said:
i was wondering..... some apps like greenify or superfreezZ use accessibility usage to track the app behaviour and auto hibernate them, but since android 9 there is a new command to restrict the background activity of an app and it is RUN_ANY_IN_BACKGROUND
you can simply enable in app info>battery>background restriction set to RESTRICT.
is it a "better" way to hibernate an app and stop all trackers, alarms and services that DRAIN the phone battery? or maybe it's is less powerfull than "force stop" the app?
how does compare DOZE to RUN_ANY_IN_BACKGROUND ? i suppose 1st is a generall switch off for all apps, BUT only on screen off. when you use the phone the "bad" app could continue to do what he wants, wakelocks, call some strange domains to receive or updload datas.... BUT WHAT IF it is restricted by RUN_ANY_IN_BACKGROUND? the app is not force stopped but should be something like hibernated when it's not foreground....?
i found some info here
App Power Management | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Force Stop = "Hibernate"
Force Stop = App is killed and removed from memory, and (for the most part) not be able to start itself up again. User can. I read you asked the exact same question elsewhere and some talked how apps can restart themselves. Yes, its true BUT its the exceptioopn, not the rule. The only app that ciones to mind at the moment in my past is Google Play. His statement is misleading in practical everyday use. Test it for yourself.
I havent used it, but, RUN_ANY_IN_BACKGROUND explicitly requires the "deny" or "allow" attribute. The app is still in memory and therefore would have some possibility of bringing itself back to life; much more so than a force-stop. Some apps are developed with running a service as a foreground app. Also, RUN_ANY_IN_BACKGROUND is a TESTING feature of android.
ie Force Stop > RUN_ANY_IN_BACKGROUND
I have a hot spot on my home screen (custom launcher allowing scripts) that turns my screen oof and then force-stops all apps that I do not want running in the background.
You want an app to stop consuming battery, then force-stop is the way to go.
"RUN_ANY_IN_BACKGROUND is a TESTING feature of android."
mhhh so u say that not every app will really stop his background behaviour for sure? i thought that the command is quite sure to keep a closed app a "not battery hungry" app, stopping some services, alarms.
basically if u would choose an app to force close apps, would u choose superfreezz (because it s foss) over other alternatives like greenify or brevent?
because i would avoid to install any app for this, IF the command RUN_ANY....... is to consider quite powerfull and acceptable to "stop draining " battery from malicious apps...
realista87 said:
"RUN_ANY_IN_BACKGROUND is a TESTING feature of android."
mhhh so u say that not every app will really stop his background behaviour for sure? i thought that the command is quite sure to keep a closed app a "not battery hungry" app, stopping some services, alarms.
Click to expand...
Click to collapse
If you want to stop it, the a force stop is the way. Its much more "powerful" than what you found.
realista87 said:
basically if u would choose an app to force close apps, would u choose superfreezz (because it s foss) over other alternatives like greenify or brevent?
because i would avoid to install any app for this, IF the command RUN_ANY....... is to consider quite powerfull and acceptable to "stop draining " battery from malicious apps...
Click to expand...
Click to collapse
I explained to you, I use a shell script to get the job done. No need for another app, that also may consume unnecessary battery and memory.