10-06-2016 21:49
10-06-2016 21:49
My Blaze has always been fairly accurate. I often run a route, and then compare it to a map to see how accurate it is, and haven't had any discrepancies. However, I recently did a tracker software update, and have run twice since... both very inaccurate. The first run said my miles were 8 min miles... I usually run about 10:30/11 min miles. Todays run on mapmyrun was 3.5 miles... the Blaze said 4.27 miles. Any thoughts as to why it is now so inaccurate? A main reason I got this watch was to use the GPS function for run tracking. TIA
10-09-2016 06:17
10-09-2016 06:17
Hi there @krreinecke. Good to see you in the Community!
I'm sorry to hear that your tracker is not being accurate. I would recommend making sure that whenever you're running you have a good signal reception as the GPS functionality relies on the GPS of your phone and a weak signal could cause inaccuracies to show up. Also, you can try to restart your tracker by pressing and holding the left and lower right buttons for 10-12 seconds and after it reboots, try it out and see how it goes.
Let me know if you need more help with this.
Help others by giving votes and marking helpful solutions as Accepted
10-09-2016 12:11 - edited 10-09-2016 12:12
10-09-2016 12:11 - edited 10-09-2016 12:12
@FerdinandFitbit wrote:Hi there @krreinecke. Good to see you in the Community!
I'm sorry to hear that your tracker is not being accurate. I would recommend making sure that whenever you're running you have a good signal reception as the GPS functionality relies on the GPS of your phone and a weak signal could cause inaccuracies to show up. Also, you can try to restart your tracker by pressing and holding the left and lower right buttons for 10-12 seconds and after it reboots, try it out and see how it goes.
Let me know if you need more help with this.
Wish it was so simple to blame it on the connection to the phone. Every single time im out jogging its off, way off. I use the google map log to get the real distance from when i was out, while fitbit log it porly. Like last time i was out jogging 6 km, it showed 11,25 km. its off by 5250 meters. THis is a major bug, if every single app are able to show real gps distance and fitbit aint, there is an issue regarding this. I have well documented over several runs this summer and with the new update that came. I wish that this bug could be fixed. If the app logged the real distance with the gps and gave the lengt to the blaze, i would be happy.
10-12-2016 14:36
10-12-2016 14:36
10-13-2016 00:13
10-13-2016 00:13
Glad to hear someone has the same problem. Fitbit seem not to respond to this kinda bug, i do hope they fix it soon.