[Updated] S Voice broken on Gear Sport and Gear S3, Samsung says fix incoming
Update (March 28):
Hey, everyone, thanks so much for taking the time to reach out about this, we are collecting more information to understand which devices to target a fix for.
I understand that this may store some important information, I have found that resetting your watch does tend to help fix this difficulty with S-Voice
I’m just trying to gather information to help the engineers fix the problem. That way we can get a fix that much faster.
Virtual Assistants, as most of you may agree, reduce human efforts by completing tasks merely with voice/touch commands. While Samsung users have access to two of such support services (Bixby and S Voice), what’s now coming to light is that the latter is not working as intended on the company’s Gear Sport and Gear S3 series of watches.
To quickly refresh, S Voice is a virtual personal assistant which facilitates tasks – like telling time, providing weather updates, opening applications, and scheduling appointments – through voice commands. But, for quite some time now, those operating S Voice on their Gear Sport and Gear S3 devices have been encountering an error (on initiating a command) notifying that “An error has occurred. I’m unable to answer your question. Try again later.”
Though the glitch was originally reported back in March, it has now gained heat and is being more widely reported, with some Gear S3 users saying they observed the problem after the recent Tizen 188.8.131.52 update.
The following user-shared video clearly showcases the error in question (at 0:08 seconds), which occurs on commanding S Voice to set a timer:
Apart from Samsung Community, affected users have also taken to Twitter to voice similar, S Voice-related complaints.
@Samsung @SamsungMobile @SamsungMobileUS S. Voice on Gear S3 is a hot steaming pile of monkey dung. Can you guys get text to speech right? Just doing "Hey Gear, set alarm for 6:30pm" doesn't even recognize anything.
— Blypto (@blypto) December 13, 2017
What’s relieving is that a Samsung moderator officially confirmed the issue recently while reverting back to a user on the official help forum. They mentioned that an update (R770XXU1APJF) is being worked on, which aims to fix the aforementioned glitch.
We’re working on a new update that should be addressing your difficulty
While searching for more information related to the update in question, we stumbled upon a page on Samsung’s official website which currently states that the update is yet to be released.
It appears that the update is coming soon. Meanwhile, keep a tab here, as we’ll let you know as and when the update (and hence fix to the problem) arrives.
Stay connected with us on Twitter (@PiunikaWeb) to hear about all related developments as and when they occur