help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Pace and elevation accuracy issues on Fitbit app

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

‎06-06-2018 15:40 - last edited on ‎06-13-2018 07:56 by Moderator Alum

‎06-06-2018 15:40 - last edited on ‎06-13-2018 07:56 by Moderator Alum

So I've noticed that ever since I started using the fitbit app to track my workouts, instead of Map My Walk... the fitbit app detects variations in pace that don't actually happen. I was walking at a consistent pace of 16 to 18 minutes per mile, yet the app says I took numerous dives to 30 minutes per mile. Additionally, there is inaccurate readings for the elevation as well. This does not happen on Map My Walk, so I'm not sure what's going on here. Any words of wisdom?

Untitled.pngModerator edit: Updated subject for clarity

Best Answer
0 Votes
3 REPLIES 3

‎06-13-2018 07:54 - last edited on ‎03-26-2025 07:29 by Fitbit Moderator

‎06-13-2018 07:54 - last edited on ‎03-26-2025 07:29 by Fitbit Moderator

Huh, this does look very strange indeed @MetalMastodon.

I'm not really sure what could have caused this and in this situation, if it was the tracker, I'd recommend giving it a restart, but since it's something with the app directly, I'm not very sure what could it be.

You could probably try logging out of the app and logging back in and see if this makes any difference. Now, when it comes to the elevation, I was also noticing some issues with the elevation gain calculation. I've already escalated this and as soon as I get any update, I'll be sure to let you know!

If you need anything else, I'm here to help.

Ps. I'm moving your post to the Android app board for categorization purposes.

Ferdin | Community Moderator, Fitbit

Help others by giving votes and marking helpful solutions as Accepted

Best Answer

‎06-13-2018 11:01

In response to FerdinandFitbit

‎06-13-2018 11:01

Hey man thanks for the reply.  I had already tried that and some other possible fixes. It didn't work. Very perplexing since Fitbit uses the same GPS as MapMyWalk....  hopefully they can fix it soon 🙂

Best Answer
0 Votes

‎06-13-2018 11:21 - edited ‎06-13-2018 11:35

In response to FerdinandFitbit

‎06-13-2018 11:21 - edited ‎06-13-2018 11:35

Here is a comparison between Fitbit and MMW readings for the same workout, this one from yesterday. As you can see, the problem continues. Note that the major dive near the start of the work-out was real, as I had stopped into the store to get some water at that time. All other recorded "dives" in pace did not actually happen. You can also see some unnatural and inaccurate rapid variations with the elevation here. Additionally, this affects the average pace and elevation gain reading... as MMW shows my average pace being 19:27 per mile with an elevation gain of 97 ft. Meanwhile Fitbit shows 20:07 with no elevation gain. (also note I do not have Fitbit and MMW synced, they were working independently from one another... so this does not have to do with third party integration problems. It appears to be an independent problem with Fitbit app's reading of the GPS data)

Untitled.png

Best Answer
0 Votes