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
Related
Does any known how to detect when user press answer button on headset? What event or message generated by system? I find only some event that occurs when user insert headset jack in phone.
The AG service gets a "AT+CKPD=200" message
What i'm interestet in ; How do you send these AT commands ?
I'm sorry, but what is "AG service"?
Audio Gateway.
As far as I remember WM5 has standart API to register AG message handler. WM2003SE and older don't have a standart way.
It's not good. I'm interested in WM2003
Voice Dialing via Bluetooth NOT available on Atom
I thought that when I bought my Atom I would have voice dialing over a Bluetooth Headset. My friend has an Exec and it works fine. However, not with the Atom. Even the latest ROM doesn't support it. I have 4 headsets, all pair in Handsfree profile, all have call answering, call ending and last number re-dial working perfectly, but none will initiate voice dialing with the Atom, but all will voice dial with my Nokia 6230.
Therefore it is not a WM5 built in feature and is still ROM dependant. It doesn't matter whether you use the built in voice program, Vito, Neuvoice or M$ Voicedial, the stack simply won't support the AT command.
C'mon O2, it's about the only thing that is crook with the Atom. Other than that it is just the worlds best pda/phone!
Re: Voice Dialing via Bluetooth NOT available on Atom
Camstech said:
I thought that when I bought my Atom I would have voice dialing over a Bluetooth Headset. My friend has an Exec and it works fine. However, not with the Atom. Even the latest ROM doesn't support it. I have 4 headsets, all pair in Handsfree profile, all have call answering, call ending and last number re-dial working perfectly, but none will initiate voice dialing with the Atom, but all will voice dial with my Nokia 6230.
Therefore it is not a WM5 built in feature and is still ROM dependant. It doesn't matter whether you use the built in voice program, Vito, Neuvoice or M$ Voicedial, the stack simply won't support the AT command.
C'mon O2, it's about the only thing that is crook with the Atom. Other than that it is just the worlds best pda/phone!
Click to expand...
Click to collapse
Couldn't agree more!
About voice dialer. I thought it was just because Atom needs bluetooth headset button to be pressed for a while to launch dialer. It acts so with wired headset. Unfortunately, i have just one bluetooth headset to play with. And it turns off after 2 sec. holding the button.
On my Dopod 818pro everything acts like a charm (VD runs after a single press), so it isn't a WM5 bug.
can someone enable activating MS Voice Command from a wired headset for WM5?
it would be greatly appreciated.
Thanks,
I have the same problem using a bluetooth headset but if I use the wired headset supplied with my Atom it works fine.
that's good news. so, many OEMs are realizing the importance of this feature. so far, they have it in the Treo 700w and according to you, the Atom.
btw, did you have MS Voice Command pre-installed in your Atom, or did you buy it separately?
thanks,
The talk button on the wired headset is a "fake" button. It generates an special pattern in the recorded audio that it's recognized by the phone application.
It generates an special pattern in the recorded audio that it's recognized by the phone application.
Click to expand...
Click to collapse
Are you sure about that?
I've disembled quite a few headsets and the usual way is to shortcircut the mic-wire with one of the stereo-wires, whitch in return has to be cought by the mainboard and then translated to a command.
I'm not sure, but seems pretty feasible. That button is only used by the phone applicacion, which needs to open the wave input device.
Detecting the button pressing is pretty simple: recording at 16 bits, the average of the absolute value of the samples in complete silence is at least 100, with the talk button pressed, 6 or 7.
Hello, Anybody succeded in activating voice command by pushing on the standard talk button of the QTEK headset? i understand there is a solution for bluetooth devices, but i tried with the standard headset and apparently it doesn't work...i am using the fantastic 2.8 ROM....
i am also intresseted to do that.
Did anyone found a solution?
It seems that the standard "Talk" button on Qtek's headset is only good for picking up incomming calls. It is not similar to voice button on the device. I've desperatly searched for registry keys to change that.
Did anyone have any luck?
Thanks,
Rostylsav
This didn't work for me, but it's easy to roll back. Pasted from Howard Forum.
Originally Posted by tbrown801
I have seen several posts about accessing Voice Command over your Bluetooth headset. I have been able to do this succefully with just a couple of steps.
First:
goto "HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path". Change the default value from "\Windows\SDDialer.exe" to "\Program Files\Voice Command\VoiceCMD.exe".
Now you should be able to activate Micrsoft Voice Command by pressing the connect button on your bluetooth headset. My Scala headset beeps twice when it's ready for the Voice Command. My husbands Motorola headset beeps once when it's ready for the Voice Command.
Then you can also enable your bluetooth headset to receive music and other sound from your MDA by running the tweak "Enable Bluetooth Receive" using the Registry Wizard Program.
@glee719: This paste you did is about using Bluetooth headset for voice-dial.
The question is about the standard headset that goes with the Wizard . . . .
afaik the push-button on the headset works similar to the 'hook' buttons (green & red). Those do not trigger voicecommand either . . . .
glee719 said:
This didn't work for me, but it's easy to roll back. Pasted from Howard Forum.
Originally Posted by tbrown801
I have seen several posts about accessing Voice Command over your Bluetooth headset. I have been able to do this succefully with just a couple of steps.
First:
goto "HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path". Change the default value from "\Windows\SDDialer.exe" to "\Program Files\Voice Command\VoiceCMD.exe".
Now you should be able to activate Micrsoft Voice Command by pressing the connect button on your bluetooth headset. My Scala headset beeps twice when it's ready for the Voice Command. My husbands Motorola headset beeps once when it's ready for the Voice Command.
Then you can also enable your bluetooth headset to receive music and other sound from your MDA by running the tweak "Enable Bluetooth Receive" using the Registry Wizard Program.
Click to expand...
Click to collapse
Sorry to tell, it is not working for me, if i create a shortcut with "\Program Files\Voice Command\VoiceCMD.exe", and click on it, the voice command will lunch, however, putting the path in the reg, soft reset, press on buletooth handset doesn't work, any idea ?
By the way, how can we Set the microphone gain on the Wizard ? and how can we set the voice command to talk more and more louder ???
Yeah i'm interested to know how to make full use of the given headset, as i use it to listen to mp3 alot. The 'talk' button looks useless other than answering calls, unlike the w800i headset.
@rookery, this is NOT about the BT headset to activate VoiceCommand
Oh Sorry, did you mean the 2.5mm handfree, I don't have it in hand, does it work by the changing the reg key ???
hi to All,
useless to say i already tried the registry change for BT, and it didn't work for the STANDARD headset that is connected through the 2.5 mm jack. maybe, it is simply not possible.....
Is there a key for Talk button in the registry?
Does anyone know if there is a key for "Talk" button function in the registry?
We know there is one for BT headsets, but what about the conventional headset which comes with the device?
Anyone figure this out yet????????
Thanks
I just got this device, and I'm mostly pleased with it after applying various tweaks thanks to the fine people on this board. One problem I'm having though, is I am not able to voice dial contacts using my bluetooth headset. I have a Plantronics M3500 paired up with the device using hands-free profile, however pressing the button on the headset doesn't do anything to the MDA no matter if it is on or in standby mode. I saw messages on here that other people have this working, but so far, I haven't been able to. Is there something special that needs to be done? It worked fine for me on my Sony Ericsson P900 phone. Any suggestions are welcome. TIA.
Nevermind....
Uh... sorry just figured it out. It does work, but differently from my P900. I used to just press the button on the bluetooth headset, but with the Wizard, I have the hold down the button for a couple of seconds. Perhaps something to do with the hands-free vs. headset profile.
Are you using the stock voice dialer or Voice Command? I have been trying to find a way to activate Voice Command via the bluetooth headset button, without any success.
glee719 said:
Are you using the stock voice dialer or Voice Command? I have been trying to find a way to activate Voice Command via the bluetooth headset button, without any success.
Click to expand...
Click to collapse
No, I'm just using the stock voice dialer. The headset is paired up with the MDA using the hands-free profile. When I press the button on the bluetooth headset and hold it for 2 seconds, I hear a litte tone and the MDA 'wakes up'. As I said in the message above, with my Sony Ericsson P900 phone, I used to just have to click the button, and the phone would go into voice dial. I'm guessing that the difference may be due to using the hands-free profile vs. the headset profile that was used with the P900.
glee719 said:
Are you using the stock voice dialer or Voice Command? I have been trying to find a way to activate Voice Command via the bluetooth headset button, without any success.
Click to expand...
Click to collapse
Follow these directions, works great...
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
Now, when you press your BT headset connect button, MS Voice command will fire up and take commands through the headset. It's reponses will be played through the headset too.
Yeah, what Dustoff said. The other thing to remember (I learned it from these forums) is that you need to press the headset button twice to fully disconnect from the MDA. The first click disconnects from Voice Command, the second click disconnects from the audio gateway.
microsoft voice command and bluetooth headset
I need help getting the microsoft voice command software to work through a bluetooth headset. I used the instruction provided via Bits Inside Registry Editor to change the command on my handheld, but was unsuccessful. My blueangel has the latest rom and ext rom updates via the standardization project, and the headset is a Motorola HS820
Please assist,
thanks
lp
Re: microsoft voice command and bluetooth headset
lebpeach said:
I need help getting the microsoft voice command software to work through a bluetooth headset. I used the instruction provided via Bits Inside Registry Editor to change the command on my handheld, but was unsuccessful. My blueangel has the latest rom and ext rom updates via the standardization project, and the headset is a Motorola HS820
Please assist,
thanks
lp
Click to expand...
Click to collapse
The keyword in your request is BlueAngel. This registry hack is for the wizard only. I am not familiar with how to do it for the BA.
Sorry...
sorry, i saw the info, got excited and didn't notice the type of phone listed.
thanks,
lp
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.
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.