03-31-2022
11:54
- last edited on
12-18-2022
20:14
by
MatthewFitbit
03-31-2022
11:54
- last edited on
12-18-2022
20:14
by
MatthewFitbit
I got my versa 3, 3 days ago, on tuesday the replies by voice worked perfectly, yesterday and today it is not working at all i get transcript error and after trying i get not available.
Ive tried reset it from fabric i did restart the device the phone, delete the device setting it up again and nothing!
I got this model for this exact reason can someone help?
Moderator Edit: Clarified subject
Answered! Go to the Best Answer.
03-31-2022 10:37
03-31-2022 10:37
03-31-2022 11:57
03-31-2022 11:57
JennW - i have the same problem.... thanks for making this post and i will up vote it.. i have some comments on yesterday in here too.
03-31-2022 11:58
03-31-2022 11:58
i have samsung note 20 Ultra - yesterday samsung updated One UI 4.1
did you have same update?
03-31-2022 11:58
03-31-2022 11:58
This is the first forum that i have found that was recent, i just got my versa 3 and worried great first week this issue didn't start until like the day before yesterday. Still no help from Fitbit?
03-31-2022 12:00
03-31-2022 12:00
I have a Samsung A52 and I havent done any updates recently and on tuesday it worked great, Wednesday and today is not working
03-31-2022 12:02
03-31-2022 12:02
I Have Android 12 One UI 4.0 and its not working
03-31-2022 12:02
03-31-2022 12:02
Same issue here, I got mine last week and it worked... Now it doesn't. I contact support via chat and it was useless. I have rebooted, restarted, uninstalled, all of it. Nothing works. I can use Google assistant to send a text, so it's not the microphone.
03-31-2022 12:03
03-31-2022 12:03
yes.. my problem happened yesterday.. was working great for 3 weeks..
then yesterday my Note 20 Ultra had Samsung One UI updated to 4.1
i was thinking that was the problem..
what i have tried:
- uninstalled my Fitbit app on Note 20 = results still N/G
- formatted my watch to factory reset = results still N/G
i will find my Note 9 and install the fitbit app and run it with that phone to see if there is issue.. and report back
thanks
03-31-2022 12:04
03-31-2022 12:04
Same! I got instructions from them via email and i followed the steps and not had worked, it is on their end lots of users are having the same issue
03-31-2022 12:06
03-31-2022 12:06
yes.. my problem happened yesterday.. was working great for 3 weeks..
then yesterday my Note 20 Ultra had Samsung One UI updated to 4.1
i was thinking that was the problem..
what i have tried:
- uninstalled my Fitbit app on Note 20 = results still N/G
- formatted my watch to factory reset = results still N/G
i will find my Note 9 and install the fitbit app and run it with that phone to see if there is issue.. and report back
thanks
03-31-2022 12:07
03-31-2022 12:07
03-31-2022 12:09
03-31-2022 12:09
03-31-2022 12:10
03-31-2022 12:10
Ma44, thanks for helping on this.. are you on Samsung One UI 4.10 or UI 4.0?
i will find old cell phone and load in fitbit app tonight to see what is up..
03-31-2022 12:12
03-31-2022 12:12
03-31-2022 12:31
03-31-2022 12:31
looks like the Versa 2 is affected..
look at the last 3 comments.. happened yesterday
03-31-2022 12:58
03-31-2022 12:58
I've a moto phone. Doesn't seem to matter which phone. That means it's a FITBIT issue.
03-31-2022 14:20
03-31-2022 14:20
good to know.. at least it isn't a Samsung thing... thanks !
03-31-2022 14:24
03-31-2022 14:24
we have the same problem in the versa 3 forum too
https://community.fitbit.com/t5/Versa-3/Transcript-error-on-voice-replies/m-p/5113699#M30386
03-31-2022 14:25
03-31-2022 14:25
Samsung A52 and Versa 3 here. Was working fine Monday. Tuesday started having issues. Wednesday not working at all. Not to mention the random restarts my watch does as well. Frustrating.
I have restarted the watch. Restarted my phone. Factory reset the watch. Unpaired and repaired. Checked for updates.
What gives fitbit? This watch has been a pain since the beginning.
03-31-2022 14:54
03-31-2022 14:54
I just replied - I think it is a system issue - Versa 2 quit replying as well even after rebooting phone and Fitbit and on a chat with Fitbit for about 1/2 hour and not fixed yet