I was wondering cuz I read an article saying that task managers actually do more harm then good.
After reading this and doing some testing with Pandora and Tune Wiki I noticed these processes ended very soon after exiting the program. I was checking this within Running Services. I then did some testing with Shop Savvy and this too closed out from Running Services within a few seconds of backing out of the app.
So as long as I used the back key android was killing the process. The funny thing is Advanced Task Manager was still showing that TuniWiki was running and Shop Savvy was running.
This tells me Advanced Task Manager needs some work especially since it was showing TuneWiki twice when in fact it wasn't running at all.
I went ahead and uninstalled Advanced Task Manager for now which was taking 22k in resources anyhow. I'll see how my droid performs without me ending tasks through the task manager.
Thanks for sharing that article. It was useful.
For what it's worth, I have been running without it now for about a month.... My phone seems to be doing just fine. Battery seems to last longer too..
I agree with this post there are some things that happen with the droid such as GPS that you are going to want to kill manually and for that you need task manager. Just dont run it in the background and use it as a tool when neededmy 2 cents is that whether I use it or not, i do not see any change in anything. It's so hard to tell what's doing what anyways because the android OS can restart apps that are setup to restart anyways and even tho an app process is still active, it doesn't mean its doing anything, just idle and using up no resources. I've also noticed that after you boot for first time and check the process list, many of my apps are there, even the one's you'd never expect to start at boot such as "Shop savvy" that have no widgets or anything that shoudl be running in background. Ininitially i'd kill all these on boot to give me a clear headWhat i've found though, is that if I do not use the task killer after boot, and just wait some time, many of those processes that started at boot are killed off, so seems the OS handles the memory fairly well and kills stuff that's not needed and is not priority.
My preference is to have a task killer but i do not OCD and use it all the time, rarely ever anymore. What I like it for is for bugs in certain software, such as the stock browser and beautiful widgets for example, sometimes will need GPS for something and if im inside, will try to find a signal for so long, hurting battery. When these things happen from time to time, i use the task manager to kill them.
Activity | Android Developers Follow the Activity Lifecycle link about 1/4 way down.
The abridged easy to read version.
4 stages of Application life
1. Active - the application currently in use, last to be killed, rarely if ever killed, only killed when the phones needs the resources to remain operating.
2. Paused - application is still active or visible, it maintains all recent application interactions, i.e paused to answer a phone call, text, etc, 2nd to be killed when a device needs additional resources
3. Stopped - application is no longer active or visible, 1st to be killed when the device needs additional resources
4. Killed - a paused or stopped application that has been killed by android because memory and resources were needed elsewhere