The number you are looking at does not include cached processes.
Reboot.
Sent from my RAZR MAXXIMUS
Yea I guess so. And about closing a crucial process I think I did that already. I disabled the clock and the upper right wouldn't move forward in time until I rebooted. Even windows will continue to keep an inaccurate clock if you disconnect from the internet...You'll just drive yourself nuts doing this. If your system isn't being bogged down, don't focus on this issue, because you're just at odds with how Android works. In general, the OS will try to keep most of the RAM occupied, so closing processes will just prompt the OS either to restart the same process (if it's used a lot) or start another commonly used process, in an attempt to be ready for your next function.
Yea I guess so. And about closing a crucial process I think I did that already. I disabled the clock and the upper right wouldn't move forward in time until I rebooted. Even windows will continue to keep an inaccurate clock if you disconnect from the internet...
Yes, the clock in Windows will continue if you disconnect from the internet, but so will the clock in Android. Now, if you were to disable the clock in Windows (not sure if that's possible, but for argument's sake) just as you're doing in Android, then I'm sure it would glitch as well!
BUT BUT...I spent 15 minutes going through the All list force stopping dozens of things that arent accurately reported in the Running list! I am never going to reboot again.. Hah!
Yes, but if the app is loaded into RAM and stays there waiting to be used, without anyone trying to constantly close it, shouldn't that on balance conserve CPU usage and battery? Besides, I thought that the idea of keeping apps in RAM wasn't so much to save battery or CPU cycles, but rather to allow the app to start up quickly and efficiently.