I was reading a web article on this the other day that completely supported what you are saying. I considered putting the link up here but decided that, probably, everyone here knew this (unlike me), so it did not happen. I wish I had done it, now. Unfortunately, I don't remember where it was. What I can say, Ron, is that it more than supported what you are saying. One of the comments was that when they stopped using the 'killer' they noticed a substantial improvement in the performance of their phone.

Being totally clueless about Android, what I took away from this article/blog was that the Android OS handles multi-tasking by 'suspending' the programs you have used (putting them to sleep?) rather than leaving them completely operative or shutting them down. So, by using a 'task killer' you are actually forcing them to shut down, possibly leaving certain 'strings' in the OS still operating (now futilely) rather than allowing them to do their job, which is to close whatever operations are deemed not necessary, which is dependent, partly, on how long it has been since it was used. So, in a sense, by using a Task Killer, you may be defeating the whole purpose of what it is supposed to be doing... and, actually increasing the workload of the OS, instead of helping it.

Please help me out here, Ron. Am I understanding this correctly?

I just discovered I had emailed myself the link.... http://geekfor.me/faq/you-shouldnt-b...-with-android/