Google Android Installable Image Available!

[cortez]

Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?

TIA,
fp

heh, i'd like to know too. got a C760 here.

With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.

What kernel is capable runnig Android? Also 2.4.20?

You need a kernel with EABI support. That's version 2.6.16 or newer.

[johnla]

Noone's tried the C1000 yet?

I'll give it a shot this weekend. Would I be able to just use the same files that the C3000 guys are using? There's no internal HD though..

[cortez]

I'll try to build versions for C7x0 and C1000 shortly, so you can join us all in this great experiment

[johnla]

AWESOME!! Most exciting thing to happen to the Zaurus community in a looong time

[Dromede]

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. :-)

[cortez]

I've just build minimal systems for the C7x0 and C1000 and hope to be able to test it tomorrow night on my C1000

[fpp]

Great news ! Thanks for making this accessible to (almost) normal humans :-)

My Z has seen little use since I've had my Nokia tablet and it's a pity - I hope this brings it a new life !

[JohnX]

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.

[Android Zaurus]

Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?

TIA,
fp

heh, i'd like to know too. got a C760 here.

With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.

The original Eu.Edge guys have done on thier C-760.
eu.edge » Blog Archive » Google Android runs on Sharp Zaurus SL-C760

And I found Android can be booted up on ready-made Angstrom kernel as long as we have binderdev.ko module.
Android Zaurus: Android Zaurus on a ready-made Angstrom image

So, Angstrom or Poky for C7x0 could be a host of Android. Question is how to get the binderdev.ko binary.

Do you guys think the driver module built for C3x00 runs on C7x0? My guess is possible because the binder driver seems not to rely on hardware much. If so, cortez's image or my binary can be used.

Cheers,

[Android Zaurus]

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.

Workaround could be my RotateView.apk.    

Cheers,

[cortez]

Hi, I have followed the instructions in the first post and have Android running! Thanks!
So, poor noob would like some help  

- How do I get my Wifi CF turned on? I am not in a chrooted environment; having followed the instructions straight from the 1rst post. Or is that chrooted too?

- What's the way back to sharp rom if needed?

Thanks!

Edit wlan0 section in your /etc/network/interface. There are a couple of samples how to configure in the interfaces file. And don't forget to delete the gateway line in usb0 section.

By the way, I found this news very interrested this morning.

Penguinistas hack Android onto real hardware
http://linuxdevices.com/news/NS4262102607.html

Cheers,

We're being watched  The news spreads itself further... see articles in techworld and pcadvisor

[spaul]

So how do people like android (I have an 860 so I cannot try it yet myself).  Innovative?  Just curious.  Thx

[speculatrix]

We're being watched  The news spreads itself further... see articles in techworld and pcadvisor

and aki news!
http://www.akihabaranews.com/en/news-15328...+Zaurus%21.html

also someone pointed out downloadsquad
http://www.downloadsquad.com/2008/01/10/go...n-sharp-zaurus/

[Android Zaurus]

We're being watched  The news spreads itself further... see articles in techworld and pcadvisor

and aki news!
http://www.akihabaranews.com/en/news-15328...+Zaurus%21.html

and...
Engadget - Android hacked to run on real hardware
Slashdot - Hackers Get Android Running on Real Hardware

Hope more guys interrested in Android on Zaurus. Let's mash it up!

Cheers,

[anil]

Hi,

   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?

Warm Regards,
Anil