Originally Posted by Sheraz150

Ah that makes sense. So it is possible to boot android, but not be able to use it lol? It would still be impressive.

According to what dcordes just posted, yes I guess it is possible to boot Android albiet missing certain drivers. Not sure which ones are working and which aren't, but it would be a fun POC (like the linux video player) .

If you want to try android I recommend grabbing some image files for nexus one as a start along with the kernel and other files from my hd2 media player build.

Google don't care for conformity so they use the yaffs2 file system that's not in mainline. At least they provide a C program called unyaffs which is useful to extract the images.
This will get you system.img files.
Additionally you need to to look at boot.img . This has kernel and an initrd.cpio.gz with init scripts and the strange busybox mutation (again no conformity. why not using busybox? it's ridiculous they obfuscate everything for no reason) to prepare the android start. There is some perl script out there called unpack-bootimg.pl which is helpful.
Soon as you got everything extracted and started looking at what the init.rc script in the initrd.gz does you will notice it tries to mount the system and data image files from nand. We don't have that so you have to work your way around this. e.g. use my angstrom builds for the mdia player to mount a repacked system.img loopfile or extract system to some sd partition. afterwards execute the android init . maybe modify the android initr.rc .

edit: btw thanks for the pointer with the bravo kernel.

Originally Posted by Crash1983

I don't think the ramt rick is causing the trouble.

Phones with the same setup (Same ROM, same Radio) show a different behavior.

Assuming that there are no differences in hardware, the problem has to be a little thing we all forgot. So we have to compare.

Could the boot loader be a reason? I am using HSPL 2.08 and have no success....

i don't think so,
cause we load another bootloader and close the wm that will access the radio or something like that

but that's only what i think with things i learned on this kinds of threads

Originally Posted by dcordes

If you want to try android I recommend grabbing some image files for nexus one as a start along with the kernel and other files from my hd2 media player build.

Google don't care for conformity so they use the yaffs2 file system that's not in mainline. At least they provide a C program called unyaffs which is useful to extract the images.
This will get you system.img files.
Additionally you need to to look at boot.img . This has kernel and an initrd.cpio.gz with init scripts and the strange busybox mutation (again no conformity. why not using busybox? it's ridiculous they obfuscate everything for no reason) to prepare the android start. There is some perl script out there called unpack-bootimg.pl which is helpful.
Soon as you got everything extracted and started looking at what the init.rc script in the initrd.gz does you will notice it tries to mount the system and data image files from nand. We don't have that so you have to work your way around this. e.g. use my angstrom builds for the mdia player to mount a repacked system.img loopfile or extract system to some sd partition. afterwards execute the android init . maybe modify the android initr.rc .

edit: btw thanks for the pointer with the bravo kernel.

Wow i'm really lost right there
Can u clearify the one and other
maybe u can provide us a progressive scheme as most of us don't know where to start
(At least I ain't and I follow this daily)

would you recommend

---

would it make sense to try some of the haret based images that are known to work on other devices to see how far it gets... although cant think of any wm devices with similiar specs to the hd2 with android working through haret.

ps) most likely wishful thinking, cant be that easy.

Don't take offence to this, but if you don't understand what he means then you shouldn't bother. The actual developers are working hard to get this working as it is and he's calling on more developers to try and help. If you don't know whats going on by following the thread, you will most likely get lost doing this.

Originally Posted by Finezt

Wow i'm really lost right there
Can u clearify the one and other
maybe u can provide us a progressive scheme as most of us don't know where to start
(At least I ain't and I follow this daily)

In a nutshell: unpack stuff from google build of nexus one rom. edit stuff in it so it knows where to look for things(nexus one looks for stuff in internal memory -ROM- but we work on the SD card). Repack everything for haret and try...if some drivers are missing or some settings are wrong you may not get much.
For example when the GUI loads it may not display anything because of different screens.
Like you would take a linux machine(desktop) with a xorg.conf file and put another monitor on it with different refresh rates supported, different color depths and so on, the monitor will not support the default xorg.conf settings and may not display anything. But in modern distros X knows how to do autodetect an do stuff right.
In an emebeded OS usually you don't have things like hardware autodetect because you don't change hardware, so any setting in the nexus one files that doesn't match with HD2 hardware will give problems and will need tracking and solving. It may not be as easy as he makes it sound...or we could just be lucky and have everything(that has a driver in the kernel) working right the first try.

Alright thanks I'm going to try this
* download the unayffs
* download a original nexus one rom
* extract the boot.img from the .zip file
* put these files included the latest kernal ( the one with 20mb )
* than try to start if don't i'll play with the settings maybe I could figure it out
then i'll let you know
Correct me if I'm doing something wrong

give me a list of files that must be edited in an android build (I'm thinking mostly having to edit init.rc and init.device.rc to match the new filesystem), the changes I have to make (new mount points), and instructions on how to make the system, userdata, and ramdisk images haret uses, and I'll test a build and post if it works.

I'm something of an android dev, but up to now I've only worked with an android device (dream/sapphire) which is pretty no-nonsense about what you have to do (flash-mount boot.img to boot, system.img to system, and data.img to userdata.img), plus the mount points are pretty much unchanged coming from AOSP.

I guess I'll have a look at the rhodium builds and see how much they differ from an actual android device's build. Something I remember from poking at it is that the images (system, userdata) are no longer yaffs but something else.

I'll check.

I understand that we are currently in POC stages albeit pretty far along thank to all involved. My question is ultimately when this becomes stable down the road and is running Android will we be running this on internal memory and not sd cards?