Anyone else get this after updating to 2.2 today, or ever?
When I try either Vlingo or Google Voice search over Bluetooth all I get is bad feedback. it's like the speaker on the phone or the mic is not being disabled.
Anyone else experience this? it's quite annoying.
I haven't tried vlingo or google voice but I have used the bluetooth dialing in 2.2 on JK3 and JK4 andit sucks even with one of the best quality headsets, Plantronics Voyager Pro, in semi noisy enviroments, driving a truck and van.
If the dialer doesn't just get the wrong name, sometimes it tries to take your voice input and create some bizzare digits to dial. At least when I used WM6 and Microsofts voice dialer it told you what it heard and then you could say no or cancel and it would stop. NOT this dialer. It'll just dial away whatever it thinks you said.
1 trick might be to make sure every number has a mobile and landline number, then at least it would ask you which to dial, at which point you could say cancel.
i'd be happy if it heard anythign. all I get is BAD feedback.
i reinstalled the app and will try again, but if it's happening with both google and vlingo reinstalling vlingo won't help.
I'll also try re-pairing...hopefully that's all that's needed.
Related
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?
no matter how I try to make it work, I cannot get voice dialing to work over my bluetooth headset. Anyone having this problem?
guyjack said:
no matter how I try to make it work, I cannot get voice dialing to work over my bluetooth headset. Anyone having this problem?
Click to expand...
Click to collapse
I think EVERYONE
the moment comes with nuance, is there any way to rip that out and add it to the hero?
For some reason, I find it easier to use the Voice Search app instead of the Voice Dialing app. If I say, "Call Dennis at Home" it works every time. BTW, I'm using a Jawbone Icon Rogue earpiece, which now supports A2DP. I do have to initiate the Voice Search by tapping the icon on the phone, though.
Bluetooth voice dialing
I would love to see one of the devs tackle this one. I have had true tap your BT device and voice dial since I started carrying a smartphone, UNTIL I switched to Android a few months ago.
Please devs, someone tackle this one. Even my old MotoQ with Winmo did it perfectly. I know you guys can do it better. Look how good Google Voice is with the keyboard and search now.
I have tried to get Nuance Voice from the Moment to work on the hero, and the phones are just too different and Nuance is to integrated to the moment. It works great though. Thats the ONLY good thing about that damn phone.
finally fixing blue tooth
Saw a recent post on phandroid that this will be fixed in android 2.2 (froyo)
And I quote:
" •Voice dialing over Bluetooth
•Ability to share contacts with other phones
•Support for Bluetooth enabled car and desk docks
•Improved compatibility matrix with car kits and headsets "
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
I got the Epic 4G on the 31st, but out of the box I can't seem to get voice dial or voice search working. I'll click on voice dial and it will say "listening" but it doesn't really hear anything. Eventually, it just times out and says "try again". The same goes for voice search. It prompts me with "Speak now" but eventually times out and says "No Speech Heard". It's as if the mic isn't working. But I don't think there's anything wrong with the mic because I can have phone conversations without any problems. So, I don't think it's a hardware problem. It seems like this is some kind of bug in the software. I don't see any settings for these apps that I can modify. Anyone else having the same problem? Any suggestions for fixing?
Nevermind
I seem to have figured out the problem. If I turn off my bluetooth headset, the voice search and voice dial work. Apparently, it cuts off the mic on the phone when a headset is paired. I'm a little disappointed because Voice Command on my windows mobile devices didn't have this problem. If I initiated voice command on the phone, the mic on the phone would still work. If I initiated voice command from my headset, it enabled the mic on the headset.
I see no options in Android to initiate voice search or voice dial from the headset. Since I normally have a headset paired at all times, I guess I can't use these apps. Bummer.
Coming from winmo, I have to say that the only thing I miss and the only thing that winmo did better than android is voice dial. Android voice dial, even in froyo and even with Vlingo does not give you a true hands free experience because you cannot initiate it without launching the program from the screen, and it will not confirm by voice -- you have to confirm with a screen press or cross your fingers and let it autodial. Very disappointing.
Disoppointed with voice recording/dialing.
I sure was hoping that 2.2 would fix the voice dialing also. This may make me take the phone back before the 30 days are up. The voice MEMO is also a problem. Go to notes and try to do a voice memo...it's hit or miss and when you do see the mic recording, it will only record for a few seconds and then a screen comes up that says it cannot connect to the server. What's up with that. Very disappointed with the voice recording/dialing features of this phone.
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