The way that these run is so that its not just chopping the heads off the apps like ATK does and the other "killers" do. It modifies the android's actual way it deal with how much free RAM is needed before it starts ending processes the correct way. So when you use things like minfree and autokiller, its not just killing them, its ending them the way that the system would normally do it.
Also, I dont know about you guys, but my droid's normal system does not like to manage RAM at all, it gets all the way down to 12Mb of RAM at sometimes and the phone does not respond the same as if it had about 40Mb free.
So pretty much what minfree has is a set of thresholds(the first three you do not want to mess with as I'm sure you already know):
- Foreground App: Dont touch
- Visible App Dont touch
- Secondary Server Dont touch
---These are by level of importance when it comes to an app that it may kill---
- Hidden App - This is the one that will for the most part designate how much RAM that your system decides to keep free, so if you are like me, you like to have a fast phone, more RAM free = faster phone. *I have mine set to 74* This may cause redraws if your system is deciding to kill the launcher constantly. So if you notice this happening feel free to turn this number down a bit. about 40Mb free and you will still be nice and smooth
- Content Provider - This one is similar to the one below *set to 94*
- Empty App - You can set this one fairly high because these are the apps that dont matter really so as soon as you system drops below whatever you have set, it will begin to phase out these useless apps *I have mine set for 138*
Think about it people, this is a Droid. It doesnt have a whole lot of RAM just to be thrown away and when it is, you suffer. It doesnt have 512Mb so you need to manage it!
Well, my one post for the day is done. Hope someone at least reads it dancedroid