[Tilt, TyTN II, MDA Vario III Android Development] WarByte:
Haha, great. Well if I am correct, even if I mess up my kernel (I do not know how I could do that but I always manage to raise the bar on stupidity some times) I think I can still hard reset since it is fixed on NAND and should remain like new. I'll share with you all what I know about compcache:

Normally when our phones run out of memory, the OS tells a process (might be the one that has been idle the most or the least important, whatever method it uses to prioritize) to terminate. The process writes a small footprint to go back to the same state it was and exits.

When you go back to your running (or that is what you think) app it restarts from storage, like you where launching it for the fist time, and tries to go back to the same state it last wrote. This is why sometimes when you go back to the browser you see it reloading the same page.

With compcache enabled what happens is: when the phone runs out of memory (I am not sure if this triggers it or if it is enabled all the time) instead of writing a state and exiting, a process is compressed and passed on to the swap space set up in RAM. When you go back to the app then it is decompressed and passed onto the main RAM space. This is quite faster than relaunching an app and restoring its state. Compcache is aimed at providing a much better multitasking experience.

Alright, now to the nasty part. To enable compcache we need four things:

rzscontrol - this controls your swap space and size, like a virtual device.

ramzswap.ko - this is the driver for the swap space.

lzo_compress.ko - compcache dependency (compression driver)

lzo_decompress.ko - compcache dependency (compression driver)

We also need some part of support from the kernel, how? I have no idea but I do know this works with newer kernels.

The first barrier in most Donut builds is loading the dependency modules, in fact all modules and it complains that the files do not exist. I solved this by using a symlink to /modules using the name of the server. After all modules are loaded using modeprob, a ramzswap0 virtual device is created which is supposed to hold your compressed data. When I try to initialize this drive, which is the very final step in enabling compcache, the rzscontrol fails with "init: not a typewriter". This was solved in most cyanogenmod builds by using a newer kerner that provides support for this modules.

Downsides to compcache: your phone will be fast at first, not fast like in you'll notice a change, fast as in when you go back to your browser it will not launch and reload your page but will look kind of like when you do an ALT-TAB in windows. With time (not too much time) your phone will start being sluggish due to the several compress and decompress operations. Compcache is also known to cause some data corruption as well and cyanogenmod builds advise not to use it.

Elander, thanks a lot for your support. I can send you the list of terminal commands if you wanna try enabling it and if you are using a newer kernel than the one I attached :) Even though I am thinking if getting a new device like everybody else I wouldn't like to lose my Kaiser. I'm planning on continuing with this builds here that is why I was messing with compcache but I am honestly running out of ideas of what to do next, seems like most things are working quite well at the time. We'll see how it goes.