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
Related
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 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.
Hi all!
I'm quite new to this forum and even though I've read every single post about the bluetooth issue obviously evident on the HTC TyTN and all the tweaks regarding disabling the cyberon speed dial in the registry and installing MS voice command and later on Cyberon Voice command, I never got the whole bluetooth voice command thing going perfectly, like many others I guess...
I could get the music playing trough my SE bluetooth headset, with all the controls working perfectly, and I could use the hardware button for voice dial, but the feedback of commands from the voice command program would never play up in the ear phones, even though it recorded my commands in the microphone and would actually call my contacts if I had the TyTN in front of me to time in and watch the top icon to see when the microphone would pop up after the keypress on my headset... Music would play perfectly but the voice command was never problemfree......
I finally uninstalled all voice command programs and went back to the included cyberon speed voice dial which works very well. I just record in my 20 or so contacts into Cyberon Speed dial and then get the connection seamlessly from my bluetooth headset and microphone when wanting to make a call with the headset!
I can listen to music all the way to uni and recieve calls and actually press the headsets voice command button and recieve + place perfect calls with the music commin back on right after my finished call!!!! FINALLY!! And I dont really mind recordin in, what like 20 names...
So to all newbs like me, don't tamper with all the registry hacks and dlls here and there, just record some contact names in cyberon speed dial and use ur favourite bluetooth supported media player (like pocket player or so, with some bluetooth enabling downloads) and enjoy true handsfree!!
PS. Sorry for the long post, and sorry if I'm repeating already given advice...
Does anyone have a step-by-step way of removing that blasted Cyberon rubbish from the Ameo? I bought (having tried, um... other sources) MSVC 1.6 UK from Handango, wondering if perhaps a real EXE-from-PC install would somehow work "better", but same problems.
I had it working yesterday via BT headset to listen, but no notifications came through so commands were messed up. Removed it, and installed again; I've remapped the "Web 'n' Walk" key to activate it. Now what I don't understand is this:
Installed yesterday. No attempt to remove Cyberon:
Worked okay for a while. Worked with BT headset button. Didn't respond to commands from BSH-100 headphones, but they're junk anyway. Bluetooth started getting unreliable and wouldn't pair with Nokia BH-200 headset after working fine with it for an hour or so.
Removed MSVC. Reinstalled. It's in the startup folder and so forth. Button on wired headset triggers damn Voice Speed Dial. Haven't tried bluetooth yet. Responds to commands with hardware button, but no option exists to map command to wired headset button.
Removed Sddaemon startup item. STILL comes up when I use the wired headset button.
It's REALLY annoying and frustrating, as MS Voice Command DOES work effectively as a tool. It just doesn't, well, work. And I think nearly all of the problems it has are down to the presence of this Voice Speed Dial, which I will never use - I'm not recording voice tags for everything, this is the 21st Century!
Also, why doesn't TCPMP follow UI conventions?! It keeps starting up in portrait mode and won't fix itself unless I use the T-Mobile "screen rotation" icon.
EDIT:
Okay. I paired the Anycom headset to it.
As a Bluetooth headset, the button dials, makes calls, and if held, brings up Voice Commander. Notifications now come through the headset, and commands are definitely going to the device, but music is played through the unit, not the headphones.
As stereo headphones, the buttons work, but it doesn't hear commands from the microphone in the headphones - only via the built-in microphone. But music (with joint stereo enabled) comes through the headphones alright.
Other than that the Ameo definitely kicks arse, having GPS etc. built in is excellent. Is it really 802.11g, though - or is it like a hacked Universal with 802.11b speed pretending to be 802.11g?
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