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.

Difference between revisions of "FAQ"

From The XDAndroid Project
Jump to navigation Jump to search
[checked revision][pending revision]
m
 
(43 intermediate revisions by 5 users not shown)
Line 7: Line 7:
 
== How can I tell what device I have? RAPH?  RHOD? ==
 
== How can I tell what device I have? RAPH?  RHOD? ==
  
When you go looking thru the STARTUPS folder of a build, the list might be daunting - do I have a RAPH?  RHOD?  DIAM?
+
When you go looking thru the STARTUPS folder of a build, the list might be daunting - do I have a RAPH (a.k.a. [[Wikipedia:HTC Touch Pro|HTC Touch Pro]])?  RHOD (a.k.a. [[Wikipedia:HTC Touch Pro2|HTC Touch Pro2]])?  DIAM (a.k.a. [[Wikipedia:HTC Touch Diamond|HTC Touch Diamond]])?
  
If you are confused, the easiest/quickest way to settle it is to pull the battery on the device - shut it down completely first, if you can.  Do not look on the battery itself, but on the phone itself - on the sticker it should say what device you have - 4 letters and 3 numbers.  Above the IMEI bar code...
+
If you are confused, the easiest/quickest way to settle it is to pull the battery on the device; shut it down completely first, if you can.  Do not look on the battery itself, but on the phone itself. On the sticker it should say what device you have — 4 letters and 3 numbers, above the [[Wikipedia:IMEI|IMEI]] bar code... It's the last part of the FCC ID (in gray)
  
RHOD100
+
RHOD100
 
or
 
or
DIAM500
+
DIAM500
 
etc...
 
etc...
  
  
 
