View Single Post
  #9 (permalink)  
Old 12-14-2007, 10:57 AM
itsamemario's Avatar
itsamemario
Lurker
Offline
 
Join Date: Oct 2007
Posts: 22
Reputation: 0
itsamemario is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quote:
Originally Posted by v8s10chevy View Post
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
All I had to do, to disable the voice app was go to the same registry folder you mentioned, but I changed the LaunchAPEnable from 1 to 0 and it stopped popping up. However when I run the app called acbtogglebt I was hoping that I would be able to integrate it with core player but it seems to pop-up the windows media playlist. Does anyone know of a way to fix it to work with sending the audio from the core player to my bluetooth headset? Either through the above mentioned app or otherwise. Thanks.
Reply With Quote