11-06-2018
02:33
- last edited on
11-07-2018
10:34
by
GraceGFitbit
11-06-2018
02:33
- last edited on
11-07-2018
10:34
by
GraceGFitbit
My Versa frequently disconnects from my Samsung S8 whilst exercising, in fact I don't recall ever the Versa staying connected with my phone, the result is that that my GPS track is incomplete.
I then have to rely on Strava for the GPS track.
I find this disconnection issue very annoying.
Is there actually solution to this or is it actually a product design fault?
Points to note:
the only exercise I am doing where I am interested in seeing my GPS track is cycling.
my phone will always be in my rear pocket of my cycling jersey.
The only thing I haven't really been doing is disconnecting my WIFI when out cycling. But could this affect the stability of the bluetooth connection between Versa and Phone?
Many thanks
Moderator edit: Subject for clarity.
11-07-2018 10:33 - edited 04-09-2019 12:31
11-07-2018 10:33 - edited 04-09-2019 12:31
Nice to see that you're digging into the Forums @cdmueller103, let me give you a warm Welcome to our Community. Thanks for all those details you provided, it's very helpful!
Indeed, Fitbit Versa works with the GPS sensors in your nearby phone. To get GPS data, you must select a GPS exercise from the Exercise app on your device and bring a GPS-enabled phone with you. We recommend turning off Wi-Fi on your phone when using connected GPS to improve the experience.
When you choose a GPS exercise, your device 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 your device 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?
It could be a good idea to check this requirements too:
Give it a shot and let me know if that works!
01-26-2019 06:38 - edited 01-26-2019 06:51
01-26-2019 06:38 - edited 01-26-2019 06:51
Hi there thanks for you reply.My replies to your replies in blue
Indeed, Fitbit Versa works with the GPS sensors in your nearby phone.
Yes, I know this
To get GPS data, you must select a GPS exercise from the Exercise app on your device and bring a GPS-enabled phone with you.
Yes, I know this. This was not an issue
We recommend turning off Wi-Fi on your phone when using connected GPS to improve the experience.
I've now been doing that
When you choose a GPS exercise, your device vibrates when your phone finds a GPS signal. If your phone doesn't find a signal immediately,I'm in the countryside. Right now as a test, I'm at my computer and if I select an exercise, the fitbit (which is 30cm away from my phone) will take up to 1 minute to tell me that its connected (from that exercise screen) i.e. 'Lets Go'. Connection is never immediate.
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.
Im almost never experiencing these conditions
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.
But I had the opinion that my phone is always connected to a GPS signal, don't see why there should be such a long delay for the FITBIT GPS function to tell me that its connected even when the FITBIT and phone are next to each other on a desk, let alone my phone in my back pocket of my cycling jersey
Note that your device uses your step count to calculate distance until it finds a GPS signal.Please see my fitbit screenshots which might explain better the issue
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?
It could be a good idea to check this requirements too:
- Bluetooth is enabled on your phone and your tracker is connected (paired) to the phone. To confirm, go into your phone's Bluetooth settings and make sure you see the Versa on the list of devices.
It is connected to Versa (classic) (as opposed to Versa)
- The Fitbit app is allowed to run in the background on your phone. For more information, see Why is the Fitbit app sending a notification to my Android phone?
Yes it is, because I'm also receiving notifications from the phone to my fitbit - although Im not sure how reliable this is
You selected an exercise type from the Exercise app that uses connected GPS. To check on Versa, tap the gear icon (
Yes I am selecting cycling
- ) on any exercise and check that GPS is listed and set to On.
Yes it is
- Your phone can identify your location and can track your location when you're not using Wi-Fi. For more information on which phone settings you may need to adjust, see How do I track my workouts with my Fitbit device?
My Phone (Samsung S8) location settings are as follows:
- Locating Method: High Accuracy ('uses GPS, wifi and mobile networks to estimate your location)
- If your mobile device is running Android 6.0 or later, see Why do I receive access requests from the Fitbit app on my Android mobile device?
I am using Android 8.0.0
Give it a shot and let me know if that works! :catvery-happy
See below some screenshots which highlight some of the issues I have been experiencing:
First screenshot from my FitBit Dashboard activity shows a cycle ride I did. Fitbit has not recorded this activity correctly.
- Its showing my total distance is 1.1km but the red line shows around 30km
- Its showing my average speed as .62 km/hr when in fact my average speed was around 27km/hr
- The spot km/hr indicated shows .72 km/hr when in fact it should be reading around 32km/hr
So whats the problem here?
Here's another screenshot showing another cycle ride with incorrect data (i shall post a screenshot of the same ride but recorded using Strava (in conjunction with Garmin cycle device)
- Its telling me I've done 1.99km but the actual distance as shown by the red line is around 50km
- Showing an average of .65kmph but my average would have been around 26kmph.
- the spot speed indicated on the map reads 1.10kmph but the actually speed would have been around 30kmph
So whats happening here?
And finally a screen shot of the same ride but a Strava Recording, which is recording correct data.
Yes i realise that GPS accuracy with a Garmin Device and Strava is going to be more accurate in regards to GPS but there is clearly a major issue with the Fitbit (in conjunction with my phone) not recording even a little bit correctly any information.
The only thing that has changed in the last two months or so that I've been using Fitbit to record my ride is that it can just about record only very approximately the route.
Another issue that I also have not been able to resolve is the 'auto-pause' function (whilst cycling). The issue here is that it would never resume automatically. So I turned this function off and have not tried it since, I know that was a firmware update that I installed around 3 weeks ago, whether or not it has resolved this issue, I cannot say.
But the auto-pause function seems to be related to the other issues mentioned above i.e. speed, distance calculation.
Many thanks for your help.
NOTE: no sure if its relevant information but when Im going cycling I am always also using a Garmin Cycling Computer that is connected via Bluetooth to my phone
01-31-2019 06:25
01-31-2019 06:25
Hi @chrisjb222, thank you for getting back to us with all those details. I'm glad to continue assisting you.
At this time I would like to know if you had check:
If you're still having difficulty, try these troubleshooting steps:
Finally, for the next time you try to do this activity can you please check the Versa every 10-15 min, to confirm that you're not loosing GPS signal.
About the "Auto-pause" I would like to know what's the result after trying again.
02-09-2019 07:15
02-09-2019 07:15
Thanks for getting back to me.
Firstly my last recorded ride a few days ago using Fitbit worked, both in the GPS tracking, total km and correct speed - i.e. it matched with my Strava recording (which is taking its data from my Garmin Cycle Device). This is one of the first times that Fitbit data is matching with my Strava Data.
However, where it does not match at all is in Calories Counted. There is a big difference. I'm not assuming Strava is correct.
Strava recorded 1260 calories. Fitbit 800. Google Fit recorded 710 and Garmin recorded 1260 (its probably synching with Strava)
Both Fitbit and Strava are set up with my correct weight. Can you advise. Which should I trust more? Strava and Garmin are more dedicated to cycling.
What do you suggest?
At this time I would like to know if you had check:
Yes
Yes its all set up correctly as previously mentioned
Finally, for the next time you try to do this activity can you please check the Versa every 10-15 min, to confirm that you're not loosing GPS signal.
So, if the Fitbit is intermittently losing the GPS signal why would that be and what can I do to prevent this from happening. If Im cycling, for sure don't want to stop to fiddle around with reconnecting bluetooth devices or turning things on and off
About the "Auto-pause" I would like to know what's the result after trying again.
I will try this again. I haven't tried it since I gave up on it.
Lastly, how I can import or synch Fitbit Heartrate into my Strava recording? ( I don't want to import all the Fitbit data of a ride because my Strava data using Garmin device is likely to be more accurate.
Many thanks
02-13-2019 07:39
02-13-2019 07:39
Thank you very much for the response @chrisjb222. I'm glad to learn that the data with Strava is matching now.
About the calories, take into account that Fitbit uses the personal information you’re asked during setup is used to calculate your basal metabolic rate (BMR), which helps determine your estimated calories burned. To learn more about it check this article how does Fitbit estimate how many calories you've burned.
When comparing data from different brands and devices it's very important to take into account that the information is't tracked differently and the algorithms are not the same. Also, it's possible to get different readings if the tracker is worn in different locations (dominant vs non-dominant wrist). We recommend reviewing the accuracy information provided on our help site at help.fitbit.com.
If the GPS signal is lost, your phone is continually searching for a GPS signal as long as an exercise is in progress. At least 24 GPS satellites are constantly in orbit around the Earth and broadcasting data. Your phone requires a direct path to these satellites in order to receive their radio transmissions. If the signal is blocked—either because you're underground, near many tall buildings, or as a result of atmospheric effects—GPS won't work. While GPS gives you a more accurate measure of distance than step counting alone, the actual accuracy depends on both your environment and the weather. If this happens again I would like to know if you have noticed any error message? Besides all the tips already provided to avoid this situation, made sure you're fully charging the Versa each time before start the activity or at least a battery level above 25%.
Lastly, up to day the option to import or sync the heart rate data with Strava. I think you could post your idea as a Feature Suggestion on our community. We're constantly striving to improve Fitbit products and services, and we very much appreciate all of the input we receive from our customers. Please take a moment to visit and give us your feedback.
Thanks a lot for taking the time to share your feedback and comments. It's very important for us to read what are you experiencing.
If there's anything else I can do for you, please feel free to reply.
04-08-2019 13:13
04-08-2019 13:13
I have been having similar issues with my Charge 3 and my Note 9. I've tried all the previous suggestions. I've always allowed it to run in the background, battery usage not optimized, etc. Some days it would take 45 minutes to get it to connect. And then never knowing if you were going to lose part of your ride. I've always used the Fitbit app and Strava simultaneously which I know they say you shouldn't do but I use Strava's live segments. Then at the end of my ride if my Fitbit logged my ride correctly I stop my Strava ride without saving it and I save the one on my Fitbit and wait for it to post to Strava. If it all works I then delete the duplicate on Strava, if not I still have the Strava I can save. I think your settings should be similar. I went into settings, device care, clicked on battery and then on the three dots in the top right corner. This takes you into "App power management". I shut all the power management toggles off and so far it has worked flawlessly since. Maybe they all don't need to be off, I started by clearing them all.
Hopefully, it will stop your disconects
04-09-2019 13:12
04-09-2019 13:12
Hi @Scott2600, I'm glad to see you here in the Fitbit Forums. Thanks for sharing your experience with us with that detailed information.
I really appreciate your intention to help.
Thanks for posting and I hope to see you chatting around enjoying the Forums!😺
11-03-2019 02:51
11-03-2019 02:51
Hey buddy.. I know this is a bit late but if you go to the page that provides information on connected devices, you will notice that if you check the Samsung S8 page, it doesn't state that connected GPS is supported.
11-03-2019 12:17
11-03-2019 12:17
That's crazy....I have been using my S8+ and Charge3 successfully for almost a year now. I think this all started when Samsung came up with a system software update that started this incompatibility issue. So, maybe we "bark up the Samsung tree". But it's just disappointing that it used to work great, but now there's issues.