Earlier this week I upgraded my Dash from Windows Mobile 5 to Windows Mobile 6. The flash went flawlessly and I didn’t have to install as many apps to get going, but I did mourn the fact that while Voice Command 1.6 would let me voice dial, I couldn’t do it from my Bluetooth headset – just from the handset. After some asking around for help, I’ve been handed the following workaround and it works for me!
The only remaining hiccup that I can’t seem to fix is that of Outlook Reminders: they fire visibly and they vibrate but there’s never any sound for the alert. When I get a new email message I get sound – even if I use the same file for reminder alerts, it just won’t fire. An odd yet minor annoyance.
Read on for the registry fix for Voice Command 1.6 on the T-Mobile Dash, running Windows Mobile 6.
Open your device-side registry editor and navigate to the following key:
On this key, look for the value BTAGExtModule and change the string there to be: \windows\vcbthag.dll (and write down the existing one if you ever have to roll back to the original value).
Now, reboot your phone. Once it’s done booting, you should be good to go! If it doesn’t work, press and hold the home key on your handset to make sure Voice Command is up and running.
This worked for me, as is: once I rebooted I hit the “button” on my Samsung WEP200 headset. Heard the earset go *Boop* and then heard the Voice Command *bebaboop* that tells me to talk now.
— Of course as this is a registry change to your phone, please use it at your own risk and don’t yell at me if you tap something wrong or don’t work with other handsets! I used it on a Dash – use at your own risk on your Blackjack, Q, Windows Mobile Professional, or Windows Mobile Standard phone. I’m just passing on what I’ve learned from other WM users in the hope that I help someone else out! —