Activating Microsoft Voice Command with Bluetooth Headset

nealferraro's picture
Submitted by nealferraro on Wed, 17/05/2006 - 18:27. Tweaking | Tweaking | Requests

Since I am not a fan of creating voice tags; therefore, the default voice dialing function which came with my Cingular 8125 was not an option. I bit the bullet and purchased Microsoft Voice Command, which actually works well. The one thing that that annoyed me was I was not able to use my Bluetooth headset to activate Microsoft Voice Command. I searched around and did not find anything on the web about a tweak, so I took it upon myself to figure it out. Would you believe that I actually figured it out! It has been about a day and phone has not blown up yet so I guess it is working.

This is the change I made…

Using Total Command I found \\registry\HKLM\Software\OEM\VoiceCommand (Default Value: \Windows\SDDialer.exe) and modified the value to \Program Files\Voice Command\voicecmd.exe This is the default location when Voice Command is installed to the main memory.

Now when I press the button on my Bluetooth headset MS Voice Command works. Unfortunately, I noticed sometimes it takes two pushes for it to respond.

If anyone is brave enough to try it, let me know how it works for you or if there is another way to do what I have done.

--


login or register to post comments | previous forum topic | next forum topic | delicious | digg | reddit | technorati | 9917 reads


WOW.
orkrust's picture
Submitted by orkrust on Wed, 17/05/2006 - 20:11.

I'm impressed. Nice find. If i had a copy of MS Voice Command i'd give it a go.

Makes perfect sense that this would work, and i really doubt the phone would have any adverse reaction to this change if it hasn't already.

Great job.

--
-orkrust (Cingular 8125 - See Profile)

login or register to post comments
Voice Command with a Blue Tooth Headset
kenche's picture
Submitted by kenche on Fri, 23/06/2006 - 20:14.

Works great but the registry reverts back to default everytime I soft reboot. Do you have a solution for this problem?

--


login or register to post comments
Be sure to wait ~2min after
nealferraro's picture
Submitted by nealferraro on Mon, 26/06/2006 - 23:43.

Be sure to wait ~2min after you make the registry change. That may help.

--


login or register to post comments
:-(
sashen's picture
Submitted by sashen on Mon, 26/06/2006 - 23:24.

I tried this and it doesn't seem to work with my 8125 and my Jabra BT500... suggestions, anyone?

--


login or register to post comments
Voice Commander over Bluetooth
lenahanb's picture
Submitted by lenahanb on Mon, 03/07/2006 - 21:58.

I did implement this change. I experiance the same 2 button press that you are talking about. The reason this happens is that unlike the voicedialer built in. VoiceCommander does not end the bluetooth connection after you complete the command. Therefore, you have to press the bluetooth button again to turn on the bluetooth headset, if you forge to do this, you will have to press it twice next time you want to do something on your headset. I havnt found a fix for this either. I just have to remember to press the button on my bluetooth after VoiceCommand has completed its task.

--


login or register to post comments
Voice Commander over Bluetooth
robhammond's picture
Submitted by robhammond on Wed, 19/07/2006 - 15:39.

I implemented the registry edit and found the same thing about the "2 button press". I would have to say that I actually like that by pressing the button once and just saying nothing until MSVC goes out of "listen mode", then the phone speaker seems to be patched to my Jabra BT250. So now i can just leave the phone on my desk and hear any audio thru BT, or when the phone rings, the MSVC announcement goes to my BT250.
However, after the call terminates, i usually find the MSVC>BT now disabled, but just repeat the above and you are back where you were.
All in all, I LOVE the fix....THANKS Neal

--


login or register to post comments
Works
kida.1's picture
Submitted by kida.1 on Sun, 19/11/2006 - 17:37.

Thanks so much for this 'fix'. I implemented this fix exactly as indicated above on my Cingular 8125. As others have indicated the bluetooth connection is not stopped after completion of the MS Voice Command thus the user must press the "talk" button on the bluetooth headset after the execution of the command to 'ready' the device for the next button press. (Cingular 8125 and Motorola H700 headset) Excellent work by all.

--
K in Denver Co

login or register to post comments
Registry Key
cprano's picture
Submitted by cprano on Wed, 21/03/2007 - 00:48.

The way I see it the registry key is HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path

Change the default value from \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe

I am working on a way to get this to work for WM6, which has VoiceCommand built in. There is an excellent blog entry on VoiceCommand over bluetooth here

--


login or register to post comments