06-25-2018 00:30
06-25-2018 00:30
I just upgraded from an Alta HR to the Versa and in nearly all respects I love the Versa.
BUT, the connected GPS is really disappointing :-(. Using it on my bike with my phone in my backpack, it just isn't really working. I start my bike ride where it says connected, then within seconds it is "connecting" which it seems to be doing 80%+ of the time. The GPS on my phone (iphone 7) works fine with Strava, so that's not the problem. It's a bit disappointing that my Versa tells me that my bike ride into work was 0.2km and took me 9 minutes...I may be slow but I'm not THAT slow haha
Does my phone need to be closer eg on my arm or on my handlebars? Or is the connected GPS really that bad?
06-25-2018 00:43
06-25-2018 00:43
Also using an iPhone 7, I haven't had many problems with the connected GPS. Occasionally it takes too long to connect but once it does it stays connected. Phone's in my pockets.
Do you perhaps have other bluetooth devices (headphones etc) that may interfere with the bluetooth signal?
06-25-2018 01:38
06-25-2018 01:38
No, no other bluetooth devices, only the Versa.
06-25-2018 02:43
06-25-2018 02:43
When I had my versa the connected gps never stayed connected. It was constantly “connecting”. I had my phone in my bag near my arm but still never connected. Because of that my data and map was always off.
06-25-2018 04:48
06-25-2018 04:48
Can you check your location services on your iPhone? I'm Android but I believe that iPhone location needs to be set to "Always" for the Fitbit app. This should help to keep the Versa connected.
06-25-2018 05:13
06-25-2018 05:13
Location is already set to Always for the Fitbit app...so that doesn't seem to be the issue.
06-25-2018 05:14
06-25-2018 05:14
I have experienced this too. I've noticed that sometimes it is much slower to connect to GPS than other times. I tend to have more success hitting start outside vs when I try to inside my home. Not sure what the dealio is because like you said, it's working fine on my phone directly. With bike rides & runs, I've started just tracking them directly with the fitbit app through track an exercise.
It's pretty inconsistent with me. but I've just started to double check that it doesn't say connecting before I start. Sometimes I also just cancel and start again and it gets itself together.
I am using a Samsung galaxy by the way.
06-25-2018 06:28
06-25-2018 06:28
mine does this too. Sometimes with running but mostly with my bike. I have no clue what my distance was Saturday but it said I went .12 mile and it took me 24:22 at .3mph.... Not sure if it related to cell tower signal? this in combination of the heart rate issue they still haven't been able to fix has me rethinking the versa which makes me sad because I love the concept of a fitness tracker with smart watch capabilities.
06-28-2018 00:49
06-28-2018 00:49
So, after a week of using the Versa I think it's safe to say that yes, the connected GPS really *is* that bad....I'm going back to Strava to track my bike rides.
What is odd, is that the Fitbit app is giving me a map showing what looks like an accurate plot of my (measured by Strava) 1.2 mile route, but then says that in 9 minutes I travelled 0.1 miles at an average speed of 0.0mph. Not very useful data! It's a bit of a disappointment, really, and I kind of wish I'd gone with a Garmin - but I do love all other aspects of the watch & FB app.
06-17-2019 03:38
06-17-2019 03:38
They should release a software update for this. It is really that bad i have also found out achter upgrading from charge 2 hr to versa. Disappointing, you get this crazy replies to keep you phone close to the watch for good connect gps. BT should be fine with random close by...
06-17-2019 11:00 - edited 06-17-2019 11:02
06-17-2019 11:00 - edited 06-17-2019 11:02
Wow got the versa for Father's day as a present. Used the Tomtom Runner 2 before without problems. And as an alternative Run keeper app.
So my 2,4 miles bikerides with the Versa are saved as +-0,5 miles and a average speed of +-4miles per hour? It's weird because the map is correct. That's a big mismatch with the real distance and speed.
06-18-2019 10:12
06-18-2019 10:12
It is pathetic, with a capital P.
06-18-2019 11:19 - edited 06-19-2019 08:25
06-18-2019 11:19 - edited 06-19-2019 08:25
So what's surprising is that I use the android app "FitToFit' to export my activities and data from Fitbit and import to Google fit. Those strange fitbit GPS speed and average mismatch activities i.e. Bikerides with a average speed of normal walking and distance totally off is first imported wrong in Google fit. But after a couple of minutes Google fixes the distance and average speed so it corrected the activity based on the map what is the only thing that is correct with the fitbit saved activity.
So my workouts are correct in Google Fit with the Versa but not in Fibit.
Give it a try if you encounter the same problems.
06-18-2019 14:04 - edited 06-18-2019 14:05
06-18-2019 14:04 - edited 06-18-2019 14:05
Maybe they can copycat that code and put it in a firmware update :), last update is more than half year old..
03-10-2020 16:24
03-10-2020 16:24
I think the less cell towers the worst it reports accurately.