Troubleshooting for Voice Command

When I try to install, I see the message “Voice Command version 1.0, 1.01 or 1.5 must be installed”. Voice Command 1.0, 1.01 or 1.5 must be installed on your desktop PC before you can upgrade. You can confirm by going to Start->Control Panel->Add Remove Programs on your desktop PC. If you do not see Voice Command in the list of programs, you cannot use the upgrader to upgrade to version 1.6.

Try the following: Install Voice Command 1.0, 1.01 or 1.5 to your desktop PC and uninstall Voice Command from your mobile device.

Try the following: Make sure that you have at least 8MB of device storage available prior to installing. After installing, Voice Command will consume a total of 4MB of device storage. Make sure that you install to main memory only and not to the storage card. Make sure you are using ActiveSync 4.0 or greater and are installing to a Windows Mobile 5.0 device or greater.

You must soft reset your phone after you’ve installed Voice Command before the Bluetooth headset will work for initiating Voice Commands.

If this doesn’t resolve the problem, it is likely that you are trying to use the Bluetooth functionality on an unsupported device. Voice Command’s Bluetooth functionality will work on devices that include the Microsoft Bluetooth stack, that conform to Microsoft’s guidelines for Bluetooth driver implementation, and for devices that have the correct hardware implementation necessary to route system audio through the Bluetooth headset.

If you have a device that does not include the Microsoft Bluetooth stack, you may be able to route all system audio through the headset using the Bluetooth stack vendor’s Bluetooth control panel. If you can, you can use Voice Command over Bluetooth by pressing a hardware button on the device and conducting the interaction via the headset. The Bluetooth audio routing options will not work properly on devices that do not use the Microsoft Bluetooth stack. You should select “Announce notifications using Bluetooth hands free if available” on these devices.

Bluetooth audio routing is working except for Caller ID

If you have a Windows Mobile 5.0 device prior to build 15097.3.0.0, you will not be able to receive spoken caller ID notifications through the Bluetooth headset. Windows Mobile with build number the same or higher than build 15097.3.0.0 includes support for Inband ringtone which is the mechanism that Voice Command uses for announcing caller ID information while the phone is ringing.

To view the build number for your device, you will first need to know if you have a Windows Mobile device with Pocket PC or smartphone software. An easy way to tell is to look at the Today screen and find the Windows Mobile flag. If it is in the top left, you have a Pocket PC. If it is in the bottom left, you have a smartphone.

For Pocket PC or Pocket PC Phone device:
Start Menu->Settings->System(tab)->About(icon)

For Smartphone based device:
Home->Start Menu->Settings->About

Some devices require a reset before Voice Command will operate.

Voice Command is temporarily disabled during phone calls.

Contacts without phone numbers cannot be called. Make sure that this contact has at least one phone number. Sometimes contacts are filed as a different name. Make sure that the name displayed in the contact list is the same as the first, middle, last name of the contact. Sometimes names have pronunciations that are not apparent to Voice Command. Try adding an alternate spelling to the “nickname” field. Make sure that you’re speaking the command correctly.

Try the following: Change your notification routing settings to "Announce notifications using Bluetooth hands free if available".

If you want appointments announced during meetings, make sure that the "Only during free time" check box is cleared.

Store all your tracks in one folder for fastest access to media.

If your media files lacks track information, Voice Command may not find them. Add track information with Windows Media Player on your desktop. You can also improve recognition by tweaking the track metadata with Windows Media Player.

Both utilities and contact lookup share the verb 'show' and sometimes a program is recognized instead of a contact.