Google assistant is basically useless. - Google Pixel 2 XL Questions & Answers

I don't know if this is just me but I cant seem to get this damn feature to work. I've trained my voice to this thing a hundred times and still it won't recognize it. I have to say it 3 or 4 times and finally, once I scream it, it might work. I look like a damn fool. Is this how it's supposed to work? By the time it does work, I could have picked the phone up and done what i was asking manually. What about when youre driving, you ask?
More than not, in the unlikely event that it will work, the phone remains locked until I enter my password. I've set the unlock-by-voice to "on" and still it will never work. What's the point if I'm driving and when it finally does recognize me, I have to pick it up and unlock it?
Has anyone else had these issues?
I'm left thinking that if Google was really pushing Google Assistant as the next big thing, they've got A LOT of work to do.

Nah. It even recognize my voice in noisy room. Although not every command would heard perfectly if its too noisy. But in a normal siatuation, it pick up 95-99% of my command and do it properly

otonieru said:
Nah. It even recognize my voice in noisy room. Although not every command would heard perfectly if its too noisy. But in a normal siatuation, it pick up 95-99% of my command and do it properly
Click to expand...
Click to collapse
Any ideas?

try saying "OK GOOGOO"

redddog said:
I don't know if this is just me but I cant seem to get this damn feature to work. I've trained my voice to this thing a hundred times and still it won't recognize it. I have to say it 3 or 4 times and finally, once I scream it, it might work. I look like a damn fool. Is this how it's supposed to work? By the time it does work, I could have picked the phone up and done what i was asking manually. What about when youre driving, you ask?
More than not, in the unlikely event that it will work, the phone remains locked until I enter my password. I've set the unlock-by-voice to "on" and still it will never work. What's the point if I'm driving and when it finally does recognize me, I have to pick it up and unlock it?
Has anyone else had these issues?
I'm left thinking that if Google was really pushing Google Assistant as the next big thing, they've got A LOT of work to do.
Click to expand...
Click to collapse
Never had an issue with the Assistant. Works in 98% of cases. Could it be that the microphone on the phone is defect?

I don't think so. It seems like once it's woken up, it acts better. The super annoying part is when the phone hears me but requires me to input my unlock code. why wouldn't it just wake up?

jbr05ki said:
try saying "ok googoo"
Click to expand...
Click to collapse
"hey goooogo" "Hey! Ok!" Lol

Also using "Hey Google" which works a treat, by passes lock screen, and has a sweet voice!

I have the same problem. Sometimes it takes forever to activate, and sometimes it doesn't listen when it does. I'm also having constant gps issues. May rma soon
Sent from my Pixel 2 XL using Tapatalk

redddog said:
I don't think so. It seems like once it's woken up, it acts better. The super annoying part is when the phone hears me but requires me to input my unlock code. why wouldn't it just wake up?
Click to expand...
Click to collapse
Try add trusted voice to smart unlock

jbr05ki said:
try saying "OK GOOGOO"
Click to expand...
Click to collapse
You're a genius, this worked for me, I've been trying to use Google Assistant with screen off and this seems to work for now

redddog said:
I don't think so. It seems like once it's woken up, it acts better. The super annoying part is when the phone hears me but requires me to input my unlock code. why wouldn't it just wake up?
Click to expand...
Click to collapse
You have to go into Google Now>Settings>Devices>Phone>Unlock With Voice Match
That should take care of the issue.

Juansegovia20 said:
You're a genius, this worked for me, I've been trying to use Google Assistant with screen off and this seems to work for now
Click to expand...
Click to collapse
Wait seriously? I thought we were poking fun at the Italian grandmother trying to talk to the Google home...well, glad it worked for you lol.
PS if you don't know what I'm talking about, look it up on YouTube.

Related

"Okay Google" only works after I tap the screen

For about a week after I got the watch, there were no issues with the voice commands but now whenever I try to use the "Okay Google" command when the screen is off it won't recognize it. I have to tap the screen to turn it on, then try the command once or twice before it picks it up. I have tried a factory reset on the watch and rebooting it but nothing seems to work. Has anyone else experienced this issue?
Same for me
Try this ,go to your phone,disconnect Google now and then reconnect it again an program the voice command
YOYO41 said:
Try this ,go to your phone,disconnect Google now and then reconnect it again an program the voice command
Click to expand...
Click to collapse
How exactly do I disconnect Google Now? I've looked through all the settings in both the Google Search app and the Android Wear app but I couldn't find anything
Open Google now ,the part where you see the cards,go to settings, and you will see at the top how to disable Google now,in lollipop is that way
YOYO41 said:
Open Google now ,the part where you see the cards,go to settings, and you will see at the top how to disable Google now,in lollipop is that way
Click to expand...
Click to collapse
I see, is there any way to accomplish this on KitKat?
kkg720 said:
For about a week after I got the watch, there were no issues with the voice commands but now whenever I try to use the "Okay Google" command when the screen is off it won't recognize it. I have to tap the screen to turn it on, then try the command once or twice before it picks it up. I have tried a factory reset on the watch and rebooting it but nothing seems to work. Has anyone else experienced this issue?
Click to expand...
Click to collapse
does the watch have an always on mic? i've never been able to get the voice response to work unless the display is active.
640k said:
does the watch have an always on mic? i've never been able to get the voice response to work unless the display is active.
Click to expand...
Click to collapse
I don't think it has. Honestly think its working as intended. Screen must be active before command.
Chris_c81 said:
I don't think it has. Honestly think its working as intended. Screen must be active before command.
Click to expand...
Click to collapse
agreed.
OP to answer your question for using the watch one-handed, the idea of being able to twist your wrist to activate the watch is helping your situation. for me, i know that this is not reliable, but this is how the watch/software was designed.
i'm hoping the moto 360.2 is more moto X like. always on mics and ambient display.
640k said:
agreed.
OP to answer your question for using the watch one-handed, the idea of being able to twist your wrist to activate the watch is helping your situation. for me, i know that this is not reliable, but this is how the watch/software was designed.
i'm hoping the moto 360.2 is more moto X like. always on mics and ambient display.
Click to expand...
Click to collapse
Got it, I thought it had an always on mic. Thanks for clearing that up for me!

"okay Google always on" turns itself back off, lollipop

I've tried it with s voice both on and off. when I first turn it on after a reboot, it doesn't train the voice model, but it says it's on but doesn't work. It then turns itself off, and trying to turn it on results in the voice model training opening , then saying it completed successfully, then turning its self back off.
Help?
No one else has experienced this?
To shut it off...i think thats what u looking for?
Go to Google. .sertings...voice, then turn off voice detection
Sent from my SM-N910P using Tapatalk
same thing on mine, its grayed out and I've heard there is no fix for it yet.
Bloodgroup said:
same thing on mine, its grayed out and I've heard there is no fix for it yet.
Click to expand...
Click to collapse
Mine looks gray to me..but it still slides to shut off.
Mine too. Is anyone on stock kernel?
Gotta disable S voice
fatboypup said:
Gotta disable S voice
Click to expand...
Click to collapse
I disabled it. Works now thanks
ibcenu said:
To shut it off...i think thats what u looking for?
Go to Google. .sertings...voice, then turn off voice detection
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I'm trying to turn it on, but it turns it's self back off with no explanation. physically moves the slider back to the off position before my eyes. It's gone back to just being grey now, though
fatboypup said:
Gotta disable S voice
Click to expand...
Click to collapse
If you read the original post, it says I've tried with s voice and without
This really isn't unique to Lollipop, as it does this exact thing on mine which is still on kitkat. Sometimes I will hear the tone acknowledging the ok google, but will immediately hear another tone. Often the screen doesn't even turn on. Even more often it just never works, although it works pretty perfectly with the screen on.
It has nothing to do with disabling svoice, although it probably is related to Samsung's implementation of svoice. Once in a while, thE phone will fail to even acknowledge an ok google request, only to sometime later say, "if you're trying to say something I didn't get that." This seems to imply the microphone is locked in the listen position, but isn't working.

"OK Google" not working

Having lots of difficulties with "OK Google" on this watch. Bluetooth stays connected fine and so does wifi because i'm getting all my notifications instantly and it doesnt say that im disconnected. When I say OK Google the prompt comes up to speak...but only like 4 of the 30 times I tried did it actually work and not show the cloud symbol. I restarted the watch a couple times and the same thing happens, i've also done a factory reset since purchasing the watch 4 days ago. Thoughts? Thanks.
ultimatdan said:
Having lots of difficulties with "OK Google" on this watch. Bluetooth stays connected fine and so does wifi because i'm getting all my notifications instantly and it doesnt say that im disconnected. When I say OK Google the prompt comes up to speak...but only like 4 of the 30 times I tried did it actually work and not show the cloud symbol. I restarted the watch a couple times and the same thing happens, i've also done a factory reset since purchasing the watch 4 days ago. Thoughts? Thanks.
Click to expand...
Click to collapse
I found it to be very hit or miss as well.
Sent from my Nexus 6 using Tapatalk
I've not had it work once yet. The mic works as if I manually launch it everything seems fine.
I've tried restarts, factory resets & all the above. I'm pretty close to returning in all honesty as the voice launch is a huge deal for me!
I use my Huawei Watch with a OnePlus One on stock COS12.1 and have the same problem.
A lot of times when I use the watch to say "Okay Google" it will tell me it's disconnected. The only work-around I found was to quickly wake up the phone and it would start working right away. It seems like the internet pauses if my phone has been idle too long. I receive notifications in real time so I don't know what's really causing it.
I had the same problem with the huawei and a dutch HTC one M8.
The problem was gone after changing "Google voice typing primary language" from dutch in english.
And teach Google the sound of my voice in "OK Google" detection =>> From any screen.
Try turning off the restricted data for google app and google play services under Data Usage in settings.
ultimatdan said:
Having lots of difficulties with "OK Google" on this watch
Click to expand...
Click to collapse
I find it very hard for it to recognise my Australian accent. However, when I put on an American accent it works 100% of the time!
Any way of fixing that?
salada2k said:
I find it very hard for it to recognise my Australian accent. However, when I put on an American accent it works 100% of the time!
Any way of fixing that?
Click to expand...
Click to collapse
Did you try going into Google Settings on your phone? There's an option to retrain the voice model in there.
ts_mpls said:
Did you try going into Google Settings on your phone? There's an option to retrain the voice model in there.
Click to expand...
Click to collapse
HI mate, yes I've done that countless times to no avail unfortunately. It works fine on my phone, but it's like retraining the voice model has no effect on the Huwaei Watch.
salada2k said:
HI mate, yes I've done that countless times to no avail unfortunately. It works fine on my phone, but it's like retraining the voice model has no effect on the Huwaei Watch.
Click to expand...
Click to collapse
Dang, I was wondering about that. Sorry!

'Hey Google' vibrate prompt instead of beep.

So I just recently flashed a build of DU to my phone and when I say 'Hey Google' the phone vibrates to prompt me that the command was understood and it is ready to listen. On stock it always would beep instead of vibrating when I did this. I prefer the beep cause if I am not near my phone I know it is ready for a command. Is there anyway to change this? I've looked through all the settings I can think of and can't seem to find anything to change it. I'm probably just overlooking it. Thanks in advance!
If you turn on any accessibility option in setting you will get it back. Sadly this is the direction google has gone with assistant. There are huge threads on this since you can't tell if the phone is ready if you don't look at it (like in your car). Many people are irritated by this and google has pretty much told us all to take a jump.
Sent from my BTV-W09 using Tapatalk
ahent said:
If you turn on any accessibility option in setting you will get it back. Sadly this is the direction google has gone with assistant. There are huge threads on this since you can't tell if the phone is ready if you don't look at it (like in your car). Many people are irritated by this and google has pretty much told us all to take a jump.
Sent from my BTV-W09 using Tapatalk
Click to expand...
Click to collapse
Wow that sucks. Thanks for the info though man I got my beep back lol.

Google Assistant First Attempt Issues

Anyone here ever have the issue where when you activate GA after a while, it sits with the animation like it's waiting for you to say something but does nothing even when you talk?
The way around is to close it and reopen but it's annoying that it doesn't work every time on first try.
SageWilliams said:
Anyone here ever have the issue where when you activate GA after a while, it sits with the animation like it's waiting for you to say something but does nothing even when you talk?
The way around is to close it and reopen but it's annoying that it doesn't work every time on first try.
Click to expand...
Click to collapse
Are you using bluetooth headphones when that happens? It's happened to me before depending on the way I opened GA
xunholyx said:
Are you using bluetooth headphones when that happens? It's happened to me before depending on the way I opened GA
Click to expand...
Click to collapse
Nope no Bluetooth
I get a this once in a while and it sucks
Same here, really annoying..
SageWilliams said:
Anyone here ever have the issue where when you activate GA after a while, it sits with the animation like it's waiting for you to say something but does nothing even when you talk?
The way around is to close it and reopen but it's annoying that it doesn't work every time on first try.
Click to expand...
Click to collapse
I had this when I used active edge to activate the Assistant, appeared but did not hear me talking. If I said "Ok google" or used the button on bottom it worked.
If that's the same for you, in settings for active edge disable and enable the assistant feature and it should start working again.

Categories

Resources