With the only two watches that still support Wear OS 3 — Samsung's Galaxy Watch4 and Watch4 Classic — Google Assistant has effectively made its debut. Hotword detection that is constantly on has led in rapid battery loss, and detection accuracy is hit-or-miss, according to user complaints. But if that wasn't enough, we've now discovered a mission-critical problem that some users have been experiencing.


Redditors have complained about their watches disconnecting from their phones at some point after installing Assistant in various posts. Attempts to re-pair have failed since neither device recognizes the other.


"If I attempt to add," u/SnooBeans6722 explained, "it asks me to pair [the watch] like it's a new phone and wants me to erase my watch, which I don't want to do because it'll be a bother setting up all the cards on Samsung Pay again."


Some customers claim they had to conduct a hard reset on their watches to resolve the issue, which is particularly concerning for those who don't have a backup to load.


If third-party complaints aren't enough for you, one of our editors even had his Watch4 disconnect from his phone.


We've contacted Google and Samsung to see if they can help, but given that it's a long holiday weekend in the United States, we're not expecting a quick answer.


Using Google Assistant on Wear OS and Android Wear watches hasn't always been a pleasant experience, so it's upsetting to learn that the service is experiencing performance difficulties on the Galaxy Watch4 and Watch4 Classic as well. But for those who have to deal with this issue on top of everything else, well, let's just say it's not enjoyable.