08-26-2020
06:16
- last edited on
09-08-2020
09:08
by
MatthewFitbit
08-26-2020
06:16
- last edited on
09-08-2020
09:08
by
MatthewFitbit
Hi everyone, has anybody else had this problem? I'm using a Charge 2 which has been fine for years but over the past few months the connected GPS on runs has been way off. Overestimating the distance by at least 1/4 mile, which also makes the pace per mile way off, by at least a full minute. I'm also tracking runs on Nike Run Club app, and since Charge 2 has to pull GPS info from a cellular device, they're both getting GPS info from the same phone but NRC is usually within .1mi of accuracy while Fitbit is incredibly wrong. How can I fix this? My Bluetooth is on, GPS signal is strong where I run, location services are set to "always on", I've reset the device multiple times. I do live in NYC but I run in an outer borough where buildings are not nearly as tall, it's more of a suburb area. Even so, GPS is one of the main features of a Fitbit so it should still work! Any ideas?