Related
Hi
First of all thank you Oasis for creating a tool to fix things that shouldn't be broken to begin with! You are an example for a lot of developers :good:
I've read the first couple of posts on the original thread but I still have a few things that are not clear..
The advice of Oasis himself is too hibernate only those apps that misbehave. He states that hibernating apps will also remove them from the memory, which will come with a performance/cpu usage penalty when you want to use them again.
In the video tutorial however Josh greenifies almost every application that doesn't need push notifications.
So this would mean that when I use an application that doesn't have notifications but I open frequently, for example Nu.nl, a dutch newsapp, it will always have to reload the app from scratch instead of loading it from memory?
So baically the best way to use Greenify would be to NOT just greenify most apps, but to use the analyzer frequently and see what's running in the background and greenify those that don't depend on notifications?
Then newsapps that don't push news, image viewers, file managers, system tools like SD Maid and simple games that don't use internet should be ok not being greenified?
Is there no big list available of apps that misbehave or are safe to keep de-greenified?
Thanks in advance for any help on this.
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
marchrius said:
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
Click to expand...
Click to collapse
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
latino147 said:
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
Click to expand...
Click to collapse
"Disable Service" (and "Autostarts") from play store.
marchrius said:
"Disable Service" (and "Autostarts") from play store.
Click to expand...
Click to collapse
Ah, I believed those were two functions withing Greenify I couldn't find
wtf, FB has 62! services! None of them where active though, until you open the app, then it was 3.
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
The only issue with this second method being that you don't always really know what these services do.
latino147 said:
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
Click to expand...
Click to collapse
Exactly. Take google play services for example. If you greenify it, you'll lose gcm and other functions and that's not advisable at all (in fact greenify hides it). But with disable service (and autostarts/system tuner)you can choose what to disable while still mantaining gcm, location services (when needed), sync etc. I can' remember what I did in system tuner regarding gplay services (I followed some tutorial), but with disable service I disabled analyticsservice (this one will reactivate itself unless you do some tweak with system tuner), refreshenabledstateservice, playlogreportingservice, googlehttpservice, playlogbrokerservice, adrequestbrokerservice, gcmschedulerwakeupservice, advertisingidservice, adsmeasurementservice, locationwearablelistenerservice, nlplocationreceiverservice, geocodeservice, dispatchingservice and playlogservice. A reboot is needed. Haven't lost a single function since weeks (gcm, location, autosync and every google app in general are working 100% fine).
Same story with play store. Apps wake it very often, so greenify it does more harm than good. Instead, you can disable pendingnotificationsservice, contentsyncservice and dailyhygiene (and will still be fully functional).
Of course these are little tips to increase performance and battery life even more. I use greenify for 90% and more of apps that "misbehave" and disable service/autostarts/system tuner for the remaining 10% "misbehaving" apps. However, an app "fixed" with such methods will stay cached while with greenify is completely closed (resulting in more cpu/time/battery consumption when loaded again).
The only issue with this second method being that you don't always really know what these services do.
Click to expand...
Click to collapse
Like I already said, for general purposes you'd better simply greenify the "misbehaving" apps. If you use it/it is woken very often, you can consider these methods.
Yes, it's a "trial and error" thing. Unless you're disabling services with self-explainatory names such as "pushservice".
Never installed Facebook official app but I heard many times that is a notorious hogger and takes many personal datas too, for which you can look for xprivacy xposed module as well.
I'll start experimenting with it today :good:
I understand the whole approach Android uses to memory management as opposed to Windows etc....
I also found this blurb below
It's important to note that Greenify is not a task killer (which you shouldn't use anyway), and it doesn't "freeze" apps. The apps that Greenify hibernates are still usable if you want to switch to them, and you can still pass data to them as though they were running. When you switch back to them, it's like you never left. Greenify just keeps those apps from launching new background processes (a problem with task killers) and you don't have to unfreeze or thaw an app to use it when you want to (a problem with "frozen apps").
Click to expand...
Click to collapse
But here is what I don't understand:
1) Even though it isn't a Task Killer per-say, it sure sounds like an advanced task killer to me. If it is preventing something from starting up, it is killing it.
2) What benefit is Greenify supposed to have? Having all (by all I mean maybe 5 at most) desired apps hibernating, I have 700MB of free memory (using xposed method). If I remove Greenify I have 1.5GB of free RAM. These numbers are with ALL applications already open since boot that I use on a daily basis.
While full memory is not a bad thing in Android, how can it be better having 1 app hog all of the memory vs having 5 apps running in the background using less memory. Can someone shed some further light on this?
mikemikemikexxx said:
While full memory is not a bad thing in Android, how can it be better having 1 app hog all of the memory vs having 5 apps running in the background using less memory. Can someone shed some further light on this?
Click to expand...
Click to collapse
If I understand you correctly you're saying that greenify uses a lot of ram? Greenify for me is idling at 5-7 mb of ram all for time.
cAase said:
If I understand you correctly you're saying that greenify uses a lot of ram? Greenify for me is idling at 5-7 mb of ram all for time.
Click to expand...
Click to collapse
Correct, it was literally using around 700Mb. I rebooted to make sure it wasn't a fluke. I removed Greenify, rebooted again and had 1.5Gb free Ram
mikemikemikexxx said:
Correct, it was literally using around 700Mb. I rebooted to make sure it wasn't a fluke. I removed Greenify, rebooted again and had 1.5Gb free Ram
Click to expand...
Click to collapse
Sounds completely weird.
the main benefit of greenify is the point that it prevents apps from starting (they are frozen untill you open them) this way the apps can't force wakelocks and your device kann stay in deepsleep state longer
mikemikemikexxx said:
Correct, it was literally using around 700Mb. I rebooted to make sure it wasn't a fluke. I removed Greenify, rebooted again and had 1.5Gb free Ram
Click to expand...
Click to collapse
As I understand, greenify to me is more to battery saver depends on stopping unwanted and unneeded wakelock when app is Greenified. Also as I understand, when an apps launch or relaunched, it will consume more ram in normal way (without being Greenified).
Try this, its not a solution, more to suggestion. Try use Wake Lock Detector along with Greenify, one app will detect the problem and another will execute an action to prevent "unwanted battery and RAM usage".
Above all, it depends on how and what method of modding you perform on your device.
Its just my logic thought(not black n white proven). Hope it will help us a little.
i8190n SlimKat9.0(Android-Andi)
But all the settings. It won't let me hibernate the apps before I've completed 10 - 15 settings and there are no explanations to what the settings are. Greentify is totally useless if you're not a techie.
RolfyBerg said:
But all the settings. It won't let me hibernate the apps before I've completed 10 - 15 settings and there are no explanations to what the settings are. Greentify is totally useless if you're not a techie.
Click to expand...
Click to collapse
Well - not my experience; defaults work well on most devices. There are brief in-app explainations for many options with expanded material in FAQs, XDA forum and G+ pages. Best consider an iDevice if you need/want handholding; genius bars everywhere.
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
mermaidkiller said:
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
Click to expand...
Click to collapse
Of course it does. The size/activity in this forum plus frequent mentions in respected publications over many years should offer some clues to its integrity. Whether it is working on your device is a different matter.
Greenify does best on rooted devices as unharnessed ROMs can both undo actions and/or misrepresent status. It's quite possible an app placed in hibernation was later woken via internal trigger that Greenify can not suppress on an unrooted device. In the case of Opera (my preferred browser) there is regular syncing of tabs and downloading of *cough* 'news' if you have those features enabled.
I also question info coming out of the "Android Assistant" app. On my device it claimed all apps had zero CPU...including itself. Also did not display system partitions correctly nor properly detect the sensor suite. Granted I only spent a few minutes poking around. Maybe some switches needed to be thrown.
Finally, you probably don't need Greenify on Oreo as Doze does a find job with power management.
planetera said:
Don't I really need Greenify on oreo? Is Doze on Oreo really that good? Can you confirm please? I've been always using Greenify but if I don't need it on Oreo, I'll remove it
Click to expand...
Click to collapse
Well don't take my word for it. Simply remove all apps from Greenify's hibernation list (hopefully there are not many there), observe device behavior over the next few days then make your own decision.
planetera said:
Well, thanks for information. Just made a quick research and everyone says Greenify is trash on Oreo. So I just uninstalled it. Thanks for heads up. Glad I've seen your comment
Click to expand...
Click to collapse
Trash? Err-no. I have it installed on every one of my devices for valid reasons. Needed for generic power management on Doze capable ROMs? Probably not (and as such serving no purpose). Enjoy your device.
planetera said:
ok, but, when Greenify hibernates an app, you don't get notificaton froms this app, but when Android itself hibernates the app, you still get notifications, how does these two compare?
Click to expand...
Click to collapse
It varies by app, developer approach and user settings. Many apps will experience delayed notifications with Doze while other punch right through. Greenify can be configured to permit notifications but only if the app utilizes GCM (Firebase). Aggressive doze, light hibernation, Xposed framework availability and several other variables contribute to notification behavior. If your head is spinning it should! End users should not need to know the contents of the underwear drawer. Best practice is to simply let Android do its thing without 3rd party tools unless one understands their behavior and application. At one time such tools were needed to achieve acceptable app/device performance and battery life. Not so today. Is such a simplistic solution 'optimal' form an enthusiasts point-of-view? Probably not. It is acceptable/reasonable from an end-user perspective? In most cases 'yes' yielding a good balance of performance and battery life with minimal interaction for those who simply want to enjoy their device vs. manage it. Good luck with whatever direction you choose.
Agree one hundred percent!
Greenify on Oreo is an appendage that is best left out in my opinion, since for most, Oreo itself manages the drain admirably. Though I have it installed, it is more by way of habit than necessity. I have experienced Oreo without Greenify and have no complaints.
Greenify is STILL works.
But its benefit on recent Android versions is not as prominent as on earlier versions.
Coz we already have Doze starting from Marshmallow.
It works for me. I have a samsung tab a 9.7 sm-t550 with an aicp 8.1 rom (lineageos based). Therefore it doesn't have the built-in samsung app device maintenance. I've also discovered a little trick to using greenify that I want to share. I use greenify with another app called shutapp. Shutapp is an app that helps you force stop apps running in the background. Except I don't do that. I use it solely for the purpose of having an accurate number of apps running in the background. Then I open the app to see which ones are running. Next I open greenify and hibernate them. I use this method, because I found that when you force stop the apps they will open back up again. Also, I use the widget from shutapp and not the floating bubble which requires extra permissions granted. The widget does the same thing without the extra permissions. This method I discovered has improved my ram and battery life drastically. I can tell because I use status bar mini pro to monitor my ram speed constantly. And finally I do have Xposed with the donation package of greenify, didn't want to leave that out. Not sure if it makes a difference or not, but wanted to be accurate. That's it, hope that works for somebody else, take care.
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
tnsmani said:
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
Click to expand...
Click to collapse
Greenify works just fine on recent Android builds. It is a tool that can be very beneficial when properly used to produce a specific outcome. That said, it is rarely needed on Android 6+ as doze handles most of the heavy lifting. Enjoy using your device vs trying to fix problems you haven't identified.
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.
My background apps are killed way too often. Is it possible to change that behaviour? Even music apps are killed while I'm playing music.
I have tried several custom roms and kernels but nothing seems to change the settings. Is either able to change RAM management settings?
I have also tried several apps that claim to be able to change RAM management settings without success.
Disabling battery optimisation doesn't help.
I have uninstalled unused apps and disabled autostart (boot completed receiver) for non-essential apps to reduce RAM usage.
When I use a RAM monitor it will show RAM usage at ~75% when apps are killed.
My old phone (Note 4) only had 3 GB ram but could still keep more apps in memory.
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
ChazzMatt said:
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
Click to expand...
Click to collapse
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Telorast said:
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Click to expand...
Click to collapse
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Worth a try. Installed Greenify and added most apps with ignore background-free.
Telorast said:
Worth a try. Installed Greenify and added most apps with ignore background-free.
Click to expand...
Click to collapse
I even hibernate alleged background free apps, just in case.
ChazzMatt said:
Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Click to expand...
Click to collapse
VERY TRUE!
This always infuriated me, not just on phones, PCs too, all the way back to the DOS days. An obsession with running in the background, as if it's particularly clever. :cyclops:
I've also found that turning off battery optimization for apps I don't want killed helps. I've had the same experience with music and podcast apps getting killed in the background and turning off their battery optimization usually fixes it.
There are some simple things to try that do not require any special apk's. One is to look in the apps section of the "Developer options" sub-menu. The default settings work well in most instances. Perhaps you accidently enabled closing of apps when a background limit has been reached or have ticked force closure of apps on exit.
Another place to look is in the "Power saving exclusions" sub-menu in the Battery settings. Music makes some boring forms of exercise less tiresome and provides additional motivation for activities that are challenging but fun (mountain biking). The music should not stop, but it might for default settings. Enabling a power saving exclusion for your music app will keep it running.
ChazzMatt said:
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Click to expand...
Click to collapse
Been using Greenify for a bit now and doesn't seem to help much. It shows a bunch of hibernated apps but multitasking is still nearly impossible.
I had assumed the problem was related to the Mem Free settings rather than actual free memory but no one here has mentioned it. Is that because no one else thinks it's the problem or maybe I have misunderstood what those settings do?
I thought apps were free to use as much memory as they want until certain thresholds on total memory usage were met, then the system would ask or force apps to release memory.
Apps that let you edit those settings usually shows several thresholds where the system gets progressively more aggressive at freeing memory as memory is running out. But they all look hopelessly out of date so maybe it works completely differently today?