|
||||
Look at HKLM\Software\Microsoft\Bluetooth\AudioGateway\
There should be an entry named VoiceCmdEnable Is yours set at 1 or 0? I dont know if this controls all Voice Command programs over BT or just MSVC (which I am assuming you dont have installed) but you might try changing this entry to 0 if it isnt already. Just a shot in the dark.
__________________
1. Read the FAQs, Stickies, Wiki
2. Do a SEARCH! 3. Be Very Specific 4. Give THANKS to those who deserve it! |
|
||||
Also, are you using wm6? The reason I ask is because by default Voice Dialer isnt installed so I am not sure how you got it on there other than MSVC?
|
|
||||
Wm6
Quote:
It's not in his change log, but possible VerizonGuy reactivated the default Voice Dialer. And you are correct, I did not install the Microsoft Voice Command (which I actually like, but just didn't bother installing yet). Hmmmm..... since that trumps the default Voice Dialer, maybe I ought to try installing that to see if it fixes my problem. I seem to remember it didn't have a "hair-trigger" like the default Voice Dialer when I was running it on my 'official' WM5 OS. Sometime today, when I goof off @ work, I'll try searching the registry more thoroughly to see if I can find anything on the default Voice Dialer. Thanks, Gervy |
|
||||
Yeah, I would definitely try installing Voice Command and see if that fixes anything. I have done a fairly in-depth search of the registry but I havent come up with anything to help other than what I posted above. But I know that in the HelmiWM6 ROM Voice Dialer is not installed. So my only suggestion would be to PM VerizonGuy and ask him if he has made any changes to the Helmi ROM regarding the VoiceDialer, and explain to him your problem and see if he has any solutions.
But, just out of curiosity, did you try the reg edit I posted? And if so, did it make any changes for better/worse? |
|
||||
Didn't try the reg edit. Installing Voice Command worked to black Voice Dialer. Though my BT headset won't activate Voice Command like it used to. I'm sure there is a fix in these forums, but i'ts not high enough priority for me to bother. I barely use it anyhow.
|
|
||||
This got my BT headset to launch only Voice command, before this hack both VC and speed dialer would launch!
Goto "HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path ". Change the default value from "\Windows\SDDialer.exe" to "\Program Files\Voice Command\Voicecmd.exe".. In my registry I also had a String Value named "PathBak" which kept changing the "Path" that I changed above back to windows dialer, I tried changing both paths to point to VC but that only caused VC to quit audio to the headset. So what I did was delete "PathBak" and all was well. Hope this helps someone! BTW: I guess you could use any path for the BT headset to launch if not VC |
|
||||
Quote:
|
|
|
|