View Single Post
Posts: 58 | Thanked: 43 times | Joined on Aug 2010
#237
Ran the 'old' settings:
echo 3 > /proc/sys/vm/dirty_ratio
echo 3 > /proc/sys/vm/dirty_background_ratio
echo 100 > /proc/sys/vm/dirty_writeback_centisecs
echo 100 > /proc/sys/vm/dirty_expire_centisecs
echo 32 > /proc/sys/vm/min_free_kbytes
echo 95 > /proc/sys/vm/swappiness
echo 666 > /proc/sys/vm/vfs_cache_pressure
echo 0 > /proc/sys/vm/page-cluster
echo 4 > /sys/block/mmcblk0/queue/nr_requests
echo 4 > /sys/block/mmcblk1/queue/nr_requests
Device is still responsive after a day. Tracker runs, camera is able to launch (this didn't work with Swappolube settings and SwapSet), but now I'm getting the message that states I can't send or reviece messages: device memory full.

Trying new settings now. @mr_jrt: including in SwapSet would be great, since it's clearly the only way to get ramz to work properly. You can also set Swappolube as a conflicting package, so users have to choose (does this make sense?).