04-17-2018 10:42 - edited 04-17-2018 10:52
04-17-2018 10:42 - edited 04-17-2018 10:52
I have done two runs with the Versa so far using the connected GPS to my phone and both runs have been extremely inaccurate. The first run was a 4 mile run, fitbit had it as a 3. The second run was another 4 mile run and at the half way point it had it at 1.4 miles instead of two.
I am coming from a Blaze and while it didn't match Google Fit 100% (normally off by .1 of a mile or so) it was never off by this much. Here are screenshots below showing it:
Completed run in Google Fit:
Complete run with Versa connected GPS:
The same run but with the Blaze and connected GPS:
And here today different location at the two mile mark in Google fit:
Versa connected GPS:
This is completely unacceptable. If this can't be permanently resolved (and I DO NOT considered constantly rebooting the device/my phone, pairing re-paring, etc a fix) then it will be going back. Add this to it deciding to give me an extra 3k steps while I was sitting on my computer doing nothing last night I am not that happy so far.
EDIT: Just noticed on today's run that the GPS line doesn't start until half way down the run but it was tracking from the start. Where it has the first mile marked isn't even a mile from the point the line starts. Just add it to the list I guess.
04-21-2018 10:55
04-21-2018 10:55
04-21-2018 11:05
04-21-2018 11:05
I have a first generation pixel xl.
04-21-2018 11:54
04-21-2018 11:54
Today was substantially worse than previously. I did notice that prior to going out, I was in the yard listening to music on my Versa with BT headphones. There was significant "stutter" in the music play. When I was indoors, this didn't happen. Is there a reason BT doesn't like big open spaces? The BT on my phone to headphones is fine. Is it the BT in my Versa that can't be outside? That might explain why I have trouble staying connected during my walk. Anyway, here's the maps FitBit vs Strava. They are both using the GPS in my phone so it isn't the GPS signal that's the problem.
Strava via Samsung S7
FitBit Connected GPS with Versa
04-22-2018 21:51
04-22-2018 21:51
Same exact problem everyone else is having. Not liking the watch, since the mapping feature (connected GPS) was the main reason I bought it.
04-23-2018 07:25
04-23-2018 07:25
So I did a long run with my blaze this weekend and it seems to be getting worse with how much it's off by. Here are the screenshots (ignore the time difference, sometimes I paused my fitbit when I stopped to check my phone but didn't pause strava)
Fitbit:
Strava:
I am thinking about trying a garmin watch if fitbit can't handle something as simple as tracking GPS distance anymore.
04-23-2018 07:29
04-23-2018 07:29
I'm happy with everything else about my Versa except for this. Exercise tracking is one of the major selling features and it doesn't really work? Do we all on this thread just have faulty devices? So frustrating. Can't participate in any distance challenges since my Versa is hopeless at calculating distance. Grrr.
04-23-2018 08:19
04-23-2018 08:19
So I think my problems were caused by the issues with Android Oreo discussed here: https://community.fitbit.com/t5/Versa/Fitbit-App-crashing-using-connected-GPS-Versa/m-p/2649966#M619...
Having deleted and redownloaded the updated app, it worked flawlessly this morning. Distance and pace were right on. I also made sure to open the fitbit app before I ran.
04-23-2018 08:43
04-23-2018 08:43
I have completely uninstalled the fitbit app, deleted all data related to the fitbit app, reset the fitbit (versa and blaze) back to factory, and then re-set up multiple times and it didn't make a difference. I've done everything short of a factory reset on my phone which I will not be doing.
The problem is with the fitbit itself and/or the app. There are tons of free apps on google play that can accurately track distance using the built in GSP in our phones without an issue. Fitbit should be able to do this and do it well, WITHOUT us having to jump through hoops such as rebooting, resetting up, blood sacrifice, etc to make it work.
04-23-2018 09:14
04-23-2018 09:14
Please let me know if this helps. I am having both issues as well. Mileage off significantly and HR of 197... totally inaccurate. I loved my Blaze but I am so disappointed with this device. If these issues cannot be resolved quickly, I will be returning.
04-23-2018 09:32
04-23-2018 09:32
Hello everyone, I hope you're doing well.
I appreciate you have reported this and I understand your concern about this situation. When you select a GPS exercise, Versa vibrates when your phone finds a GPS signal. If your phone doesn't find a signal immediately, keep in mind that environmental factors including tall buildings, dense forest, steep hills, and even thick cloud cover can interfere with your phone’s ability to connect to GPS satellites. For best results, wait for your phone to find the signal before you start your workout. However, if you don't want to wait you can start your workout and GPS tracking begins when your phone finds a signal.
Note that Versa uses your step count to calculate distance until it finds a GPS signal. In this scenario, your total distance calculated for the workout may be slightly less accurate than if GPS data were available for the entire duration. For more information, see How accurate is GPS?
Before starting your exercise, please make sure all requirements are correct:
After verifying all the requirements, try using GPS again by following the instructions in How do I use exercise apps and modes on my Fitbit device?
If you're still having difficulty, try these troubleshooting steps:
If after trying these troubleshooting steps your Versa is still not connecting to the GPS on your phone, keeps disconnecting or the map is not accurate, please let me know so I can determine which troubleshooting steps should we take next.
Thanks for your patience and understanding, if there's anything else I can do for you, please feel free to reply.
04-23-2018 09:48
04-23-2018 09:48
@MarcoGFitbit I have tried all of your suggestions to no avail. The distance continues to be off by about 35%. My phone does not lose gps connection since my Strava app, running on my same phone, has a consistent signal and measures the distance correctly. I think it's the bluetooth signal between my phone and my Versa. My bluetooth headphones don't have a problem and my Versa bluetooth gives me no trouble indoors, only outside. Is this an indication that my Versa's bluetooth is faulty?
Since I'm trying to improve my fitness, it's not realistic to stop every time my Versa tries to reconnect and to, as you state:
If you're still having difficulty, try these troubleshooting steps:
My heart rate will slow back down and my exercise won't be as effective. Any other suggestions? Since the Exercise portion of the Versa features with "Connected GPS" are a big part of what FitBit is selling, it would be really nice if this would work.
04-23-2018 11:55
04-23-2018 11:55
I am also have problems with Android 7.
Only had my one a couple of days and first walk today which has no app and should be automatic.
When I got home I checked the app but first I noted the app status message was flashing something about GPS is Running and hours later it says steady "Connected GPS is running"
The app says "Sync Error, please try again" which I have but it must still be connected as it still sends alerts to the Versa.
It also said well done about my activity but it does not seem to exist.
I noted on my phone the GPS icon is on all the time and I have tried turning BT off and back on.
I would also have preferred a Walking option in the exercise app as auto seems suspect.
It decided that mowing the lawn was a bike ride yesterday 🙂
04-23-2018 12:06
04-23-2018 12:06
04-23-2018 12:43
04-23-2018 12:43
Just did my first Connected GPS exercise with my new (as of today) Versa (which didn't work). I've previously had the Charge HR and Blaze, both of them have had issues staying connected to the GPS in the past. Kathy is right in that other apps that track using GPS always seem to work fine and it's always just Fitbit that either never connects (this exercise, it never moved from "Connecting to phone...") or frequently disconnects during the exercises. I was outside, in wide open area, the GPS location indicator was lit solid on my phone, signifying that an app was trying to track location. It never did and my exercise show zero GPS activity.
I've rebooted my phone and will try again later to see if it works.
04-23-2018 12:49
04-23-2018 12:49
As per Kathy's advice I see on the web interface where you can add walking.
Syncing seems to have failed now with a general error which fitbit are aware of 🙂
I got my gps connection to end by loading the exercise app, selected running, waited for gps and then closed the app.
I then got a 5000 step award but I guess will now have to wait for fitbit to fix the problem...
[quote]We are aware of an issue which may interrupt device syncing. Thank you for your patience while we work to get this resolved quickly. Your steps are still being counted![/quote]
04-24-2018 13:34
04-24-2018 13:34
Just bought my Versa yesterday, went on a run today. Exact same problem that everyone else has... Lost GPS signal from my phone a mile into my run. WiFi was off. All settings were where they were supposed to be. My MoblieRun map made it look like I flew over a river... Very upset... This was the main reason I bought this watch. Thought it would be an improvement over the Blaze. I hope it gets fixed soon!
@MarcoGFitbit is FitBit aware of this issue? I seems that everyone has followed your suggestions in your previous posts and the problem still exists.
04-24-2018 14:00
04-24-2018 14:00
I tried my also today only walking using the excercise app.
First walk, the GPS would not connect till I loaded the app and selected the device. The status message on the app then said GPS.
Not a very long trip and of course only at walking speed but it did log it and the map looks correct.
My second outing worked without any manual intervention.
Trip to shop
04-24-2018 15:47 - edited 04-24-2018 15:49
04-24-2018 15:47 - edited 04-24-2018 15:49
Try turning off wifi and bluetooth scanning under Android locations, then use GPS only, not "high accuracy". I also turn off wifi completely to eliminate any interference with the bluetooth connection.
I find as long as the watch and phone keep their bluetooth connection, I get accurate results. Version 2.69 and 2.7 have been much better at this than earlier ones. I used them with a Blaze and now my new Versa.
MobileRun is a good alternative if you have a decent GPS lock on your phone and don't use "pause" during the activity, you'll lose the entire run then when you complete it. If they ever fix this, I'll stop using connected GPS entirely. You still get heart-rate and step data from the tracker, if you have it on.
04-24-2018 16:37
04-24-2018 16:37
Yes, I’m having that same issue during my walk at this one specific area I walk. I check my versa and I see “connecting..” after my walk when I check my app, I always get this triangle as my route and I know we didn’t walk that triangle plus I lose miles too. But my friend whom I was walking with tracked our same walk on his blaze and it was correct. It’s quite frustrating. I’m guessing since we walk near the mountains and there’s a lot of trees, could it be interfering with the Bluetooth connectivity?
04-24-2018 17:04
04-24-2018 17:04
I'm using a T-Mobile Galaxy Note 8 that is updated to Oreo and have yet to get a connected run throughout and have incomplete data to base my exercise on. If I use another running app or Strava, I get everything working perfectly throughout.
It's sad I can't rely on this, but your proposed fixes make this a take a break watch and not a exercise tool.
I did a 3 mile run and my map is less than a mile and stops, even though I ran a large loop.