The XDAndroid Project is no longer active.
This site provides archived information from while the project was under development. Some links may no longer function.

FAQ

From The XDAndroid Project
Jump to navigation Jump to search

FAQ

Contacts

How to sync WinMo with Google

On the Android side, if you simply set your Google account to sync, (and you sync with WinMo) all your contacts will synchronize between operating systems - if you add a contact in WinMo, it syncs to your Google account, and same if you add a contact in Android.

How much space do I need on my Storage Card?

The data.img file by default is 256mb. With everything else, it's usually around 480mb, so a 512mb card will just barely suffice - you won't be able to fit much else on the card except for XDAndroid however!

My touchscreen doesn't work / poorly calibrated

Delete the ts-calibration file from the root of your SD card (or where ever you run haret.exe from). The next boot you will see a calibration screen, watch the boot process carefully!

LED always orange / green

This represents sleep state (Orange=Wake, Green=Sleep). If you never seen green, the phone isn't properly sleeping. Make sure GPS is disabled, as this will kill sleep.

Time Drift

There are two types of time drift reported - if you notice your clock drifting in Android, download ClockSync (on the Market) - I have it set to sync the clock every hour.

The second type of drift people have reported is when they boot back to WinMo, and they're clock is 6, 8 etc hours off. This is because Windows stores the time locally, and Linux (and a lot of other systems) store in UTC or GMT. Usually if you sync the time in WinMo with your network provider, you'll never have a problem. Some have said this still doesn't work, then a third party app for WinMo that keeps time in sync is necessary.

Google Voice Issues

If you have trouble dialing out using Google Voice, place this line in your startup.txt (in the 'cmdline' section...)

north_am_dialing=1

Wifi problems

If the AP is secured with WEP, it will not work. This protocol is extremely insecure, but if you do not have a choice there is an app called 'wifi-ace' on the market that can resolve this issue for you.

If you have issues with hidden networks, the aforementioned app will fix this too!

Startup.txt Options

lcd.density=X - usually set to 240 for Rhodium/Topaz/Blackstone. 210 for Raphael/Diamond.

msmvkeyb_toggle=off - disables virtual keyboard during boot (keep this off, trust me...)

gsensor_axis=2,1,3 - for Rhodiums.

force_cdma=X - 1 for CDMA, 0 for GSM. Default is 0, so if this statement is missing it will use 0.

physkeyboard=

rel_path=X - if you wish to put Android in a different directory other than the root of your SD, modify this statement. I have mine 2 folders deep - if you were looking at it thru Android the path is '/sdcard/Androids/TP2Ref/' - so my rel_path=Androids/TP2Ref.

htc_battery_smem.fake=1 - disables the "Low Battery" warning message below 15%.

acpuclock.oc_freq_khz=XXXXXX - replace the X's with a number. Stock speed cannot be achieved with this statement, so remove it if you want to use the stock 528mhz clock. Otherwise, the numbers go in 19.2khz steps:

pm.sleep_mode=X **Recommended setting is 1** (Thanks to dirtypiratehooker for this info)

   * '4' will do "wait for interrupt", no change in arm11's clock or voltage
   * '3' will do "wait for interrupt and ramp clock", the arm11's clock is lowered to 20MHz instead of 300-500, and voltage is lowered too.
   * '2' will do "app sleep", arm11 is still on, but put into low power mode (registers are still saved)
   * '1' and '0' will totally power off the arm11 (so we have to restore registers and things ourself), don't know the differences between them.