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
Related
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
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 folks,
I have a Cingular 8525 (Hermes 100/TYTN, I believe) running WM5 on the stock ROM from Cingular/AT&T (the recently upgraded one). I am trying to redirect all audio output, no matter what it is, to my Plantronics Model 340 headset. This is a monaural headset, but I don't care, because all I want to do is listen to voice podcasts and audio quality is not an issue.
A few people have told me about the program "BTAudio," but I tried this and it doesn't appear to work on my phone. Running the BTAudioOn program produces a soft hiss in the headset, but other than that you hear nothing through it. BTAudioOff turns off the hiss.
I thought that maybe this would work better with the WIDCOMM stack that you folks have been working on, but I can't find an actual install guide for that or anything saying "hey, this is ready to go and you should use it now."
Help?
http://www.teksoftbluemusic.com/
It works great, for me.
vmiguel said:
http://www.teksoftbluemusic.com/
It works great, for me.
Click to expand...
Click to collapse
Thanks! anyone else have other ideas? I would prefer not to go with trialware as there exist other solutions that work fine on other handsets.
I feel like there's just one little thing I'd have to tweak somewhere to get it to work, if only I knew what it was.
Actually, a couple of things happened here:
1) At first it didn't work.
2) Then I held down the button on my headset, and the Voice Speed Dial application started itself, all the audio was redirected to the headset for about 5 seconds, and then it stopped.
3) Then THIS stopped and wouldn't work anymore. Then when I pressed the "play" button in the Today screen plugin, it started working (for the two-minute trial period). I haven't been able to make it work again since.
I think there is some chance I could make this work if I could disable the Voice Speed Dial application, but I don't know how :-/
Hi Again,
RE: the old Voice Command issue with the Touch....When I am using my bluetooth, I hit the call button on the earpiece and get the tone. I say, for ex., "call home", and get the usual voice response, "Call Home?", to which I respond yes. Then i just get the end tone. It doesn't dial the number. Works fine without ther bluetooth. My understanding was VC didn't work at all with BT, but now that I'm this close, I'm wondering if there is a fix...Also, not to beat a dead horse, but anything new on voice notifications, especially Email and appointments. I really miss that from my old BlackJack with VC 1.5....
Thanks all,
Gary
Bluetooth and Voice Command 1.6 work perfectly on my Touch Cruise. (Although, it might be causing an issue with A2DP...I have to investigate to make sure though.). Eitherway, the point of my post was to let you know that VC 1.6 does over bluetooth, with not only commands, but also voice notifications coming over properly. So maybe the problem is your Radio ROM? Have you tried any others? Do the Radio ROMs from the MSM7200 models work for you guys with the MSM7500? If so, the most upto date Touch Cruise Radio ROM could do the trick for you.
Similar problem here.
With my stock touch, VC1.6 works better then with previous devices, but still not 100%.
I can initiate calls by pressing the button on my headset and, unlike devices of the past, notifications can be heard via the headset.
Where I have a problem, is in VC recognizing my response to confirmations. Anotherwords, if I have confirmations turned on for voice dialing, and say "dial Michele at home", VC will come back and confirm "dial Michele at home?". But when I acknowledge and say "yes", it does not recognize this, and times out.
If I turn confirmations off completely, everything works fine.
You can actually hear the confirmations lol? When I tried it I could barely hear the confirmations.
Dew.man,
How do you turn off confirmations? I can see the check boxes for voice enabling, and calendar reminders, but nothing about disabling the confirmations. (I have ver. 1.60.4622, is there a newer one?) Also, (for mindfrost) regarding the volume thru the bluetooth, there is a fix for that which works great. I'm at work and I'd have to look for it, but it is probably on this site . And the ever popular "audiopara" fix works GREAT for all other volume issues. Just drop the folder in the phone's windows directory. It is available on this site as well.
Gary
garpt said:
Dew.man,
How do you turn off confirmations? I can see the check boxes for voice enabling, and calendar reminders, but nothing about disabling the confirmations. (I have ver. 1.60.4622, is there a newer one?) Also, (for mindfrost) regarding the volume thru the bluetooth, there is a fix for that which works great. I'm at work and I'd have to look for it, but it is probably on this site . And the ever popular "audiopara" fix works GREAT for all other volume issues. Just drop the folder in the phone's windows directory. It is available on this site as well.
Gary
Click to expand...
Click to collapse
I would love to know the fix for the BT issue, please post.
After months of tweaking (including Jetware, that doesn't even have direct support for Touch), I did finally get MS VC working well on my Touch, even with voice confirmation and all. But it would take out my A2DP stereo capability time and time again. I implemented every other tweak and tip out there. Besides A2DP being unusable, it would also take out being to listen to Sprint TV over a BT headphone, which was a real bummer.
About 3 months ago I finally gave up VC. I had to ask what were my must haves, and they were rock solid A2DP to play my Rhapsody to-go tracks on the memory card with my two BT stereo headphones, and listening to SprintTV over the BT mono or stereo. Voice command was third on the list, and I'd just had to survive with the mickey-mouse voice dialing that came with the Touch... I uninstalled the MS VC for good.
Now everything is rock solid, and I much regret the literally hundreds of hours of my life I wasted on VC, not to mention my $40 bucks.
For those of us who don't use stereo bluetooth.. ie, myself I'd love to know what the fix was for getting the confirmation volume corrected. It'd make voice dialing in noisy places (such as while driving, in airports, etc) a whole lot easier. If anyone in this thread recalls, what was the solution to that?
Ok, so coming from a Nokia N80, I'm used to holding down the call/answer button on my Jabra BT530 headset, the phone beeps and displays "speak now", i say the contacts name and it dials...
Trying the same thing on my Samsung Galaxy S has no effect???
Supposedly this phone and the BT530 support handsfree profile... so what gives?
I've also tried with a BlueAnt ST3 carkit... and when you push the call button, you just get this funny "bong" noise and nothing happens on the phone...
I went into the BT settings on the phone, and the only profiles it has listed against the BT530 are "phone" and "media"...
Does this mean I have to use the phone to initiate calls? I seriously hope not, as that is now illegal in NZ while driving (which is about the only time I actually use BT) and is liable to land me a $150 fine for using my phone while driving!!!
Unfortunately, its a limitation of Android up to 2.1 Eclair. Voice dialing by bluetooth only works in Android 2.2 Froyo builds which are starting to show up little by little. Until, your phone gets Froyo, you will not be able to dial by bluetooth.
Thanks for the clarification...
I was going mental thinking I had it working when I first got the SGS (ie. before I got "Odin-Flash Happy" ) and that I had "broken it" by using one of the "unofficial" firmwares...
I will be able to sleep tonight
Now I just need a nice stable 2.2 firmware to get leaker
Is this officially listed as a Froyo capability?
I find this seriously limiting, and even dangerous.
What about sending audio to a mono bluetooth headset? Will this be possible with Froyo?
I tried Super BT Mono, but it doesn't seem to work on the Galaxy S.
Thanks!
one tap on the BT headset main button
wait for beep beep
yell out the name (it always gets it wrong)
then it launches the confirmation window
select from (application, contact, phone, crap load of stuff)
then dial...
even though it works... it's not "automatical" enough
it's more like a voice search, than a voice dial