[Q] tun.ko not module but permanent / clocks and keyboard

---

hi.

1)
I still seem to have problems with VPN eventhough I activated all necessary modules and compiled the kernel.

What happenes if I compile tun.ko (tunneling service) not as a module but permanent in kernel. is vpn widget working too?



2)
the on screen keyboard is a little unresponsive but especially on the first keystroke after a longer break. I think it is the cpu clocking down. is there a way to prevent deep clocking down whilst he keyboard is open?

short update on the first question:
I found out that tun.ko module was not loaded by a script. when initialising a vpn connection via VPN Widget it took a long time to connect. then somehow the tun.ko module got loaded and connection was made. I now have an additional script where tun.ko is loaded with insmod.

Question is: is vpn widget still working when tun.ko is not a module but permanent in kernel?






second question:
I know there was a thread somewhere here on xda about a hacked keyboard app. The hack was not about cpu, but something about memory. The thread did not have many responses, probably nobody understood what the developer did...
But I don't find the thread any more...