I've uploaded a new version of the Android image for the Zaurus SL-C3x00 models. I've added additional packages, and the key settings as well as the RotateView applet from Android Zaurus are installed on default. More info can be found here.

Have fun!

woohoo, I will download for playing with it tomorrow!

Great work, thanks!


--edit--

would it be possible please to give the MD5's of all the files just so we can be sure the downloads were successful

BTW, would you like somewhere to mirror the files?

I get a kernel panic - not syncing: No init found.

You did choose the default option from Altboot on the first boot (boot from microdrive)?
Because, as a programmer would say about his/her program "on my machine it did work perfectly"

First time I tried (C3100) it hung on update immediately after printing


so I checked the md5sums, found gnu-tar was wrong, re-downloaded it, was still wrong, took a known good working copy from my angstrom downloads whose md5 did match yours, tried again, got the same result.

previously, my first ever android install, it went very smoothly.

--edit--
hope you don't mind but I put a mirror of the files on my downloads site:
http://www.zaurus.org.uk/downloads.html

I've downloaded the files myself and tried to reinstall. At the point of "Extracting root filesystem" it shows a "bus error".
Did you see the same error? If I continue, this ends up with a kernel panic (logically without a filesystem) like BarryW
I'll have to check later to see what is happening. In the meantime I've uploaded the android-root.tar.gz again.

no, I didn't get a bus error; but that might be due to corrupted updater.sh - I found it tried to save it as updater.sh.html and the size was bigger; similar problem with gnu-tar.. am wondering whether it tried a unix to dos conversion?

I don't get the altboot menu. Should I have installed after using a different image? This was installed after a cacko install on a 3200.

Okay, here's what I did. I flashed the image with the files on my local system, just to make sure it works. Since this is the case, I re-uploaded all files.
I don't have much time now, so either download and check yourself if the new uploaded files work, or be patient and wait until I double checked them.

Yea, still does the same thing.

It's because of a problem in the gnu-tar binary. Whatever I do, it just uploads a small part. I've adjusted the download link so it points to the SL-C1000 directory. This is the same binary, so it should work if you re-download gnu-tar.

I was just about to post the md5 is wrong..


Maybe if you zip it up first??

It should be okay now, please let me know if it works for you now. Thanks in advance!

Works now!! Thanks! Now to figure out that rotation thing....

sigh. I know what I was doing wrong! I was flashing from CF, but left an SD card in the slot (a 4GB one at that which upsets the cruddy sharp maintenance kernel). Yes, your original gnu-tar was bad (I tested it anyway), but the one I lifted from Angstrom backup was good.
sorry for wasting your time

Thanks for using RotateView.apk.

Currently, it is packaged as com.google.android.rotateview. I will conflict in a Java way if (and only if) Google makes their own applet with the same name.

I'd better repackage it, like net.seesaa.androidzaurus.rotateview.

Guys who already Android up on you Zaurus, you might want to check this.

Do you have tmpfs already mounted on somewhere in your file system? It's easy to check. On the text console, type;

# df -h

If you see a word of tmpfs, you have one.

My Angstrom has;

tmpfs 30.3M 0 30.3M 0% /media/ram

If you have tmpfs larger than 15MB or so, try to modify a little your android-root/a.sh;

Before
mount -t proc proc /proc
mount -t sysfs sysfs /sys

After
mount -t tmpfs tmpfs /tmp
mount -t proc proc /proc
mount -t sysfs sysfs /sys

Yes. Just add a line to mount your tmpfs as /tmp. Then try boot Android up.

How is it? You'll notice a lot less HDD LED brinking than before. And a little bit faster.

The reason is Android generates shared memory as temporary files in /tmp. By mounting /tmp as tmpfs, we move the shared memory out to RAM.

I come up with this tip in the course of trying to bring Android up without chroot.

Android Zaurus: Boot Android up on Zaurus without chroot
http://androidzaurus.seesaa.net/article/79313160.html

Cheers,

Same here.. Uh I cant see the altboot loader neighter. Should I install that seperate?

Please (re)download the gnu-tar executable. This looks like you're using the corrupted one, which was replaced with a working one a while ago.

If this doesn't work please create a (empty) file called install.cfg on the sd-card and reflash. At the end of the installation you should now be asked if you want to install the additional packages mentioned in the file. When this question appears, look closely at any errors on screen, and report them here. To finish the installation, answer the question with N (since the file is empty anyway).

When the extraction of the root filesystem is successful, the kernel panic should disappear and Altboot will be started automatically.