I posted the same on Howard-Forums but no reply :-(
Is there any specific profile that the bluetooth headset needs to support in order to use it with Microsoft Voice Command ?
I have an iTech R35 Clip bluetooth headset. The headset supports Hands Free, Headset and Wireless Stereo.
When I set it as Hands Free, wneh I receive a call I can hear on the headset who is calling but I can not answer the phone using the button on the headset (it does not do anything). When I set it as Headset, I can answer the phone but voice command does not announce who is calling.
Using both settings (Hands Free or Headset), when the phone is idle, pressing the button on the headset will activate voice command BUT I can only use the phone's mic to enter commands (it does not accepts commands using the headset's mic).
I have done all the registry hacks to de-activate the SDDialer and activate Microsoft's Voice Command.
So some questions:
- Anyone with the iTech R35 out there that successfully is using this headset with Tytn and Microsoft Voice command with the ability to "speak" commands on the headset's mic ???
- Anyone out there with any other stereo bluetooth headset (preferably with ear buds) that successfully is using MS Voice Command with their headset (including the ability to "speak" commands using the headset's mic)?
Read the wiki!
There tends to be no reply here if the subject has been covered thoroughly in the wiki. If you take a look at the TyTN wiki here: http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils at the section marked Use MS Voice Command instead of the built-in Cyberon Voice Dialer and the corresponding forum thread here: http://forum.xda-developers.com/viewtopic.php?t=59541 then you should find answers to most of your questions and more.
Have you tried the Cyberon Voice Commander program from the Dopod extended rom? I think MS Voice Command can be picky about headsets; i am using the full Cyberon prog with a Nokia HS-12W A2DP headset and just picked up a V-3 BTH8 headset and both work no problem with my TyTN for voice dialling and starting programs. It differs from VC in some functionality but for voice dialling they are basically the same.
Related
My "old" P800 was able to announce who was calling in my Bluetooth headset. After pushing a button on my Bluetooth headset I was able to do voice dialling. It could even pick up the call without pushing a button on Bluetooth headset.
Can wm 2005 on the Prophet do all this?
I have this working on my Jamin without any hacks
Care to share how? I just got a JAMin. No mention of voice dial except by launching program and certainly no mention of BT button. Pairs with my Plantronics M3000 fine but BT button doeas nothing. Any ideas?
Regards
Query to Wardy about Bluetooth Headset & Voice command
Hi Wardy does your Jamin let you control MS Voice command using the button on the BT headset? Or do you have to press the voice command button on the PDA and then talk through the headset?
Voice Command, once it is installed on the Prophet, works just like it did on the Magician. However, the Prophet (at least in Jamin flavor) has an app that lets you create voice tags to control most of it's functions, and this app can be started by using the button on your bluetooth headset (and accepts audio from your bluetooth headset). There are a few limitations, though: you have to create a voice tag for every single item that you want it to launch... and you can't create a voice tag for Voice Command :?. In other words, it is (as far as I'm concerned) completely worthless :evil:
Re: Query to Wardy about Bluetooth Headset & Voice comma
crackerjack said:
Hi Wardy does your Jamin let you control MS Voice command using the button on the BT headset? Or do you have to press the voice command button on the PDA and then talk through the headset?
Click to expand...
Click to collapse
Hi no sorry I am using the supplied voice command software. Its not a problem for me putting voise dial numbers in and I believe it gives better recognition than text to speach. But that's my view
Does anyone know if when using MS Voice Command with the Artemis and bluetooth headset can you hear the confirmation voice through the headset or does it come out the Artemis speaker. I want to be able to press the bluetooth headset button and hear the tone for MS Voice Command then speak the name of the person and hear it repeated back to me through the bluetooth headset. Is this the way it works on the Artemis???
do both version 1.5 and 1.6 work with the atom?
does the registry patch with 1.5 make it work with a bluetooth headset?
does the voice dialer that comes with the atom exec interfere with voice command or do i simply install 1.6?
has anybody here used ms voice command, if so which version and with or without bluetooth and how is the performance?
thanks 4 any info
actually can the build-in voice dialer be made to work with a bluetooth headset, i tried but without luck
HI,
I'm using 1.6 with bluetooth and no problems
so you can voice dial with the bluetooth right?
did you have to do anything with the built-in voice dialer program or just ignore it
Just ignore it.
Microsoft Voice Command works well. It transfer the audio to headset when the headset button is pressed. You can even set it to make announcement to headset.
My only problem is, it speaks too fast & I do not know how to set it.
I'm running MSVC 1.6 on my Atom but the voice dial over BT headset does not work properly.......however 1.6 is much better than 1.5 and I would still recommend it.
Check out this registry edit to SLOW down MS Voice Commander. I set mine to 3 and it is just peeerfect!
http://www.pocketpctweaks.com/pocketpc_tweaks/increase_voice_command_speed
Thanks for the info, angusc.
I should have added that I have tried the Motorola HS700 and also the I-Tech Clip R35.....neither of these seem to work with MSVC but I think it is more to do with the O2 ATOM PDA rather than the BT headsets.
Has anyone got Cyberon Voice Commander 2.0 (not voice dial, the whole commander that runs apps and doesn't require tags) to take audio input from a bluetooth headset?
So far, I've got the button working - simply changing the registry entry HKLM\Software\OEM\VoiceCommand Path to the proper location of the VoiceCommander.exe executable.
Audio output also works - I hear the request for a command from the bluetooth headset.
Talking into the headset does not work. I have to be close enough for the phone microphone to pick up my command for it to work. After the phone recognizes a command, the confirmation audio "Call so and so?" comes out of the phone, not the bluetooth headset.
I hate the robotic quality of MSVC and I prefer the functions of this one, but the bluetooth thing is a deal-breaker if I can't get it to work. Anybody out there using this app on their Mogul / Titan?
You ever get any further with this?
I have had a Jabra BT Headset for a couple of years and it works well. I have recently purchased a XCarLink with BT and am now using this in my car instead of the headset. One thing that I liked about the headset was how it worked with M$ Voice Command - i.e. press the 'Talk' button and Voice Command would start and you could say 'call xxx' etc. With the XCarLink if I press the 'Talk' button this justs stops any music that was playing but doesn't start Voice Command.
Is there any tweak I can apply to get this behaviour?
Andy
More testing......
I have been doing some more testing with this as the Jabra BT headset stopped activating Voice Command...
Anyway I have tested a couple of different versions of Voice Command (1.6.19214 & the one from the Diamond 1.6.19581) and both behave the same. If A2DP Joint Stereo is enabled (HKLM\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings - UseJointStereo=1) then the 'Talk' button on the BT headset no longer activates Voice Command. If Joint Stereo is disabled the 'Talk' button activates Voice Command (after a soft-reset).
I haven't had time to check the behaviour with the XCarLink but I will post the results when I do.
If anyone has any experience with this or knows a fix then I'd appreciate it.
Andy
Anyone been able to get voice dialling working from the Xcarlink? I just bought one and am having the same problems.