01-21-2018 11:02
01-21-2018 11:02
Normally when I start a run my Blaze is connected and working fine. But anywhere from 1-2 miles in, it will buzz and give a disconnected error. It supposedly keeps tracking my distance and time, but is way off (I'm guessing because it's not connected to the phone's GPS).
I've tried some of what's suggested in the forums, without finding a solution. I use bluetooth with a number of other devices and have no issues. On the last several runs I've had nothing connected to my phone except the Blaze, and so it's not interference from something else. And I've had it fail when the watch is on my left wrist and my phone is in my left hand, so it's not out of range.
Is there any solution to this?
01-23-2018 04:38
01-23-2018 04:38
Hello @Bfordham, good to have you here as a new member of the Fitbit Community! Indeed, the issue with the time and distance most likely is related to the GPS is loosing connection with your tracker as you mentioned.
If the issue persists on a daily basis, beside the recommendations you have tried already, review the following post: My Blaze GPS is not working.
Keep in mind a weak GPS signal can be caused by environmental factors such as tall buildings, dense forest, steep hills, or even thick cloud cover. All of these factors can interrupt the connection between your tracker and GPS satellites.
Hope this helps. See you until the next opportunity.
"Great things are done by a series of small things brought together.” What's Cooking?