My device (ASUS TF201, unrooted, stock Firmware) is running on Android 4.1 and has 1GB of RAM installed. However I noticed that only 200-300 MB's are left and marked "unused". Also I know that does not necessarily means that all "used" RAM is really in use. For example cached Apps may be hold in RAM for faster start-up and this RAM may be freed by Android if more memory is needed. So I tried the following steps to get more unused RAM as I am experiencing Force-Closes from another App which (may) result from insufficient memory available.
I checked running apps and force-closed some of them but this gave me not enough RAM. Although this list contains Apps which may be responsible for almost 100 MBs of RAM but not for 600 MB. So I checked which Apps are cached, and closed all of them giving me also only a few MB's.
I rebooted my device but after start-up 600 MB's are already used.
I performed cold-boot still 600 MB's are already in use.
I pushed the reset button which immediately shut down my device, but after reboot 600 MB's are still in use.
I performed a factory reset and did not installed any other app (nor did I performed an backup-restore, as I didn't specified any Google account so far). But still 600 MB's are used.
I applied all of those memory task killers which all performed bad and killed only those apps I could kill myself. Except one profiler gave me a hint: It sayed that 300 MB's are used by the kernel and 300 MB's are used by apps. I also provided me a button for killing all running apps. Direct after this still 200 MB's are in use (it says "kernel memory") but after 15min again 600 MB's in use (with again 300 MB's per kernel- and app-memory). Is that normal that so much memory is used?, I mean this is factory reset no additional apps were installed by myself!
I also tried to to force-close and disable almost all apps which are currently running and which I don't need but still around 600 MB's are in use.
As I fear to loose warranty if I open the back of the pad I cannot put off power. (But of course I could wait until no battery is left) But I won't think that this will help, as this should have worked with a hardware reset or cold-boot as well.
So what can I do?