[HTC Sensation] 3c:
Sorry folks, I can't let this writing without responding... So my apologies in case I misinterpreted something or get out of my boundaries...

Nevertheless I think this is not the place to discuss this. So Mike if you want, I just remove the whole post! But I'd like to share my own experience, maybe this will shed some different perspective on this.

What are you talking about with Dalvik VM? Do you think killing an app running on a VM (Virtual Machine) will make you system unstable? The VM purpose is to isolate every processes, making the whole system more stable!

'in a negative' fashion? So you agree then? Why use an ATK if it's negative anyway?

So I strongly disagree with everything you both said!

Android has its own task killer integrated (will call it OOM to simplify) ! And it's probably one of the worse ATK you can get when you have a phone with plenty of memory! Actually the worse with low memory as well!

When you have plenty of memory OOM will keep every app running! Even those consuming precious CPU, those badly programmed, games, etc... So your 512Mbytes memory phone leaves you with 20Mbytes for example, and gets so slow you wonder why. A reboot and you're ready again thinking it was just unstable!

When you don't have much memory like in the old days, this OOM **** is killing stuff almost blinding with some weird algorithm based on usage, memory/cpu consumption, but nothing really logical. So the game consuming CPU in the background might well be kept because it's the one you used most! While the widget app you're looking at will be killed instantly!

So yes I definitely use an ATK in which I can select which app to kill when not used, the frequency of killing, etc... Actually I only kill apps when screen goes off, so when I switch it back on it's clean, and I don't mess with apps restarting constantly (killing-restart are a big lag builder). I prefer to uninstall those apps or freeze them (always freezing Maps! Just in case I want to use it one day).

My Sensation has 130-150Mbytes of RAM at all times, no lag on stock ROM/kernel whatsoever.

Even if I set Android killer to keep those 130Mb, it won't actually hold, and Android killer will kill some apps I use often! So the ATK is doing a better job.

Here are 4 other reasons why I use an ATK and wish I could disable the OOM:

- My kid installs many games on my phone, and I was tired of them continually running in the background eating CPU like crazy!

- By the way, ALL AdMob apps running latest Google SDK today have memory leaks and cpu usage problems (except those from developpers who found good and crazy work around), thanks to Google for that! So the ATK keeps my phone clean anyway! OOM does not!

- You've probably seen comments about widgets stopping to refresh! Android killer! A service being stopped unexpectedly? Android killer!

- Why do you think Google Maps, GMail, Email and so many like those are constantly restarted/running on your phone even you never use them? Nobody ever complained about those! But when an app from Android Market does the same for the same reason, you can be sure the dev will take the heat, big time! Even if on the long run his app consumes less than apps not being used at all!

- I develop apps and I often install test APK on my phones (like 100 times a day or more). When I do, OOM will kill most other apps I installed and need to keep running (widgets, notifications, battery monitor)! but it won't kill Maps, EMail, Facebook etc... which I never use!

So who's the ROM killer here?

Voila, that was my personnal experience on the subject. Don't run in flames, just trying to show you an app developper's and user's perspective.

Mike, thanks again for this great ROM, looking forward to your next creation along with Faux123's updated kernel!