Why does Android's speech recognition suck so bad on my new Google pixel 2?

  • Thread starter Thread starter Android Central Question
  • Start date Start date
A

Android Central Question

I had an LG V10 and the speech recognition was significantly better than this garbage from Google's new pixel 2. I either have to correct it all the time, which it should be learning from those Corrections and it does not, or I have to erase what it changes and type it letter by letter. Google, you suck!
 
Welcome to Android Central! My Pixel 2 XL and my wife's Pixel XL (1st gen) both have excellent speech-to-text, so you might just have a faulty unit. Make sure your secondary mic (at the top of the phone) isn't blocked (either by a case or clogged by lint). Also, test out the secondary mic by making a speakerphone call to somebody -- do they tell you that you sound muffled? If so, then the secondary mic is the problem.
 
Everyday I'm appalled at how terrible my Google pixel phone is at voice to text recognition. I'm constantly correcting it. It never learns my corrections and continues to make the mistakes over and over again. It is stuck on stupid.

I would understand if I was speaking with an accent or slurred my words, but that is definitely not the case. It's just that it sucks. No doubt about it.

I have used a similar feature on other phones, different from pixel, with much better results. You would think that Google could get this part right. It seems relatively simple. Certainly, compared to so many other more complex applications that they have almost perfected.