I'm trying to activate Assistant voice typing on Gboard on a Pixel smartphone.
"Hey Google, type" causes the nearby Google Home device to define "type."
You say in the Assistant typing smartphone settings that to start typing with voice, to say "Hey Google, type." But even when I whisper into the phone so the Google Home devices nearby don't activate, it still uses a nearby one to give me the definition of "type."
I can only start Assistant voice typing on the smartphone with my voice by saying "Hey Google," because you insist on not allowing us to use custom, or different wake words. And you also apparently can't activate it by holding down the power button to start Assistant voice typing, because when I do that, then the phone gives me the definition of "type."
Why can't you just make things that work? It is INFURIATING how bad you are at designing things.
The solution is simple: use a less ambiguous word! "Type" is very ambiguous. How about, "Hey Google, start typing" or "Hey google, voice typing" - or anything to allow Assistant to determine that you want to START TYPING instead of give the definition of the word "type." Is that so hard?! No complex, tricky, machine learning needed. Just map a phrase with a function, so when you hear that phrase, you activate that function.
Or, if I ask it to do the same thing multiple times and you keep doing the same thing, how about asking, "did you mean something else?" YES! "Did you want to start voice typing instead?" YES!
Why is your smart home tech so DUMB? The hardware is fine. But the software is terrible.
Google Assistant typing has worked, with voice activation, on my device before. So there's no reason it shouldn't again. It stopped working because it turned itself off, probably because I turned on Voice Access, which I only just learned causes Assistant Voice typing to not work.
It's bad accessibility design that you can't use Voice Access with Google Assistant Voice Typing enabled. If Voice Access isn't currently active, and Google Assistant has to wake using "hey Google," why can't both be used, just not simultaneously?
Maybe in a few years when I buy a new smartphone you'll have these kinks ironed out, so I can help you alpha test all the new issues and only have a properly functional device years after purchasing.
You're doing a very good job of driving me away from your products and ecosystem. #1 word I associate with Google these days? Frustration!
Stop shipping products and features that don't work properly! I encounter weekly issues with your products, and I'm sick of it. I'm sick of having to make a note of issues to report via this forum. I'm sick of having to try and send feedback via "Hey google, send feedback," or trying to make an note, and saying a word it doesn't like, and it saying, "I'm sorry" and discarding what I just said, because it's trying to be smart and second guess what I asked it.
I installed Bing AI app and started using Chat GPT recently. I've been using Chat GPT for days and I'm already willing to pay a monthly fee. I've been using YouTube for years, and I'm still unwilling to pay a monthly fee.
And Chat GPT don't even have an app yet, nor is it pulling data from the internet - it's just using training that cutoff in 2021. It's that good. It's that useful.
Hear that? That's the sound of market share loss and job cuts if you don't sort your products out. You're not too big to fail. Ask any other large company that has.
I used to have a high opinion of Google. Not anymore. Google is an endless stream of annoyances and frustrations these days.
