04-23-2020
12:51
- last edited on
09-22-2020
12:25
by
RicardoFitbit
04-23-2020
12:51
- last edited on
09-22-2020
12:25
by
RicardoFitbit
This has been an ongoing issue for the entire time that I've owned my Versa, and I think that's a couple of years now. I think it may be partially due to the complete failure of the Versa to ever reliably connect to the Samsung S10 phones, even this long after the phones were released. If it never, ever worked, that would be bad enough, but why does it work sometimes and not others? What the hell is with that? I'll get notifications and no problems connecting to GPS for a couple of days, and then suddenly, nothing, and that lasts for days or a week until suddenly it starts connecting again. Why is this?
After the new update today I wasted 30 minutes that I should have been running getting the firmware update on the Fitbit because I thought that was why it wasn't connecting to GPS when it worked three days ago. Nothing. Nada. Fitbit didn't get a map, Strava couldn't get heart rate, all because the Versa absolutely refuses now to connect to my phone no matter what I do. Is this issue going to be fixed? Is it a known issue? Will I be able to use this device as an exercise watch now, or did you finally break this functionality for good this time?
I'm tired of these devices being completely unreliable, and the constant excuses that Fitbit gives us. I know a lot of us have been very patient, and time is not fixing this and neither is Fitbit.
Moderator Edit: Clarified subject