i'm currently trying to make it run on a C1000 running angstrom console image. it does run, but i can't get past the bouncing red eye. it just keeps bouncing and nothing happens. the main problem with running android on a C1000 and on earlier models is the jffs2 filesystem. i heard android won't work on a jffs2 filesystem. i'm currently trying to run it from the sd card. any useful advice is most welcome. :-)

I got it running on my C1000 last night. I used an Angstrom 2.6.23 kernel that I applied the patch at http://androidzaurus.seesaa.net/ to. Then I grabbed the android.tgz.part?.rar from http://yonggun.tistory.com/ and followed the instructions for running it. The first time I started it I got nothing but the "Cylon eye" but after rebooting it started no problem the next time. The touchscreen seems to work inconsistently and when android is oriented "portrait" style the touchscreen still acts like landscape.

I got it running on my C1000 last night. I used an Angstrom 2.6.23 kernel that I applied the patch at http://androidzaurus.seesaa.net/ to. Then I grabbed the android.tgz.part?.rar from http://yonggun.tistory.com/ and followed the instructions for running it. The first time I started it I got nothing but the "Cylon eye" but after rebooting it started no problem the next time. The touchscreen seems to work inconsistently and when android is oriented "portrait" style the touchscreen still acts like landscape.

Great work!

Touchscreen is a issue. The orientation problem might caused by MOUSE_X=640, MOUSE_Y=480 in .config file eventhough frame buffer is 480x640. Could be fixed by modifying .config but not tried yet.

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?