Charge 2 not recording GPS data accurately

[SunsetRunner]

This is my 3rd Fitbit,

1st owned a Charge 1 HR it broke, (stuck on FW update)

2nd Charge 1 HR Stopped working a few months later.

3rd (current) Charge 2 Never worked out of the box as advertised.

Problem....  Cycling and GPS 

It simply DOES NOT work, from the beginning it used to track my ride, while often losing connection, the KM posted never matched my cycling computer, (which I know is accurate)

Later on it began to post ridiculously inaccurate distances.  I would ride 40 miles it would map it correctly but claim i rode 2.

this was an ongoing issue for months then winter hit and i didn't use it assuming a fix would come out.

Now 2019 summer the fitbit got even worse now I start the tracking for cycling and 5 sec later a message will pop up telling me check fitbit app. i acknowledge it, but no gps tracking.

Reboot the phone the device and nothing.  I've tried everything reinstall app change phones, turn off wifi, turn off BT headphones, load up app. give app full permissions, factory reset phone etc.

1/50 times it may work, most times it connects and by the time I get down the street it's disconnected.

Sometimes my Stava app will record properly yet the fit bit app fails.  Why does a free Strava app work yet fitbit can't get this resolved? I know I'm not the only one with this issue.

MY SUGGESTION.

Stop the real time GPS transfer of data from the phone to the device! It's very simple the ONLY thing the device needs to do it trigger the phone to start recording GPS tracking, the fitbit only needs to record vital statistics only, then when the ride it compete the device will send a signal to the phone to stop the gps tracking.  Unless I'm mistaken this seems like simple solution to a flawed design.   I don't need to know the real time speed I'm traveling that's why I have a cycling computer,it's not even practical to be looking at your wrist for speed, it's dangerous. 

I don't know what the current issues are, I may try using my old wired headphones with a separate music source to listen to, so it doesn't conflict with the current phone and apps.  My phone is a decent phone newer then the Charge2, I assume the CPU and BT connection is adequate.  I'm not sure if fitbit can communicate to the phone when it's in my pocket behind my seat but I have no issues listening to BT music when it is placed in this location.

With my very poor experience with FITBIT I can't see myself using this thing anymore or ever considering buying another one, I would try out the competition instead.

Moderator edit: updated subject for clarity

[AlvaroFitbit]

@SunsetRunner, it's great to see that you've visited the Fitbit Community! Sorry for the delay in my reply.

Let me help you with your Charge 2 not recording your GPS data and thank you for troubleshooting this issue. This issue is being investigated by the team but still thank you for reporting it. I suggest you try using only the Fitbit app and when recording GPS distances try using the Run option as it has shown that it provides better results at distance detection than the other options. Still you can try refreshing the link between your phone and your tracker by doing the following:

• Go to your phone's bluetooth settings and remove all devices listed there.
• Restart your phone and restart your device. 
• Also, if you are using an Android device, check that your app has the necessary permissions (settings > apps > Fitbit > permissions) and make sure bluetooth and location services (GPS) are on. 
• You can find additional suggestions here.

Let me know how it goes.

[Andyfitz]

I have also previously posted this same problem.  Mine started May 23, 2019.  That was the last date the mapping recorded properly after two years of working correctly.  After that date there was incorrect logging every time I used it.  I tried the solution given and it worked the first time I used my fitbit to record a bike ride.  But that only lasted that one time.  It is still logging incorrect mapping and distances.

[Lumiukko]

Triggering the phone to start recording data is a really good Idea, Fitbit should heed it. You could also offer to truncate recorded tracks in case too much was recorded.

Additionally it could be offered to upload gpx/tcx/geojson tracks. I am recording my tracks with a third party app because of this exact problem (showing I only rode 0.07 km, when it was actually 5).

[SunsetRunner]

I'm back after a week weeks to report Alvaro's solution worked for me, For 2 weeks now my fitbit is recording correctly again. 

I still think fitbit should rethink the current process fitbit records.  I think fitbit triggering the Phone to record would be a much more reliable way to gps track.

Thanks for all the help.