In order to get Android properly configured for your device you need to find out what specific device model you own. The easiest way to do this is to take out the battery and look at
the device underneath where the battery was. The device model code should be printed there in the
format DIAM### or RAPH###.

You need to acquire the necessary files in order to run Android. Premade packages are available here which basically consist of three elements.

• Base Files
• Kernel Image
• Configuration text file

The Base files are basically Android, while the kernel image features more device specific features.
The configuration file is basically just a text file with various variables which defines certain settings such as kernel image name, resolution, and so forth. Hardware details can be found here.
The most important thing to note is the fact that the Kernel Image is mostly specific to the Raph and the Diamond
while the configuration text file, often named startup.txt (older packages used default.txt), is specific
to, not only the two different models, but for each model number as well. Meaning the RAPH800 requires a
different configuration file than the RAPH100.

So, with this in mind, head over to the download section and grab your desired package. Generally,
the newest package is the recommended one unless otherwise specified.

Then you should check out the three auto build services.

Kernel images

Rootfs

Initrd

This will ensure you have the latest up-to-date files!

The installation procedure varies from package to package so its generally a good idea to follow the installation instructions on the download page. But in general, after you have downloaded the package, you just need to extract the contents on to your Internal Storage (if you have a Diamond) or the Storage Card (if you have the Raphael), open up the file explorer in Windows Mobile and run haret.exe before crossing your fingers while watching the console text printing out. After about 60-90 seconds, you will hopefully be seeing Android loading up. If not, then you need to start troubleshooting A good source for help would be the forums

So, Android didn't boot up as expected. There are many possible reasons for this. In 80% of the time, the problem is due to incorrect startup.txt or kernel image, so try to use a different kernel image and make sure your startup.txt is the one you should be using on your device model. If that is not the problem, then the combination of base files, kernel image and startup.txt most likely just doesnt work for your device and you will have to find a different combination.

Other solutions that often solve problems people are having includes formatting the memory card, removing old Android files or just simply reboot the phone and try again.

If you are still having problems, now would be a good time to check the forums..

In order to get a working data connection you will have to do a few things. All is nicely outlined in this guide and following it should get you up and running in no time!

Both CDMA and GSM devices should be able to get a working data connection now. Make sure you have the latest Android package, kernel image, rootfs and initrd!

CDMA network support remains a major issue in the porting project. The bottom line currently, CDMA devices (RAPH500/800, DIAM500/800) is not getting an cellular network coverage in Android. There does exist a few scattered kernel images which provides some kind of CDMA support, but they are currently outdated and obsolete.

The problem is that CDMA is implemented hardware wise which leads to the need for CDMA specific development, whereas no one with a CDMA device has really worked on the project. Hopefully, this will be sorted out soon.

The battery life in mobile phones is largely dependant on two things: Hardware (size of battery, effect usage of other components, etc) and the power management in the operating system. This is why you will most likely notice a decrease in battery life while using Android. Power management is one of the areas we are working on, but expect battery life to be very short, depending on which Android package and kernel image you are using. Its an area where improvement is to be expected. Just don't panic if you find out your phone dies out after a few hours.

If you are going to modify your startup.txt, its useful to know the related parameters you need to edit in the configuration .txt file (startup.txt). Here is a simple overview.

I will be trying to collect startup.txts for all devices so this will be updated as I make progress. If you have any additions or corrections, please let me know.

Last updated: March 12th, 2010

RAPH100

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage.20100207_140206
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=raph"
boot

RAPH110

set ramsize 0x6000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage
set initrd initrd.gz
set cmdline "root=/dev/ram0 init=/ console=tty0 mem=76M msmsdcc_id=3 zmgdevname=/dev/mmcblk0p1 imgdevnum=1 imgdir=/ msmts_calib=0x6D.0x5D.0x340.0x375 mddi.width=320 mddi.height=480 lcd.density=192 ppp.apn=wap.cingular ppp.username=WAP@CINGULARGPRS.COM ppp.password=CINGULAR1 clock-7x00.a11=500 msmvkeyb_toggle=off"
boot

RAPH500

set ramsize 0x6000000
set ramaddr 0x10000000
set mtype 2039
set KERNEL zImage
set initrd initrd.gz
set cmdline "root=/dev/ram0 init=/ console=tty0 mem=76M msmsdcc_id=2 zmgdevname=/dev/mmcblk0p1 imgdevnum=1 imgdir=/ msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off"
boot

RAPH800

set ramsize 0x6000000
set ramaddr 0x10000000
set mtype 2039
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3"
boot

DIAM100

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1805
set KERNEL zImage.20100207_140206
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,-1,3 board-htcraphael-navi.wake=0"
boot

