Hi everyone! Just got the Edge after switching to Verizon (damn Note not available thanks to recall) and I have a problem with Google Now not hearing any voice commands. If I have a bluetooth headset on it works fine, but using the phone's mic somehow doesn't work. I tested S Voice and that responds fine, but when I switch to Google it doesn't work at all. Already tried uninstalling updates and switching off permissions.
Thanks!
You know the screen has to be on, or the device has to be charging for Google Now voice commands to work right? Other than that, I don't know what the problem could be.
Yes, but even from inside the app, if I click on the mic, and hear the confirmation sound, the phone won't hear anything I say unless I deep throat the phone, and even then it misinterprets my commands. S Voice and the voice recorder app work fine, but just not Google Now.
alcaponed said:
Yes, but even from inside the app, if I click on the mic, and hear the confirmation sound, the phone won't hear anything I say unless I deep throat the phone, and even then it misinterprets my commands. S Voice and the voice recorder app work fine, but just not Google Now.
Click to expand...
Click to collapse
Is your offline language set to the language you speak? Verify that and also try to retrain the recognition. If that doesn't work I know that the S6 had problems with Google now working when S Voice wasn't disabled.
Sorry for the delay but yes it is. I have since gotten rid of the S7 Edge in order to get the Note...lucky me...but thanks for your help!
alcaponed said:
Sorry for the delay but yes it is. I have since gotten rid of the S7 Edge in order to get the Note...lucky me...but thanks for your help!
Click to expand...
Click to collapse
A little off topic, but you kept your note?
I had this issue when I had Cortana installed with Hey Cortana turned on. No chance you have that on is there?
Didn't see you had gotten rid of it....best of luck.
Outbreak444 said:
A little off topic, but you kept your note?
Click to expand...
Click to collapse
I'm waiting for the damn Pixel to ship. Just annoying because so many Note users have to buy different phones so it's getting backed up.
Related
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
How can we make the LG HBS-730 Blue tooth headset/headphone work with the LG G2 (clearly an aptx phone too)?
LG Voicemate shows "connected device does not support Bluetooth voice recognition"
With Stock ROM but rooted phone
1. It pairs etc just fine BUT the call button appears to do nothing?
2. Assuming we can get the call button to work how to get google to be the dialler (not sure what default is as headset/phone's call button appears to not function)
The Tone+ are compatible with the G2, By hitting the call button on my set I get the stock android voice control.
If I swipe up from the home button I can just say "ok google" through the tones and it works.
EGBTMagus said:
The Tone+ are compatible with the G2, By hitting the call button on my set I get the stock android voice control.
If I swipe up from the home button I can just say "ok google" through the tones and it works.
Click to expand...
Click to collapse
huh? how is it possible that yours does that yet mine doesnt?
all the other buttons work except for the call button
Mine works perfect. Works with AptX too after I forced that enabled on my phone. Voicemate and Google. Phone button brings up stock android voice commands. VS980.
Steamer86 said:
Mine works perfect. Works with AptX too after I forced that enabled on my phone. Voicemate and Google. Phone button brings up stock android voice commands. VS980.
Click to expand...
Click to collapse
hmmm wonder if Verizon has slightly different software?.....
How did you force it to work with AptX and why force it when the box clearly states AptX? (least the AU model D802TA does)
evangelionpunk said:
hmmm wonder if Verizon has slightly different software?.....
How did you force it to work with AptX and why force it when the box clearly states AptX? (least the AU model D802TA does)
Click to expand...
Click to collapse
I'm on LG-D800 AT&T and aptX was not enabled when I bought it. Maybe yours is. Look at this post on how to check is aptX enabled or not and if not how to enable it. BTW, I'm on CleanROM and call button on HBS730 initiates voice dialer.
I forgot a link;
http://forum.xda-developers.com/showthread.php?p=47084027
thanks alex I went ahead and followed those steps.
I also unpaired and repaired the device and now HOLDING the call button down (as opposed to just pressing it) autocalls the last number dialled. hmmmm
Voicemate still doesnt recognise it
That is how holding the button is suppose to work. Given it a couple quick clicks? There is a slight lag every once and a while due to sleep. Odd yours is not working... Also, Verizon's isn't displayed or enabled out of the box.
Steamer
On HTC One just have to click it once (not hold it down for a second or so).
Just checked and on CM single click does result in voice dialler popping up etc ie working properly hmmm
evangelionpunk said:
thanks alex I went ahead and followed those steps.
I also unpaired and repaired the device and now HOLDING the call button down (as opposed to just pressing it) autocalls the last number dialled. hmmmm
Voicemate still doesnt recognise it
Click to expand...
Click to collapse
There is one more thing you should try on stock ROM. Disable Voice Mate. It's useless anyway. Maybe LG HBS730 is having a conflict with it.
The native way the button works for redial is hold... I may be confused as to what you meant. I use the Tone+ every day. A single quick push works 99/100 times for me for voice command. That is very odd, works all over for me. I am on Verizon's variant though. Yeah, Voicemate is subpar to Google's search, and Google searches the phone anyhow. Its only useful to make fun of, or I have just yet to find out any good use.
evangelionpunk said:
thanks alex I went ahead and followed those steps.
I also unpaired and repaired the device and now HOLDING the call button down (as opposed to just pressing it) autocalls the last number dialled. hmmmm
Voicemate still doesnt recognise it
Click to expand...
Click to collapse
I just did this and it's amazing solution for me. Maybe it will work for you as well. With press of the call button on your Bluetooth headset you'll start Google Now Voice Search. From it, you can dial, redial, navigate, play song or album, launch app, search the Web,... Even works with screen off.
Voice Mate? Nah... Google Now Voice Search is much better solution.
Look at post #30.
http://forum.xda-developers.com/showthread.php?p=46870972
Thanks! Now I can use Now instead of ****ty voice dialer.
2 simple commands is all I need
alex72 said:
I just did this and it's amazing solution for me. Maybe it will work for you as well. With press of the call button on your Bluetooth headset you'll start Google Now Voice Search. From it, you can dial, redial, navigate, play song or album, launch app, search the Web,... Even works with screen off.
Voice Mate? Nah... Google Now Voice Search is much better solution.
Look at post #30.
http://forum.xda-developers.com/showthread.php?p=46870972
Click to expand...
Click to collapse
Thanks this worked perfectly but the fact is Google Now doesn't work well.
What I would like to see is when I push the Bluetooth button on my headset, it opens the Voice Mate application.
I really just want to be able to say:
1. "Play Music" to start shuffling through my on board music, or Google Play music either way (it's all the same)... Google Now can't do this at all as much as I've tried saying "Listen to <song/band/album name>".
2. "Call so and so" to make phone calls. The system Voice Dialer App works better for this than Google Now.
Google Now may work better in general if I am actively using my phone with my eyes and hands but to me the idea of using voice commands is so that you don't have to look at or touch your phone. My Lg Tone + opened S Voice no problem on my SAMSUNG Galaxy Note II (on older version of Jellybomb... 12.1 I think it was)... Why does the LG Tone + not open Voice Mate by default on the LG G2? I don't get it... this seems like a given for LG.
That's enough ranting lol. I love this phone so far. Anyway if anyone can bump this to a developer or something it would probably be relatively easy for a smart person to fix... I am dumb I just follow the smart people in this world
Thanks yall! I hope we can figure this out. :laugh:
My testing with Voice Mate and Now has reverted me back to stock commands. Just works. None work well enough.
Yea G Now and Voice Mate both don't work that well but for simple commands like "Play Music" and "Call Steve" Voice Mate works fine.
I got the update that enabled the ok google hot word from anywhere, but for some reason, I cannot get it to recognize my voice in the training screen. I have to be screaming at it for it to pick it up. With my N7, it works perfectly, no screaming required
Anyone have this problem? Oh, and If you don't have it already, follow this: https://plus.google.com/app/basic/stream/z12sczagllb1inism235gtbp1mb2j3qb204
bump.
I also noticed something else. Even in the voice recorder app, if the phone is more than a foot away, it doesn't pick up the sound very well. Is this the same for everyone?
This suggests that you may have issues with the microphone. Is your in-call quality good?
Right basically I got a g2 a couple of weeks ago and loved it but it started developing call issues where the person on the other end couldn't hear me very well or I sounded muffled (I swapped phones with someone during a call and it did sound awful) now I've tried the tutting noise cancellation thing of in call settings and a blast of compressed air.
but I was wondering if when I changed the battery a few days ago whether I may have dislodged something slightly and was wondering if anyone knew exactly where the mic was and what to look for. Now I don't mind changing the mic and everything else over as it was fairly easy doing the battery but thought I'd ask on here before ordering more parts
Do you have ok google from any screen turned on? I had the same problem, but after I turned off that option my calls are back to normal.
Sent from my Xposed G2
Ah not tried that one will give it a go, cheers
I have the same problem, but it only happens when I'm taking to them while laying down (thus the phone is parallel to the ground).
Are you laying down when this happens?
hootowlserenade said:
Do you have ok google from any screen turned on? I had the same problem, but after I turned off that option my calls are back to normal.
Sent from my Xposed G2
Click to expand...
Click to collapse
Thank you that appears to have done the trick might have to look into it though seems a bit daft offering a feature that messes up your calls, and I quite liked having it... Battery replaced, new white back cover on, next up is to try root it again and chuck cyanogen on it
mackster248 said:
I have the same problem, but it only happens when I'm taking to them while laying down (thus the phone is parallel to the ground).
Are you laying down when this happens?
Click to expand...
Click to collapse
No, but I do like the idea of my phone being lazy though and not working properly because it's lying down
I'd like to see a software patch that disables google now when a call is in progress... Pointless to be talking to someone and they hear you say "ok google" anyway... Maybe the solution is on Google's side of the equation. Shouldn't google be able to make some code telling the service to stop when a call is in progress, then reactivate once the call has ended? The service is pretty much useless during a call anyway, unless you want the other party to hear what you're searching google for.
Sent from my Xposed G2
chrisgrim said:
Thank you that appears to have done the trick might have to look into it though seems a bit daft offering a feature that messes up your calls, and I quite liked having it... Battery replaced, new white back cover on, next up is to try root it again and chuck cyanogen on it
Click to expand...
Click to collapse
Messes up the stock alarm too
hootowlserenade said:
I'd like to see a software patch that disables google now when a call is in progress... Pointless to be talking to someone and they hear you say "ok google" anyway... Maybe the solution is on Google's side of the equation. Shouldn't google be able to make some code telling the service to stop when a call is in progress, then reactivate once the call has ended? The service is pretty much useless during a call anyway, unless you want the other party to hear what you're searching google for.
Sent from my Xposed G2
Click to expand...
Click to collapse
I wonder what else it had messed up as I noticed since turning it off I've got track info back on my car stereo when I connect my phone, like you said gotta be a Google fix and not lg, no point having it if it is gonna cause issues
Have a issue with Google now not detecting my voice. It's also present in other apps like maps and YouTube. When I press the mic it doesnt pick up my voice.
I have to restart my phone then seems to work fine.
Any other people with similar issue ?
I just updated yesterday too
It's m on the T-Mobile g6 variant
Sent from my LG-H872 using Tapatalk
This is an issue with Google Assistant. Seems to happen every once in a while for some reason, at least it did on my G5 after it updated to Assistance. Retrain the voice model.
Sent from my LG-H872 using Tapatalk
I am as well facing the same issue on my G6
BuLLeT_PrOOf_wAlleTz said:
Have a issue with Google now not detecting my voice. It's also present in other apps like maps and YouTube. When I press the mic it doesnt pick up my voice.
I have to restart my phone then seems to work fine.
Any other people with similar issue ?
I just updated yesterday too
It's m on the T-Mobile g6 variant
Click to expand...
Click to collapse
I've had this. It's a big where Google thinks the mic is in use. Only fix is reboot that I've found
Either reboot or force close the Google app. Sometimes closing all apps in your recent apps menu works but I just force close the Google app
My "OK Google" voice detection keeps turning itself off in the settings. So I have to go in, turn it on and retrain the voice model. Super annoying.
vintagerock said:
My "OK Google" voice detection keeps turning itself off in the settings. So I have to go in, turn it on and retrain the voice model. Super annoying.
Click to expand...
Click to collapse
I saw an article on Android authority that advised users with the "ok Google" voice detections problem to go in to apps and clear all data for the Google app. Then reboot and retrain voice. It worked for me so far.
bowhunt2005 said:
I saw an article on Android authority that advised users with the "ok Google" voice detections problem to go in to apps and clear all data for the Google app. Then reboot and retrain voice. It worked for me so far.
Click to expand...
Click to collapse
I've done that and it still happens randomly. Force close the app or wait a little it comes back. I'm like 99% positive it's something to do with either Googles servers or some bug in the app somewhere
Yeah, it's a Google assistant issue. Happens across all three of my devices. My Google Homes have been acting wonky today, too.
Sent from my LG-H872 using Tapatalk
I had this issue up until the last update.
Clear the Google app data by going to Settings – Apps – Google app – Storage – Manage Space and tap on Clear all data. Then restart the phone and you should now be able to retrain the voice model. Go to Settings – Google Services – Search – Voice – “OK Google” detection – Retrain Voice Model. The voice command should now work as expected.
Hi,
I also have the LG G6 and unless I literally shout 'OK Google' it will not active Google assistant. Any ideas on how this can be fixed? I have tried everything already suggested.
Thanks,
Sam
Sam_6788 said:
Hi,
I also have the LG G6 and unless I literally shout 'OK Google' it will not active Google assistant. Any ideas on how this can be fixed? I have tried everything already suggested.
Thanks,
Sam
Click to expand...
Click to collapse
I have the same issue! Did you find a solution?
Same here.
I have to say ok google at least 6 times before it works.
Its an lg g6 problem...coz on my s8 plus it was perfect.
I have tried everythng to get my mic working again. It work fine if i record video. But calls, and whatspp, skype and other apps cant use the mic. Anyone...I contacted LG and they said they have to fix it? But to me it seems software related.
AsuraDas said:
I had this issue up until the last update.
Click to expand...
Click to collapse
The update fixed the issues for me.