Android Possible On Sl-6000, Let's get Android on the Tosa Options

[AsLan^]

Sorry for not posting this in the Tosa forum but there's like 20 sticky threads in there so I figure it would probably be overlooked (and it is Android related too).

I would like to try getting Android on the 6000 but I'm not really sure how to go about doing it.

Do we have to use the Angstrom distribution kernel and put Android on top of it (like how cortez is doing it on the 3000)? Is there some way we can make an easy to flash distribution?

I'm not really sure where to start, and some things that might be obvious to others are unknown to me (for example, I can't figure out how to turn the tar.gz packages built by the Angstrom auto-builder into an installable image for my 6000) so I need help. But, I'm a pretty quick learner and if anyone's interested in helping me I'd like to give it a shot.

Android with Angstrom could be the modern OS that revives our 6000's and makes them useful again!

[speculatrix]

a cool idea. yeah, I'd start by installing the smallest angstrom image possible, then copying in the android rootfs, and using cortez's chroot method.

when you know that works, it should be possible to do away with chroot and simply merge the android directory hierarchy with angstrom

finally, use the D+M boot option to take a rom snapshop and publish

[AsLan^]

finally, use the D+M boot option to take a rom snapshop and publish

I'm afraid I also don't know how to specify any boot options. I'm not running any kind of boot manager.

[cortez]

finally, use the D+M boot option to take a rom snapshop and publish

I'm afraid I also don't know how to specify any boot options. I'm not running any kind of boot manager.

By "D+M boot option" speculatrix means the NAND Backup option in the Diagnostic (ROM) menu. To get there, use D+P+Reset, you will hear a beep and a graphical menu is shown. Scroll right with the D-pad until you are on page 4/4 and then there will be two options for NAND Backup, and NAND Restore.

The version you took from my blog actually is the M5-RC15 release, which was the last "early-look" version before version 1.0 was released. The fact that you see the "oscillating cylon eye" indicates that you've setup everything correctly. The reason Android doesn't boot is because you're kernel doesn't contain the Android Binder device driver.

Add the driver, rebuild and flash the kernel and you're all set. Sounds easy, but I know it's not

[AsLan^]

Thank you for clarifying the NAND backup procedure.

The version you took from my blog actually is the M5-RC15 release, which was the last "early-look" version before version 1.0 was released. The fact that you see the "oscillating cylon eye" indicates that you've setup everything correctly. The reason Android doesn't boot is because you're kernel doesn't contain the Android Binder device driver.

Add the driver, rebuild and flash the kernel and you're all set. Sounds easy, but I know it's not

It's good to hear that it's setup properly so far

Regarding rebuilding the kernel etc. does this mean I will have to set up bitbake? (I don't think Poky Linux has a build for the tosa).

Also, how do I go about getting the newer version of Android, is it just a matter of downloading the Android SDK and locating the tar.gz file? (getting ahead of myself )

[cortez]

Thank you for clarifying the NAND backup procedure.

The version you took from my blog actually is the M5-RC15 release, which was the last "early-look" version before version 1.0 was released. The fact that you see the "oscillating cylon eye" indicates that you've setup everything correctly. The reason Android doesn't boot is because you're kernel doesn't contain the Android Binder device driver.

Add the driver, rebuild and flash the kernel and you're all set. Sounds easy, but I know it's not

It's good to hear that it's setup properly so far

Regarding rebuilding the kernel etc. does this mean I will have to set up bitbake? (I don't think Poky Linux has a build for the tosa).

Also, how do I go about getting the newer version of Android, is it just a matter of downloading the Android SDK and locating the tar.gz file? (getting ahead of myself )

Setting up bitbake (Poky or OpenEmbedded) is a good and quick option to get a working build environment. You could tweak one of the provided kernel packages easily to build a kernel for the tosa, even with the latest 2.6.30 sources. The latest kernel should work using stock kernel.org sources without the need for patches.

To get the latest Android version you could rip the file system from the emulator (as I did with the pre-releases) or rebuild it from source (as described here)