I have had a read of everything I can find in relation to this, but have come away more confused than ever.
I have to P6800 3G model, and a Blueant Q2. No dramas with pairing, connecting, receiving calls etc etc, but when I try to activate voice commands..."this feature is not supported on your phone".
From everything I have read this is not a new problem with Samsung devices.
This is my first experience with Honeycomb.
Have tried installing Vlingo and setting it to 'in car', but that didn't work.
My next step might be something like Cyberon Voice Commander, but I am loathe to try that before I can be sure I am not missing something obvious and simple.
Maybe the only "simple" thing here is me
scarytas said:
I have had a read of everything I can find in relation to this, but have come away more confused than ever.
I have to P6800 3G model, and a Blueant Q2. No dramas with pairing, connecting, receiving calls etc etc, but when I try to activate voice commands..."this feature is not supported on your phone".
From everything I have read this is not a new problem with Samsung devices.
This is my first experience with Honeycomb.
Have tried installing Vlingo and setting it to 'in car', but that didn't work.
My next step might be something like Cyberon Voice Commander, but I am loathe to try that before I can be sure I am not missing something obvious and simple.
Maybe the only "simple" thing here is me
Click to expand...
Click to collapse
Where are you trying to use voice commands? I do know that voice commands from the Google Search bar at the top of your homescreen works just fine for me, even for voice dialing.
However, it should be noted that voice commands are not being picked up via your bluetooth mic, rather they will be picked up by the mic on the 7.7 itself.
Thanks,
Correct the voice commands for voice dialing are not being sent via BT. All other pre determineed voice commands, like "call back", "answer", "ignore" all work fine.
When I request the BT headset to set up the voice dialing it just comes back as "device not compatible".
All other voice commands via the 7.7 mic work fine, just can't get those voice commands working via BT.
It seems to be a common problem, and was hoping that someone had a work around.
Seems to me to be a really silly omission not to be able to use the device in a totally "hands free" manner.
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.
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 "
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.
I recently purchased a bluetooth receiver for my car, but when I push the button the only option my N4 gives me is to dial a contact. Is there a way to make it use any voice command, i.e. "navigate to 123 Xyz Street" or "send text message....", or "what is the temperature in Chicago?" etc.?
Anybody?
I guess nobody else is interested in actually doing useful things via bluetooth? Seriously, Google Now Search can dial contacts, why can't I use that via bluetooth instead of the limited voice dialer?
hfuizo said:
I guess nobody else is interested in actually doing useful things via bluetooth? Seriously, Google Now Search can dial contacts, why can't I use that via bluetooth instead of the limited voice dialer?
Click to expand...
Click to collapse
I have my phone installed in a holder on my dash. I simply just use google voice commands to do everhting regards to dialing (just do it from my phone instead of from my car). My bluetooth is limited in my car. Not sure if there is any work-around.
Not positive about this, but I believe it may be headset/device dependent...as in not all Bluetooth devices allow you to utilize voice commands through your phone.
Sent from my Nexus 4 using xda app-developers app
I don't know if this is still the case, but a couple of years ago when Google first supported voice dialing via Bluetooth, the problem they cited was that the bit rate for audio via Bluetooth was insufficient for their voice recognition software. I haven't tried it with the N4, but if it still doesn't work, that could be the reason.