Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Blaze and Runkeeper not tracking the same information

Replies are disabled for this topic. Start a new one or visit our Help Center.

First of all, I love my Blaze.  No major complaints.  For mapping runs, though, I've always used Runkeeper.  And just lately I've started doing runs using both Runkeeper and my Blaze at the same time.

 

The distance measurements are always almost exactly the same.  Only difference is that it's about 1-2% lower on the Fitbit than it is on Runkeeper.  But I'm chalking that up to better smoothing of the route.  The Runkeeper maps tends to have me jagging around more, running through people's yards, a quick spike out into the middle of the run, etc.  The Fitbit map is smoother.  So I'm thinking the Fitbit distance measurement is probably a tad more accurate because it doesn't count those jags.

 

But the elevation measurements are way off.  Runkeeper is way more accurate, at least in comparison to the hills I know are really there.  The Fitbit elevation maps seems to be totally made up.  For example, on this morning's run Runkeeper shows me all the hills and valleys that I know are really there, says I started at ended at about 520 feet elevation, which I know is true, and says my entire run had 268 feet of elevation increase.  Fitbit says I started at 165 feet of elevation, went up a single hill to an elevation of 1069 feet, and then slowly came down hill for the last four miles of the run, and even though I went from 165 to 1069, I had a total of 765 feet of elevation climb.

 

I guess I'm not really looking for a fix, but it does mean if I want anything approaching reality for elevation measurements, I need to stick with Runkeeper.  Any ideas why elevation could be so fictitious?

 

 

Moderator edit: updated subject for clarity

Best Answer
0 Votes
1 REPLY 1

Hello there @CardboardElvis, thanks for stopping by. I'm sorry for the late response. Thank you so much for the details provided. 

If the activity on your Blaze ended without you making it to end, I would say it could be because of your sleeve probably. If your tracker loses GPS connectivity with your phone or even if it loses connectivity bluetooth connectivity with your phone, the activity will not give you a GPS map in the end but will still log your activity.

Also, your activity tracker doesn't stop if it considers you've stopped running, it will continue to track that until you decide to stop it.

What I can recommend to make sure this will not happen again, is to restart your tracker. You can easily do this by pressing the left and lower right buttons for 10-12 seconds. This will make your tracker to reboot.

Also, it could help setting it up as a new device. For this, go to the Account section at the top right corner on the Fitbit app and select the option that says "Set up a new device". Follow the on-screen instructions and once you're done, your tracker should be syncing without a problem.

Whenever you're recording any exercise, make sure nothing gets on the way of the display that could press any button and make the activities to stop.

Let me know if you need further assistance, I'll be around. 

Maria | Community Moderator, Fitbit


Was my post helpful? Give it a thumbs up to show your appreciation! Of course, if this was the answer you were looking for, don't forget to make it the Best Answer! Als...

Best Answer
0 Votes