Hello,
Can you tell me if you have the same problem? When I say "Ok Google" and the phone is locked, it takes a while for the assistant to open and listen to my request (sometimes a few seconds). I have already excluded the app to optimize for the battery but nothing changes.
Do you have a solution to this? Thank you in advance.
Related
Hi all.
I have recently started to use "OK Google" more and more frequenty, especially after getting my Moto360 watch.
Unfortunately I have realised that not all the "OK Google" functions that were supposed to work, is working.
Here I am especially referring to the following which I've tried and confirmed not working:
"navigate to ......."
"directions to ....."
"where am I"
"How many GB pounds in 1 dollar?"
"set alarm to 3 hours from now" nor "set alarm"
Actually most of the commands shown on the "ok-google-20-useful-things-you-can-say-to-your-android-phone" list from makeuseof doesn't work (do a Google to find the link )
My Nexus 4 has the latests 4.4.4 installed and "OK Google everywhere" is also working everywhere as supposed to, recognizing my "OK Google" command.
But instead of doing the actual action I'm asking/requesting it is always just doing a normal "search" on Google and displays the results
Any idea of how to solve this problem?
It should be noted that I am not located within the US if it has anything to do with this?
Best regards
Thomas Jespersen
With all of the settings correctly configured and several Google voice training programmings later, I am only getting about a 25% detection rate when saying "Ok Google" - especially when the phone is off or on the lock screen.
Anybody else have this issue?
For me OK, Google and the S Voice stopped working after an hour and never worked since then.
Magnesus said:
For me OK, Google and the S Voice stopped working after an hour and never worked since then.
Click to expand...
Click to collapse
Wow, really?
I'm very curious to see how others are fairing with this
Well, what is funny is that S Voice woke my phone a few times while I was playing games on my computer and once when I was watching a movie. I turned it off, something must be wrong with my voice pattern or something. :laugh: I never intended to use it anyway - was just playing with it - so it's not a huge loss for me. I think I might have blocked too many apps or I need to reboot or something because my fingerprint sensor also does strange things.
I just discovered Nova Launcher is causing this problem. When using TouchWiz home it works perfectly.
Anybody know how to get in contact with Nova Launcher?
Dissable svoice then go into google search app info and clear info. Now when you go into google now voice settings you can set it up with google recognition. It won't work when the screen off buy at least it works the rest of the time.
beno0055 said:
Dissable svoice then go into google search app info and clear info. Now when you go into google now voice settings you can set it up with google recognition. It won't work when the screen off buy at least it works the rest of the time.
Click to expand...
Click to collapse
I already have S Voice disabled, but I'm a little confused about what this would solve?
using hot boots causes this problem too. I had some problems with nova launcher but now it works just fine.
try to reboot and check you google now settings+ you can turn it on or off in nova's settings
I newly have a Moto 360 and I don't like that a) anybody shouting 'Ok, Google' next to my watch will enable voice listening, and b) that music playback stops once voice listening starts, e.g. when accidentally tapping the watchface.
Is there a way to just disable voice commands and let the watch just use tapping, swiping, and all this?
Yes this is a annoying behavior. If you put the wear device in flight mode nothing else will work. Even the time display will be wrong after some time. Because I didn't found a solution I've coded myself a little app which mutes the microphone, and disables the speech recognition:
Ups, Im not allowd to post a link. Simply search the play store for "mute wear mic"
have fun
flex48
Sorry, disregard post...
flex48 said:
Because I didn't found a solution I've coded myself a little app which mutes the microphone, and disables the speech recognition: [...] "mute wear mic"
Click to expand...
Click to collapse
Sorry that I answer late.
I would see it the same way as the person in the single review on Google Play — I would not trust this app, I would not even install it.
In the last time I'm more and more looking for Open Source software.
I really want to know what an app does.
So, as your app is not even a paid app, and a very small one, grab some non-copy license and post your source code, then I'll happily try your app.
Ever since I got my S7 Edge replacement from the Note 7, Google Voice is being troublesome. I can't get it to recognize my voice correctly, well sometimes. For example if I ask it to list "nearest restaurants near me" it will search for "Near Me" like if it didn't understand my first two words. Or other times It says "if you said something, I didn't understand you". I tried uninstalling and\or cleaning cache from Google apps, but doesn't fix the problem. Can this be a software problem or the phone Mic being defective?
dja2k said:
Ever since I got my S7 Edge replacement from the Note 7, Google Voice is being troublesome. I can't get it to recognize my voice correctly, well sometimes. For example if I ask it to list "nearest restaurants near me" it will search for "Near Me" like if it didn't understand my first two words. Or other times It says "if you said something, I didn't understand you". I tried uninstalling and\or cleaning cache from Google apps, but doesn't fix the problem. Can this be a software problem or the phone Mic being defective?
Click to expand...
Click to collapse
Are you saying "Ok google, nearest restaurants near me" or "Ok google..." *Wait for prompt* "nearest restaurants near me"?
I don't know if the wait would help, I know that I wait until I hear it make the noise before I continue to say anything. Give that a shot and see if it helps.
You can test out your microphone but I don't see a need to if you use the phone to talk to others and they don't have any problem hearing you.
What launcher are you using? I use Google now myself and I don't need the pause but am just used to waiting in case it didn't hear me when I say the command.
Also try going into Settings -> Applications -> Default Applications -> Phone Assistance App and see if you have Google App as the chosen app. Not sure if that would help but it's worth a shot.
I am definitely waiting until it gives the tone and then speak right after. I just noticed that the delay is on the Google app and not when using voice typing on the Samsung keyboard which brings up Google Voices well.
Simialar Issue
dja2k said:
I am definitely waiting until it gives the tone and then speak right after. I just noticed that the delay is on the Google app and not when using voice typing on the Samsung keyboard which brings up Google Voices well.
Click to expand...
Click to collapse
I am having a similar Issue on my S7 Edge. The "Ok Google" prompt works just fine but then the mic cannot hear me at all. If I am on a Bluetooth device it works just fine and all other voice apps including the Google Assistant in Allo work fine. I have done a factory reset, I have disabled S-Voice and all other apps that use voice work just fine. I am at a loss at this point.
rbdavis76 said:
I am having a similar Issue on my S7 Edge. The "Ok Google" prompt works just fine but then the mic cannot hear me at all. If I am on a Bluetooth device it works just fine and all other voice apps including the Google Assistant in Allo work fine. I have done a factory reset, I have disabled S-Voice and all other apps that use voice work just fine. I am at a loss at this point.
Click to expand...
Click to collapse
Make sure the Google App has permission to access your microphone. I would assume it does if the hotword detection works but still worth a shot.
I found a workaround that seems to work better on detection....
Have the phone at a distance and the top mic underneath your mouth level. Seems to give me less false positives this way, I have no idea why. Hope this helps.
What I did was uninstall the update for voice recognition and re download it. Helped immediately.
csstamatin said:
What I did was uninstall the update for voice recognition and re download it. Helped immediately.
Click to expand...
Click to collapse
can you explain how to do that. im having the same problem for a while now and it really irritating
ajkron said:
can you explain how to do that. im having the same problem for a while now and it really irritating
Click to expand...
Click to collapse
Sure, go into setting, then language and input. From there click on google voice typing then click offline recognition and u should be able to uninstall then reinstall the software for it. Hope that helps.
Hello all!
I am facing a very annoying issue:
For questions like "what's the weather?" Google Assistant/Google Now only shows the result without saying anything.
Similar behaviour when asking "drive me home": navigation starts without any announcement.
On the contrary, Google Assistant speaks/answers normally to phrases such as: "tell me a joke".
I've already tried any solution found on the Internet with no luck (check output, clear data, uninstall google search, etc.).
I'm pretty sure it's not account-related because I'm using the same account on a Nexus 5 without any problem.
anyone in a similar situation ?
Cheers,
Tony
tonycapuozzo said:
Hello all!
I am facing a very annoying issue:
For questions like "what's the weather?" Google Assistant/Google Now only shows the result without saying anything.
Similar behaviour when asking "drive me home": navigation starts without any announcement.
On the contrary, Google Assistant speaks/answers normally to phrases such as: "tell me a joke".
I've already tried any solution found on the Internet with no luck (check output, clear data, uninstall google search, etc.).
I'm pretty sure it's not account-related because I'm using the same account on a Nexus 5 without any problem.
anyone in a similar situation ?
Cheers,
Tony
Click to expand...
Click to collapse
yep. I went through all the settings, and no joy. had to quit, if anyone found something to workaround, would be great
Same here. I have this issue after the September update
+1
When I tell "Go home" to assistant it replies me with going home or similar and opens maps
Happy to hear I'm not alone ... so to speak..
I guess, we must wait for a bugfix, then...
Cheers,
Tony
Try to delet voice model in google setting ..voice ...and then again retrain voice model ....that solved problem for me
I'm also having this issue. I've tried installing text to speech data, changed speech output to on... And factory reset. Nothing works. If anyone found a solution, do update here. Not pleased with the phone ?
try deleting user data of google play services and google app
My MI5S is the same.
varun.gid said:
try deleting user data of google play services and google app
Click to expand...
Click to collapse
Done. Nothing new!
I also have the same problem, the assistant is giving audio feedback for a lot of queries and command.
Same here. Thanks for confirming that i am not the only one.
Might be the wrong thread to point it out but "ok google" by voice still gets triggered hence the detection is turned off. Is that normal? Can anyone else confirm this? I personally hate the feature, imagine your mic is always on just to catch those two words all the time. It's not the tin foil hat thing but the resource it uses for this feature ...
Cant reproduce it. I have it disabled on both on Google options and nova launcher
Sent from my Mi A1 using Tapatalk
Same issue here but...
You can use the phrase 'tell me about my day' it will announce the weather.
Ppfawade said:
Same issue here but...
You can use the phrase 'tell me about my day' it will announce the weather.
Click to expand...
Click to collapse
LOL. This is called cheating!
Also I confirm the problem.i tried everything.
Me too
I have that problem too on my OnePlus 3T running AOSPA.
Before I had the same issue when I was running FreedomOS.
I'm pretty sure that the logcat in the following screenshots shows the reason for it.
Unfortunately I can't find anything useful about it using Google...
I also think that this problem occurs only/mostly on Chinese phones, because most of the rare Google results refer to Chinese phones.