Database Users

Voice Talk not doing voice dial when screen is locked

Hi guys,
I have been trying to find answers for this problem ever since i bought my Galaxy S2..but no luck so far.
The problem is trying to voice dial someone while the phone is paired with a bluetooth headset and on standby/screen locked mode. In other words i want to be able to voice dial someone when my galaxy is in the pocket instead of having to unlock the screen and go for voice dial and then say command which negates the whole point of having voice dial.
So far when i press the bluetooth's button, the phone goes - "what would you like to do" and then i try saying ''call (person)" but the phone seems to be doing nothing after that..but when the screen is unlocked and i do the same thing, it actually does dial(no point because if i am able to take the phone out and unlock it, i might as well dial it instead of voice). What really hits me is that the bluetooth actually does trigger the voice talk application and the phone requests me to say what i want to do but after that nothing happens.
Can you guys tell me whats going on? This problem is really making me hate this phone because the phone boasts so many ads about voice dialling but it cannot do a simple voice dial which is possible on ancient phones. Cheers

I've been playing with this for the past couple of days and here's what I've learned. It's complicated because there are multiple settings that effect each other. The phone has to be on to use Voice Talk. It can be locked, but has to be on and active. In other words, Voice Talk won't wake the phone up if it was shut off with the on/off button. Also, the app has to be in the foreground for it to listen. If you go to the home screen or launch another app its no longer active and listening.
Also, similar to the OP, my headset reacts strangely when I use its command button. When I push the button and say "phone command," it says "activating your phones inbuilt calling features," and then says "this feature is not supported on the connected phone." But, after that, Voice Talk is still listening but acts wonky. Instead, I set Voice Talk to Listen Over Bluetooth and I don't have to push anything - I just say Hi Galaxy. OP, I bet your headset's experiencing something similar. Try turning on Listen Over Bluetooth and Wake Up Command and then just say Hi Galaxy to start Voice Talk. I bet it works. Don't forget you can also set Motion to on and then just tap the phone twice (even if its locked) to activate Voice Talk. I'm guessing that uses less battery on both the phone and headset then leaving the Wake Up Command on.
Here's my take on each of the settings:
Listen Over Bluetooth
Has to be on for Voice Talk to work via a headset. If not, you can hear the prompts through the headset but Voice Talk is listening through the phone's built in mic.
Auto-Start Listening
I haven't figured this one out. Either off or on the phone seems to behave the same way. The best I can figure is that Voice Talk starts listening immediately the first time its opened instead of having to tap the button to make it start listening.
Wake Up Command
If Listen Over Bluetooth is active, the Wake Up Command has to be on for Voice Talk to hear Hi Galaxy.
Driving Mode
Is really mislabeled. All it does is announce new e-mail (but not read them) and read text messages.
So that's my take. I'd be interested in everyone else's experiences and if they've learned anything different or better.

