OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

2 Pages V  < 1 2  
Reply to this topicStart new topic
> Android Sl-c3x00 Image Updated
Android Zaurus
post Jan 18 2008, 05:06 PM
Post #16





Group: Members
Posts: 45
Joined: 30-December 07
From: Japan
Member No.: 21,136



QUOTE(cortez @ Jan 18 2008, 05:44 AM) *
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!


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.
Go to the top of the page
 
+Quote Post
Android Zaurus
post Jan 19 2008, 02:43 AM
Post #17





Group: Members
Posts: 45
Joined: 30-December 07
From: Japan
Member No.: 21,136



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,
Go to the top of the page
 
+Quote Post
draco.mars
post Feb 6 2008, 05:12 AM
Post #18





Group: Members
Posts: 1
Joined: 6-February 08
Member No.: 21,340



QUOTE(BarryW @ Jan 17 2008, 09:53 PM) *
I get a kernel panic - not syncing: No init found.

Same here.. Uh I cant see the altboot loader neighter. Should I install that seperate?
Go to the top of the page
 
+Quote Post
cortez
post Feb 6 2008, 12:43 PM
Post #19





Group: Members
Posts: 376
Joined: 18-March 04
From: The Netherlands
Member No.: 2,380



QUOTE(draco.mars @ Feb 6 2008, 02:12 PM) *
QUOTE(BarryW @ Jan 17 2008, 09:53 PM) *
I get a kernel panic - not syncing: No init found.

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.
Go to the top of the page
 
+Quote Post

2 Pages V  < 1 2
Reply to this topicStart new topic
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 17th December 2014 - 04:42 PM