DIAM200

set ramsize 0x08000000
set mtype 1805
set KERNEL zImage
set initrd initrd.gz
set cmdline "msmts_calib=115.105.863.911 pm.sleep_mode=0 msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=210 board-htcraphael-navi.inversion=1"
boot

DIAM500

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage.20100207_140206
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 board-htcraphael-navi.wake=0 physkeyboard=fuze"
boot

Blackstone

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3"
boot

Rhodium

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage.20100207_140206
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 force_cdma=1 physkeyboard=rhod210"
boot

Topaz

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage.20100207_140206
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x395.0x3d5.0x79.0xa0 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3 sensor=topaz force_cdma=1"
boot

Blackstone

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set KERNEL zImage.20100207_140206
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3"
boot

Considering the Touch Pro and Diamond has a native VGA (480x640) resolution, Android looks really “small” on such a high resolution screen. In order to fix this, just add the following lines to your startup.txt within the quotes:

mddi.width=320 mddi.height=480 lcd.density=240

Keep in mind that this should be placed within the quotes in the startup.txt file, so you would end up with something like:

set mtype 2039
set kernel zImage
set initrd initrd.gz
set ramsize 0x6000000
set ramaddr 0x10000000
set cmdline "root=/dev/ram0 init=/ console=tty0 mem=76M msmsdcc_id=3 zmgdevname=/dev/mmcblk0p1 imgdevnum=1 imgdir=/ msmts_calib=0x81.0x393.0x358.0x7D clock-7x00.a11=500 msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240"
boot

Save and boot into Android and enjoy a lower resolution which is easier to handle!

WiFi is working and rapidly improving. In order to use it, you need a recent Android Package, available from the download area here. It should now work pretty much out of the box. However, do keep in mind that in its current state, WiFi really eats the battery.

One of the first issues many encounter is that Android asks for the PIN code but wont accept the one entered. The solution is quite simply to disable the PIN Code protection prior to booting up Android!

The PIN Code protection setting is a SIM card setting so it doesn't matter what phone you adjust it on either, as it is stored in the SIM card. just so you know!

Once you have downloaded the latest Android package right here at Connect-UTB you should race over to the three auto build services and grab the latest copies.

Improvements are numerous and its recommended that you get the latest kernel image, Rootfs and Initrd

Kernel Image Auto Build Service

This service holds the latest kernel images (zImages)

Link (Updated)

Rootfs Auto Build Service

This service holds the newest rootfs files

Link

initrd Auto build Service

Here you will find the latest initrd

Link

So make sure you check all three from time to time in order to stay in tune with the latest updates! Also keep checking Connect-UTB :) If you need any help at all, please dont hesitate to check out the forums!

On some Diamonds, such as the DIAM200 (AKA T-Mobile MDA IV Compact), the back and home button are on the bottom while the call and end button are on the top. This leads to an issue when in Android, as the button mapping on most Diamonds and Touch Pro’s are exactly opposite. However, this can easily be solved by putting the following line in your in your startup.txt:

board-htcraphael-navi.inversion=1

Save, and enjoy!

If you find that the bootup console hangs at the waiting for SD-card error, you will probably need to reformat your memory card. Note: This assumes that you are using the correct startup.txt and kernel image for your device.

The Sdcard reformatting tool is recommended

This Android porting project supports a wide range of HTC devices. They all have similar internal hardware and that is why they are all supported. Other devices such as the HTC Kaiser and HTC Vogue also run Android well but that is a totally different porting project not covered here.

Currently supported devices:

• HTC Diamond
• HTC Raphael (Touch Pro)
• HTC Blackstone
• HTC Topaz (Diamond 2)
• HTC Rhodium (Touch Pro 2)

If you own any of these devices you can feel free to try running Android on it with the files available here at Connect-UTB

Due to the fact that the HTC models running Windows Mobile features different buttons than those featured on Android devices, the button mapping is a bit different.

1. Power Button
Press: Go home screen
Hold: Switch between Application

2. VolUp
Press: Increase ringtone, media and incall volume

3. VolDown
Press: Decrease ringtone, media and incall volume. Can also set vibrate and Silent.

4. Home Button
Press: Open up setting

5. Call Button
Press: Open recent call
Hold: Launch Voice dialer

6. Back Button
Press: Goes back one previous screen

7. Call end Button
press: Turn off display or end phone call
Hold: Set audio on or off, Airplane mode or turn off device

8. Centre Button
Press: Accept or select. Also used as scrolling, zoom in or out.

9. Android Menu tab
Pull up or down to open / close Program tab

10. Notification tab
Pull up or down to open / close notification tab

11. USB
Plug in USB for adb, USB debugging, charging