This page tries to serve as a comprehensive listing of known issues and their fixes if available. Keep in mind running the Android operating system on non-supported devices (especially those meant to run Windows Mobile originally) is not really supported, especially since the versions of Android currently available are tailored to the T-Mobile/HTC G1, which has different hardware.

If you need to get to a shell to review log files or some other reason the procedure is as follows.

• Open the keyboard
• Press the FN button
• Press the top left function button
• To exit the shell press the FN button then the top right function button.

This probably means you are running an older ROM/radio that has boot problems. Try upgrading to a newer ROM and use a radio from the 1.65.24.xx or 1.71.xx.xx series. For more information on ROMs, visit the Kaiser ROM development forum on XDA Developers. For more information on radios for the Kaiser, read the Ultimate Radio Thread to find new radios and information about them.

• Make sure you have an up-to-date radio from the 1.65.xx.xx or 1.71.xx.xx series
  • You can find this information out in the About screen of Windows Mobile or from the red text on boot up
  • For more information on radios for the Kaiser, read the Ultimate Radio Thread to find new radios and information about them.
• Make sure you have no PIN code set on your SIM card
  • To find out if you have a PIN/remove it:
    • Open Settings (in Windows Mobile) and tap Phone from the Personal tab
    • Tap the PIN2 or PIN/PIN2 tab (depending on your ROM)
    • Ensure that the check box to require a PIN code to use the phone is unchecked
• If neither of the above solutions works, there seems to be a bug introduced in recent builds that is unresolved. Ensuring you have done the following
  • Upgraded to a recent radio (see above)
  • Removed the PIN2 code from your SIM card (see above)
  • Formatted your SD card as FAT32
  • Deleted all Android related files and re-downloaded and extracted the newest version
• If you still have problems after ensuring you have following all of the above steps, consider asking someone in the IRC channel (#htc-linux @ Freenode)

Please see the Setup/Troubleshoot Data Access page for help configuring your device's internet access and troubleshooting information specific to data setup.

Many Android applications are currently incompatible for a variety of reasons.

If the application appearance seems wrong, (buttons off screen, huge icons, etc.) it is a resolution issue, as the Kaiser's screen is QVGA (320x240px) whereas the HTC Dream/G1's screen is HVGA (480x320px). Many applications are designed specifically for HVGA resolution, and as a result have formatting issues on other devices. See the mddi.width_and_mddi.height of the Boot Options page to learn how to use non-native resolutions on your device.

Many applications simply do not function for unknown reasons. They might attempt to make use of non-functional features on the device, causing them to malfunction and crash. Try the application again in a newer release, as bug fixes and new features are constantly being added.

The recommended setting for pm.sleep_mode is 1. It has also been noted that turning off background syncing will give the normal battery life seen in winmo.

Currently, the way Android works is that there are two files (system.img and data.img) that together make up the equivalent of the internal storage for the Android device. The SD card is then seen as separate. Currently, Android does not write to the internal flash (where Windows Mobile is installed) at all. A limitation of Android is that applications can only be installed to the internal storage. For current purposes, the data.img file (which is where all installed applications and other data is stored) is released with either a 64MB or 128MB file, some of which is already in use. EVEN IF YOUR SD CARD IS 2/4/8GB, YOU ARE STILL LIMITED TO THE SIZE FOR INSTALLING APPLICATIONS! If Android shows you as still having space in the “Internal phone storage” section of the “SD card & phone storage” settings menu, but you continue to receive the warnings, try completely reinstalling Android. If the problem still persists, you probably have a faulty SD card.

From linux or another operating system with ext2fs tools and dd do:

 dd if=/dev/zero bs=1M count=1234567890 >> data.img 

but replace 1234567890 with how many megabytes you want to ADD to data.img.

For example, I wanted a 256MB data.img, so I ran:

 dd if=/dev/zero bs=1M count=192 >> data.img 

Then do a simple:

e2fsck -f data.img
resize2fs data.img
e2fsck -f data.img

and copy back to your SD card. You should have as much space as you want.

Make sure that you have a “cache” folder on your SD card. If it doesn't exist, create it and reboot Android, then try again.

The current builds of Android are from the 1.1 SDK. Because you would not normally have a real GPS when testing with an SDK, Android includes a default GPS demo mode of a car driving around on some California highways. This is happening because GPS has not yet been implemented on your device. Check the Port Status page for more information.

In Android, open the Settings application, and go to the Date & time menu option. Uncheck Automatic if checked, and set your date and time manually - making sure to set the proper time zone in the process. This will change your system clock, resulting in the incorrect time being displayed in Windows Mobile. To prevent this, set Windows Mobile to the “Visiting” time zone setting with London (GMT+0) as the location before booting Android, and then change it back when you are in Windows Mobile, or use an application such as TimeSyncTZ to fix your time in Windows Mobile.

Check the board-kaiser-keypad.atttilt section of the Boot Options page for information on how to configure the keyboard on your AT&T Tilt or TyTN II.

This issue is resolved on the newest builds of Android. Check the board-htckaiser.panel_type section of the Boot Options page for information on how to specify your panel type to fix the issue.

When you run Harnet, if you get an error that says “Failed to load file \Storage Card\zImage” or something like that; you have one of two problems.

1. The file is not named correctly; this is commen when you use your phone to download a new file, like zImage. You phone may try and give it an extension, and zImage does not have one. To fix this (mainly for the zImage error), use Total Commander; it will display the entire file name and extension; I just downloaded one and when my phone downloaded and saved it, it was named “zImage.” not “zImage”; using total commander I deleted the period at the end and now it works.

or

2. The file is missing, or no located where the default.txt file says it is located. 1st; Check and make sure the file is on the root of your SD card and has a normal name (when you download the file it normally has a wierd name and needs to be renamed).

2nd; Make sure your default.txt says it is located normally. When I used to jump between different base files, I kept editing the default.txt file and left the file named wierd; well I forgot and for a while was never able to get harnet to run. Once I renamed the file to a normal name and set the default.txt to the normal name, it worked.

Make sure you are using a zImage that has the audio fix

This happens only for some and not on every build. Try using the 10/23/09 zImage found on the Kaiser builds page or try using a 320×480 resolution

1st Check out XDA here Pre-Built Builds ION HERO DONUTand FAQ's and here Google Android and Linux for KAISER!!

If you found other issue that is not listed here, please submit it in a bugtracker.