I'd like to add a couple things that have caused RMA / device exchanges or a whole lot of customer support calls that have gone on for hours when this stuff was not necessary at all...
(1) Customers report the touch response of their Pocket PC 5.0 or Professional 6.0 device is so impossibly bad, they can no longer even get to Start > Settings > System tab > Screen and do the alignment utility. They hard reset the device, and the screen response to tapping is still horrendous. Technician's think their only option is to exhange the device.
The fix? At least on some models (ex. HTC Kaiser / TyTn II and cousin models) you can press the Internet Explorer launch button at the same time as the center button of the 5-way navigation pad. This short cut pops you into the screen calibration. Then the customer absolutely must use a stylus precisely, not tap the calibration targets with a big fat inaccurate thumb.
(2) Customers are driven mad when they find that their contacts in the device won't synchronize to their computer's Outlook. They don't see any specific error messages either, it's like ActiveSync is miffed or something. They phone tech support and may go through endless call backs agonizing over this symptom.
The reason? Apple iTunes has a Contacts and Appointments component that is an Outlook COM add-in on Windows XP and Vista computers. Those iTunes conduits may prevent ActiveSync or WMDC from communicating contacts and calendar data to Outlook. You have to go into Outlook's Tools > Options > Advanced Options (or in Vista, Tools > Trust Center > Add-ins) to knock out the pesky iTunes conduit.
(3) Bluetooth headsets are a constant source of tech support nightmares for Windows Mobile users. Regretably, there's no single easy fix. Often the user ends up blaming the device, not the Bluetooth headset (and they may have tried a couple headsets) -- so they demand a replacement of the Windows Mobile device on the theory that it's Bluetooth radio is somehow weak or defective.
Sometimes the Bluetooth headset is not getting initialized correctly, there's usually a button that has to be pressed for a few moments and a blinking light, etc. but the process varies depending on the manufacturer.
Past that simple "user error" situation, there are some 2007 models of Windows Mobile 5.0 devices that don't support the Extended Synchronous Connection Oriented (eSCO) Bluetooth profile used by some Bluetooth headsets. You just won't be able to get these to play together nicely, there will be problems.
Another thing is that some device models in combination with some Bluetooth headsets have quirks that surprise users -- the behavior goes against their expectations so they assume somehting is broken. For example, you may find you cannot initiate a 3-way conference call from the Bluetooth headset, even though it is the control interface for regular calls. Or you may find that if you answer a call by touching the screen of the device, the Bluetooth headset gets upset and won't let you do the audio of the phone call through the headset. Or you try to, on the fly, transfer an active phone call from the device to the Bluetooth headset, and it won't take over the audio. All these symptoms are "features limitations" -- not out and out malfunctions.
Lastly on Bluetooth headsets: complaints of low audio volume. This is often due to low battery on the headset or merely weak cell phone signal inside a building (i.e. enough signal to make a call, but amplification is challenged). But often the quality of the (older?) Bluetooth headset is just not good. If you do Internet search engine queries such as these, you can get an impression of what other users have experienced with a given headset model:
- <headset model> low volume -battery
- <headset model> not hear
- <headset model> audio quality
-----
Anyway, those are three pain points I've seen. Obviously this forum is not like "Windows Moble Owner's" forum where detailed troubleshooting is done, but I thought I'd mention some heavy hitters that I have seen for some time.