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
I've never been much of a voice control person. Speaking outloud to my phone seems so impractical in public places.
However with a new car and new phone I'm starting to get used to it and the problem I'm finding is the things I can't do. I really want to be able to pause podcasts and music and stuff like that with voice. Connecting to bluetooth is another example.
One major annoyance is how setting reminders still needs you to click the screen.
It's a weird thing, I either don't want it or I want MORE !!!!
Part of me is just making a point and part wondering if people know magical voice tricks
I am hoping it is really trained to your personal voice. It will be funny when both the wife and I say "OK GOOGLE" at night and both phones takes commands.
thebitjockey said:
I am hoping it is really trained to your personal voice. It will be funny when both the wife and I say "OK GOOGLE" at night and both phones takes commands.
Click to expand...
Click to collapse
It tries to only respond to your voice. It usually works, but not all the time. (If another person with a similar voice tries it)
For some reason when I'm trying to use ok Google on any screen it is very spotty if it works or not. Occasionally it will work, but most of the time it just doesn't do anything. I have any screen turned on and I also have it turned on so that should detected when the screen is off. Very rarely do either of these work, & I have to go back to the home screen and hit the microphone for it to work. Anyone know how to fix this? I have tried retraining a couple of times also.
Google App --> Settings --> Voice --> "OK Google" detection --> Retrain voice model
The service that does that apparently gets killed after a while, requiring a reboot. It's happened to me a bunch of times, for more than a year now, since the N6. It happens with other random stuff too. The N6 has a "safety" (according to a Moto rep at their forums) feature that rings the first 2 seconds or so of a phone call or alarm/timer at very low volume before it rings at full volume. Also for when you switch to speakerphone. Whatever service causes this behavior does get killed as well after a while, and the N6's alarms and rings sound off at full volume immediately, until after a reboot.
Honestly...Google Now has gotten so unreliable for me I've stopped using it. It used to be flawless...but I feel like the more they add to it the worse it gets. I don't know. Maybe it's just me.
isimme said:
Google App --> Settings --> Voice --> "OK Google" detection --> Retrain voice model
Click to expand...
Click to collapse
I mentioned that I already tried that
tropazr said:
Honestly...Google Now has gotten so unreliable for me I've stopped using it. It used to be flawless...but I feel like the more they add to it the worse it gets. I don't know. Maybe it's just me.
Click to expand...
Click to collapse
Yes, the Nexus 5 was much more reliable.
First noticed this in Android Auto car mode app.
Occasionally it just wont respond to "OK google"
I can start my journey, make a call using "OK google"
This can work fine, but sometime it will just stop listening.
It seems to happen after a call was made. Its as if the Call app has not released the mic.
This doesn't always happen and seems inconstant. It can happen from any screen not just Android Auto.
My wife's S8+ behaves in the same way
Once it is ignoring the "OK google" command. you need to go into the google app and it will start working again
However it has on one occasion stopped working in the app. A reboot fixed that.
Anyone else having this trouble or have a theory or a solution for this?
I have been encountering the same issue as well.
wish34 said:
First noticed this in Android Auto car mode app.
Occasionally it just wont respond to "OK google"
I can start my journey, make a call using "OK google"
This can work fine, but sometime it will just stop listening.
It seems to happen after a call was made. Its as if the Call app has not released the mic.
This doesn't always happen and seems inconstant. It can happen from any screen not just Android Auto.
My wife's S8+ behaves in the same way
Once it is ignoring the "OK google" command. you need to go into the google app and it will start working again
However it has on one occasion stopped working in the app. A reboot fixed that.
Anyone else having this trouble or have a theory or a solution for this?
Click to expand...
Click to collapse
i had the same problem, it started with my s7 a few months ago..
when it continued on my s8 i was bummed.. i read somewhere to shut off the "My Feed" (previously called Now Cards i think)
i did that and have had no problem for 3 days now, the bummer is i like "my feed"
Still having this issue...... not as often though
Every other phone I've had has flip to mute. Every time a customer calls me at the butt crack of dawn I'm reminded to ask about this but I never do. I looked everywhere, or so I think. Is it gone? Any alternative?
Thaunks much,
Dave
TT_Vert said:
Every other phone I've had has flip to mute. Every time a customer calls me at the butt crack of dawn I'm reminded to ask about this but I never do. I looked everywhere, or so I think. Is it gone? Any alternative?
Thaunks much,
Dave
Click to expand...
Click to collapse
There is a new feature rolling out call flip to shhhh or something as part of something Google... Dunno when though
I'm sure there is also an app on the play store that would do that for you... And I'm positive you can do it with Tasker but it would require some setup that isn't super intuitive since Tasker does a bunch of things...
This has been baked into so many stock ROMS for years, I'm shocked this isn't in this one. I use tasker and have quite a few configs but I'd rather not have to rely on it for that. I'm not even sure which sensor i'd have to monitor to determine the unit was flipped over rather than just moved in my pocket while ringing.
Dave
TT_Vert said:
This has been baked into so many stock ROMS for years, I'm shocked this isn't in this one. I use tasker and have quite a few configs but I'd rather not have to rely on it for that. I'm not even sure which sensor i'd have to monitor to determine the unit was flipped over rather than just moved in my pocket while ringing.
Dave
Click to expand...
Click to collapse
Yes, missing that also.
Meh just setup proper quiet times via scheduled do not disturb. Takes care of those butt crack of dawn callers.
autosurgeon said:
Meh just setup proper quiet times via scheduled do not disturb. Takes care of those butt crack of dawn callers.
Click to expand...
Click to collapse
It isn't always during DND times. There are many times I'd just like to flip the phone. I can mute w/ the volume buttons but for some reason that does not send callers to VM and they just call again.
Dave
I think there is an app that will do this. I had this with the Moto x pure and I got twist for camera working for a time on the ph1via some app. The same app had a facedown silence mode if I recall. Problem is I can't remember what app it was.
Ok I think an app is what i need as I had 3 customers wake me up this AM. I'll google around.
Dave
I use AutomateIt Pro with accelerometer with two separate rules: one to mute on face down and one to unmute on face up; both with a 10% tolerance.
Sent from my PH-1 using Tapatalk
Thanks i tried a similar thing in tasker and I could only get it to vibrate. Audio silent never did anything. It seems since do not disturb is around that that silent feature doesn't work.
Dave