That buggy pos called Voice Talk from gs2, now called S-Voice, is back to being a buggy pos on gs3.
It has a hard time doing the actual voice recognition. I actually had to rename a contact because it just can't match simple phonetic words with contact names.
Sometimes it fails to recognize and dial a bluetooth call, and then you have to reboot the phone. Sometimes it will stop listening half a seconds after starting to listen (with a bt car kit).
Your standard google Voice Dialer is much better. It doesn't require an internet connection either.
Could someone please make a flashable zip to replace s-voice with voice dialer.
EDIT: BTW, if you disable "double click home button to start s-voice" in s-voice settings, the home button lag magically disappears.
Is everybody else's bluetooth voice dialing just god awful?
S voice is crap, so it's frozen. Google's Bluetooth dialer is just the worst thing I've ever seen. Has anybody found out how to get Bluetooth dialing working properly?
Why in the world can't they just make Bluetooth launch voice search?
Sent from my SAMSUNG-SGH-I337 using xda premium
switters1 said:
Is everybody else's bluetooth voice dialing just god awful?
S voice is crap, so it's frozen. Google's Bluetooth dialer is just the worst thing I've ever seen. Has anybody found out how to get Bluetooth dialing working properly?
Why in the world can't they just make Bluetooth launch voice search?
Click to expand...
Click to collapse
Old thread, but I'll revive it because I want to talk about the same subject. I agree with the OP, and I'm surprised how badly Android/Samsung handles blutetooth voice dialing. (My last phone was an iPhone 3GS, and voice dialing worked great from day 1 back with iOS 3 or 4, whatever it originally came with.)
I frequently use bluetooth voice dialing in my car, either from a headset or speaker phone. This is a must-have feature for me.
Svoice is completely unacceptable because it requires the phone to be unlocked. If you have to mess with the phone to unlock it, then that defeats the purpose of voice dialing. I do understand that Svoice can do other things besides voice dialing, things which should be restricted by the lock screen. What I don't understand is why they don't give the users the options to enable selected features such as voice dialing while the phone is locked. But they don't, so Svoice had to go.
With Svoice uninstalled or disabled, Google Search takes over the voice dialing duties. It works ok, or at least it used to with Google Search v2.x. One thing about it that I don't like is that it wakes the phone (activates the screen) when you initiate voice dialing, so you can end up with accidental screen touches while voice dialing (if you don't have a pass code, or if it hasn't timed out yet). The screen should remain locked.
In recent versions of Google Search (starting in v3.x?), they decided to make voice dialing worse! If a person has multiple numbers, you can not directly select one, you have to wade through a stupid menu every time.
Say for example I have a contact named Tim Brown who has 3 numbers: home, work, mobile
With Google Search 2.x, you can do this:
Me: Call Jim Brown Home (or I can even just say "Call Jim Home" if I only have one Jim in my contacts)
Phone: Do you want to call Jim Brown at home? Say OK or Cancel.
Me: Ok
Phone: dials
With Google Search 3.x it ignores the location and always presents a menu:
Me: Call Jim Brown Home (the word "Home" is ignored)
Phone: Say Select 1 for Jim Brown Home, Say Select 2 for Jim Brown Work, Say Select 3 for Jim Brown Mobile, or say Cancel
Me: (If I can remember which freaking number was Home) Select 1
Phone: Do you want to call Jim Brown at home? Say OK or cancel
Me: (Yes I do, you stupid phone, I just told you so!) OK
Phone: dials
What a pain in the butt that is. Ironically, if you open Google Search by launching the app (i.e. by interacting with the screen), then it will listen to the "Home" part. It just ignores it if you are voice dialing, which is where you really need it. Does anybody from Google actually use this stuff?
My solution is this. Since my phone is rooted, I have the option of uninstalling Google Search v3.x, find v2.8 on the Internet, and install it on my phone. Then be sure to ignore any updates in the Play store. This works good enough. I can select a specific number when voice dialing, and I can voice dial while the phone is locked. It still turns on the phone screen when I voice dial, but I can live with that.
Note that I don't use Google Now, so I don't care about any new features that are included in the newer versions of Google Search. If you do use Google Now, this solution may not be acceptable to you.
If anyone else has a better solution, please share it.
Thanks
I tried using the Bluetooth Launch app to activate google voice search instead of the voice dialer, but that didn't work while the screen was locked. So for now, I'm sticking with the solution mentioned above (i.e. using google search v2.8).
Anyone having this issue where s voice is randomly turning itself on when you are having a conversation with someone? It doesn't matter if it's in my pocket or not, it just happens. Even more annoying is you can't change the activation command to something less nerdy and obvious. Do you guys turn off the activate when screen is on option?
Sent from my SM-P600 using Tapatalk 4
another issue i have is if i tell s voice to "call marcos pizza" it only looks in my contacts. If I use google voice search, it looks it up and calls. Lame!
So, is that just how it is, s voice not as powerful? I'd really like to use the screen off wake up feature that s voice provides, but not if it sucks like this.
another issue i have is if i tell s voice to "call marcos pizza" it only looks in my contacts. If I use google voice search, it looks it up and calls. Lame!
So, is that just how it is, s voice not as powerful? I'd really like to use the screen off wake up feature that s voice provides, but not if it sucks like this.
I guess another solution is to keep the "hi galaxy" screen off wake up for when I need it and just use the double tap for regular google voice for most functions
Hi galaxy
open google search
lol
I have a Nexus 6P running the latest version Android 6.0.1. However, it is very odd that I never had this issue with my Nexus 6.
I have a car that just has a simple phone button (Bluetooth) to press which makes a sound and at that point I can simply say something like "Call Tom Brady". The phone usually uses my Verizon network to call the contact without any problems. I have been noticing that for a lot of my contacts 'Google Now' is trying to call them via Google Voice. The phone literally says calling so and so via Google Voice and then never connects. I don't know if this is because these contacts have a Gmail account or what, but it is very annoying and it never ends up connecting.
I bet if I uninstall the Google Voice app everything would work, but I need it for my visual voice mail.
One thing I have already tried is in the Google Voice App settings change it to 'Do NOT use Google Voice for any calls'.
This did not fix the issue.
Is there any Google Now settings or Google Voice settings that anyone can think of that might help me here?
Sync is somewhat limited and the "phone" button is useless... I have never ever used it to redial a number.... Don't think I have ever redialed a number.
So is there anyway to reconfigure that button to launch google voice search and use the car mics to search?
If not, is there a way I can redial a number and launch the voice search function? Maybe somehow launch it with sync? Idk.
Tried using automation apps but none of them have a "call end" function
For more information:
2013 Ford Edge, Sync2
Thanks!
No, you can do that with mirroring or sync 3 (2016+)