I changed the path to voice command in the registry (HKLM/Software/OEM/VoiceCommand/ Path=\Program Files\VoiceCommand\voicecmd.exe), but my Cardo Scala-500 headset still does not activate Voice Command. I searched extensively, was not able to find how to make them talk to each other. Any ideas? Anybody else using MDA+Scala-500 combination with Voice Command successfully? I am on the last official T-mobile ROM.
I don't know if it is anything related. When I first paired my Wizard with a Motorola Bluetooth, the pairing process says it is hands free device. However, it will not do voice dial. Then I tap long on the selection of this device in Bluetooth configuration and bring up the menu. In the menu, I select make this device the default hands free. Afterwards, it will work with voice dial.
You need to check to see if that headset supports voice dialing. I beleive that there are some out there that don't.
The "Hands Free" checkbox is checked on the device. And the manufacturer says it does support voice dialing. Anecdotal evidence (online search) also says that some people were able to use MDA with this headset and MS Voice Command.
Can it be a function of my ROM or any radio versions? They are in my signature if it matters.
Also, the headset has "Bluetooth version: 1.2 Class2". I do not know what that means, maybe that is why I think it may matter.
Different headsets behave in wildly different ways when it comes to activating voice dialing. My Moto HS850, for example, activates VC on the second push of the button, and you can tell at the same time it is pulling all sounds from the phone so you can hear the "bling-bling"... and then it takes its sweet long time in allowing the phone to return to normal so you cannot use VC again until that happens. My Bluespoon AX2 is different, in that it works every other time, and my Jabra BT800 just plain doesn't even work.
I suggest you play around with the BT config in your phone to see what works best for you.
I tried one click, double-click, tripple, and push-and-hold - nothing works.
Also, just tried a colleague's headset (Jabra JX10), it does not activate Voice Command on my Wizard either. I am going to talk to the manufacturer of my headset, see what they say.
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.
Ah, Lost my Motorola HS-850 which worked fine with Voice Command, been going through a number of different units, the Jabra J10, Motorola H700 both great headsets except for the fact that they seem to mess up and stop working after a first phone call that started with Microsofts Voice Command. I think the problem is due to the fact that Voice Command doesn't close the bluetooth connection properly since the built in Voice Dialer seems to work.
Does anyone know if there is a versions of Voice Command (official or hacked) or any other way to get Voice Command to "behave more freiendly" with some of the Bluetooth headsets?
i got a jabra 250v and it works flawless heres what i do.. hit my button once and wait for the tone.. do w/e command i wanna do and let it go through then once the command is over with i hit the button again to close the connection so if u are doing a call this is the step i use.. push button once.. wait for tone.. say call erich. hit the button to finish call. wait 1sec then hit the button again to close the bluetooth connection ...works flawless for me
Jacob-mda: That what I used to do with my old Moto HS-850 and it worked perfectly.
Unfotunately this isn't the case with all bluetooth headsets, especially newer ones, I've gone through about 4 or 5. Voice Command doesn't break the connection since it doesn't support bluetooth directly and most of the newer headsets hang after the first call and the only way to get them back is to restart the device or run another program like cyberon speed dialer that resets the connection. Not sure why if it's a version difference in bluetooth implentation, or just some headsets are more forgiving.
Unless there is a way to get it working which I'm not aware of, we need some little utility that would do whatever cyberon speed dialer does to reset the connect and then launch Voice Command, this would make it work with a lot more (if not all) bluetooth headsets which would be great!
It's a shame, I'm caught up between deciding what I want more, a better headset and using cyberon speed dialer (with voice tags yuk) or going with a working headset with Voice Command.
Anyways, it would be great if someone could right something that would reset the connect and then launch voice command. It might not be perfect but I'm sure it would make a lot of people (including myself) with non compatible headsets very happy
Hi,
I'm no developer so I don't know if this would work but if there is a developer out there with spare time and knowledge of the Bluetooth Stack, maybe they can confirm if this is possible and even write something.
Headsets like the Motorla H700 and the Jabra J10 seem to lose the ability to activate Microsofts Voice Command after the first call. I notice that if I run Cyberon's Speed Dial after this happens, Voice Command activates when the headset button is pushed.
Cyberon's Speed Dial is obviously resetting the connection or something. So wouldn't it be possible to write a small wrapper that would reset the connection to the headset and then launch Voice Command. This utility could be set in the registry for Voice Dialing and it would reset and launch Voice Command.
If this works it would make a lot more bluetooth headsets useable with Voice Command.
Just a thought (as dumb as it may be
Hi,
Search the forum..there is a solution with A2dp and the compatible BT headsets.
I searched didn't see it, if there is a solution, can someone point me to the solution or thread.
I recently had a Pioneer aftermarket stereo in my car and it was extremely convenient: hitting the phone button on the stereo immediately launched voice command through the radio's sound system, so that I could dial by voice and never have to take the phone out of my pocket, unlock it, etc. My car was totaled in a crash and in the new vehicle there's a separate BT system which doesn't do any of this - it pairs and calls come through it, but it won't activate voice dial; it can only dial the numbers stored in its own (local, limited) memory and won't let me give the phone other commands. So I'm thinking of replacing it, but I need to know: what feature am I looking for that enables the radio to connect to the phone and launch voice command without me having to touch the phone at all? What determines this? How do I know which stereo will activate VoiceCommand and which will only dial?
Thanks,
Mike
I thought it was the vendor/radio that determines what the buttons do. Same problem here, buttons don't always do what I want them to!
laserbeme said:
I thought it was the vendor/radio that determines what the buttons do.
Click to expand...
Click to collapse
seems reasonable, but what feature is it? When trying to pick the right vendor/radio, what am I looking for specifically? The salesmen know nothing about BlueTooth and VoiceCommand... What BT signal/message is being sent to the phone to activate ViceCommand?
Mike
The Voicecommand signal. I think your radio company decides which buttons have what functionality. If your phone doesn't have features that the radio has or vice versa, then it doens't work. The newest rom posted has, based on what I've read and seen, slightly improved BT functionality. (Although music by BT sucks, argh.)
Ive noticed something very strange with this headset. When I use the button on my Samsung Modus 3500 to either launch voice dial, redial or to hang up a call, Google Voice Search wont use any microphones on the phone and wont work. If disconnect from bluetooth and reconect it works again.
I tried to use a mono blueant headset and eveything functions the way it should, never a glitch. Im thinking it might have something to do with either the AD2P profile or the voice dialer taking over, honistly I dont know, I just want to know if anyone else has noticed anything like this.
And yes, i understand that Voice Search dosent work thew the headset, but the mic on the phone should ALWAYS activate when Voice Search is used.
Im using Macnut 13 right now, but I have tried this on evey Froyo ive installed including JK2 and JK6. Same results on TWO diffrent vibrants. Right now the workaround is to use the Bow Tie app fromt the market, but I would rather get the stock mic working right and consitant.
To test you headset:
1. Connect you headset to the phone
2. Hold down the button on the headset to redial, or just press it to bring up the dialer
3. Use the button to hang up
4. Try to use Google Voice Search by talking into the handset.
Post results here with your headset model and if it is AD2P capable. This may be a problem unique my model. If its not, then its something that the devs should look at. Chances are its a simple fix somewhere.
Read more: http://eb-productions.proboards.com...lay&board=vibrantacc&thread=129#ixzz17gWk3YRF