Thanks for posting that Trident.
While that FAQ does a good job of explaining how Android's RAM management system works, which I had no idea about, it doesn't to a very good job of convincing me of the negative aspects of using a Task Killer.
Let me explain my reasoning/rebuttals to a few lines in the FAQ:
-"Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again."
Who cares? Maybe a process will reload itself, maybe it won't. If it's a process I am killing, I am hoping it won't. If it's a process I do want running, I will put it on the ignore list on TasKiller. This also assumes that most processes will reload themselves, only a few core processes (such as Calendar, Corporate Calendar, etc.) generally reload themselves. Also, do processes have feelings? How can a process not "be ready" to be killed. It's as ready as I want it to be.
-"Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few."
Well that's just dead wrong. I use TasKiller day in and day out and I've never had an alarm not go off or not received a text message. This really limits the author's credibility, if he's wrong about this who knows what else he's wrong about.
-"The only true way to prevent something from running at all on your phone would be to uninstall the .apk."
Bologna. The only processes that tend to restart themselves are core processes that cannot be uninstalled (unless maybe you're a root user? i'm not). And if this were true, fine, I'll just kill the process again.
-"One thing that I forgot to even address here is that memory works a bit differently in linux than it does in Windows. In general the way memory works is you really only need as much as you plan on using. So if your combined running programs use 100mb of memory, 150mb is more than enough. There is no need to clear what’s running in memory before you hit that 150mb cap. Now in Windows it seems that the system performs a bit better when you have less stuff in memory, even if it’s not full. No doubt those who have been on computers for a while will remember there used to be programs that could clear your memory in Windows also.
Linux however isn’t generally affected by this. While I admit that I don’t know the architecture and reason for this… linux will run the same regardless of if you have 20mb free memory or 200mb."
Somehow I'm just not entirely convinced this is true. I don't understand how Linux can magically run the same on less CPU without lagging when Windows can't, and if the author admits that he doesn't understand either, well, it's just not very convincing.
-"Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while."
Maybe "eventually" isn't good enough for me.
-"I have also seen people incorrectly assume that the more memory in use, the faster their battery will die."
This must be why most of the comments for Task Killer apps on the Android Market say something like "5 stars! This app helped me significantly extend my battery life!"
-"When can a task manager be a good thing?? To help you determine what IS slowing down your phone; what may actually be draining your battery faster. That is actually what helped us discover that there appears to be a bug still left over from 1.5 that is causing slow downs on our CDMA Hero’s even today. While an item using up memory isn’t going to hurt things, an item chewing through your CPU absolutely will. Now I still don’t suggest using a task killer to kill a program that is using up your processor (unless of course it is a zombie process that is going crazy, but you should probably just reboot in that case). But it can help you see what’s going on with your phone."
So the end conclusion of a FAQ titled "Why You Shouldn't Be Using A Task Killer With Android" is "Maybe you should be using a Task Killer with Android". Man, I'm convinced! I'm uninstalling TasKiller immediately!
While that FAQ does a good job of explaining how Android's RAM management system works, which I had no idea about, it doesn't to a very good job of convincing me of the negative aspects of using a Task Killer.
Let me explain my reasoning/rebuttals to a few lines in the FAQ:
-"Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again."
Who cares? Maybe a process will reload itself, maybe it won't. If it's a process I am killing, I am hoping it won't. If it's a process I do want running, I will put it on the ignore list on TasKiller. This also assumes that most processes will reload themselves, only a few core processes (such as Calendar, Corporate Calendar, etc.) generally reload themselves. Also, do processes have feelings? How can a process not "be ready" to be killed. It's as ready as I want it to be.
-"Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few."
Well that's just dead wrong. I use TasKiller day in and day out and I've never had an alarm not go off or not received a text message. This really limits the author's credibility, if he's wrong about this who knows what else he's wrong about.
-"The only true way to prevent something from running at all on your phone would be to uninstall the .apk."
Bologna. The only processes that tend to restart themselves are core processes that cannot be uninstalled (unless maybe you're a root user? i'm not). And if this were true, fine, I'll just kill the process again.
-"One thing that I forgot to even address here is that memory works a bit differently in linux than it does in Windows. In general the way memory works is you really only need as much as you plan on using. So if your combined running programs use 100mb of memory, 150mb is more than enough. There is no need to clear what’s running in memory before you hit that 150mb cap. Now in Windows it seems that the system performs a bit better when you have less stuff in memory, even if it’s not full. No doubt those who have been on computers for a while will remember there used to be programs that could clear your memory in Windows also.
Linux however isn’t generally affected by this. While I admit that I don’t know the architecture and reason for this… linux will run the same regardless of if you have 20mb free memory or 200mb."
Somehow I'm just not entirely convinced this is true. I don't understand how Linux can magically run the same on less CPU without lagging when Windows can't, and if the author admits that he doesn't understand either, well, it's just not very convincing.
-"Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while."
Maybe "eventually" isn't good enough for me.
-"I have also seen people incorrectly assume that the more memory in use, the faster their battery will die."
This must be why most of the comments for Task Killer apps on the Android Market say something like "5 stars! This app helped me significantly extend my battery life!"
-"When can a task manager be a good thing?? To help you determine what IS slowing down your phone; what may actually be draining your battery faster. That is actually what helped us discover that there appears to be a bug still left over from 1.5 that is causing slow downs on our CDMA Hero’s even today. While an item using up memory isn’t going to hurt things, an item chewing through your CPU absolutely will. Now I still don’t suggest using a task killer to kill a program that is using up your processor (unless of course it is a zombie process that is going crazy, but you should probably just reboot in that case). But it can help you see what’s going on with your phone."
So the end conclusion of a FAQ titled "Why You Shouldn't Be Using A Task Killer With Android" is "Maybe you should be using a Task Killer with Android". Man, I'm convinced! I'm uninstalling TasKiller immediately!
Upvote
0
I have never claimed or attempted to be an expert on the subject. People have asked for my opinion and I have provided it. I also do not condemn anyone for using one. Everyone's phone is different and everyone's needs are different. What you use and what I do will result in different battery life and system performance no matter what. My primary objection to task killers, as I have stated repeatedly, is the forced or "advised" use when people first purchase their phones. 
