agbommarito wrote:
I've been doing what you suggest for a while (ie running more aggressive MIN FREE settings). Yet I noticed in comparing the 99_lowmemorykiller file from v2.2 to the one in v2.3, the default settings have been changed to a less aggressive setting. In v2.2, the default setting was size: 8M 12M 20M 60M 80M 100M, and in v2.3 the default setting is size: 8M 12M 20M 50M 70M 90M.
I wonder why?
The best thing I can suggest is experimenting. Apps like ROM Toolbox make it easy to use a new set of values. Keep in mind they ned to be used for a while - a week at least - to gauge their full effect and usefulness. Using something like SuperSU you can also record the actual command issued by the app and place new values into the original script.
As for values actually used - they are a double edged sword. They are good and bad. While an aggressive setting will flush things out of RAM faster setting things too aggressively will also start to kill other apps you don't normally want to kill (depends on how they were coded and what kill/protection value they set in Android for themselves). Occasionally, people have seen their launcher flushed out and restart. Or, apps like button savior (which are intended to remain running at all times) get flushed out and need to be restarted.
A happy medium is imperative and when dealing with a low memory device like the HD2 and possibly lots of things using memory regularly this becomes a very fine and difficult line to walk. The fewer apps that run all the time the better the HD2 will perform.
Tytung has to balance his ROM for native use but everyone who installs it uses it differently. I do not envy Tytung's dilemma since it is likely impossible to make it responsive for everyone. He can probably tell you what his thinking was when he changed it as I cannot read minds.
That is why I always suggest experimenting with one's own installation and finding the ideal balance, if there is such a thing.
