First off credits goto all those working hard and having sleepless nights, people like: dcordes, netripper, druidu and all those I didnt mention!
I have just made this thread to get developers a kickstart, so that they dont have to read hundreds and hundreds of posts.
IRC: #htc-linux @ Freenode
Getting the kernel (taken from http://forum.xda-developers.com/show...84#post2269384 ... credits to dwaradzyn): (UPDATED, new ARM toolchain and now working)
mkdir ~/android cd ~/android git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git cd kernel git checkout -b htc-msm-2.6.25 origin/htc-msm-2.6.25 cd .. wget http://www.codesourcery.com/gnu_toolchains/arm/portal/package3382/public/arm-none-eabi/arm-2008q3-39-arm-none-eabi-i686-pc-linux-gnu.tar.bz2 tar xvjf arm-2008q3-39-arm-none-eabi-i686-pc-linux-gnu.tar.bz2\?lite\=arm cd kernel make htcraphael_defconfig ARCH=arm export PATH=~/android/arm-2008q3/bin:$PATH make zImage ARCH=arm CROSS_COMPILE=arm-none-eabi-
Open your favourite text editor to create the file "DEFAULT.txt" and put the following in it:
set MTYPE 1910 set KERNEL zImage set INITRD android.bin set RAMSIZE 0x5e set RAMADDR 0x10000000 set cmdline "root=/dev/ram0 rp init=/init console=tty0 mem=94M" bootlinux
Is the android.bin in http://h3po.de/public/diamond_android_0.8.zip the same? (Havent checked)
Now the new points of attention are:
1. Touchscreen calibration:
I have seen people talking about a red dot in the upper left corner, I have seen it once so far and didnt notice any major miss calibration when using the dev tools > pointer locator ... the only this malfunctioning is the x inversion and that you need to double tab (or is this standard behaviour? It looks like it remembers the last pressed location). Also the onscreen keyboard is very flickery, minor issue should be easy to fix (during loading it looks like it is flickering on the readout of the touchscreen).
2. Hardware support:
Adding various support for hardware, to output sound and all other "required to call" fuctionality.
Also not forgetting to access internal memory, maybe the best workaround to loading a fully fledged Android is to make a minimal initrd to setup internal storage and from there load the rest. Should be much easier when it all gets incorporated into a ROM, instead of loading with haret ... which poses serious problems regarding initrd loading and who wants WM6x/7 on his phone anyway when Android becomes usable. Loading from haret does make working with it for now a little easier. Maybe a GRUB like approach and loading straight from a filesystem (ROM or internal storage)?
Some other request:
Pointers to Android OS sources or atleast a working 1.0 (latest branch?) initrd.
Going back to desktop: insert and remove stylus.
Selecting and opening, use double tabbing and mirror x for now.
Using onscreen keyboard: havent figured it out yet sadly.
Ill try to update the post, also PLEASE people refrain yourself from posting in this thread ... let's make a good go at keeping it clean. If you do not intend to be working on getting Linux / Android to work on the Diamond and family please post somewhere else. No harsh feelings, but threads getting cluttered with "Great work!" and "wehn iz android really workn on me phone?" do mess things up by quite a bit.
DO NOT ASK FOR REQUESTS, focus is on the basics first ... input, output and storage.
Dont forget to check: http://wiki.xda-developers.com/index...e=RaphaelLinux
Developers, please post updated links / patches and all that would help us make progression.