The stand-out feature of Google Pixel Buds is that they’re supposed to be able to translate spoken languages in near real-time.

In my real-world tests, however, that wasn’t the case at all.

I took the Pixel Buds out on the streets of Manhattan, speaking to a Hungarian waiter in Little Italy, multiple vendors in Chinatown and more. If you press the right earbud and say “help me speak Chinese,” for example, the buds will launch Google Translate, you can speak what you’d like to ask someone in another language, and a voice will read out the translated speech through your smartphone’s speakers. Then, when someone replies, you’ll hear that response through the Pixel Buds.

The microphone on the Pixel Buds is really bad, so it barely picked up my voice queries that I wanted to translate. I stood on the side of the road in Chinatown repeating myself at least 10 times trying to get the phone to pick up my speech in order to begin translation. It barely worked, even if I took the buds out and spoke directly into the microphone on the right earbud, and often only translated half of what I was trying to ask. In a quiet place, I was able to allow someone to respond to me, after which I’d hear the English translation through the headphones. That was neat, but it barely ever actually worked that way.

To mitigate this, I found it was just easier to manually open the Google translate app, speak into my phone’s microphone, and then let someone else also speak right into my phone. This executed the translation nearly perfectly, and meant that I didn’t need the Pixel Buds at all.

Source: Tech CNBC
Google's new headphones promise amazing translation features, but they're really bad