Related
I could not stand the vlingo crap that Samsung put on the galaxy s2. The thing would not recognize what I was saying when I was just trying to make a call. I don't need the thing to type out a text message for me, I just need to be able to make calls hands free with my bluetooth. Another plus is that the Google Voice Dialer does not require network connectivity to do the voice recognition unlike vlingo. Here's how to do it. You gotta have root to do this. If you want vlingo back, push VoiceToGo.apk from here to /system/app
1. Download VoiceDialer.apk from here
2. remount via adb
3. Push VoiceDialer.apk to /system/app/VoiceToGo.apk
Now you have the stock Google voice dialer that detects commands better than vlingo, at least for me.
This also works by renaming VoiceSearch.apk to VoiceToGo.apk....the google voice search that's on the phone works pretty well for dialing also, but will allow you to search google for stuff via your bluetooth headset also.
I think this option is already available under settings -> voice input and output -> voice recognition -> change to Google from Samsung voice powered by vlingo.
Correct me if I am wrong though.
It did nothing for me, vlingo would come up even with google selected
Sent from my SPH-D710 using Tapatalk
you can download google voice search from the market and when you hit the "search" button on your phone for the first time it will ask which one you want as default
https://market.android.com/details?id=com.google.android.voicesearch&hl=en
vide infra said:
you can download google voice search from the market and when you hit the "search" button on your phone for the first time it will ask which one you want as default
https://market.android.com/details?id=com.google.android.voicesearch&hl=en
Click to expand...
Click to collapse
Google Voice Search and Google Voice Dialer are 2 different apps.
When I first longpressed the search key, it offered vlingos voice talk or googles voice search as the two options, and I had set googles as the default and since forgot about vlingo.
I bought ifrogz luxe earbuds today, and when I click the remote, the dreaded vlingo launches. Im not rooted, and was wondering if I could make it launch googles voice search instead.
Yeah, samsung cheated and locked vlingo to the headset key. Thanks. I was hoping that someone would fix this before an aosp rom came out
Sent from my SPH-D710 using Tapatalk
Thanks for this. Vlingo is the worst app I have ever used for bluetooth dialing.
ElAguila said:
Thanks for this. Vlingo is the worst app I have ever used for bluetooth dialing.
Click to expand...
Click to collapse
I have reason to believe that vlingo does not in fact use the bluetooth microphone when you activate it with bluetooth, even if you do set it in the settings. After I installed my exhaust in my car the microphone icon was fully lit when I was driving because it was picking up the rumbling. I get no problems with google voice dialing or even when I set the voice search for the bluetooth voice dial.
I can't get this to work, I pushed the apk as instructed, I connect my blue tooth and press the button, but i get no prompt.
Make sure to remount for r/w access, push to system/app as VoiceToGo.apk not VoiceDialer.apk and if ask else fails, delete the old VoiceToGo.apk before pushing. You can always do it via root explorer too
Sent from my SPH-D710 using Tapatalk
thanks, I did use root explorer and rename it to VoiceToGo before pushing. I should note that I did not have an old voicetogo.apk .... could that be my problem?
What ROM are you running? VoiceToGo is vlingo voice app, if you have it running and the apk doesn't exist, I'm not sure what you could do. You could try install the voicedial.apk
Sent from my SPH-D710 using Tapatalk
worked for me
Works great on my epic 4g touch. The google voice search has worked better than vlingo for me so this is great. I couldn't do it with the adb, I kept getting a remount error but the root explorer was simple and easy. Also, fyi you can replace vlingo with the app google car home for when you dock it in the samsung car dock. This is a much better interface that also uses google voice search. Check this link out and make sure to follow his instructions on the order of install.
http://forum.xda-developers.com/showthread.php?t=1257329
---------- Post added at 02:49 AM ---------- Previous post was at 01:53 AM ----------
Note: Voice dialing worked as stated in my post. But for voice search to execute when the bluetooth button is pressed I had to install bluetooth launcher from the market. In bluetooth launcher choose voice search, then I chose com.google.android.voicesearch.recognitionactivity. This only worked after I had replaced the vlingo app with voice dialer.
Krisregas1 said:
Works great on my epic 4g touch. The google voice search has worked better than vlingo for me so this is great. I couldn't do it with the adb, I kept getting a remount error but the root explorer was simple and easy. Also, fyi you can replace vlingo with the app google car home for when you dock it in the samsung car dock. This is a much better interface that also uses google voice search. Check this link out and make sure to follow his instructions on the order of install.
http://forum.xda-developers.com/showthread.php?t=1257329
---------- Post added at 02:49 AM ---------- Previous post was at 01:53 AM ----------
Note: Voice dialing worked as stated in my post. But for voice search to execute when the bluetooth button is pressed I had to install bluetooth launcher from the market. In bluetooth launcher choose voice search, then I chose com.google.android.voicesearch.recognitionactivity. This only worked after I had replaced the vlingo app with voice dialer.
Click to expand...
Click to collapse
Yeah, I tried that Bluetooth launcher app but it still would launch vlingo, that's why I went on my quest to replace it
Sent from my SPH-D710 using Tapatalk
I have to say guys, I have had the exact opposite experience on my original Epic 4G. The Google Voice Dialer is single handedly THE worst piece of crap I have ever used. Not once has it ever properly understood my commands. Google Voice Search thankfully does as well as this Vlingo app when I took it from an Epic 4G Touch and pushed it to my Epic 4G. Both of these programs work near flawless for me for proper voice detection. I've had such horrible experiences with the stock Voice Dialer that I delete it from every ROM I use upon first boot. So I'm not sure why you are singing Voice Dialer's praises when it simply isn't true at all.
Orbiting234 said:
I have to say guys, I have had the exact opposite experience on my original Epic 4G. The Google Voice Dialer is single handedly THE worst piece of crap I have ever used. Not once has it ever properly understood my commands. Google Voice Search thankfully does as well as this Vlingo app when I took it from an Epic 4G Touch and pushed it to my Epic 4G. Both of these programs work near flawless for me for proper voice detection. I've had such horrible experiences with the stock Voice Dialer that I delete it from every ROM I use upon first boot. So I'm not sure why you are singing Voice Dialer's praises when it simply isn't true at all.
Click to expand...
Click to collapse
maybe it's your Bluetooth headset. I have a jawbone hero and I NEVER have issues with it recognizing and interpreting what I say. Vlingo NEVER interprets what I say. It's as if it doesn't utilize the Bluetooth and it's using the phone's microphone.
Sent from my SPH-D710 using Tapatalk
I prefer google voice search to voice dial just because it can execute more commands although voice dial has worked well for me. As far as getting the bluetooth button to launch voice search it does work for me when I replaced the vling with voice dial. Then select bluetooth launcher and select voice search. Then it comes up with a dialog box asking which program you want to use as your default bluetooth launcher(voice search) or voice dial. But it's all for not really because voice search does not use the bluetooth headset microphone for input so I went back to voice dial for now. Come on Google add bluetooth microphone input for voice search.
Krisregas1 said:
I prefer google voice search to voice dial just because it can execute more commands although voice dial has worked well for me. As far as getting the bluetooth button to launch voice search it does work for me when I replaced the vling with voice dial. Then select bluetooth launcher and select voice search. Then it comes up with a dialog box asking which program you want to use as your default bluetooth launcher(voice search) or voice dial. But it's all for not really because voice search does not use the bluetooth headset microphone for input so I went back to voice dial for now. Come on Google add bluetooth microphone input for voice search.
Click to expand...
Click to collapse
Replacing VoiceToGo.apk with voicesearch.apk gave me Bluetooth recognition. Only thing I didn't like about it was that it didn't repeat my command back to me
Sent from my SPH-D710 using Tapatalk
nacron said:
Replacing VoiceToGo.apk with voicesearch.apk gave me Bluetooth recognition. Only thing I didn't like about it was that it didn't repeat my command back to me
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Is there one that repeats the command and asks for confirmation like Microsoft Voice Command does on Windows Mobile? I hate not being able to cancel if it guesses wrong.
PLEASE, help me. I've looked around and only found a couple of post within threads that specifically target these two issues. Most people are concerned about voice dialing over bluetooth which is answered by several apps, Voice Command included. But, I'm pretty sure a lot of people have been frustrated by or are curious about this:
It seems REALLY dumb of Samsung to disable or remove the ability for bluetooth voice input in stock apps. I know there's Voice Command, but I have 2 problems with that - 1. it just kinda totally sucks, IMHO; 2. If you launch something like Google Navigation, but it or you get the address wrong, you cannot use voice commands to input the new address within the application, you have to back out an try again. If I tell it to navigate to "Alewife Station" and Navigation comes back with a list of wrong guesses, I have to back out. Also, no voice-to-text once you are in your messaging app. It's fine for the initial message out, but not your reply if the app is open. No 3rd party voice assistant apps. No Google search outside of Voice Command. Essentially, no bluetooth voice input outside of their precious little app that is not as all inclusive as they'd like to make it seem.
My second gripe is using the audio out for only media/notifications, but not phone calls. The audio quality is markedly better when using the audio out on the car dock verses an FM transmitter, especially in the city where it's hard to find an open frequency. But if I receive a phone call while docked the audio switches to the phone's speakerphone. And even with a bluetooth paired it takes the input from the phone (the mic is blocked by the dock) WTF?! So I have to dismount my phone (which is illegal in some states) or fumble through the menus to turn off the audio out setting, then switch my radio to FM and hope I'm in a clear area, just to take/make a call? So much for 'eyes on the road'.
These two decisions seem counter intuitive and odd oversights for a flagship smartphone.
ANY suggestions or solutions are welcome. If you'd like to build an app to address one or both of these issues, I'll test it all day on my phone (that's why I pay $8/month for insurance) and support your development time. I'm sure many, many people would be happy to have this function.
Sorry about the rant, but the fact that this is not a standard function irks me.
I agree. I hate the voice command bull. It never calls the correct person. I say call Ted and it calls pat. I hate that program. And as far as I could tell the only way to get rid of it is if you rename another app and push it to the System folder.
I just want Google voice search over Bluetooth.
No ideas? Please? Anyone?
I'm relatively new to the Epic so maybe I'm just missing something obvious, but I have run into a real issue with voice dialing via BT.
When I hit the talk button on my BT device and say "Call Home" it immediately starts dialing, and in almost every case it's the wrong contact.
Is there some way to get a voice prompt/confirmation before the dialing starts?
Download another voice dialer from the Play store. Top Voice Control used to work well for me.
Sent from my PantechP4100 using xda premium
Thanks for the option, but it's asking me to install a TTS (text to speech) library even though I already have one installed...
mbellot said:
Thanks for the option, but it's asking me to install a TTS (text to speech) library even though I already have one installed...
Click to expand...
Click to collapse
Just let it grab one from the Play store for free. It will go through the install process. It should have recognized the one you had though.
Sent from my SPH-D700 using xda premium
When I first had an Android phone I would have to go through a session talking to my phone, so it would get used to the nuances of my voice when I talked to it. This would allow me to use voice commands through a BT speaker in my car. Moving from Android to iPhone and Siri this was more seamless. Siri just picked up on my voice with no such session. Now that I am back to Android with the G Pro I see that the Voice Commands app still sucks when it goes to understanding the nuances of my voice, yet I do not see a way have that same talking session with the device.
So the question is what do ppl do when it comes to talking to your G Pro. Is Google Voice Search better, but how do I make it the default app instead of the terrible Voice Commands app?
Thanks,
Steve
I havent had any issues with google voice search I just programmed it to my qbutton
Sent from my LG-E980 using Tapatalk 2
jprosek said:
I havent had any issues with google voice search I just programmed it to my qbutton
Sent from my LG-E980 using Tapatalk 2
Click to expand...
Click to collapse
The problem seems to be that when you use a BT car speaker the button you push to talk to the device is tied to Voice Commands, so I cannot seem to get around this, unless someone can tell me how I can change this so it will bring up Google Voice Search instead.
I'm used to the iOS voice app that has an embedded dialer. Is there an analog in Android? Even though I have GV set to ask whether to use GV or my cell number to dial, it seems the only way to dial is to choose a contact from GV app. Using the native dialer always dials from my cell #.
Is there a hidden feature or alternate app for dialing?
You don't need Google voice that's a completely different service. Use google now its much better and it will search anything from any screen by saying "OK google" once you set it up. I'll attach some screen shots for you.
Sent from my LG-D850 using XDA Premium 4 mobile app
I forgot one picture, also here is a guide for the voice commands
http://trendblog.net/list-of-google-now-voice-commands-infographic/
Sent from my LG-D850 using XDA Premium 4 mobile app
Pilz said:
You don't need Google voice that's a completely different service. Use google now its much better and it will search anything from any screen by saying "OK google" once you set it up. I'll attach some screen shots for you.
Sent from my LG-D850 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, but that's actually not the issue - I'm trying to use Google Voice to that it sends my office phone number as callerID when I call clients from the road. Unfortunately, Google's brilliant (not!) use of "Voice" for the name of a service makes searching impossible to find help on the app. (Google Voice Dialing, as in Dialing with the Google Voice cloud app)
I'm actually using google voice for a second phone line I use with clients. It rings on my desktop and forwards to my cell. I would like to be able to dial out from my G3 using Google Voice so that the callerID that gets sent is my office number, not my cell number. As I said, if I select a contact from the GoogleVoice app, it asks whether to dial with the GVoice app (which goes through a telephone gateway with the Office CallerID), or to dial with the native phone app, which would send my cell phone CallerID.
overzeetop said:
Thanks, but that's actually not the issue - I'm trying to use Google Voice to that it sends my office phone number as callerID when I call clients from the road. Unfortunately, Google's brilliant (not!) use of "Voice" for the name of a service makes searching impossible to find help on the app. (Google Voice Dialing, as in Dialing with the Google Voice cloud app)
I'm actually using google voice for a second phone line I use with clients. It rings on my desktop and forwards to my cell. I would like to be able to dial out from my G3 using Google Voice so that the callerID that gets sent is my office number, not my cell number. As I said, if I select a contact from the GoogleVoice app, it asks whether to dial with the GVoice app (which goes through a telephone gateway with the Office CallerID), or to dial with the native phone app, which would send my cell phone CallerID.
Click to expand...
Click to collapse
My apologies, usually people mean google now, I don't use google voice do I can't offer any advice, but I hope you find an answer.
Sent from my LG-D850 using XDA Premium 4 mobile app
Groove ip should enable your google voice number to be the native caller id.
3nJo1 said:
Groove ip should enable your google voice number to be the native caller id.
Click to expand...
Click to collapse
Thanks - I'll give it a try; that's a VoIP solution though, right? I was hoping for an ability to direct dial (from the gv app). I'm still discovering some of the weird things that work better under iOS than android, and am kind of surprised when it's the native Google stuff that is "behind".
Yehp, it's done wonders as my office phone, you could at the least have it request permission when dialing to which number you'd like to use, just a click away, about the same or less amount of clicks you'd use compared to going into gv, selecting a contact, and dialing. With groov normal contacts, select or dial, await popup for which dialer you wish to use, and bam!
If you go into the Google Voice app on your G3 and then go into the Settings for the Google Voice app, you should see an option entitled "Making calls". In that section you have 4 choices to select from for how you want Google Voice to behave when you make a call from your phone using the native phone app:
1) Use Google Voice to make all calls
2) Do not use Google Voice to make any calls
3) Only use Google Voice for international calls
4) Ask every time I make a call
It sounds like you'd prolly want to go with option 4. That way when you go into the Phone app on your G3 and dial a number to place an outgoing call, Google Voice will pop up and ask you if you want the outgoing call to be placed with either your Google Voice number or your "real" phone number that you got from your carrier. This way you have the choice presented to you for every outgoing call you make from your G3.
I've used Google Voice for years now and this is how it's always worked. I use option 1 for my own needs on my cell phone because I just give everyone my Google Voice number and never give out my "real" cell number except to a few choice friends and relatives, so I always want my outgoing calls to show my Google Voice number to the person I'm calling.
Hope that helps you out.
That works too ^^^^^^^^
The thing is I started using groove when google voice would not allow me to make any calls using the app its self ....
*edit*
I forgot before I said that, yes you can make calls with gvoice, but your caller id will be some other number.
GrooVe IP will allow you to make a call whether on wifi or data (note the full ver is the one that allows the data call) Google's a thing..... and it will also show your gvoice number as the number you are calling from, as well as you can recieve calls to your device instead of just acquiring a voicemail to call back from....
[SOLVED]
Okay, so something that was installed, or uninstalled, as I was fiddling with the phone caused GVoice to lose its hook into the calling processes. Uninstalling GVoice and then reinstalling (from the Play store) re-attached it and now it seems to be working correctly. Thanks for everyone's suggestions!
ranphi said:
If you go into the Google Voice app on your G3 and then go into the Settings for the Google Voice app, you should see an option entitled "Making calls". In that section you have 4 choices to select from for how you want Google Voice to behave when you make a call from your phone using the native phone app:
1) Use Google Voice to make all calls
2) Do not use Google Voice to make any calls
3) Only use Google Voice for international calls
4) Ask every time I make a call
It sounds like you'd prolly want to go with option 4. That way when you go into the Phone app on your G3 and dial a number to place an outgoing call, Google Voice will pop up and ask you if you want the outgoing call to be placed with either your Google Voice number or your "real" phone number that you got from your carrier. This way you have the choice presented to you for every outgoing call you make from your G3.
I've used Google Voice for years now and this is how it's always worked. I use option 1 for my own needs on my cell phone because I just give everyone my Google Voice number and never give out my "real" cell number except to a few choice friends and relatives, so I always want my outgoing calls to show my Google Voice number to the person I'm calling.
Hope that helps you out.
Click to expand...
Click to collapse
Just a clarification for future searchers - yes, this is supposed to be how it works but somehow my phone stopped doing this. No matter what the setting was, dialing from the phone app dialed with the cell number, and choosing a received message or missed/placed call from the Voice app would dial using the Google Voice interchange. It was weird and, apparently, very unusual behavior.