First, he starts heavily delayed and now also with serious errors. Google didn’t do well with the new Assistant for Wear OS. The stupid thing is that the app is now available for the most popular Wear OS smartwatch, of all things, and crash-landed at the same time. To be honest, we didn’t wait that many months for such a disaster.
Two serious problems are emerging. On the one hand, users with the Samsung Galaxy Watch 4 complain that the battery life is noticeably shorter after installing or setting up the Google Assistant. Some write about the “battery killer”, others are less harsh with their statements and say “that’s not good”. In general, however, the experience is negative.
Battery: Google Assistant fails in the Siri comparison
Different tests have comparable results. Google Assistant with hotword recognition is draining the Galaxy Watch 4’s battery way too much. The Verge found that Assistant squandered a whopping 20 percent of the battery in just two hours. Siri on the Apple Watch with comparable settings only eight percent. Ouch.
The reason for the high battery consumption is the constant monitoring. If you configure your watch so that it doesn’t listen to “Hey Google”, you shouldn’t have battery problems. That’s what the colleague from 9to5Google says after his own test. This behavior doesn’t have to be surprising, because Google points to increased energy consumption.
The assistant unpairs smartwatch from phone
A real problem is an unintentional decoupling of the smartwatch from the phone. That wouldn’t be so bad if you could connect the devices again and use them as before. But exactly that doesn’t seem to be possible so easily, reports Android Police. The devices can no longer be found.
So Google and Samsung have to go back and quickly push a few updates.