[Touch CDMA General] anywhereanytime:
VC 1.6 WORKS - but NOT with Bluetooth

Today I played some more and VC 1.6 definitely works over the speaker and built-in mic - VERY COOL - BUT, NOT with bluetooth (we are using the Blue Ant Z9)

SAME PROBLEM reported across many threads - when VC 1.6 "confirms" the command, it then hangs up (turns off listening)

This seems to be a common problem across many HTC devices, so I searched quite a lot and found this under the Hermes thread.

http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils

ANY EXPERTS OUT THERE to give this a try and report back ??

--------------------------------------------------------------------------

How to make Microsoft Voice Command 1.6 work (WM5 & WM6 tested!).

(caution, this MAY disable all incoming call notifications over the speaker and obviously doesn't route the notifications to the headset - that's a MS stack problem...)

NB The 'Program Files' directory mentioned several times below, may be different on non-english language versions of WM (see below).

Install VC 1.6 (make sure it is in Main memory)

Download Bluetooth Voice Command 0.9f.cab here - related forum thread

Download ?BTVoiceCommand.exe here - related forum thread

Download replacement btagext.dll here (Unknown if this works with WM6?) - related forum thread

Run .9f Hack

Create the Folder \Program Files\Bluetooth Voice Command (should be created during the .9f cab install)

Copy ?BTVoiceCommand.exe and btagext.dll into this folder

Go to newly created BT Voice Command config (in Programs) and tick the check box "Enabled"

Set command duration to 30 (or more - check by experiment when set up)

Set or check that the following registry keys are set (I had to manually change Path to ?BTVoiceCommand.exe.)

HKLM\SOFTWARE\OEM\?VoiceCommand\Path = "\Program Files\Bluetooth Voice Command\?BTVoiceCommand.exe"

HKLM\SOFTWARE\OEM\?VoiceCommand\?VoiceCmdDuration = 30

HKLM\SOFTWARE\Microsoft\Bluetooth\?AudioGateway\?BTAGExtModule = "\Program Files\Bluetooth Voice Command\btagext.dll"

a. (For reference: http://xdaforums.com/showthread.php?t=283412&page=7 )

*Go into the registry (HKLM\SOFTWARE\OEM\?VoiceCommand\) and set ?LaunchAPEnable to 1 (I wasn't sure if this was necessary...but it's working now)

Soft reset device

Delete Headset Pairing

Recreate Headset Pairing.

*NOTE: first time you invoke voice command using BT headset button, you may get the "run this program yes/no?" option on your screen. You have to QUICKLY hit "yes" or your phone will have to be soft reset to exit the prompt.

Set Side button to ?VoiceCommand (if desired for backup when using Mortscript described below)

You may also need to create the directory \Program Files\Bluetooth Voice Command and move the files over if you live in a different country and MS installs everything to something similar - like Programme...

WM6 specific:

If using the .09f file downloaded from the link above, the registry key should look slightly different:

HKLM\SOFTWARE\OEM\?VoiceCommand\Path = "\Program Files\Bluetooth Voice Command\BTVCBasic.exe"

You may still encounter a problem where approx 15 s after initiating a call using MSVC from your headset button, the sound is routed back to the handset. A subsequent press on the button usually reroutes the sound to the headset, but sometimes disconnects the call instead. We are hoping for a fix for this.

--------------------------------------------------------------------------