BarryH_GEG said:
I've been playing with this for the past couple of days and here's what I've learned. It's complicated because there are multiple settings that effect each other. The phone has to be on to use Voice Talk. It can be locked, but has to be on and active. In other words, Voice Talk won't wake the phone up if it was shut off with the on/off button. Also, the app has to be in the foreground for it to listen. If you go to the home screen or launch another app its no longer active and listening.
Also, similar to the OP, my headset reacts strangely when I use its command button. When I push the button and say "phone command," it says "activating your phones inbuilt calling features," and then says "this feature is not supported on the connected phone." But, after that, Voice Talk is still listening but acts wonky. Instead, I set Voice Talk to Listen Over Bluetooth and I don't have to push anything - I just say Hi Galaxy. OP, I bet your headset's experiencing something similar. Try turning on Listen Over Bluetooth and Wake Up Command and then just say Hi Galaxy to start Voice Talk. I bet it works. Don't forget you can also set Motion to on and then just tap the phone twice (even if its locked) to activate Voice Talk. I'm guessing that uses less battery on both the phone and headset then leaving the Wake Up Command on.
Here's my take on each of the settings:
Listen Over Bluetooth
Has to be on for Voice Talk to work via a headset. If not, you can hear the prompts through the headset but Voice Talk is listening through the phone's built in mic.
Auto-Start Listening
I haven't figured this one out. Either off or on the phone seems to behave the same way. The best I can figure is that Voice Talk starts listening immediately the first time its opened instead of having to tap the button to make it start listening.
Wake Up Command
If Listen Over Bluetooth is active, the Wake Up Command has to be on for Voice Talk to hear Hi Galaxy.
Driving Mode
Is really mislabeled. All it does is announce new e-mail (but not read them) and read text messages.
So that's my take. I'd be interested in everyone else's experiences and if they've learned anything different or better.
Click to expand...
Click to collapse
Thanks for this detailed reply. I think at some point I have tried these settings but not sure if they were in the exact matching order. I will give it another go with everything set up to the way you have mentioned and see what I get. I am sure I am very close to actually getting it to work though..fingers crossed ..and yes if anyone else have different combinations of settings or ways they got it to actually work from a locked screen, please share it here. Thanks.

BarryH, I did try those exact settings like you had mentioned but still no luck. On triggering the voice talk with bluetooth headset's button, i can hear voice talk say "what would you like to do?" and does not respond to anything i say. (while screen is off).
I am thinking of installing Vlingo and trying to get that to work this way? Not sure if it would make a difference though.

vijith555 said:
BarryH, I did try those exact settings like you had mentioned but still no luck. On triggering the voice talk with bluetooth headset's button, i can hear voice talk say "what would you like to do?" and does not respond to anything i say. (while screen is off).
I am thinking of installing Vlingo and trying to get that to work this way? Not sure if it would make a difference though.
Click to expand...
Click to collapse
If you do what I suggested you don't have to push the command button. The phone will be listening for the "hi galaxy" command all the time.
Sent from my GT-I9100 using XDA Premium App

I noticed the same thing, when paired with my car, the phone does not respond to pressing the button on my parrot if the phone is locked
I disabled the factory lockscreen and now use widget locker instead, problem has gone away

connectsys said:
I noticed the same thing, when paired with my car, the phone does not respond to pressing the button on my parrot if the phone is locked
I disabled the factory lockscreen and now use widget locker instead, problem has gone away
Click to expand...
Click to collapse
I was thinking of trying this next as I have run out of options..so you say it worked? Then I will get widget locker and see how I go. So let me get this straight - i get widget locker and use the lock screen that comes with that or using widget locker i disable the stock lock? Or I should disable the stock lock from settings and then use widget locker? Cheers

yea disable stock lock in settings and then use widget locker only for lockscreen

connectsys said:
yea disable stock lock in settings and then use widget locker only for lockscreen
Click to expand...
Click to collapse
Tried this last night and unfortunately its still doing the same thing. On holding the bluetooth headset's button while the phone's screen is off I can hear the phone go "what would you like to do" and right after this i say commands like "call (someone)" but nothing happens. When the phone's screen is on, it actually works when i do the same thing which just surprises me to as why. Also when the screen is off and voice talk not on the front screen the wake up command doesnt work. So again a person has to leave his screen on (without letting the phone go to standby) and leave the voice talk app running for voice dial to work.
And to make things worse the double tapping with motion turned on settings doesnt bring up voice talk when the screen is off..again putting me in the same situation. The only way voice talk work on this phone is when the screen is on so far which isnt really practical in situations you would want to use voice commands..i hope samsung or google brings a better solution to this issue because this phone's got so much boasting about being able to voice command but isnt able to perform what an iphone or old nokia do

If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!

k1sr said:
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
Click to expand...
Click to collapse
I cant agree more about it being counter-intuitive..and yes its not nice the voice prompts coming through the phone but i remember once somehow the voice prompts did come through the bluetooth headset i dont know how. Like you said something is not letting it operate properly, like blocking it. I havent used this Tasker but have used task manager like apps in the past. So you believe you could try to figure out a fix for this..i appreciate your efforts because I am just lost at the moment. Let me know how you go mate. And I will let you know if I get around this issue too. Thanks mate

