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: 

Cues not being recorded correctly

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

‎10-28-2019 15:00 - last edited on ‎10-29-2019 15:37 by Fitbit Moderator

‎10-28-2019 15:00 - last edited on ‎10-29-2019 15:37 by Fitbit Moderator

I have recently moved over from IOS to Android and now my cues whilst I am out on a run dont report accurate distances on my Fitbit Blaze. Today I ran for 6km in a time of 33mins when I look at the recording on the app it only shows 5.12km. I have to say I think this is correct judging by previous runs, but the split time cues were indicating I was running much faster then that recorded on the splits page, never had a problem with this when I used my iphone on IOS.

 

Has anyone any idea what is going wrong and what i could try to sort it out.

 

Moderator edit: Subject for clarity 

Best Answer
0 Votes
2 REPLIES 2

‎10-29-2019 15:36 - last edited on ‎09-18-2025 06:44 by Fitbit Moderator

‎10-29-2019 15:36 - last edited on ‎09-18-2025 06:44 by Fitbit Moderator

Hi @Bankfield88, welcome to the Community Forums, thanks for bringing this to my attention.

I appreciate the information and details that were shared in your post. To better assist you with this, can you please let me know which Android mobile device are you using? When was the first time you experienced this and how many times since then? Does this occur with specific exercises or just with one of them? If you haven't already done so, please restart your Blaze and try the following steps:

  1. Force quit the Fitbit app.
  2. Uninstall the app from your mobile device.
  3. Make sure that the Android version is up to date.
  4. Reboot your mobile device.
  5. Reinstall the Fitbit app.
  6. Login using your account credentials.
  7. Let me know if the issue persists.

Keep me posted and let me know if you require further assistance.

Best Answer
0 Votes

‎10-30-2019 01:24

In response to RicardoFitbit

‎10-30-2019 01:24

Hi
My Android devise is a Honor 20 Pro, I have tried rebooting my watch and reinstalling Fitbit app all without success.
The issue has been present since I switch over from my Apple phone. I have had some runs that appear to be ok, but on the rout I took on Monday I have had an issue 3 or 4 time in the last 6 weeks.
Thanks
Best Answer
0 Votes