Charge 2 & Z2 Force Run Tracking Errors

[mmarion3624]

---Mods this is not spam can we quit marking it as such?---

I'm using a Charge 2 with my Moto Z2 Force: Within the last few weeks my runs have been recorded as shorter than the actual distance run. For instance, a 9.3 mile race over the weekend was captured at 7.57 miles. I use the FitBit with Strava and Strava's segment feature recognized the route as the proper 15k distance.

Sometimes the FitBit run map shows odd vectors for my run, not accurately capturing my movements. Other times it will cut street corners at an angle, making the inaccuracies a little harder to catch. I know the device is using my phone's GPS so I've cleared the cache on all GPS related apps to great results on my phone yet the issue persisted over the weekend. I have noticed an icon on the FitBit showing a phone with lines coming out of it to the right, which I believe indicates it's searching for a signal. Is it searching for the connection with my phone or is this GPS related, or both?

I cannot determine if my Z2 Force or the Charge 2 is the issue. I have...

-Disconnected & repaired my devices via Bluetooth

-Cleared the cache on all GPS and fitness apps

-Updated all apps

-Rebooted the FitBit

-Fully charged everything & tested to consistently inaccurate results

-I have screenshots illustrating the most recent error. 

I will be doing a field test with my work iPhone 6s tomorrow and this same Charge 2 device to see how it goes. Any other bright ideas in the community? I'm open to them. Training for a marathon and want to fix this ASAP. Thanks!

[AlvaroFitbit]

@mmarion3624, 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 GPS distance calculation. This is an issue that is actually being investigated by the team. It is suggested you try using Run before any other option is it is found that this gives the best results but still the issue with the distance can still appear. You can also check this article for tips on how to improve the GPS detection when using the Fitbit app.

Let me know how it goes.

[mmarion3624]

Thanks for the response, Alvaro!

I do have news: last night's test run & bike ride went okay trying the watch w/ an iPhone. Distance & GPS map was right on. The symbol I'm attaching showed up much less than it has been when running linked to my Moto Z2. Is there a known Fitbit/Android hiccup being worked?

Testing the iPhone on a longer run tonight, I'll chirp back in.

[mmarion3624]

Update #2: the iPhone/ Charge 2 GPS combo hung with me for a 5+ mile run last night. I frequently checked my status using the quick view wrist turn on the watch & didn't spot that "GPS Searching" icon once. 

I (painfully) wiped my Moto Z2 Force and will be testing it with the Charge 2 tonight. Hoping it sticks with me, otherwise that was a big waste & I'll be in the market for a new phone. I'm more suspicious of the phone than the watch after these field tests. 

[mmarion3624]

Update #3: After the factory reset of the Moto Z2 Force the phone paired with my Charge 2 but won't sync with it. I fired up my work iPhone and tracked a run with it: functioned perfectly. At this point I'm confident the issue is my Motorola which is a shame but I can upgrade.

My only question is if anyone else with this same model phone is having similar connection problems? I'm wondering if I just have a whacky handset or if it's a known compatibility issue other users are experiencing. 

[mmarion3624]

August Update: The saga continues! Performance w/ the work iPhone 6s has & continues to be excellent. That said the Android Pie update was available for my Moto Z2 Force today & after the update the phone properly synced with my Charge 2 watch. 

Am I ready to trust the Z2/ Charge 2 pairing to track a long run? Not really but will try a shorty next week to see how it goes.