04-26-2017 09:59
04-26-2017 09:59
When running small distances ie 5-10 miles, my Blaze is about the same as the Endomondo on my phone. But I've just ran the London Marathon and my Blaze reckons I ran around 32 miles!! Just a tad out!!! Has anyone else had similar problems? If this is the norm, I will get rid of it, because quite frankly, it's useless then!!
04-26-2017 10:15 - edited 04-26-2017 10:17
04-26-2017 10:15 - edited 04-26-2017 10:17
@Ninjadad what m [de did you use ehen recording your marathon, was the connected gps used and a map displayed after a sync?
You say 5-10 miles it is close, but dont say how close. Was the error percentage is it about the same as the marathon?
Without knowing if connected gps, your carrying the phone, was used it is hard to answer.
04-26-2017 11:46
04-26-2017 11:46
04-26-2017 11:46
04-26-2017 11:46
04-26-2017 12:12
04-26-2017 12:12
Without a map, this would mean there was no gps. Your tracker then will use the stride setting to calculate, think it as take an educated guess, at the distance.
Fitbit will use the age, gender height, etc to guess at the users stride setting, this is fine if the user is an average person of which there is no such tging, or let the user set it for them self.
As for using gps in the multisport mode, if enabled there will be a phone icon on the screen of the Blaze. If this icon has a line through it then gps is not connected.
See this doc http://help.fitbit.com/articles/en_US/Help_article/1935 for more info.
04-26-2017 12:40
04-26-2017 12:40
04-26-2017 12:40
04-26-2017 12:40
04-26-2017 12:52
04-26-2017 12:52
Lets go to your Blaze settings - exercise shortcuts - tap on run. Now enable gps
04-26-2017 13:16
04-26-2017 13:16