One of the critical safety features of any phone is the ability to place a call by voice command while driving.
The Samsung Galaxy S III has two major failings in supporting this basic need. Problems with S Voice and problems placing calls from a locked phone using a bluetooth headset.
S Voice supports voice dialing, although rather poorly. S Voice is slow to process what I've said (unlike voice typing in every other app) and frequently fails due to "network error".
But worst of all, if I set S Voice to never auto-dial (because I want to confirm that it hasn't misrecognized who I am trying to call), rather than reading me the name it matched and asking me if I want to dial, it only displays the match on-screen, which is useless when driving.
Even if I am willing to trust S Voice to auto-dial, there is still a fatal flaw in voice dialing that I haven't found a way around.
In the phone app, under call settings, Accessory settings for call, Outgoing call conditions, you are able to set whether, when using a bluetooth headset, you are able to use the headset's call button to place a call when the phone is locked.
The problem is the phone's definition of "locked".
If the phone's security is set to only need to swipe the screen to unlock, this feature works as you would expect. However, anyone who is concerned about security of their data would never consider this setting as locked.
If you have your phone's security set to require anything other than a swipe, be it face recognition, PIN, pattern or password, you are unable to place a call using your bluetooth headset's call button.
In other words, there is no safe way to place a call while driving unless you leave your phone with no security.
Ignoring for the moment the significant shortcomings of S Voice for dialing, as delivered to the customer you can not safely use your Galaxy S3 to place a call while driving.
Has anyone found a way to place a call when the screen is locked with a PIN?
Better yet, has anyone found a voice dialing app that works on the Samsung Galaxy S3 as a replacement for S Voice?
Any suggestions on how to get the Galaxy S III to match the capabilities of every other phone I've ever owned will be greatly appreciated.
You can use S Voice with a lock screen, under the setting menu for the application there is a option to unlock device with wake up command.
As for the time it takes to do a action depends on the data connection because the app requires data to work.. Mine is almost instant when I say something and so far it has worked well on responding to mu words.
Check the wake-up setting and try speaking clearer may help.
Wildman, for some reason, you just don't get what we are saying here. It's not working! Maybe it is just our phones? I don't know? Maybe your's works fine. But ours do not. At all. Ever. We want HANDS FREE phone operation. I have know that in my life and I want it again! LOL
I understand what you are reporting but mine works but after experimenting with my device I am starting to think its got something to do with the BlueAnt headset software I may installed and how my system is configured, I have S Voice disabled and once I activate headset the BlueAnt default option showed and once I told it what I wanted to do with speed dial option it defaults to the search app instead of S Voice.
It works fine for me but this may not be because the device now that you point it out... MyBlueAnt T2-BK-USEN-US,
Jabra 4050 bluetooth, Jabra Cruiser Bluetooth Car Kit and factory car stereo in my truck works voice dial fine.
I agree, and this is maybe the issue that causes me to return this phone. My Jabra Supreme has worked perfectly with 3 phones. This idiotic S-Voice is completely killing my ability to dial while driving. Even with the phone unlocked I will press my earpiece to dial, s-voice will start to tell me missed events (I couldn't care less) and then stop in the middle of the sentence. It usually takes 10 tries to get a call through. I get a huge amount of Network not found errors when trying to voice dial. Is there any way to disable S-Voice when using Bluetooth? If I could just get back to the simple communication between headset and phone I could keep this thing.
THANK GOODNESS, someone to feel my pain! LOL On some other forums, I have been attacked for complaining about S-Voice. All of you just described what I am going through. And like Adamant, I am probably going to take the phone back tomorrow. And, also, like Adamant, I don't want to! Dang it! I just want to use my phone HANDS FREE! I have contacted Verizon, Samsung and Jawbone and am more confused than before. Samsung said my phone was too smart for my bluetooth! And that there was nothing they could do about my phone not recognizing my sister's name. This is my favorite example: I say 'Call Rite Aid Pharmacy' simple enough. Phone says 'I can do an internet search for 'Call Rite Aid Pharmacy' !!!!!!!! About enough to make me want an iPhone! not really. But I am going to trade 'down' for a Razr Maxx, I think?
I had no problems with my MOTO Razr! oh yeah, one more thing...S VOICE <Comment deleted per the Verizon Wireless Terms of Service.> ...I could go on; but won't
Message was edited by: Verizon Moderator
S-Voice works like a vacuum cleaner, like a baby on a bottle, like the life-stealing machine on the Princess Bride, like the biggest black hole in the universe, like drinking a milkshake from a straw. And I can only hope that, even if Samsung and Verizon are denying it, that they will address it in the near future. If not, it will be the last Samsung phone I ever buy. C'mon everyone, you KNOW it is not working like it should! You love your phone; I love it too. But I expect a little more than this on a phone that is doing battle with the iPhone 5! S-Voice is so far off; it is laughable; if I weren't such a hindrance.
I agree S-Voice needs a lot of work but I do not use it to care, now as for comparing devices to be in competition with the iPhone 5 you are mistaken...
I do not consider the iPhone all that, I admit they opened doors with the first iphone but in my opinion they have been lacking on new technology since.
The S3 is a superior device in so many ways that the voice dial isnt a deal breaker... Now dont get me wrong I hope they fix the issue or at least allow access to the original voice dialer that other android devices are using.
I have been on the fence all day as to whether to take it back or keep it. I want to keep it; obviously. Just keep hearing 'thunder' Guess I'll probably keep it and hope that everyone admits to seeing the 'elephant' in the room and a fix will be made available promptly. Thanks Wildman; you are a very polite Wildman!
Got the Razr Maxx HD and I knew immediately that I had made the right choice. It paired with my Jawbone ERA in 10 seconds and was pleasantly saying, 'please say a command'...'calling Laurie Fike' And not ONE dropped call today! I am very, very happy that I followed my gut instinct and got the phone that is right for me. I hope that Samsung/Verizon will fess up and fix this beautiful phone. It was served up before it was done.
I finally gave in my Samsung Alias 1 for this Galaxy S3. I'm experiencing the same problem as you and more. Why is it almost impossible make a hands-free call? The voice2text is so good, yet the same excellence does not apply to voice recognition with respect to my contacts list which ought to be far simpler.
I know a Carla C**., a Carla B**., and a Karla B**. If I say the full name of one, nonetheless Galaxy offers all 3 (actually, it more often offers only the two that start with "C" or it says it can't find any of them(!!)) and it won't read them aloud 1by1 like my Alias 1 did. Instead, I'm supposed to look away from the wheel and use my hand to select the name I want. How is this progress?
Is there something I'm missing? The "Help" section on the phone is very limited. It sounds like I may need to get a RAZR.
The issue is that the voice dial and the voice search is two different apps and the one for voice dial does not utilize the online database used by other apps to increase accuracy..
I use Google Now as default voice command app but it can't be triggered from a Bluetooth headset.. hopefully someone work this problem out soon..
The sg3 is more like the B1, as in bronze age, when it comes to voice dialing. my motorola flip phone that I bought in 2005 had superior voice dialing features. With the G3 If I say call jim soandso (which requires initial touch pad input) the pos comes back with "you have more than one match for jim soandso." (yes all you g3 owners are cringing at that friggn sound). And that is the end of the voice dialing routine. the G3 then goes silent. But not before it finds every variation of jim in my contacts and locks them on the screen. It doesn't read the options after the initial command. So in reality the g3 does not have voice dialing. No matter what, you have to look at the phone and input with the touch screen! Are there any options! As a phone, the g3 isn't all that good.
Nothing like a little frustration to get you off your butt. After trying about five bizarro 'assistants" I found MyMotospeak on the android marketplace. Does one thing -- dials the phone. It is bluetooth compatible, gives feedback on how to use it better as you use it. Just say the name and it reads back the options: jim soandso or jim whatshisbucket and mobile, home, etc. Speak your choice and it dials -- plain, simple and works. app and widget. free!
No Wildman, not going online is not why voice dialing on the S3 does not work well. My Samsung Allias 1 never "went online" and it was excellent. The more likely answer is they simply discarded the old software. Someone else has said the RAZR voice dialing works well so I may yet give in and go with that instead. I'm not finding enough use with the S3 in other ways to justify having it, except perhaps for voice2txt for texting.
Sorry but the issue isn't old software but more like the data base that the application uses to understand commands given, the files for a OS like Android or Windows will use a larger amount of data so apps like this has started using cloud base data.. The bad part about this that the voice dial application does not have access to data like this.
Try this: go to the Google App store and download "Jeannie" and change all of the sound options to Google.
I had a hard time telling the system to call my friend whose first name is Ed. It would find his wife if I called for only the last name. I tired to edit the name in the contact list with no avail until I simply entered Ed as the prefix.
After I did these things, "Jeannie" seems to get it right. I am presuming that either I can set the phone to show the microphone to "Jeannie" in my car and the Bluetooth will either take my voice command or the phone will if I press the "Microphone" screen. For now, this will satisfy my needs. I expect that Samsung will be working on this as I had a Samsung regular phone back when and it worked with voice commands on Bluetooth devices.
I haven't used the Apple app, but this one seems pretty feisty.
Hi all -
I am glad I found these posts. I just downloaded Jeannie yesterday. I have been struggling for days trying to get my new headset - jawbone icon - to voice dial on my S3. I lost S-voice with my jelly bean update. And have tried several voice dialers and assistants so far.
One of the main things I think is happening to me is that my microphone is not "turning on" at the phone level. Everything seems to be working and the phone itself shows the dialer window and asks for input. but only give me a short opportunity to answer, barely enough time to say "call" and then closes. It looks like the mic icon is in the off state. If I would click it on, it would likely work but that defeats the purpose of hands free!
Any ideas? Any fixes? I have looked for days.... a reset is not a likely option. I have had this phone too long.
Thanks - RJ
I say remove S-Voice all together. It's crap anyway and who wants their phone to waste time talking to them when it doesn't work that well (yes, Siri is for people in the "apps" line). Before my gs3, I had a google nexus S with native android 4.2 (no one in the verizon world has this version yet) and google's voice system was AWESOME. Super fast, super responsive and no conversing ... just a well-functioning product for adults.
The latest version we have is 4.1.1 using a combination of S-Voice and Google Voice functionality. S-Voice is unfortunately used to launch apps and handle commands like "call so and so" or "call 401 ... " Voice typing and so forth are all native google.
Having just picked up the Galaxy Note 2 (running Jelly Bean 4.1.1), this inability to voice dial while pin-locked still persists. There is a setting from phone->settings->Accessory settings for call-> Outgoing call conditions - Make calls even when device is locked, but it does not appear to apply to the pin-lock. It does work with the swipe-lock, but that isn't exactly "locked", is it?
I got my s3 last week with a new Bluetooth earpiece and had the same problem, only intermittently being able to initiate a voice activated call, although I could receive a call fine. Technical support was no help. I downloaded and installed ATK. I know some people do not like the app, but I had used it with my droid x. I set it to crazy and wen through the ignore list carefully. The Bluetooth call making has not failed at all today. I do not use a pin code to unlock. I would give ATK a try.
I posted about using ATK to help the bluetooth problem, but that fix was not lasting. I dug a little deeper and found with Jellybean I was the proud recipient of Google Now, which also tries to use bluetooth and learn your preferences. I saw where Google Now was implicated in car bluetooth difficulties, so I turned Google Now off (Google Now - settings - off). S Voice still is not as reponsive as I would like, but it does place calls now (most of the time, if you are patient). MyMotoSpeak, mentioned above, was not compatable with my earpiece.
You can disable S-Voice: Go to Settings->Application Manager->All then choose S-Voice and select "Disable." I have a Motorola headset and after I disabled S-Voice, I was able to use MyMotospeak, which responds to the headset even with a pin-lock. I was given the chance to use Google Now as well, but I did not try to see if Google Now would respond to the headset while pin-locked. I am used to MyMotospeak and prefer to continue to use it while hands free. Hope this helps.
Guess I spoke too soon. I can get Google Now to start when I activate voice dialing from my bt headset (using bluetooth launch), but it does not seem to always work. *sigh* All my phones prior to this just *worked* with voice dialing. Why o Why can't this one just work as well? I would be *fine* with S-voice if it worked when the phone was pin locked. If samsung could just fix that problem... *sigh*
S-Voice does appear to fail with "network failure". I looked into this a bit. I disabled S-Voice and used the old one. It also fails when bluetooth is connected to a plantronics headset. So I turned off the headset and fussed around some more. Voice calling did work without the headset. But, the headset is really needed for voice usage. In many states, it is illegal to hold a phone while driving (ps, I approve of the laws!). So I fussed around some more, flipping various options (voice,music) and trying to power on/off and re-pair the headset and the phone. Somewhere along the line, the voice stuff started working again. Well almost. The S-Voice app screen could appear by selecting the app from the screen and it did not crash. But it wanted to search the internet for "Hello Galaxy" and showed a button to push. Pushing that button did nothing. But you can tap the microphone button and use the voice commands to do simple things. <mic> then "Stop" and it says "Canceled". I did lots of simple experiments.
I'm a software engineer. I can recognize a fundamental software bug in this. The Android software structure is Java based with little tiny blocks that all have to interact. But these blocks are built in an isolated "container" structure so system level functionality is hard to get a handle on. This bug appears to be of that sort and probably will be hard to fix. I expect a series of band-aides to come out. The thing is supposed to be a telephone first and a small computer second. There are laws covering how a telephone must be used while driving and this thing exhibits sporadic functionality for the basic functionality.
There is nothing wrong with the bluetooth in your cars or headsets. You don't have to worry about WiFi or 3G/4G/LTE/GSM/CDMA or any other alphabet soup. The problem is the software in the phone itself. Other phoe don't have the same problem.
Fix it, its broken.