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

IPB

Welcome Guest ( Log In | Register )

> Android Possible On Sl-6000, Let's get Android on the Tosa
AsLan^
post May 21 2009, 09:48 PM
Post #1





Group: Members
Posts: 45
Joined: 3-June 04
From: Seoul, Korea
Member No.: 3,555



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!
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
speculatrix
post May 25 2009, 01:23 PM
Post #2





Group: Admin
Posts: 3,281
Joined: 29-July 04
From: Cambridge, England
Member No.: 4,149



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
Go to the top of the page
 
+Quote Post
AsLan^
post May 27 2009, 04:16 AM
Post #3





Group: Members
Posts: 45
Joined: 3-June 04
From: Seoul, Korea
Member No.: 3,555



QUOTE(speculatrix @ May 25 2009, 01:23 PM) *
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.

Go to the top of the page
 
+Quote Post
cortez
post May 27 2009, 06:33 AM
Post #4





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



QUOTE(AsLan^ @ May 27 2009, 02:16 PM) *
QUOTE(speculatrix @ May 25 2009, 01:23 PM) *
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 wink.gif
Go to the top of the page
 
+Quote Post
AsLan^
post May 27 2009, 07:01 AM
Post #5





Group: Members
Posts: 45
Joined: 3-June 04
From: Seoul, Korea
Member No.: 3,555



Thank you for clarifying the NAND backup procedure.

QUOTE(cortez @ May 27 2009, 06:33 AM) *
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 wink.gif


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

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 laugh.gif)
Go to the top of the page
 
+Quote Post
cortez
post May 27 2009, 12:58 PM
Post #6





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



QUOTE(AsLan^ @ May 27 2009, 05:01 PM) *
Thank you for clarifying the NAND backup procedure.

QUOTE(cortez @ May 27 2009, 06:33 AM) *
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 wink.gif


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

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 laugh.gif)

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)
Go to the top of the page
 
+Quote Post
AsLan^
post May 29 2009, 12:35 AM
Post #7





Group: Members
Posts: 45
Joined: 3-June 04
From: Seoul, Korea
Member No.: 3,555



QUOTE(cortez @ May 27 2009, 12:58 PM) *
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)


Unfortunately, I've run into some problems with openembedded and building tosa images. I've posted the details over here in the tosa forum.

If you or anyone else following this thread can get me back on track I'd appreciate it smile.gif
Go to the top of the page
 
+Quote Post

Posts in this topic


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

 



RSS Lo-Fi Version Time is now: 27th December 2014 - 11:24 PM