Google Android Installable Image Available!, Full distro for SL-C3x00+SL-C1000. Need testers for SL-C7x0/860 Options

[cortez]

Hi,

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.

Installation is done in the usual way:

1. Download zImage.bin, updater.sh, gnu-tar and android-root.tar.gz and copy the files to a SD card
2. Remove battery and power adapter cable
3. Wait for 5 seconds
4. Replace battery, close and lock battery cover
5. Attach power adapter cable
6. Keep OK button pressed while pressing on/off switch
7. From the Japanese menu, choose option 4 (Update), then 2 (SD) and finally Y

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.com
Updated: A test version for the SL-C7x0 and SL-C860 can be downloaded from www.omegamoon.com. Please test and give feedback

Greetz,
cortez

[cortez]

I'm trying to get this thing to work on my C1000, but this is giving me some headaches. I did some traces to find out what is happening, and I get following socket error during the start of runtime:

CODE

socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=@property_service}, 19) = -1 ECONNREFUSED (Connection refused)
close(3)                = 0

On the working SL-C3100 version this looks like:

CODE

socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=@property_service}, 19) = 0
recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{"\200\", 4}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {5}}, msg_flags=0}, 0) = 4
mmap2(NULL, 32768, PROT_READ, MAP_SHARED, 5, 0) = 0x40000000
close(5)                = 0
close(4)                = 0

Any ideas what the reason could be?

[cortez]

I'm trying to get this thing to work on my C1000, but this is giving me some headaches. I did some traces to find out what is happening, and I get following socket error during the start of runtime:

CODE

socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=@property_service}, 19) = -1 ECONNREFUSED (Connection refused)
close(3)                = 0

On the working SL-C3100 version this looks like:

CODE

socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=@property_service}, 19) = 0
recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{"\200\", 4}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {5}}, msg_flags=0}, 0) = 4
mmap2(NULL, 32768, PROT_READ, MAP_SHARED, 5, 0) = 0x40000000
close(5)                = 0
close(4)                = 0

Any ideas what the reason could be?

I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here the init executable needs to be patched.

* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file

I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.

[osteron]

I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here the init executable needs to be patched.

* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file

I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.

Perhaps they got it to work because their /tmp is assigned to ramfs and not to the jffs2 part.

[Android Zaurus]

I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here the init executable needs to be patched.

* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file

I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.

Perhaps they got it to work because their /tmp is assigned to ramfs and not to the jffs2 part.

We want the source code of init!

I was lucky to have C-3000, which is equipped with versatile ATA HDD. For the NAND model, yaffs2 might need to be ported.

Cortez, what happens if you go back to run Xzygote, dbus-daemon, runtime instead of init?