I have a plantronics headset, and I'd like to use google voice rather than s voice or the crappy google dialer. So I followed this guide: http://brandtkrueger.wordpress.com/...voice-actions-the-default-instead-of-s-voice/
(tl;dr: use Bluetooth Launcher app, have it activate com.google.android.googlequicksearchbox.VoiceSearchActivity)
And it works most of the time, but the problem I'm having is that if I've used it once (i.e. the search bar has text in it) re-activating the bluetooth headset by pressing the button doesnt allow me to say something new unless I clear the box by hitting the back button.
Any ideas?
Related
I installed and uninstalled the JETware Hands-free Extension and since doing so voice dialling via Bluetooth has stopped working.
If I press the voice dial button on my BT carkit (Parrot CK3200) it now launches the phone app, and not the voice dial up.
[HKLM\SOFTWARE\OEM\VoiceDialer\Path] is set to \WINDOWS\sddialer.exe
Pressing the Voice Dial button on the handset launches voice dialer.
So it is just the bluetooth command which is wrong. Any ideas how to fix it?
Don't know if it will help but the attached cab file sorted out my voice dialling over btooth - couldn't find the thread I got it from so you may want to search it out before trying it.
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.
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
So I recently got a Plantronics Voyager Edge headset and noticed an interesting bug...
Every function appears to work fine. I can communicate with the phone via voice through the headset. And if I search for a business or something and hit the call button in the search results, everything works fine.
If, however, I dial a number manually or select a number from my contacts - the call isn't immediately sent to the headset. I have to toggle the speaker phone and then back to the headset to get the call to go through the headset.
Anyone had this issue? If so, is there a fix you're aware of?