Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)

• InitRD - 20100813-b11116a
• Rootfs - 20100828-c29a486
• System - XDAndroid 2.2.AOSP.3.9.10.RC.2.2
• Kernel - 20100830_01302 (no debugging)
• Headset support - Credits to Oliwe
• 3D support for Blackstone/Diamond/Raphael (Rhodium/Topaz have no 3D)- Credits to Oliwe
• Gallery working - Credits to Oliwe
• Touchscreen Calibration is back! During first clean install, touch each of the five calibration points CAREFULLY to calibrate your screen before installation completes. Plus, general touchscreen fixes and power off support - Credits to Oliwe
• Back to basics System... stock Android system.
• Takes about 5 mins usage before the system starts to speed up, so expect it to be a little sluggish for the first 5 mins.
• None 3D devices may not show boot screen, so please be patient during install (screen will show black)
• I'd advise that once installed, you also launch SpareParts, and configure the window animations etc to 'fast'
• There is a chance that after installation, some Startup.txt settings MAY be incorrect for your device. If you discover any mistake, PLEASE let me know, I will correct asap. I need your help on this guys.

• Step 1 - Prepare your SD Card
  Find a nice clean SD card to load Android on.
  You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
  *Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
  Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
  
  
• Step 2 - Download and install the CAB
  Download and install the following 'full package' cab (a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid Cab button below.
  
  
  
  You MUST install on the Storage Card. The cab file will take a couple of minutes to install Android. Please be patient.
  
  For those that are interested the cab files does the following:
  - Installs Android in the root of the SD Card
  - Deploys the correct Startup.txt for the device (the user can choose their device type)
  - Adds a high res icon for Android in the root of the SD Card
  - Installs a shortcut in Program Files named "Android" (launches Haret.exe)
  - Installs the high res icon in the registry for WM6.5 users
  
  
• Step 3 - Run Android
  Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
  Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
  The reason the first boot takes longer is that Android is 'preparing' your device for the first time.

• Step 1 - Prepare your SD Card
  Find a nice clean SD card to load Android on.
  You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
  *Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
  Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
  
  
• Step 2 - Download and extract the ZIP
  Download and install the following 'full package' zip(a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid zip button below.
  
  
  
  You MUST unzip to the ROOT of the Storage Card. The zip file will take a short while to extract. Please be patient.
  
  
  Once you've extracted the zip:
  - Click Auto-Setup.exe to configure XDAndroid for your particular device
  
  
  
• Step 3 - Run Android
  Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
  Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
  The reason the first boot takes longer is that Android is 'preparing' your device for the first time.

• SDCard - Most SDCards are working, but if you the 'waiting for SDCard' message, you should try one of these fixes (and please let us know if it works)
  Fix 1: Format your card with this tool http://www.sdcard.org/consumers/formatter/
  Fix 2: Edit your startup.txt file and add these entries to your cmdline:
  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
  msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
  Fix 3: Tell your wife / girlfriend that you are about to make some modifications to her phone... change the ringtone and steal her old Class 2 SD Card to use with Android. She will never discover what you have done, and if she does, you'll be able to use Android to send texts to your former girlfriends ;-)
• SDCard - A few users have claimed to have had trouble using their SD Cards after installing XDAndroid. Some of those have reformatted the SD Card, and it worked, some couldn't recover it. This is a minority of users, but be warned.
• Camera - Not working
• GPS - working
• Battery Status - Highly problematic for most users (don't trust the capacity Android tells you, it's simply up and down a lot, and highly inaccurate)
• WiFi - Working for most people, suspected to cause slight heat, definitely drains the battery faster than WinMo.
• Audio - Speaker working for most people, microphone can have issues
• Deep Sleep - Working for most people, but can have issues waking up (sometimes, it will not wake up)
• GPRS - Working
• 3G - Working for most
• PIN Code - Unknown
• GSensor - Working (Screen only handles 0 and 270 degrees)
• Bluetooth - Experimentally working (don't expect too much, but it's working for a number of users)
• OpenGL ES - 'should' be working but only for Blackstone... more to follow soon
• USB - Supported, but will NOT operate in mass storage mode. You can charge via USB and you can debug, but forget accessing your files by it.
• Headphone Socket - Semi working (see FAQ for details on how to make it work)
• Application Errors: It's very common to see 'Application (xxxxxx) is not responding: Force Close or Wait'. Click wait. I do not know the precise reason for this, but from what I can gather, it COULD be related to the slow speed of the SD Card causing the app response times to JUST be a little too slow for Android's liking, thus causing the message. This seems to happen more after bootup or wakeup when the device is busy doing stuff in the background.
• Cannot choose ringtones: This is believed to be caused by the media scanner failing (due to discovering some filenames with none English characters). The best option of all is to use a CLEAN SD Card. But, if you insist on hosting other files on the same SD Card, you MUST make sure they have English character filenames.

yaronimo said:

Hi,
Here is what I've done:
After Formatting to fat32 and copying the content of both zips I still needed a startup.txt for my blackstone, so I took one from the startup configs of the 2.2V1.6, but I wonder, since android freezes after a few moments, is it the right thing to do?

Here is its content, should it work with this last build?

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

If this is not right then what should be the best "startup.txt" for non-overclocked Blackstone ?

I've tried with the startup.txt that came with the first zip, same results.

Click to expand...

Click to collapse

miniterror said:

maybe a strange question but will this be updated?
last update is from september
i want to put this on touch pro 2 but if a update is coming soon i will wait for it

Click to expand...

Click to collapse