05-16-2016
04:38
- last edited on
01-09-2019
18:49
by
DavideFitbit
05-16-2016
04:38
- last edited on
01-09-2019
18:49
by
DavideFitbit
I just brought a Blaze and went for 1st run with phone for GPS, the distance is completely incorrect by about 6 kms. Strava had the same incorrect distance. Has anyone else had any issues with Blaze and GPS?
Any idea how to fix this please
Moderator edit: subject updated for clarity
05-16-2016 06:54
05-16-2016 06:54
I use Strava when I ride, and it's always has more distance than my Blaze connected to my iPhone.
I've never seen both be that wrong though. My Blaze is always 3% short compared to my Surge which was +/- 1%.
Support will have you make sure you have a stride length set. But that's a bunch of crap. I've proven to them that they are not using stride length for distance with GPS tracking turned on.
At lot of people complain about distances being short. But 6 KMs that's a huge difference. Over 3 miles... Wow...
They only thing I can think of is you must have been in a very poor GPS signal area. For both to be that wrong.
What was your real distance you ran?
05-16-2016 16:45
05-16-2016 16:45
Hey John
I actually ran 16.8km. I'm trying another GPS system although I've never had any problems with it before with any other fitbits I've had 😞
05-27-2016 17:42
05-27-2016 17:42
Hi guys, i want to know how i get the secon clock face on the left on my fitbit blaze. It isn't in the fitbit app on my phone but it is all over the fitbit website on the blaze.
05-29-2016
14:36
- last edited on
01-09-2019
18:49
by
DavideFitbit
05-29-2016
14:36
- last edited on
01-09-2019
18:49
by
DavideFitbit
I have noticed this too. I love the Fitbit Blaze but there is a huge difference between the gps used on the phone and that of my running watch. Its annoying so at the moment I do not use it for my primary recording device.
01-15-2017 19:01
01-15-2017 19:01
The second from the left is argyl I think. You can select a face from the computer, i don't think you can from your phone.