Related
A lot of times I will get random programs that I never use listed as open in the task manager. Mp3 store, nba league pass, documents to go, they all keep opening up again even though I never use them. Is there a reason for this? There are other apps that do this too, I just listed the ones I see most often.
Yes, this is normal. Android loads applications until the RAM is almost full, so they're ready to pop up in an instant when you actually launch them. If an application requires more RAM to work with than available, the system will shut down some of the inactive applications.
There are those task auto-killer programs out there that people use because they think it makes their phone run faster or tidied up, but in fact, most of the time they will slow it down because applications will take longer to start. And consume more power, because there's more work to do when starting an app. A properly written application won't consume any power when inactive, and the RAM has to be powered anyway, so that's why you want it to be used as much as possible.
Thanks for the info!
Is there anyway to exclude certain apps from opening up? There are apps on the phone like mp3 store or the stock messaging app that I would never use, so it would be more worthwhile to get the system to keep apps I actually use open instead of just random ones.
djsaad1 said:
Thanks for the info!
Is there anyway to exclude certain apps from opening up? There are apps on the phone like mp3 store or the stock messaging app that I would never use, so it would be more worthwhile to get the system to keep apps I actually use open instead of just random ones.
Click to expand...
Click to collapse
Search.. All your questions have been asked and answered before.
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
EverythingNook said:
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
Click to expand...
Click to collapse
Everything I've read says you don't need it with Android 2.2 and above.
I use it, nice quick and easy way to close things (like emulators that normally won't shut themselves off.)
dsf3g said:
Everything I've read says you don't need it with Android 2.2 and above.
Click to expand...
Click to collapse
me too but my friends have 2.3 and they use it.
I use it if videos start to stutter (ie youtube etc). It seems to help.
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
alright ill stay away from it thanks!
That about sums it up. The only time an app should be killed is if a bug causes it to hang or slow down severely. Otherwise, let the Android system handle things itself.
In my experience it's nice to have for when you need to kill off a specific game or resource intensive app that seems to be slowing things down.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
so would you recommended going into the app itself and picking the apps i want to be closed? or could i also use the widget to close all of them?
I would only recommend going into the app itself, long-pressing on the app you want to kill, and then pressing kill. Closing all of them just forces a large number of apps to restart. I really only use it to kill certain apps that are more difficult to close.
Does stopping running processes from the Manage Applications settings have any permanent effect on the phone? If I turn off the phone and turn it on again, will it fix whatever I stopped?
It's ok right to turn off processes? Nothing is really deleted right? Sorry, I'm new to android and smart phones in general/
Running processes are running programmes located in the RAM, so turn them off will only stop them running without wipe them from storage.
Not sure why you want to manually stop running processes, it’s likely they will auto restart after a while anyway. Beside Gingerbread is quite good at manage running apps, so there really is not a need to manually terminate running processes.
Nope. It will not have any permanent effect. You'll just clean up your RAM a bit, but everything you stopped will be started again when you turn on your phone or even in a few seconds.
Agree with the user above about Gingerbread app managing.
Sent from my MB855 using XDA App
In my opinion, the *only* reason to manually stop a process is because it's gone rogue and slowing down your device.
Any form of automatic task killing is ultimately counter-productive!
Regards,
Dave
If you root u device, u can use "Gemini App" to kill apps permanently. Just select them and mark " block", u also can kill processes completely and configure the auto-run
Problem with multitasking : everytime I'm using the browser and switch to some other app and switch back to browser, browser restarts it self
I'm using nik_v4
use a different browser like opera,boat browser,firefox etc.
it depends, the system might be aggressively freeing up memory once you switch the application (that is if you are low on free memory) or another thing, it depends how you switch the application. in this case, a browser, you usually click Home and start another app (that send the current application in pause mode, in the background), but if you clicked Back to get back to the homescreen, the system will interpret this as a kill application sign, it will not keep it in the background. i'm not giving alternatives just trying to explain how stuff works. check if you are low on memory, try it with different browsers (i recommend Dolphin browser).
facing similar problem with firefox
andrei.je said:
it depends, the system might be aggressively freeing up memory once you switch the application (that is if you are low on free memory) or another thing, it depends how you switch the application. in this case, a browser, you usually click Home and start another app (that send the current application in pause mode, in the background), but if you clicked Back to get back to the homescreen, the system will interpret this as a kill application sign, it will not keep it in the background. i'm not giving alternatives just trying to explain how stuff works. check if you are low on memory, try it with different browsers (i recommend Dolphin browser).
Click to expand...
Click to collapse
i switch between apps using long press of home button still browser keeps closing and restarting i always have atleast 150 mb memory free
suggest a few memory hogging apps i'll remove them if i have
at least 150mb free means you don't have a memory problem. but this behavior is a bit odd. it might be from the current kernel you are using and it might be implementing a very aggressive memory freeing task manager (killing any application as soon as it is sent in the background). if you have installed a market task manager or any memory freeing app i suggest you uninstall them. you might also wanna try flashing a new kernel and see if it changes anything (make sure new kernel is compatible with your current ROM). i'm using niks 4.0 ROM with RCMIX-Vivo kernel and i don't have this problem.
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
if you rooted, you can use Autostarts or ROM toolbox from the playstore. it can change the receivers of the apps not to start at boot
CooLasFcuK said:
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
Click to expand...
Click to collapse
The simple answer is that you don't need to stop them!
As you say, Android is already very good at keeping track of background processes, to the extent that if a new program needs more RAM, Android itself will kill a background process that hasn't been used for a while to free up RAM for the new program.
The Cached processes screen SHOULD be full of recently used programs; it shows that Android is doing what it is supposed to do and is shifting inactive processes out of active RAM in case you want to load it again, without completely dumping the process memory.
Now, as for the side effect you mentioned, that would be a significant hit on battery life. By holding programs in RAM as it is supposed to do, the OS can load the program quickly and cleanly and more efficiently by simply reading the RAM rather than reading flash, writing to RAM, then reading from RAM. The general mantra for UNIX based systems is that unused RAM is wasted RAM.
Another thing to note is that if you do not close tabs when switching active programs (including going to homescreen) then the Browser is designed to hold that tab in memory. Even if you close the Browser (excluding closing the tab specifically with the "little x"). Even if you reboot the damn phone, it will still load the tabs/pages you had open last. The pages are not held in memory as such, just what was open and what tab order, so if you do open the browser after a while, it will load the last page from scratch.
TL;DR version: The running and the cached processes will remain exactly where they are until a new program needs more RAM than is available, at which point Android will kill something to make room. You do not need to do this manually. It will cause more power drain by making very inefficient use of RAM/Flash memory. Empty RAM is wasted RAM.
whilst Chaos is right, I notice severe performance drops when ram is filled, despite Androids theoretical advantage. It doesnt work...
Best to prevent from loading altogheter.
Root, lose warranty, backup apps, uninstall or freeze apps so the bloatware is removed.
For others, change autostart settings in Romtoolbox. So they wont start on boot.
Search for safe stuff to delete. There are lists for that
Sent from my GT-N7000 using Tapatalk 2
Or just dont install the apps that you dont really need.
Via GtN7000
LoVeRice said:
Or just dont install the apps that you dont really need.
Via GtN7000
Click to expand...
Click to collapse
Lol, even then you might still need to remove bloatware lol
Sent from my GT-N7000 using Tapatalk 2
Thanks so much for detailed answers.