For the time being posted here in "General Discussion" since there is no dedicated Android subforum (yet). Tested on my SL-C3100, this is a small bootable Poky 2.6.23 kernel with a copy of the Android OS from the SDK (qemu) emulator.

Flashing starts, and you are asked if you want to flash the kernel, if you want the microdrive to be formatted and if you want the root filesystem to be installed.Accept all questions answering them with y

After flashing is complete, the machine is rebooted. Login with root and type /start to start Android. This is the basic version, without any of the patches found across the Net.

Have fun, and share your results and findings here please!

Updated: There is a special version for the SL-C1000. Downloads and instructions can be found at www.omegamoon.comUpdated: A test version for the SL-C7x0 and SL-C860 can be downloaded from www.omegamoon.com. Please test and give feedback

We are trying to get the Android framework (binary) working on our custom hardware that is based ARM11 core. We do have a 2.6.23 kernel with ABI support and the android-root.tar.gz suggested in your post is being used as the rootFS. However when we try launching the /start script from console, it is unable to load the binderdev.ko module that is shipped with android-root.tar.gz archive. Hence we have added the binder module support into our custom kernel (binder module source code has been taken from from the linux-2.6.23-android-m3-rc20.tar archive) as static driver. After having added this support, the re-built kernel has been tried with aforesaid rootFS, but after couple of initial messages it bails out with segmentation fault. When I tried the strace utility to trace through the execution, it has been found that the "binder module is failing with Descriptor2Node failed". The complete strace log is give below:

--admin's note - text snipped and put in an attachment to make thread more readable--

It would be really great if someone can give some input/suggsetions regarding this. Can the pre-built Android binaries run on ARMv6 compatible machines? How do we move forward and get the framework properly working on our custom hardware?