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
My phone is not rooted. This just started this week. I have not adjusted any settings for quite a while so I am pretty sure I did not do anything to cause it.
Since getting my Note 3 in October I use the voice method of inputting text for email and sms quite often. When starting a message where I want to voice inpput, I click the microphone button and speak what I want to send. Works well for me. Thursday the phone started making a loud, very annoying, beep type sound whenever I launch this by clicking the microphone. It happens even when the phone is in silent mode. I checked the sound options in the phone settings and everything is set as it has always been. All system and keyboard sounds are turned off. I also tried another keyboard app rather than the phone default and it is the same with that.
Does anyone have an idea why this started and how to silence it? Thanks!
I guess this is not an issue for others here. I did find the exact problem on another forum and it started for him just a few days ago also. So maybe something updated automatically that caused this. We will see if more people start complaining about it. By the way we have tried a few different suggestions, including resets, but nothing turns off the noise yet.
0n edit: I looked at my apps to see what recently updated. One of the recent updates was to Google Search. I uninstalled all the updates to Google Search and the problem is gone. So it is a bug in the most recent update to Google Search that turns on that sound with no way to turn it off.
I flashed CLoudy 1.4 on my VZ980 a few days ago, and only today did I go the use Google Now and noticed the "Ok Google" hot word doesn't work. No problem, I tapped on the mic and get the familiar sound like the microphone starts to listen, but then it stops after 2-3 seconds and doesn't hear me at all.
SO I tried installing Open Mic+ to see if that works...and the hotword works flawlessly. With the screen off, I can say "Ok Google" and it turns on and changes to the google now interface and the mic button turns red as if listening and then turns off again.
There must be a check box or download I'm missing, but what? I've went thru the settings in google now and the hotword detection is on, setting all look correct.
I'm thinking it has to be a phone issue more than a ROM issue that is why I am asking here.
bump?
Xsoldier2000 said:
bump?
Click to expand...
Click to collapse
Wow, no one has this issue?
try the openmike+ threads
send from the jungle
I had this happen too on the stock rom, but determined it was g2 xposed causing the issue. Once I disabled long press to launch voice search, this stupid bug stopped. Really annoying, I feel your pain.
-VZW LG G2 VS980
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
Hello,
My new pixel 4xl is working great except for 2 reasons. The main one being I don't get turn by turn voice navigation. I get no voice at all when navigating. COnsidering I drive for Uber on the side this is very bad.
I checked all settings and they are all correct as far as I can tell - play over bluetooth and everything is on. Doesn't matter if I am on BT or not, nothing. I've tried rebooting of course.
Second smaller issue is no audio sound goes off when What's App messages come through. I've checked all those settings in Apps & NOtifications and they all look good. What gives?
pixelsquish said:
Hello,
My new pixel 4xl is working great except for 2 reasons. The main one being I don't get turn by turn voice navigation. I get no voice at all when navigating. COnsidering I drive for Uber on the side this is very bad.
I checked all settings and they are all correct as far as I can tell - play over bluetooth and everything is on. Doesn't matter if I am on BT or not, nothing. I've tried rebooting of course.
Second smaller issue is no audio sound goes off when What's App messages come through. I've checked all those settings in Apps & NOtifications and they all look good. What gives?
Click to expand...
Click to collapse
Try opening the Android Auto app. on your phone & check 'Driving Mode' is not selected to 'Do Not Disturb'. I had a similar problem where my Music app was not showing up & turn by turn voice navigation was muted.
After changing this setting AA now appears to work as it should. Sounds like you might have the same problem. Anyway, worth a try. Good luck [emoji106]
See attached screenshot...View attachment 4860981
Sent from my Pixel 4 using Tapatalk
Do you have captions enabled when there is voice? This may do closed captioning while silencing the volume until you adjust the volume.
Someone in the 4xl mentioned a similar issue. I think they worked out that they were on the maps beta. Coming out of that resolved the issue.