I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
scandiun said:
I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
Click to expand...
Click to collapse
Look elsewhere. Greenify doesn't "freeze" any app.
tnsmani said:
Look elsewhere. Greenify doesn't "freeze" any app.
Click to expand...
Click to collapse
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
scandiun said:
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
Click to expand...
Click to collapse
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
tnsmani said:
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
Click to expand...
Click to collapse
Yes Hibernation Manager and Greenify only work when screen is off. That's enough for me, but do you know if any app that does it also when the screen is on? (App always hibernating unless on foreground)
Related
I've tried doing a lot of personal research before asking. I have watchdog and betterbatterystats. I found 2 apps chewing away at my battery. After using the app I always press back and then it pops up do you really want to exit and I select yes. However, I look at the processes and I will see it running in the background. Using stuff like advanced task killer (and a bunch of other killer apps) doesn't help, as soon as it kills it, the thing just spawns again. I had to force close it or sometimes reboot the phone. Is there any app that locks down these apps so it only allows process to run when the app is in the foreground and as soon as we leave it closes all aspect of that app? (I can't uninstall those 2 apps cause they are kinda essential; but by no means does it require any background process or need to be constantly running). So far it only runs in the background if I opened the app once, but if it starts to auto run I'm screwed.
Is there any app like the cydia backgrounder where I can set a whitelist or a blacklist that only lets the app run in the foreground and as soon as I press home it will stop all its process.
Autostarts in the market. It let's you see what apps start up under what conditions. I would assume you can just doable all conditions the apps can start up from and it would do as you describe.
Sent from my GT-I9300 using Tapatalk 2
joshnichols189 said:
Autostarts in the market. It let's you see what apps start up under what conditions. I would assume you can just doable all conditions the apps can start up from and it would do as you describe.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I have autostart doesn't work, ok I give you an example:
Groupon app. If you don't load it after a reboot it doesn't run, however as soon as you opened the app once. Theres like no way to close it.
Come-on... one of you guys must know how to close an app and prevent it from loading up after I leave the app. Isn't there anything like cydia backgrounder that I can set so apps are only allowed to load in the foreground and closes as soon as go back to the launcher???
Solution
The best solution to this is to install titanium backup. After that, create a widget in ur homescreen and select titanium backup widget (action). Then, select the action freeze/defrost/launch and after select the app ex. Facebook and create the widget. After, you will notice that the widget for the Facebook app has created to ur homescreen with a green locker. If u press on it, it will lock the app (freezed it actually) so it doesnt run. if you want to run the app, tap again on it and automatically will defrost it and launch it.
Hit thanks if i helped you
jcheong said:
I've tried doing a lot of personal research before asking. I have watchdog and betterbatterystats. I found 2 apps chewing away at my battery. After using the app I always press back and then it pops up do you really want to exit and I select yes. However, I look at the processes and I will see it running in the background. Using stuff like advanced task killer (and a bunch of other killer apps) doesn't help, as soon as it kills it, the thing just spawns again. I had to force close it or sometimes reboot the phone. Is there any app that locks down these apps so it only allows process to run when the app is in the foreground and as soon as we leave it closes all aspect of that app? (I can't uninstall those 2 apps cause they are kinda essential; but by no means does it require any background process or need to be constantly running). So far it only runs in the background if I opened the app once, but if it starts to auto run I'm screwed.
Is there any app like the cydia backgrounder where I can set a whitelist or a blacklist that only lets the app run in the foreground and as soon as I press home it will stop all its process.
Click to expand...
Click to collapse
I just want to add some info for a better understanding even if I understand what you meant.
1. A package showing in the process list after you chose "exit" is a sign for a service running. This is not necessary bad as there are many services doing nothing but waiting for events to process (of course some service do stuff in the background and it is good to look after those).
2. In Android there is no such concept as an app, there are activities (dialogs), and services and both have pretty complex life cycles (not just opened or closed) as you can see here
But back to your question: the right way to get rid of apps you don't want/need (also called bloatware in some cases) is to freeze them. One good tool for doing that is titanium backup.
chamonix said:
I just want to add some info for a better understanding even if I understand what you meant.
1. A package showing in the process list after you chose "exit" is a sign for a service running. This is not necessary bad as there are many services doing nothing but waiting for events to process (of course some service do stuff in the background and it is good to look after those).
2. In Android there is no such concept as an app, there are activities (dialogs), and services and both have pretty complex life cycles (not just opened or closed) as you can see here
But back to your question: the right way to get rid of apps you don't want/need (also called bloatware in some cases) is to freeze them. One good tool for doing that is titanium backup.
Click to expand...
Click to collapse
I understand the point of apps that show up and are 0% cpu usage like facebook etc. I was only using it as an example. There are plenty of other apps that do infact chew up cpu and battery after it is loaded for the first time and is unable to close the background processes (they are shown in the watchdog and betterbatterystats). So the only way is to freeze and unfreeze everytime I use these apps?
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 often see a few apps running in the background and wonder why they are not Grenified. This happens to me most with YouTube, Google Drive & Titanium Backup. There doesn't seem to be a reason why they should run in the background, thus I'd expect them to be hibernated by Greenify.
I have a rooted LG L7 II device running CM11.
Digdis said:
I often see a few apps running in the background and wonder why they are not Grenified. This happens to me most with YouTube, Google Drive & Titanium Backup. There doesn't seem to be a reason why they should run in the background, thus I'd expect them to be hibernated by Greenify.
I have a rooted LG L7 II device running CM11.
Click to expand...
Click to collapse
Did you Greenify those apps? I had to ask since you didn't specifically say so. Also, is Greenify enabled in Device Administrators and Accessibility settings? And are you running Greenify in Root mode or Boost mode?
tnsmani said:
Did you Greenify those apps? I had to ask since you didn't specifically say so. Also, is Greenify enabled in Device Administrators and Accessibility settings? And are you running Greenify in Root mode or Boost mode?
Click to expand...
Click to collapse
Thanks. Gotta to admit that I didn't Greenify them manually, but waited for Greenify to do it automatically. I now sent them manually to hibernation and will keep track on whether they run in the background as they did before.
However, isn't the whole point behind Greenify that you don't need to do it manually, but let Greenify do that for you? AFAIK, neither of these apps have anything to do in the background, so isn't Greenify supposed to notice that and send them to hibernation?
Digdis said:
Thanks. Gotta to admit that I didn't Greenify them manually, but waited for Greenify to do it automatically. I now sent them manually to hibernation and will keep track on whether they run in the background as they did before.
However, isn't the whole point behind Greenify that you don't need to do it manually, but let Greenify do that for you? AFAIK, neither of these apps have anything to do in the background, so isn't Greenify supposed to notice that and send them to hibernation?
Click to expand...
Click to collapse
Greenify doesn't automatically greenify(!) any app. There are many apps running in the background, some required, some not required. So you make the choice to greenify whatever you choose to, depending on your requirements. This is because if you greenify all the apps running in the background, you will lose some functionality. While you may choose to greenify one particular app because you don't need it to run in the background, I may not agree with you since I may require its functionality. So to each his own. That is the beauty of Greenify, that it allows you to choose.
However, once you greenify a particular app, Greenify takes over and further greenifying that app is automatic.
tnsmani said:
Greenify doesn't automatically greenify(!) any app. There are many apps running in the background, some required, some not required. So you make the choice to greenify whatever you choose to, depending on your requirements. This is because if you greenify all the apps running in the background, you will lose some functionality. While you may choose to greenify one particular app because you don't need it to run in the background, I may not agree with you since I may require its functionality. So to each his own. That is the beauty of Greenify, that it allows you to choose.
However, once you greenify a particular app, Greenify takes over and further greenifying that app is automatic.
Click to expand...
Click to collapse
Thanks for your answer. I did Greenify apps manually in the past, ones that I considered their running in the background as unnecessary (such as a shopping app I had which kept notifying me of new deals). However, I thought that Greenify could somehow identify apps who run in the background without need, and so it would send them to hibernation automatically. Guess I was wrong here.
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Did you try the shallow hibernation or normal hibernation?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Yes, Greenify is working on many (tens of) thousands of devices. Likely YOUR device, rom or kernel is aggressively clearing memory due to limited resources. What are you using?
tnsmani said:
Did you try the shallow hibernation or normal hibernation?
Click to expand...
Click to collapse
I tried both but app restarts instead of resuming.
Yes, Greenify is working on many (tens of) thousands of devices.
Click to expand...
Click to collapse
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
devsk said:
I tried both but app restarts instead of resuming.
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
Click to expand...
Click to collapse
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Davey126 said:
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Click to expand...
Click to collapse
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Personal conclusion: Greenify (currently on v4.6.3) works exactly and perfectly as advertised!
Personal remark: I concur with @Davey126. Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Android hibernation is not the same as Windows hibernation. Resumability is not assured - especially on a resource constrained or highly 'tuned' ROM. You should probably read up on how it works and the primary objective of Greenify which is to suspend unwanted background activity. In that respect it shares many characteristics with doze.
Oswald Boelcke said:
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Click to expand...
Click to collapse
Did you use the pause/resume feature of the Andoku game or did you just click the game to start it again, and it resumed where you left off? Typically, if you resume using the game's feature, you have to click through 3 times to resume your game. If the app is resuming from where it left off, its 1 click just to start the game.
If you resumed the app as if you switched to it using app switcher, then something definitely is broken on my end.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Click to expand...
Click to collapse
I do the same.
Oswald Boelcke said:
Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
Click to expand...
Click to collapse
I am stock Pixel 3 XL with Magisk 18.1 root. Nothing else. I have given all perms needed by greenify.
Android hibernation is not the same as Windows hibernation.
Click to expand...
Click to collapse
I think this is where likely the disconnect is. I started using greenify several years ago (I have been here on these forums for a while, I keep that dated forum reference in my signature for remembering how far android and this community has come). If I recall correctly, I used to be able to resume apps, just by clicking or switching to them. Now, I notice a different behaviour: the app restarts from scratch. That's all. Obviously, I preferred the app to not start but resume like I was just switching to it.
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
olliebean said:
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
Click to expand...
Click to collapse
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Davey126 said:
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Click to expand...
Click to collapse
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
olliebean said:
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
Click to expand...
Click to collapse
Well, no ... but this is not the place for that discussion. Not going to get into Android 101 or validating speculation around various actions.
---------- Post added at 05:18 PM ---------- Previous post was at 04:52 PM ----------
devsk said:
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
Click to expand...
Click to collapse
Sorry it is not working with your device/kernel/ROM/root solution. Could be an adverse interaction with the doze mechanisms in Android 9, aggressive memory management settings (eg: VM, LMK), resource mapping of the app(s) you are trying to hibernate, etc. I have not see a lot of feedback from Pie users as doze generally addresses rogue background activity and corresponding power drain. So the behavior may be different on that platform. I use Greenify on a variety of devices for other reasons for which it continues to work well. Just another tool in shop; appropriate selection is the key to success. Good luck.
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?