Quote:
Originally Posted by NiLuJe
@geekmaster: That's usually what happens when the kernel doesn't know what to do with the binary (wrong arch), but, err, that seems unlikely here?
I'm not sure anyone here ever had any experience with a K1 though, so, good luck ;p.
|
That binary is the same one in my "video player" thread. I wanted to see if it would at least run before modifying the framebuffer location (and I was even thinking of making a symlink from /dev/fb0 to /dev/fb/0 so the old gmplay would still work as-is. No "wrong arch" binary, so still a bit
confuzzled about the problem on my K1. Will revisit later...
More puzzling is why my install.sh cannot source a companion script, even when copying similar code directly from the resident "otaup" script (where it should be safe to assume that it does indeed work).
I think it would be cool to launch a KUAL-like menu from an update-install.bin file, without any rooting or jailbreaking involved (other than borrowing from the jailbreak method of running root-code. Another thing I have wanted to do is a custom RAM-resident uboot and/or kernel to launch a root (native) menu system with MfgTool (usb downloader mode), to launch and run apps from user store (or SD card, in the case of the K1).