I've seen that answer a lot, about how Android handles memory. Admitadley I haven't done any specific googling myslef. I have, however, observed how my my Linux boxes have handled it and after looking at the image posted I truly am going to be Googling Android specifically because it seems to me that it should free up memory before it gets to the point of the screenshot; can you imagine what the swap file looks like because it makes me wonder if it isn't full, assuming its a compressed RAM swap, and spilling over as a file on the card as well when things might be better already freed up at this point. If it was a desktop then I'd understand, but its a phone and you want a smooth experience out of it as much as can be provided. Its one thing to say "Learn how Android uses RAM" but I sure hope you do when you say it. As for me, I'll stop there and say that I really genuinley intend to find out (have the google search bookmarked for free time) because I know that my phone lags at times before it gets even close to what's posted, that I've never seen it get to what's posted, and that these setting can be easily changed on a rooted device... and that based upon experience with my previous Android that sported way more bloatware but a lot less lag, I've long been wondering if the settings could be just a little better. Usually its not a good idea to second guess the manufacturer but at the same time, a small change in a value can go a long way at times. Not saying you're wrong to say so, just saying that I hope you gave the answer as a person who genuinely understands for themselves and aren't just repeating others, lobie81.
All that said though, and knowing that my phone's ROM is supposed to be one of the more carrier bloat free varieties, what little I can see of the running services suggest that he might have a lot of things going that could be better handled by one process, like sticking it all in Tasker however that's a bold assumption based on a small portion of what's available to be seen.
