bigsupersquid
o_O
the bootubuntu script is similar in function.
there is a piece of it I'm going to cannibalize and absorb into mine, the part which checks for the existence of a directory before creating it.
let me know if my script gives you trouble and I'll try to help with it.
I forgot to mention, many of the chroot 'boot' methods I've looked at can't be politely shut down and require phone reboot to unmount. Mine (and it looks like your bootubuntu script as well if I'm reading it right,) can be exited and even run again afterwards without rebooting.
My eventual goal with this is to avoid the VNC viewer (another big slowdown for the chroot) and get access to the framebuffer device from linux. Android configures the fb device differently than X, and trying to use it as-is results in a blank screen. It doesn't lock up the phone, but no display without reboot.
@mmarz, you said in the first post that there was a problem with the soft keyboard? I haven't noticed any issues with mine except that I can't find a free 'full' keyboard for esc,ctrl,alt and F-keys.
The android-VNC-viewer I'm using (on google code , also an older version is in the market,) has them in the 'send keys' submenu, but I haven't gotten a soft keyboard with more than a ctrl key to use in the terminal.
(I added my 2 cents on the swype beta forum about special keys but they don't seem to care.)
The chroot method I'm using usually only seems to slow Android down if some CPU-intensive work is going on in the chroot, like building a package from source, running debootstrap, or something like that.
I'll wager the loop-mount is causing most of your system lag.
there is a piece of it I'm going to cannibalize and absorb into mine, the part which checks for the existence of a directory before creating it.
let me know if my script gives you trouble and I'll try to help with it.
I forgot to mention, many of the chroot 'boot' methods I've looked at can't be politely shut down and require phone reboot to unmount. Mine (and it looks like your bootubuntu script as well if I'm reading it right,) can be exited and even run again afterwards without rebooting.
My eventual goal with this is to avoid the VNC viewer (another big slowdown for the chroot) and get access to the framebuffer device from linux. Android configures the fb device differently than X, and trying to use it as-is results in a blank screen. It doesn't lock up the phone, but no display without reboot.
@mmarz, you said in the first post that there was a problem with the soft keyboard? I haven't noticed any issues with mine except that I can't find a free 'full' keyboard for esc,ctrl,alt and F-keys.
The android-VNC-viewer I'm using (on google code , also an older version is in the market,) has them in the 'send keys' submenu, but I haven't gotten a soft keyboard with more than a ctrl key to use in the terminal.
(I added my 2 cents on the swype beta forum about special keys but they don't seem to care.)
The chroot method I'm using usually only seems to slow Android down if some CPU-intensive work is going on in the chroot, like building a package from source, running debootstrap, or something like that.
I'll wager the loop-mount is causing most of your system lag.
Last edited: