'Hey, Google' command now rolling out to Assistant on Android phones

Ever since the Google Assistant first launched on the 2016 Pixel and Home, there have been some differences between the AI on both platforms. Google Assistant can do certain things on Google Home that it can't on phones and vice versa. Google's been working hard at bridging that gap, and in the latest attempt to do this, users are now gaining the option to prompt the Assistant on their phone by saying "Hey, Google."

You've been able to use this command on Google Home since its release, but the only way to get the Assistant's attention on mobile has been the classic "Ok, Google" phrase. There's nothing wrong with "Ok, Google", but "Hey, Google" is a lot more natural and just rolls off the tongue better than the other option. As someone who uses "Hey, Google" about 99% of the time with my Google Home rather than "Ok, Google", this is awesome news.

However, in that same breath, it's also got some people concerned.

A lot of users (myself included) have taken to using "Ok, Google" for their phone and "Hey, Google" for Google Home as to not trigger both devices at the same time. With "Hey, Google" now coming to Assistant on phones, it's much more likely that you'll turn on the Assistant on your phone and Google Home when just trying to get the attention of one of them.

If this sounds like a nightmare, fret not. You'll get a notification when the update reaches you saying that you can now train the Google Assitant to respond with the "Hey, Google" command, but you aren't required to do so if you don't want to. Use it if you want, or ignore it if you don't.

I've already gotten the option to use the "Hey, Google" command on my Pixel 2 XL, so keep an eye out for it on your device if you haven't seen it yet.

'Hey, Google' command now rolling out to Assistant on Android phones

I just whish Google would allow us to specify different wake words for each device. Like for example if I want to set an alarm on my phone I cannot do it by voice if I'm by my Google Home... Every time the Google Home answer and set it on the Home and not my phone... This doesn't do me any good when my phone is next to my bed and not the Home.

Not a fan of this change. Despite best software efforts, my phone and Google Home will occasionally both launch the assistant upon saying 'okay Google'.... My work around was to only use 'Hey Google's for the Home...

of course I'm still waiting for my free home mini promo, but I thought home and phones hearing your voice were supposed to work together in determining which responds? this would certainly be part of the "bridging that gap" the article refers to, but when both devices can do something (like phone calls) then it should ask you for clarification if you didn't specify in the original command. (ie "call ... on phone", or "listen to ... podcast on home", much like the existing "view ... pictures on tv" option)

my 'hey google' on phone option showed up Sunday. I was confused that Assistant was suggesting I help it learn because I'd already done that (very recently since Pixel 2 arrival). I even messed up during re-training, not expecting to alternate between Ok and Hey and had to start over. heh.

Actually, they do sometimes respond at the same time, which is why they're suggesting to ignore training the Hey Google command on the phone. I will ignore it because it used to drive me crazy when they would both answer to OK Google.

Not only are they NOT smart enough to avoid responding simultaneously, but the setup of the Google Home is laughably bad. You need to use your phone and the Google Home app to setup your Google Home initially. At least at launch when I got mine, it included training Home to respond to OK Google. Of course, the phone also responded to OK Google, despite being in the middle of setup. It was a train wreck. I ended up having to run the phone out of the room and into a hall closet when I reached that portion of the Home training, so the phone wouldn't interrupt trying to respond. It almost seemed as if no one at Google had ever actually set a device up before shipping.

As suggested, I will ignore training the phone to do the "Hey Google" because I hated when my Phone and Home both would answer OK Google commands, especially when I was setting an alarm at night. I now have 2 Google Home Minis in addition to my Google Home because I was tired of yelling for the Google Home, especially when the AC was creating background noise and because I wanted to use it as an alarm near my bed. And since my phone is also near my bed, i don't want the home devices to be confused with my phone after I say a command.

I suspect that Google will add a button that allows users to specifically turn off the "Hey" option on a device.

I don't see Google allowing specific voice trigger commands because both Hey Google and OK Google are also passive forms of marketing Google Assistant.

I have this question. What all phones will this work with ? I have an older Galaxy S III that I still like very much and use everyday because it suits my purpose. Just wondering what the oldest android phones will work with this.

I find this somewhat confusing because I never have to say "OK Google" or anything else to my Moto X Pure Edition. I just ask my question and get an answer. I do tap the microphone Icon before saying my question.
Just Saying

Not to troll but what is confusing to you? You personally​ activate voice commands by tapping the microphone button. As such obviously you won't need to say 'OK Google' to activate them on your phone, so what are you just saying?