Related
Hi, guys. I have a little problem and I hope you can help me. Sometimes (it's not usual, but sometimes it happens) my phone (Nexus one, CM7) runs quite slowly, and not fluent at all, just because of an app that is eating all the memory / processor. If I kill that app, problem solved. OK, this is not the real problem here.
When this happened the first time, I went to the running services section in settings, and I checked that the services listed are not ALL the running processes, so even if I kill all the services there, there are still running apps. Then, I tried to install several app killers, just to check if they kill all the running apps, but not only they don't list all the running apps, but also when killing all, there are still apps that keep running (like some games), and the only way I found to find them is checking one by one in the apps list, if they are running or not.
Is there any app to check at once ALL the running apps? I have looked for it, but all I have found are apps to do exercise ("running apps", D'oh!), and stuff like that.
Thank you.
Here's a little something...
Is your phone rooted? - If so, I highly recommend 'Autostarts' - (Search on play).
You can literally set apps not to run from the moment you start-up your phone, stopping them in their tracks until you say so. These include system apps and bloatware and it does a great job of pinpointing which apps are operational & when they are. Some apps open in the background at inappropriate times and you'll be shocked to see how many take up memory without you even noticing.
Give it a whirl.
---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------
Sorry, if you aren't rooted, you could try 'Gemini App Manager' (Also on the Market).
It isn't as streamlined as Autostarts, but there are plenty of additional options built in. Great for any non-rooted phone.
Hey there all, this is 2 Bunny again. As many of you know, back in October I had to make an emergency switch from Windows Mobile to Android. As you've all read in my posts, it has been a very "mixed" experience with both some impressive and downright pathetic discoveries, but one of the worst things about it (beside the complete inability to sync) is the way that Android closes your programs whenever it feels like it instead of letting you close them. Sometimes I'll be browsing the internet in Opera Mobile and I'll switch over to the email program briefly to check something, when I hold down the "home" key and pick OM from the list of recently used programs, it starts it all over again, and I know for a fact I didn't choose "exit".
Sometimes I'm glad Android "cleans up" (like if I back out of a program that has no "exit" option) because it saves me the trip to the task manager later, but is there any way I can prevent it from closing stuff I'm actually still using?
Thanks.
- 2 Bunny
kainppc6700 said:
Hey there all, this is 2 Bunny again. As many of you know, back in October I had to make an emergency switch from Windows Mobile to Android. As you've all read in my posts, it has been a very "mixed" experience with both some impressive and downright pathetic discoveries, but one of the worst things about it (beside the complete inability to sync) is the way that Android closes your programs whenever it feels like it instead of letting you close them. Sometimes I'll be browsing the internet in Opera Mobile and I'll switch over to the email program briefly to check something, when I hold down the "home" key and pick OM from the list of recently used programs, it starts it all over again, and I know for a fact I didn't choose "exit".
Sometimes I'm glad Android "cleans up" (like if I back out of a program that has no "exit" option) because it saves me the trip to the task manager later, but is there any way I can prevent it from closing stuff I'm actually still using?
Thanks.
- 2 Bunny
Click to expand...
Click to collapse
Try ZDBox application.....maybe you'll find a solution to that problem!!
jimsiv said:
Try ZDBox application.....maybe you'll find a solution to that problem!!
Click to expand...
Click to collapse
Interesting. So that can prevent it from closing certain programs?
- 2B
kainppc6700 said:
Interesting. So that can prevent it from closing certain programs?
- 2B
Click to expand...
Click to collapse
Yup. I've been using it for a long time. As far as I know you can set certain apps to Protect so they're not closed.
ZaIINN said:
Yup. I've been using it for a long time. As far as I know you can set certain apps to Protect so they're not closed.
Click to expand...
Click to collapse
Great, I'll give that a try and letcha'all know if it works.
- 2B
Update - well it seemed promising, but it didn't work unfortunately. ZDbox said it was "protected", but that didn't stop Android's hammer of making people's lives miserable.
Any ideas if I might be doing something wrong in ZDBox (I did turn off the notification thing) or if there is other software I might be able to try?
Thanks.
- 2 Bunny
If rooted try V6 supercharger script. Just do a search on XDA. It rewrites your phones memory management to increase multitasking capabilities by reconfiguring your ram. If not rooted, your choices are severely limited by existing software to hardware configurations preset by the android operating system and the device manufacturer. Go through all of your programs and clear out all of your allocated cache memory. Freeing up ram memory may help your multitasking needs.
Sent from CDMA V6 SC GNexus w/Liquid & Franco.kernel
As mentioned by others, the most likely culprit is high memory utilization. However, there are a few other reasons that may contribute to the application closing down. Android "ranks" applications from 1 to 5 (where 5 means it is the first to get killed) based on certain criteria. Because xda won't let me link to it (I'm a new user), I have posted them at the bottom of my message.
Chances are, you are seeing the behavior in numbers 4 and 5. The fact that Android keeps applications in a least-recently-used list means that if you have applications which you just accessed but appear to have closed when you come back to them, then, once again, it is likely you are using a lot of memory that the phone is aggressively trying to keep cleaned up.
Although, it is possible that a small number of your problems are based on poorly implemented applications since the developer website states "If an activity implements its lifecycle methods correctly, and saves its current state, killing its process will not have a visible effect on the user experience..."
1. Foreground process
A process that is required for what the user is currently doing. A process is considered to be in the foreground if any of the following conditions are true:
It hosts an Activity that the user is interacting with (the Activity's onResume() method has been called).
It hosts a Service that's bound to the activity that the user is interacting with.
It hosts a Service that's running "in the foreground"—the service has called startForeground().
It hosts a Service that's executing one of its lifecycle callbacks (onCreate(), onStart(), or onDestroy()).
It hosts a BroadcastReceiver that's executing its onReceive() method.
Generally, only a few foreground processes exist at any given time. They are killed only as a last resort—if memory is so low that they cannot all continue to run. Generally, at that point, the device has reached a memory paging state, so killing some foreground processes is required to keep the user interface responsive.
2. Visible process
A process that doesn't have any foreground components, but still can affect what the user sees on screen. A process is considered to be visible if either of the following conditions are true:
It hosts an Activity that is not in the foreground, but is still visible to the user (its onPause() method has been called). This might occur, for example, if the foreground activity started a dialog, which allows the previous activity to be seen behind it.
It hosts a Service that's bound to a visible (or foreground) activity.
A visible process is considered extremely important and will not be killed unless doing so is required to keep all foreground processes running.
3. Service process
A process that is running a service that has been started with the startService() method and does not fall into either of the two higher categories. Although service processes are not directly tied to anything the user sees, they are generally doing things that the user cares about (such as playing music in the background or downloading data on the network), so the system keeps them running unless there's not enough memory to retain them along with all foreground and visible processes.
4. Background process
A process holding an activity that's not currently visible to the user (the activity's onStop() method has been called). These processes have no direct impact on the user experience, and the system can kill them at any time to reclaim memory for a foreground, visible, or service process. Usually there are many background processes running, so they are kept in an LRU (least recently used) list to ensure that the process with the activity that was most recently seen by the user is the last to be killed. If an activity implements its lifecycle methods correctly, and saves its current state, killing its process will not have a visible effect on the user experience, because when the user navigates back to the activity, the activity restores all of its visible state. See the Activities document for information about saving and restoring state.
5. Empty process
A process that doesn't hold any active application components. The only reason to keep this kind of process alive is for caching purposes, to improve startup time the next time a component needs to run in it. The system often kills these processes in order to balance overall system resources between process caches and the underlying kernel caches.
PAIN IN THE REAR TO DO THE INSTALLATION Reply
That sounds promising. I'll give it a try and letcha'all know if it works or not.
Just FYI, the installation is a HUGE pain. I messed around with it for a solid hour and a half, maybe two hours to get it up and running, so it better work or I'm out the time I put in and I'd have anotherwise useless something running/taking up space.
Thanks.
- 2B
Looks like I wasted my time. Not only did that not have any effect, it seems to have permanently brought back the useless update nagscreen - a million thumbs down to "supercharger" for being the most useless waste of an hour and a half of my life.
Not to be mean here, but did anyone try the suggestions before posting them?
Guess I'm off to the recovery menu again to try and get rid of the nagscreen, that is if I'm not booted out first.
- 2B
SAVE THE PROGRAMS Reply
Any updates on this?
Thanks.
- 2B
Any updates on this?
Thanks.
- 2 Bunny
FORCE CLOSE Reply
Any updates on this?
- 2B
STILL FORCED CLOSED Reply
Any updates on this?
- 2B
Yes.
Install V6 Supercharger and bulletproof Opera Mobile/Mini.
Are you sure you had it installed and it was running actually?
Your kernel needs to support init.d scripts.
If not, prior to installing V6 create init.d folder in /system/etc/ and grant it all the permissions. Download Script Manager app and set V6 scripts from init.d folder to run at boot.
I hope it works.
Simple Workaround:
Download MinFreeManager app and tweak your min free settings according to your RAM. More RAM = More Agressive Settings. Google android minfree and you'll find how to.
Boy124 said:
Yes.
Install V6 Supercharger and bulletproof Opera Mobile/Mini.
Are you sure you had it installed and it was running actually?
Your kernel needs to support init.d scripts.
If not, prior to installing V6 create init.d folder in /system/etc/ and grant it all the permissions. Download Script Manager app and set V6 scripts from init.d folder to run at boot.
I hope it works.
Simple Workaround:
Download MinFreeManager app and tweak your min free settings according to your RAM. More RAM = More Agressive Settings. Google android minfree and you'll find how to.
Click to expand...
Click to collapse
I'll tell you what, I screwed around with that "supercharger" for so long, I really don't want to look at it again (I think my ROM might actually have it included). All I know is that it did install because when I restarted the device, I got the stupid update nagscreen back.
I am going to try that "MinFree" program though and report back what I figure out. So far it seems to be working, so this could be promising, but I'll keep ya'all posted.
- 2B
BULLET Reply
kainppc6700 said:
I'll tell you what, I screwed around with that "supercharger" for so long, I really don't want to look at it again (I think my ROM might actually have it included). All I know is that it did install because when I restarted the device, I got the stupid update nagscreen back.
I am going to try that "MinFree" program though and report back what I figure out. So far it seems to be working, so this could be promising, but I'll keep ya'all posted.
- 2B
Click to expand...
Click to collapse
Update. Looks like "MinFreeManager" isn't doing its job either.
Any other ideas? Anyone? I'll even try the "BulletProof" thing.
- 2B
I use the browser and check email while browsing without any problem returning to the browser. In your first post you said you use the home button. Doing that will close the browser. Use the back button to return to the browser.
Sent from my LG-P500 using XDA
fdaconta said:
I use the browser and check email while browsing without any problem returning to the browser. In your first post you said you use the home button. Doing that will close the browser. Use the back button to return to the browser.
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Actually, the home key leaves it running. I usually check right away, and at first it continues running; it's when you're not watching that it takes it right out from under you. It might just be this build of Android.
Is anyone else running Gingerbread and having this problem?
Does anyone know of any kind of solution?
Thanks.
- 2 Bunny
PROGRAMS CLOSING BY THEMSELVES Reply
Any updates on this?
Thanks.
- 2 Bunny
Firstly, I'm a non-root user of Greenify. When I first installed it (over a year ago, I believe), I was able to add most of my apps to hibernation (by hitting the "+" button and then "show all apps", then "More" at the bottom, and then choosing the apps from there. I admit, I have many apps installed (I know, it's not great and I tend to collect apps more than I use them but that's why I installed Greenify) so once I went to hibernate all those apps, it would take a bit but eventually go through with the additions. From then on, I would periodically add newly installed apps to the hibernation protocol through the same routine (+, Show all apps, More). I hadn't installed new apps for awhile until recently, when I decided to do another round of additions but for the past few months, any time I've tried, I get the loading circle for a second before it freezes and nothing happens - I have to close the app and reopen it only to run into the same issue again. I can hibernate the apps previously added with the widget and from the app itself but I can't add any new ones to the hibernation list. I've tried multiple times and even let my phone sit there with the frozen spinny circle to see if it just needs time to load but after 5 whole minutes of waiting, I had to give up. I do have a lot of apps but most of them have been given the hibernation treatment so the remaining pool of apps to be added to the list should be relatively small and when I choose the option to "hibernate system apps", system apps show up in the list when I hit the "+" (although I haven't added any system apps to the hibernate list for fear I could mess with my phone's functionality) but I when I hit the "More" option at the bottom, it does the same spinny-circle freeze thing again and marking or not marking "show all apps" makes no difference. I have a Galaxy S8, update to Oreo 8.0 so I'm wondering if this is an issue I'm running into because of the update, but I think I had this problem before joining the Beta. Any help would be greatly appreciated. I also have the donation package - I've had it since shortly after installing Greenify and there weren't any problems since then before the last few months. Thanks!
ActionGabby said:
Firstly, I'm a non-root user of Greenify. When I first installed it (over a year ago, I believe), I was able to add most of my apps to hibernation (by hitting the "+" button and then "show all apps", then "More" at the bottom, and then choosing the apps from there. I admit, I have many apps installed (I know, it's not great and I tend to collect apps more than I use them but that's why I installed Greenify) so once I went to hibernate all those apps, it would take a bit but eventually go through with the additions. From then on, I would periodically add newly installed apps to the hibernation protocol through the same routine (+, Show all apps, More). I hadn't installed new apps for awhile until recently, when I decided to do another round of additions but for the past few months, any time I've tried, I get the loading circle for a second before it freezes and nothing happens - I have to close the app and reopen it only to run into the same issue again. I can hibernate the apps previously added with the widget and from the app itself but I can't add any new ones to the hibernation list. I've tried multiple times and even let my phone sit there with the frozen spinny circle to see if it just needs time to load but after 5 whole minutes of waiting, I had to give up. I do have a lot of apps but most of them have been given the hibernation treatment so the remaining pool of apps to be added to the list should be relatively small and when I choose the option to "hibernate system apps", system apps show up in the list when I hit the "+" (although I haven't added any system apps to the hibernate list for fear I could mess with my phone's functionality) but I when I hit the "More" option at the bottom, it does the same spinny-circle freeze thing again and marking or not marking "show all apps" makes no difference. I have a Galaxy S8, update to Oreo 8.0 so I'm wondering if this is an issue I'm running into because of the update, but I think I had this problem before joining the Beta. Any help would be greatly appreciated. I also have the donation package - I've had it since shortly after installing Greenify and there weren't any problems since then before the last few months. Thanks!
Click to expand...
Click to collapse
You may have to go through a tedious process. Clear the data and cache of Greenify, uninstall it, reboot and then reinstall it. Grant the necessary permissions through adb. Then choose all the apps that you want to hibernate. Other than this, I don't think that there is any other way to solve your issue.
Be aware that backing up and restoring the settings of Greenify may also restore the issue you are facing.
tnsmani said:
You may have to go through a tedious process. Clear the data and cache of Greenify, uninstall it, reboot and then reinstall it. Grant the necessary permissions through adb. Then choose all the apps that you want to hibernate. Other than this, I don't think that there is any other way to solve your issue.
Be aware that backing up and restoring the settings of Greenify may also restore the issue you are facing.
Click to expand...
Click to collapse
Also recommend being judicious about what apps are added to Greenify's action list. With the introduction of doze Android does a pretty good job reigning in resource abusers. Adding a huge portfolio of apps to Greenify has few/no upsides and can potentially lead to greater resource consumption and poor overall device behavior. Greenify is best used for targeted action against demonstrated 'bad actors' that do not respond well to native resource management. On Oreo your list of Greenified apps should be quite small.
This is a very strange bug. I was updating PUBG and cleared the recent apps before going to bed only to wake up in the morning and see it not completed. I tried multiple times but the same happened. So I can conclude that the download manager gets "EXITED/STOPPED" by clearing play store from the recent apps. This shouldn't happen as download manager is an integral part of the android system and it's functioning shouldn't have anything to do with exiting the store.
Is anyone else having this problem. Kindly comment below.
Are you under tencents pubg? Why are they asking us to side load thru apk,wierd
Aimara said:
Are you under tencents pubg? Why are they asking us to side load thru apk,wierd
Click to expand...
Click to collapse
Yes. I was updating the game through play store. Sorry for not being informative in the first place.
MasterFURQAN said:
Yes. I was updating the game through play store. Sorry for not being informative in the first place.
Click to expand...
Click to collapse
Official update is up ,I just cancel the apk download from their website, downloaded almost 600 mb, then I cancel ,wierd I can't find half file where did it go ?
Aimara said:
Official update is up ,I just cancel the apk download from their website, downloaded almost 600 mb, then I cancel ,wierd I can't find half file where did it go ?
Click to expand...
Click to collapse
I don't think you get my query. This is what happens:-
1. I update/download an app on the Play Store
2. I clear recent apps including the play Store
3. This freezes/ stops the update/ download.
So I guess that clearing the store from the recent apps also somehow closes the download manager. This shouldn't happen.
That's the problem I faced too none of aps including play store run in the background.If recent tabs is cleared the apps stops working
---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------
Someone please tweet about this issue to jai mani POCO India head
MasterFURQAN said:
I don't think you get my query. This is what happens:-
1. I update/download an app on the Play Store
2. I clear recent apps including the play Store
3. This freezes/ stops the update/ download.
So I guess that clearing the store from the recent apps also somehow closes the download manager. This shouldn't happen.
Click to expand...
Click to collapse
maybe you need to enable playstore in background to stay open ? anyway why would need to download overnight , took me less then 10 mins to d\l it
Ashish M Shet said:
That's the problem I faced too none of aps including play store run in the background.If recent tabs is cleared the apps stops working
---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------
Someone please tweet about this issue to jai mani POCO India head
Click to expand...
Click to collapse
Did you find any solution ?
I have a solution:
STOP CLOSING APPS.
You are destroying your performance and battery life by doing this. ONLY close apps if they're malfunctioning. It does NOT make your phone faster to clear apps.
I thought this crap was put to rest years ago, wow.
MasterFURQAN said:
Did you find any solution ?
Click to expand...
Click to collapse
Ya lock the apps in memory and remove the battery saver option for the apps!
Ashish M Shet said:
Ya lock the apps in memory and remove the battery saver option for the apps!
Click to expand...
Click to collapse
I can't find downloads/ download manager in the app saver list.
Yea I realised it last night.. I put pubg on update and went to sleep only to realise that the update failed somehow.. This has to be the problem I faced.
CosmicDan said:
I have a solution:
STOP CLOSING APPS.
You are destroying your performance and battery life by doing this. ONLY close apps if they're malfunctioning. It does NOT make your phone faster to clear apps.
I thought this crap was put to rest years ago, wow.
Click to expand...
Click to collapse
Clearing recent apps doesn't necessarily mean closing the app especially for a system app like download manager.
MasterFURQAN said:
Clearing recent apps doesn't necessarily mean closing the app especially for a system app like download manager.
Click to expand...
Click to collapse
That's exactly what it does, actually. It doesn't just "hide" then - it calls onDestroy (sometimes, it's not guaranteed) and disposes the activity, so next time you run it it has to be recreated from scratch again.
But yes, you are at least correct in that it shouldn't terminate any associated services. Maybe that's an MIUI "feature" of closing the apps.
But my point still stands - you shouldn't close recent apps unless necessary. Any Google result will tell you this, it's mainstream knowledge these days.
If you can't help yourself, see a doctor for OCD treatment. It's a 6GB device for God's sake, you will open 100 apps and still not run out of RAM. No it will not make PUBG FPS better. No it will not make your device switch apps faster. It does ONLY harm.
CosmicDan said:
That's exactly what it does, actually. It doesn't just "hide" then - it calls onDestroy (sometimes, it's not guaranteed) and disposes the activity, so next time you run it it has to be recreated from scratch again.
But yes, you are at least correct in that it shouldn't terminate any associated services. Maybe that's an MIUI "feature" of closing the apps.
But my point still stands - you shouldn't close recent apps unless necessary. Any Google result will tell you this, it's mainstream knowledge these days.
If you can't help yourself, see a doctor for OCD treatment. It's a 6GB device for God's sake, you will open 100 apps and still not run out of RAM. No it will not make PUBG FPS better. No it will not make your device switch apps faster. It does ONLY harm.
Click to expand...
Click to collapse
Damn!! People clearing their recent apps have OCD. Really ? I've been using android phones for years. My previous phones had 365 apps installed in it and I had to use almost 50 to 70 or more of them daily. The thing is most if not all android apps have background services and these services do NOT get stopped even if you clear recent apps while other apps just get cached to the RAM and they too don't stop by recent apps clearing. And then there are wakelocks and GCM which are the reasons for apps giving you notifications and things like that. I can go on but I think you get the point by now.
I clear apps because I just like to see a clean UI. I know that these apps don't just get stopped by this. If I really wanted to stop an app I'd do it for saving battery and NOT for saving RAM and I'd use advanced apps like greenify and wakelock detectors for this because clearing apps won't stop these apps. Some apps just prevent the device from going to deep sleep and this is the reason for overnight discharge on most phones.
Peace.
nC3rtaintiy said:
Yea I realised it last night.. I put pubg on update and went to sleep only to realise that the update failed somehow.. This has to be the problem I faced.
Click to expand...
Click to collapse
I think the problem is with big apps. Whenever I install a small size app maybe upto 100 MB, it gets installed without any problems but whenever I tried to install/update a large app like PUBG, it never gets completed giving errors like error 495. Today it stopped at almost 1.05 GB. I'll check and see if I can find a fix.
CosmicDan said:
I have a solution:
STOP CLOSING APPS.
You are destroying your performance and battery life by doing this. ONLY close apps if they're malfunctioning. It does NOT make your phone faster to clear apps.
I thought this crap was put to rest years ago, wow.
Click to expand...
Click to collapse
But this shouldn't happen on stock Android though.. Even on iOS swiping out apps from recents doesn't mean the user wants to force stop it. Xiaomi designing it's skin to do this is really counterintuitive. Because of this we are having all sorts of problem like this and messaging apps not receiving notifications in the background.
WingXBlade said:
But this shouldn't happen on stock Android though.. Even on iOS swiping out apps from recents doesn't mean the user wants to force stop it. Xiaomi designing it's skin to do this is really counterintuitive. Because of this we are having all sorts of problem like this and messaging apps not receiving notifications in the background.
Click to expand...
Click to collapse
After a few days of use, I don't think that is the case. I tried multiple downloads/ updates from the store and cleared recent apps but they continued without any freezes or stops. The problem appears when I install/ update a large sized app like PUBG. It'll go on for sometime and then just freeze and return an error. Last night it stopped at almost 1gb+ with an error code 495.
WingXBlade said:
But this shouldn't happen on stock Android though.. Even on iOS swiping out apps from recents doesn't mean the user wants to force stop it. Xiaomi designing it's skin to do this is really counterintuitive. Because of this we are having all sorts of problem like this and messaging apps not receiving notifications in the background.
Click to expand...
Click to collapse
Mmm, it may be Whetstone at work again. That horrible thing. Is there a "Memory Optimization" setting in Developer Options? If so, turn it off.
CosmicDan said:
Mmm, it may be Whetstone at work again. That horrible thing. Is there a "Memory Optimization" setting in Developer Options? If so, turn it off.
Click to expand...
Click to collapse
There is MIUI Optimization in Developer settings but i don't think it helps disabling it in this case.(it helps a little bit on scrolling performance BUT after 3-4 days it becomes slow again for me..I think MIUI's Touch response & Scroll performance is very bad compared to Stock/Neuxs 5... Correct me if it's only for me)
MIUI has very weird ram management which literally kills the apps & all the services when you clear it from recent and there's no way to stop this on MIUI from my past 2 weeks of experience and research
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?