k1sr said:
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
Click to expand...
Click to collapse
Ok i found a way to get this voice dialling to work when the screen is off but not using a bluetooth headset, instead the wired headset for the time being.
So I can trigger voice dial when the phone is in the pocket and voice prompt comes to the headset, i say command and it works . I dont mind it working for the wired headset as that is good enough for the time being while driving. If you need to know how i got this done just give me a buzz. There are two pieces of software that I got to set this up. Cheers.

I just deleted built in vlingo crap and took generic Google voice dialer apk from my nexus s. Plus side you don't have to be connected to net to dial contacts and I can hear reply in headset as well.
Sent from my GT-I9100

[Q] Very specific problem with voice dialing from bluetooth headsets

Hi everyone,
First off, I'd like to start by wishing to everyone happy Holidays!
I have been literally searching all over the Internet for any information regarding the issue I am about to describe in detail and since no solutiuon was found, there's nothing left for me to do but ask for help, and hopefully get the right answer. That's why I want to be as specific and informative as I can.
The problem I am having is this; I recently purchased a new Jabra Motion bluetooth headset and decided to start using the voice dialing function on my Galaxy S4, since it works very well (when it works) and is really a breeze, especially while driving.
In short, the problem is that the S4 completely loses audio (other party hears nothing as well) after initiating a call, via voice dial commands through any bluetooth headset (I'll get to that). When that happens, the phone has no in-call audio whatsoever (with headset on or off, with speakerphone or earpiece on), no matter how many times I start or receive a call and nothing brings audio back, except a reboot from the i9505's power button menu. All other audio works, like videos, unlock sounds, ringtone, music, even the little chirp right before the other party's phone starts ringing and the hangup chirp can also be heard. The worst part is, that it occurs completely at random, it can happen on the 1st time I voice dial or the 10th time, for example. The problem has not shown itself, when initiating a call normally or picking up with a headset connected, before audio gets lost.
Before purchasing the Jabra Motion I've been using an earliest model Jawbone Icon and had never even tried the voice dialing feature on any previous phones or the S4. After encountering this problem I tried to test whether or not it would happen when using that headset, the result was yes, so it is safe to say it will happen when using any bluetooth headset, with the same randomness.
This is what both headsets launch on the phone, when attempting to voice dial:
View attachment 2474439
The phone itself is a completely stock and un-rooted 16GB Galaxy S4 i9505, running the latest available Jelly Bean 4.3, build: XXUEMJ7.
The headsets are always connected to 2 devices simultaneously (in case that might shed some light)
What I've tried so far (no difference made, at all):
- Toggled bluetooth off and on
- Tried unpairing and re-pairing both headsets on both phones, or only on i9505
- Tried factory resetting both headsets
- Tried to toggle, while in call, between speakerphone, earpiece, headset, turning off headset and all possible combinations
- Removed Jabra companion app and services app, then reinstalled, then tried without the apps installed.
- Cleared cache from both Jabra apps.
- Cleared cache from system apps such as dialer, bluetooth and Google Search.
- Contacted support of both Samsung and Jabra (huge waste of time)
Sorry for the very long post, but I want to be clear and comprehensive as possible. Any help would be highly appreciated.
Please no factory reset suggestions, I am aware of that possibility, but do not want to go through all the trouble to set up tons of apps and stuff again.
Thanks in advance to anyone willing to help!

Anyone?

Please?

[Q] S Voice won't activate from headset

Until yesterday, I was able to activate S Voice using my S4 headset when the device was locked. Now for some reason it will only work if I first unlock the phone first. The music controls still work when locked, but long pressing on the headset button no longer does anything. It's really frustrating cos I don't think I've changed anything, and it's a feature I use a lot.
Does anyone have any ideas how to fix this? I'd really appreciate any help with this.

Launch App with button bluetooth headset (G2 d802)

With samsung (s3, s4, s5) when I press the bluetooth headset button, it starts S-voice and voice commands work.
On g2, I press the button and nothing happens, why?
What can I do?
I tried to install several apps, without success!
Help me
thx in advance

ilrisolutore said:
With samsung (s3, s4, s5) when I press the bluetooth headset button, it starts S-voice and voice commands work.
On g2, I press the button and nothing happens, why?
What can I do?
I tried to install several apps, without success!
Help me
thx in advance
Click to expand...
Click to collapse
With mine it starts google search.
Did you configure the voice commands?

No! What should I do?
The problem is that when I press the headset button, nothing happens! You only hear a beep
But You work? Ex. With bluetooth launch?

raduzione
I activated google and now the "bluetooth headsets" but will not start anything!

Nothing?

seems inconsistent to me.
with the screen on, I get the voice dialer thing (not google voice search, the old school voice dialer)
with screen off, i get nothing. I tried bluetooth launch from the play store and didn't get it working there either.
I also tried this on my Nexus 5 with very similar results....although, I was able to launch google voice search for the first couple times, then it just stopped working.
FWIW, using an LG Tone+ headset and searching for ideas as well.
would love voice search to pop up with the screen off.

Hi,
I have a similar problem with my car bluetooth "talk to dial" button.
When I pair my G2, this button is disabled; when pairing other phones (Nexus 4, Galaxy Nexus) the button is active and starts google now.
I think this is related with the HFP protocol. Any ideas on how to fix this?

turdbogls said:
seems inconsistent to me.
with the screen on, I get the voice dialer thing (not google voice search, the old school voice dialer)
with screen off, i get nothing. I tried bluetooth launch from the play store and didn't get it working there either.
I also tried this on my Nexus 5 with very similar results....although, I was able to launch google voice search for the first couple times, then it just stopped working.
FWIW, using an LG Tone+ headset and searching for ideas as well.
would love voice search to pop up with the screen off.
Click to expand...
Click to collapse
Works on display on? What ROM do you have?
I turned on screen does not work, nothing happens!

ilrisolutore said:
Works on display on? What ROM do you have?
I turned on screen does not work, nothing happens!
Click to expand...
Click to collapse
CM11.
with display off, It triggers voice dialer.
with screen on, it triggers google voice search.
I'm trying to work with tasker to get this thing working...but I'm not a tasker power user by any means, so I dont have high hopes

[Q] Bluetooth / Google now

Hey,
I'm running the 9505 s4 4.4.2.
For the first time since the nexus one I think I've run into an issue no android phone can get around.
I ride a motorcycle and picked up the Sena 20s Bluetooth headset.
This is my first Bluetooth headset and something I've waited over a year for.
The issue is the dedicated phone button to access your device through voice.
By default this button launches voice dialing on android instead of Google now.
With iPhone it launches siri.
I have tried to reassign the button to Google now but this only works if the device is not locked.
Is there any way around this?
Is there any device that will allow Google now to launch?
Any word if android 4.5 / 5.0 will fix this?
Perhaps a ROM that enables this?
Any advice is appreciated as I currently stand it is looking like iPhone is the only option.

Another option may be the motto x with active listening.
I've heard Google may make this available to all devices, but I was under the impression that this "always listening" is completely Dependant on hardware?

I have the same problem!
I have this exact same problem. Even when the phone is unlocked, google now is a bit spotty in loading when hitting the phone button.
Google did just release an update for Google Now that allows you to access google now from any screen, even the lock screen. That being said, the phone button on the Sena 20s STILL loads the phone dialer. The phone dialer is honestly not good and google now seems to be better to use for dialing people anyway. I wonder if we can submit a request to Sena to have this feature added. It's probably just the button calling up voice dialing instead of google now.
Try submitting a feature enhancement request, I might do the same.