04-16-2023
09:51
- last edited on
04-16-2023
10:49
by
MarreFitbit
04-16-2023
09:51
- last edited on
04-16-2023
10:49
by
MarreFitbit
Gps setting in Charge5 is set to use phone.
On my phone gps, internet and bluetooth are enabled.
I start biking on Charge5.
When i am finished i stop biking on charge5.
Most of the time no route is recorded!
Sometimes it does work.
I checked with maps on the phone: gps is working correctly.
I have the impression that if the charge5 loses contact with the phone for a short time, or if maybe the gps signal is gone for a short time... tracking is just stopped.
The charge5 does no retries.
This is a very annoying bug.
Moderator Edit: Clarified subject
04-16-2023 10:51 - edited 04-16-2023 12:36
04-16-2023 10:51 - edited 04-16-2023 12:36
Hi there, @Rob1951. Welcome to the Fitbit Community Forums. Thanks for the details provided in your post about the issue with your Charge 5.
Please bear in mind that if the GPS signal is lost during the exercise/activity, a map might not appear in the Fitbit app. Also, note if you begin moving before you get a GPS signal, your device calculates distance using your steps until GPS connects. GPS dropouts can be caused by several things (tall buildings, trees, overcast, etc.). If you're having issues with the GPS connection, see Why isn't GPS working on my Fitbit
If you lose connection, please try the steps provided here How do I get my Fitbit device to connect to GPS?
Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...
04-16-2023 12:29
04-16-2023 12:29
But, I use te gps from my phone, not the gps builtin to the charge5.
The phone gps almost never fails.
04-16-2023 12:39
04-16-2023 12:39
The problem is maybe in the Bluetooth connection.
The charge5 is on my wrist, my phone is on my back, the distance is about 60cm, Bluetooth should work fine.
But whatever is the cause the charge5 should resume route tracking if communication is back again.
There is a bug in this respect.