Summary: Voicecommand via Bluetooth [STILL UNDONE]

[licht77]

After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.

Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!



WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.

PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.

PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)

This problem can be solved by changing a key in the registry:

HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)

Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.

PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)

There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/

I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)

PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.

PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?

PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?

And last but not least: Will you still be able to use your phone as a "phone" then?


Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto

Regards, Licht

 

[mobilehavoc]

Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.

Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.

Would LOVE to have a fix that would let me use with all headsets.

How does the jetware stuff work? I heard it screws up some other things?

 

[dfoody]

Cause of "works only once" problem discovered?

I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:

All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.

I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").

Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.

 

[licht77]

Changed over to Tytn... works perfectly without any hacks

 

[bittermormon]

here's my FWIW answer:

After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)

Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.

Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.

Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.