{| cellpadding="20" cellspacing="0"
 
{| cellpadding="20" cellspacing="0"
 +
|Devices with physical keyboards:
 +
|-
 
|Rhodium: [[File:599px-HTC_Rhodium.jpg|thumb]]
 
|Rhodium: [[File:599px-HTC_Rhodium.jpg|thumb]]
 
|Raphael: [[File:HTC_Raphael.jpg‎|160px|thumb]]
 
|Raphael: [[File:HTC_Raphael.jpg‎|160px|thumb]]
 
|Kovsky: [[File:Htckovs100yk8.jpg‎|150px|thumb]]
 
|Kovsky: [[File:Htckovs100yk8.jpg‎|150px|thumb]]
 +
|-
 +
|Devices without physical keyboards:
 
|-
 
|-
 
|Topaz: [[File:741px-HTC_Topaz.jpg|230px|thumb]]
 
|Topaz: [[File:741px-HTC_Topaz.jpg|230px|thumb]]
Line 29: Line 33:
 
== How do I overclock? ==
 
== How do I overclock? ==
  
Place this command in your <tt>startup.txt</tt> - <tt>acpuclock.oc_freq_khz=614400</tt> for 614.4mhz.  Choose multiples of 19.2mhz, or the system will default to the closest multiple for you (for example if you put in 700000 it will really be ~692mhz instead of 700mhz.)
+
Place this command in your <tt>[[startup.txt]]</tt>: <tt>acpuclock.oc_freq_khz=614400</tt> for 614.4&nbsp;MHz.  Choose multiples of 19.2&nbsp;MHz, or the system will default to the closest multiple for you (for example if you put in 700000 it will really be ~692&nbsp;MHz instead of 700&nbsp;MHz).  (See also [[Kernel boot command-line parameters]].)
 +
 
 +
The 'max' you can overclock varies by device, and some devices can be pushed farther than others.  It seems best to establish what max you can hit in WinMo, and apply that to Android (disable OC in WinMo before booting Android...)  Anything over 700 seems risky, although some RHODs run up in the 800+ range without issue.  If you're having problems, ramp this value down first, if not completely disabling it before moving on to other troubleshooting steps.
 +
 
 +
== HaRET failing to boot? ==
 +
:''See also [[HaRET]].''
 +
# Don't overclock WinMo.
 +
# Look over the directions in the build thread again.  Make sure you have all the necessary files, in the correct location.
 +
# If it's still failing to boot, format your SD card using the [http://www.eocfiles.com/bdc86eb1ed2989c30dcd1902e84939ae/bootdisks/SP27608.exe HP Tool] (for Linux, whatever tool seems to do the job &mdash; it's just the built-in Windows/WinMo format utilities that seem broken...)
 +
 
 +
== How can I update? ==
 +
 
 +
Well if you're adventurous and want to try upgraded the components of the build, see the [[Incremental Updates]] page.
  
 
== How do I migrate my contacts from Windows Mobile? ==
 
== How do I migrate my contacts from Windows Mobile? ==
Line 43: Line 59:
 
== Do I have to run this at the root of my SD? ==
 
== Do I have to run this at the root of my SD? ==
  
No, you can set a rel_path value in the <tt>startup.txt</tt> file.
+
No, you can set a rel_path value in the <tt>[[startup.txt]]</tt> file.
 +
 
 +
I have mine two folders deep; from within Android it would be /sdcard/Androids/TP2Ref.  My <code>rel_path=Androids/TP2Ref</code>.  This goes between the quotes, after <code>set cmdline</code>.
  
I have mine two folders deep - from within Android it would be /sdcard/Androids/TP2RefMy rel_path=Androids/TP2Ref. This goes between the quotes, after set cmdline.
+
== Why can Android not see my SD card?  It says "No SD inserted"!! ==
 +
 
 +
Well, the theory is the built-in Windows and WinMo format utilities are broken.  Backup all the data on the card, do a full format, FAT32 on the card using the [http://www.eocfiles.com/bdc86eb1ed2989c30dcd1902e84939ae/bootdisks/SP27608.exe HP Tool]Restore all the data on the card, and apps within Android should now see the card.
 +
It seems that this error occurs when there's no partition table on the SD card (even if the card is FAT32 formated). You can reformat it with Mac OS X Disk Utility. As long as you put a partition table (MBR format), Android will be able to read your FAT32 formated partition.
  
 
== How do I fix a non-functioning or miscalibrated touchscreen? ==
 
== How do I fix a non-functioning or miscalibrated touchscreen? ==
  
Delete the file <tt>ts-calibration</tt> from the same directory in which you run <tt>haret.exe</tt> to boot Android. During the next boot, the device will prompt for touchscreen re-calibration.
+
Delete the file <tt>ts-calibration</tt> from the same directory in which you run <tt>[[HaRET|haret.exe]]</tt> to boot Android. During the next boot, the device will prompt for touchscreen re-calibration.
  
If you have any issues calibrating, you might need to go back to an older kernel.  The .35 framebuffer commit seemed to cause this issue, so you can go to a kernel before it - [http://zimages.googlecode.com/files/htc-msm-linux-20101204_010857-package.tar.bz2 1231] for example works.
+
If you have any issues calibrating, you might need to go back to an older kernel.  The .35 framebuffer commit seemed to cause this issue, so you can go to a kernel before it; [http://zimages.googlecode.com/files/htc-msm-linux-20101204_010857-package.tar.bz2 1231] for example works.
  
 
== How do I prevent clock drift? ==
 
== How do I prevent clock drift? ==
  
XDAndroid currently suffers from two types of system clock drift. Gradual clock drifting may occur. To alleviate this, download ClockSync from the Andriod Market. An hourly synchronization setting is recommended.
+
XDAndroid currently suffers from two types of system clock drift. Gradual clock drifting may occur. To alleviate this, download [https://market.android.com/details?id=ru.org.amip.ClockSync ClockSync] from the Andriod Market. An hourly synchronization setting is recommended.
 +
 
 +
Additionally, the clock may be skewed by a matter of hours when rebooting back into Windows Mobile. When this occurs, the offset will likely be the same as the local timezone's offset from [[Wikipedia:UTC|UTC]] (for instance, if in Eastern Standard Time, the clock will be five hours ahead when rebooting to Windows Mobile). This is due to time handling differences between Windows Mobile and the Linux kernel. It is recommended that Windows Mobile be configured to synchronize the clock automatically. Otherwise, a third-party application may be needed to maintain the clock properly.
  
Additionally, the clock may be skewed by a matter of hours when rebooting back into Windows Mobile. When this occurs, the offset will likely be the same as the local timezone's offset from UTC (for instance, if in Eastern Standard Time, the clock will be five hours ahead when rebooting to Windows Mobile). This is due to time handling differences between Windows Mobile and the Linux kernel. It is recommended that Windows Mobile be configured to synchronize the clock automatically. Otherwise, a third-party application may be needed to maintain the clock properly.
+
== Why does GPS lock take forever? ==
  
== How can I dial out with Google Voice? ==
+
Basically our Android port doesn't support any advanced GPS features like warm injection.  Read more [http://forum.xda-developers.com/showthread.php?t=969761 here].
  
Some users have issues dialing outbound calls through Google Voice. If you experience this, add the following to your ''cmdline'' in <tt>startup.txt</tt>: <tt>north_am_dialing=1</tt>
+
We've noticed that if you use QuickGPS in WinMo (or even get a GPS lock in WinMo) prior to booting Android, the GPS lock times in Android are greatly reduced.
  
 
== Which ''cmdline'' arguments are available in <tt>startup.txt</tt>? ==
 
== Which ''cmdline'' arguments are available in <tt>startup.txt</tt>? ==
  
See [[Kernel boot command-line parameters]]
+
See [[Kernel boot command-line parameters]].  Note - some of these commands are outdated and deprecated (will be ignored).
 +
 
 +
== WiFi doesn't work at all? ==
  
== How can I tether (wifi/USB)? ==
+
If you upgraded your kernel (see [[Incremental Updates]]) then make sure the modules-xxxx.tar.gz file matches the kernel (zImage).  Sometimes the modules don't unpack correctly either, if you suspect this is the case (you know you've matched the zImage to the modules correctly) then try [http://forum.xda-developers.com/showpost.php?p=16616048&postcount=70 this trick] (thanks Starfox).
  
USB tethering doesn't work natively yet, but there is an app on the market called "EasyTether". Free, but blocks HTTPS on the free version (note: adb is needed, see [[#How-To ADB]]
+
If you have tried to use WiFi and every possible fix suggested fails - and the error states "Unable to scan" the issue probably lies in the <tt>wifi-nvram.txt</tt> file - basically Android doesn't know the MAC address of your WLAN card.
  
Wifi tethering *should* work out of the box (Settings -> Tethering & Portable Hotspot).  If it doesn't there's two options as far as I'm concerned - [http://southcape.org/2010/03/18/xdandroid-eclair-wifi-tethering/ XDAndroid Wifi Tether] or 'Barnacle' Wifi Tethering (on the Market).
+
See [http://forum.xda-developers.com/showpost.php?p=9187263&postcount=80 F22's post] on how to workaround this issue.  Not everyone needs this fix, and we haven't determined why some do and others do not...  Unfortunately you have to cp this file.  You can try to add the cp line in your froyo.user.conf, but all other methods (bind mount, symlink) seem to fail - so don't bother.
  
== Why does Google Goggles Fail? ==
+
== How can I tether (WiFi/USB)? ==
  
IPV6 is the reason, and despite popular belief our builds do support it, they just don't have it enabled.
+
USB Tethering should "just work" now.  Make sure it is enabled in Settings &rarr; Wireless & Networks &rarr; Tethering & portable hotspot &rarr; USB Tethering.
  
To enable it once, 'modprobe ipv6' will enable it for that sessionTo enable it on boot, add that line to your user.conf file, in the 'CustomCommands' section.
+
WiFi tethering ''should'' work out of the box (Settings &rarr; Wireless & Networks &rarr; Tethering & Portable Hotspot)If it doesn't there are a couple of options: [http://southcape.org/2010/03/18/xdandroid-eclair-wifi-tethering/ XDAndroid Wifi Tether] or [https://market.android.com/details?id=net.szym.barnacle Barnacle Wifi Tether] (on the Market).  Neither of these solutions use a true AP, only adhoc.  If your device requires a true AP (not adhoc!!) then the built-in wireless tethering solution is the only option.
  
 
== What is ADB / How-To ADB ==
 
== What is ADB / How-To ADB ==
Line 83: Line 108:
 
ADB = Android Debugging Bridge.  [http://developer.android.com/guide/developing/tools/adb.html Official Google ADB Page]
 
ADB = Android Debugging Bridge.  [http://developer.android.com/guide/developing/tools/adb.html Official Google ADB Page]
  
It also kinda works like USB Mass Storage using an app called Droid Explorer.
+
It also kinda works like [[Wikipedia:USB Mass Storage|USB Mass Storage]] using a Windows app called [http://de.codeplex.com/ Droid Explorer].
  
 
In addition, you can use it to get a console connection into the phone.
 
In addition, you can use it to get a console connection into the phone.
  
If you want to pull logs, the most popular kind are dmesg, logcat and logcat -b radio.
+
[[Logs]] can be pulled with adb.
  
adb shell dmesg > dmesg.txt will dump a dmesg log (kernel traces) to a file, dmesg.txt on your computer - note this command will drop dmesg.txt where ever you are currently running the command from - watch the path you are at!
+
There are many other ADB functions which I will not address here, please see the official ADB link above.
  
adb logcat > logcat.txt will dump a logcat file (userland traces).
+
[http://forum.xda-developers.com/showthread.php?t=849718 Windows How-To]
  
adb logcat -b radio > logcat_radio.txt will dump a logcat -b radio file (logcat specific to the radio/RIL).
+
[http://forum.xda-developers.com/showthread.php?p=11823740 Linux (Ubuntu) How-To]
  
You can also run these on the phone directly - note, dmesg runs and ends while the two logcat commands run continuously.  You will have to break them (CTRL-C) to get the log to quit and give you back a prompt.  There are many other ADB functions which I will not address here, please see the official ADB link above.
+
[http://forum.xda-developers.com/showthread.php?t=1099481 Further Reading] (thanks slycker)
 
 
[http://forum.xda-developers.com/showthread.php?t=849718 Windows How-To]
 
 
 
[http://forum.xda-developers.com/showthread.php?p=11823740#post11823740 Linux (Ubuntu) How-To]
 
  
 
== What is an APK / How to install apps/programs ==
 
== What is an APK / How to install apps/programs ==
Line 105: Line 126:
 
APK = Android application package file [http://developer.android.com/guide/appendix/glossary.html from the Android Glossary]
 
APK = Android application package file [http://developer.android.com/guide/appendix/glossary.html from the Android Glossary]
  
Of course you can install apps thru the Market, but if you wish to install apps manually using an APK file, there is a folder - <tt>AndroidApps</tt> off of where you run <tt>haret.exe</tt> from.  Simply place the APK inside this folder, and on the next boot the APK will be installed on the system.  Notice there are folders within this main <tt>AndroidApps</tt> folder, do not place any APKs inside these folders - they are there for you to pick and choose some apps that some may find useful, but we didn't want to automatically install them for the sake of having a clean build.
+
Of course you can install apps through the Market, but if you wish to install apps manually using an APK file, there is a folder &mdash; <tt>AndroidApps</tt> &mdash; off of where you run <tt>[[HaRET|haret.exe]]</tt> from.  Simply place the APK inside this folder, and on the next boot the APK will be installed on <span class="plainlinks">[http://www.proposable.com <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">proposal software</span>] the system.  Notice there are folders within this main <tt>AndroidApps</tt> folder. Do not place any APKs inside these folders. They are there for you to pick and choose some apps that some may find useful, but we didn't want to automatically install them for the sake of having a clean build.
  
 
There are some other methods for installing APKs, which pertain to native Android devices and are outside of the scope of this FAQ.
 
There are some other methods for installing APKs, which pertain to native Android devices and are outside of the scope of this FAQ.
  
=HTC Touch Pro 2/Tilt 2 (Rhodium)=
+
== How can I theme the build? ==
  
== Which features are not currently supported? ==
+
Entropy512 has created [http://forum.xda-developers.com/showpost.php?p=14514109&postcount=1516 a post] on this subject.
  
* BT - pairs but doesn't pass any audio/data
+
== Can I store apps on the SD card / I'm out of space!! ==
* 3.5mm jack - RHOD400/500 has this plug, and it doesn't work at the moment
 
* USB - only works for adb (debugging)
 
* Button LEDs - 4-button lights will be stuck on (at the bottom of the phone) if you boot Android with them on in WinMo.
 
  
For a more complete list, please see [http://forum.ppcgeeks.com/tp2-android-development/132515-read-before-you-post-something-isnt-working-known-issues-affecting-all-builds-2-9-a.html this PPC-Geeks forum thread] (thanks manekineko)
+
Well first of all, everything is on the SD card - so the apps are already on your SD card.  Please don't use app2sd for this reason... it won't work.  However, instead of being directly on the SD they're stored in this <tt>data.img</tt> file (along with every other user-related thing like SMS's, phone call log, etc etc).  So if you go to Settings -> SD Card & Phone Storage -> "Internal phone storage" is basically this <tt>data.img</tt> file.  There is a pretty slick app that allows you to expand the size of this file - just make sure you have the space on your SD!  [http://forum.xda-developers.com/showthread.php?t=824154 Data Expansion Tool]
  
== Why is the device's notification LED always orange or green? ==
+
== What about MMS? ==
  
The notification LED indicates sleep state (orange LED indicates device is awake; green LED indicates device is in sleep mode). If the LED is always orange, the phone isn't properly sleeping.  Make sure GPS is disabled, as this will prevent the phone from sleeping.
+
With the new RIL & MMS work by hyc (Sprint was especially broken...) MMS is now possible in both directions! You have to get [[Version FRX07]] and set your APN according to [[MMS]].
  
== How do I connect to WiFi networks with WEP encryption? ==
+
=HTC Touch Pro 2/Tilt 2 (Rhodium)=
  
There is currently [http://bugs.xdandroid.com/show_bug.cgi?id=90 an issue with WiFi access points which use WEP encryption]. The system currently does not support WEP out of the box, but a Market app called '''wifi-ace''' will work around this issue until it is resolved by XDAndroid.
+
== Which features are not currently supported? ==
  
== Why do I not have service? ==
+
* [[Wikipedia:Bluetooth|Bluetooth]] - Fix is in the works.  See [http://forum.xda-developers.com/showthread.php?t=1076884 this thread] for more information on how to manually setup the fix.  Not easy!  Still a WIP as well.
 +
* USB - everything except USB Mass Storage should work in respect to USB.  You can use Droid Explorer (Windows app) which leverages ADB to sort-of "fake" USB mass storage.
  
The main reason for not having service would be the force_cdma setting in the <tt>startup.txt</tt> file.  If you are using the phone as a GSM device, force_cdma=0 needs to be present in your cmdline with no other force_cdma statements!  This is the default, so if you do not have a force_cdma= statement, the default value is 0. If you are using the device as CDMA, this needs to =1.  The phone cannot be used as both currently - one or the other, choose wisely.
+
For a more complete list, please see [http://forum.ppcgeeks.com/tp2-android-development/132515-read-before-you-post-something-isnt-working-known-issues-affecting-all-builds-2-9-a.html this PPC-Geeks forum thread] (thanks manekineko)
  
== The power and end button do the same thing, what gives? ==
+
== How do I connect to WiFi networks with WEP encryption? ==
 
 
In some of the older builds, power was mapped as home.  There was a decision that was made (very controversial I might add) to remap power to be power.  Problem is, the end key is also power by default.  There's a couple of options:
 
  
* F22 has been maintaining a modified rootfs ([http://forum.xda-developers.com/showthread.php?t=935710 thread]) file that allows you to change all sorts of button-mapping related things.  Hopefully it'll get committed soon!  (Hint hint F22...)
+
There is currently [http://bugs.xdandroid.com/show_bug.cgi?id=90 an issue with WiFi access points which use WEP encryption]. The system currently does not support WEP out of the box, but a Market app called '''[http://code.google.com/p/android-wifi-ace/ wifi-ace]''' will work around this issue until it is resolved by XDAndroid.
* Alternatively, and perhaps slightly easier - in the app Spare Parts (on the Market if your build doesn't include it) you can change the "End Key Behavior" so you can make it act as the home button - note, this only effects short press, not long press.
 

Latest revision as of 11:36, 28 November 2011


General FAQs

How can I tell what device I have? RAPH? RHOD?

When you go looking thru the STARTUPS folder of a build, the list might be daunting - do I have a RAPH (a.k.a. HTC Touch Pro)? RHOD (a.k.a. HTC Touch Pro2)? DIAM (a.k.a. HTC Touch Diamond)?

If you are confused, the easiest/quickest way to settle it is to pull the battery on the device; shut it down completely first, if you can. Do not look on the battery itself, but on the phone itself. On the sticker it should say what device you have — 4 letters and 3 numbers, above the IMEI bar code... It's the last part of the FCC ID (in gray)

RHOD100

or

DIAM500

etc...


Devices with physical keyboards:
Rhodium:
599px-HTC Rhodium.jpg
Raphael:
HTC Raphael.jpg
Kovsky:
Htckovs100yk8.jpg
Devices without physical keyboards:
Topaz:
741px-HTC Topaz.jpg
Blackstone:
HTC Blackstone.jpg
Diamond:
HTC Diamond.jpg

How do I overclock?

Place this command in your startup.txt: acpuclock.oc_freq_khz=614400 for 614.4 MHz. Choose multiples of 19.2 MHz, or the system will default to the closest multiple for you (for example if you put in 700000 it will really be ~692 MHz instead of 700 MHz). (See also Kernel boot command-line parameters.)

The 'max' you can overclock varies by device, and some devices can be pushed farther than others. It seems best to establish what max you can hit in WinMo, and apply that to Android (disable OC in WinMo before booting Android...) Anything over 700 seems risky, although some RHODs run up in the 800+ range without issue. If you're having problems, ramp this value down first, if not completely disabling it before moving on to other troubleshooting steps.

HaRET failing to boot?

See also HaRET.
  1. Don't overclock WinMo.
  2. Look over the directions in the build thread again. Make sure you have all the necessary files, in the correct location.
  3. If it's still failing to boot, format your SD card using the HP Tool (for Linux, whatever tool seems to do the job — it's just the built-in Windows/WinMo format utilities that seem broken...)

How can I update?

Well if you're adventurous and want to try upgraded the components of the build, see the Incremental Updates page.

How do I migrate my contacts from Windows Mobile?

How to sync WinMo with Google

In Android, simply add a Google account to sync normally. The account will eventually synchronize the contacts that were added to it by Windows Mobile as directed in the above page. Changes and additions to the contact list will be continuously synchronized between the two operating systems.

How much space do I need on my Storage Card?

The absolute-minimum supported card size is 512MB. For reference, a complete XDAndroid system will usually occupy about 480MB of space (including a 256MB data.img file which appears after initial installation).

Do I have to run this at the root of my SD?

No, you can set a rel_path value in the startup.txt file.

I have mine two folders deep; from within Android it would be /sdcard/Androids/TP2Ref. My rel_path=Androids/TP2Ref. This goes between the quotes, after set cmdline.

Why can Android not see my SD card? It says "No SD inserted"!!

Well, the theory is the built-in Windows and WinMo format utilities are broken. Backup all the data on the card, do a full format, FAT32 on the card using the HP Tool. Restore all the data on the card, and apps within Android should now see the card. It seems that this error occurs when there's no partition table on the SD card (even if the card is FAT32 formated). You can reformat it with Mac OS X Disk Utility. As long as you put a partition table (MBR format), Android will be able to read your FAT32 formated partition.

How do I fix a non-functioning or miscalibrated touchscreen?

Delete the file ts-calibration from the same directory in which you run haret.exe to boot Android. During the next boot, the device will prompt for touchscreen re-calibration.

If you have any issues calibrating, you might need to go back to an older kernel. The .35 framebuffer commit seemed to cause this issue, so you can go to a kernel before it; 1231 for example works.

How do I prevent clock drift?

XDAndroid currently suffers from two types of system clock drift. Gradual clock drifting may occur. To alleviate this, download ClockSync from the Andriod Market. An hourly synchronization setting is recommended.

Additionally, the clock may be skewed by a matter of hours when rebooting back into Windows Mobile. When this occurs, the offset will likely be the same as the local timezone's offset from UTC (for instance, if in Eastern Standard Time, the clock will be five hours ahead when rebooting to Windows Mobile). This is due to time handling differences between Windows Mobile and the Linux kernel. It is recommended that Windows Mobile be configured to synchronize the clock automatically. Otherwise, a third-party application may be needed to maintain the clock properly.

Why does GPS lock take forever?

Basically our Android port doesn't support any advanced GPS features like warm injection. Read more here.

We've noticed that if you use QuickGPS in WinMo (or even get a GPS lock in WinMo) prior to booting Android, the GPS lock times in Android are greatly reduced.

Which cmdline arguments are available in startup.txt?

See Kernel boot command-line parameters. Note - some of these commands are outdated and deprecated (will be ignored).

WiFi doesn't work at all?

If you upgraded your kernel (see Incremental Updates) then make sure the modules-xxxx.tar.gz file matches the kernel (zImage). Sometimes the modules don't unpack correctly either, if you suspect this is the case (you know you've matched the zImage to the modules correctly) then try this trick (thanks Starfox).

If you have tried to use WiFi and every possible fix suggested fails - and the error states "Unable to scan" the issue probably lies in the wifi-nvram.txt file - basically Android doesn't know the MAC address of your WLAN card.

See F22's post on how to workaround this issue. Not everyone needs this fix, and we haven't determined why some do and others do not... Unfortunately you have to cp this file. You can try to add the cp line in your froyo.user.conf, but all other methods (bind mount, symlink) seem to fail - so don't bother.

How can I tether (WiFi/USB)?

USB Tethering should "just work" now. Make sure it is enabled in Settings → Wireless & Networks → Tethering & portable hotspot → USB Tethering.

WiFi tethering should work out of the box (Settings → Wireless & Networks → Tethering & Portable Hotspot). If it doesn't there are a couple of options: XDAndroid Wifi Tether or Barnacle Wifi Tether (on the Market). Neither of these solutions use a true AP, only adhoc. If your device requires a true AP (not adhoc!!) then the built-in wireless tethering solution is the only option.

What is ADB / How-To ADB

ADB = Android Debugging Bridge. Official Google ADB Page

It also kinda works like USB Mass Storage using a Windows app called Droid Explorer.

In addition, you can use it to get a console connection into the phone.

Logs can be pulled with adb.

There are many other ADB functions which I will not address here, please see the official ADB link above.

Windows How-To

Linux (Ubuntu) How-To

Further Reading (thanks slycker)

What is an APK / How to install apps/programs

APK = Android application package file from the Android Glossary

Of course you can install apps through the Market, but if you wish to install apps manually using an APK file, there is a folder — AndroidApps — off of where you run haret.exe from. Simply place the APK inside this folder, and on the next boot the APK will be installed on proposal software the system. Notice there are folders within this main AndroidApps folder. Do not place any APKs inside these folders. They are there for you to pick and choose some apps that some may find useful, but we didn't want to automatically install them for the sake of having a clean build.

There are some other methods for installing APKs, which pertain to native Android devices and are outside of the scope of this FAQ.

How can I theme the build?

Entropy512 has created a post on this subject.

Can I store apps on the SD card / I'm out of space!!

Well first of all, everything is on the SD card - so the apps are already on your SD card. Please don't use app2sd for this reason... it won't work. However, instead of being directly on the SD they're stored in this data.img file (along with every other user-related thing like SMS's, phone call log, etc etc). So if you go to Settings -> SD Card & Phone Storage -> "Internal phone storage" is basically this data.img file. There is a pretty slick app that allows you to expand the size of this file - just make sure you have the space on your SD! Data Expansion Tool

What about MMS?

With the new RIL & MMS work by hyc (Sprint was especially broken...) MMS is now possible in both directions! You have to get Version FRX07 and set your APN according to MMS.

HTC Touch Pro 2/Tilt 2 (Rhodium)

Which features are not currently supported?

  • Bluetooth - Fix is in the works. See this thread for more information on how to manually setup the fix. Not easy! Still a WIP as well.
  • USB - everything except USB Mass Storage should work in respect to USB. You can use Droid Explorer (Windows app) which leverages ADB to sort-of "fake" USB mass storage.

For a more complete list, please see this PPC-Geeks forum thread (thanks manekineko)

How do I connect to WiFi networks with WEP encryption?

There is currently an issue with WiFi access points which use WEP encryption. The system currently does not support WEP out of the box, but a Market app called wifi-ace will work around this issue until it is resolved by XDAndroid.