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: 

kilometer Run Cues

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

‎01-09-2018 00:47

‎01-09-2018 00:47

Why doesn't ionic have a run cue for 0.5 KM?, mine only shows cue option for .4 km.

Best Answer
4 REPLIES 4

‎01-09-2018 03:45

‎01-09-2018 03:45

0.25 would also be useful. I posted about it previously with regard to the Surge. It appears that support for other than miles is not a priority.

Best Answer
0 Votes

‎01-09-2018 03:49

In response to dude

‎01-09-2018 03:49

thanks for the response. Was wondering if i was missing something obvious.
Best Answer
0 Votes

‎10-19-2018 21:23 - edited ‎10-20-2018 07:24

‎10-19-2018 21:23 - edited ‎10-20-2018 07:24

0.4 km is a useless lap cue - should be a factor of 1 km ( i.e. 100m, 200m, 250m or 500m).  The bigger problem is the 0,4 cue is NOT 400m, but slightly longer  (i.e laps at 5,65km and 6,05 km)  

 

Assume this could be a metric conversion from 440 yards ?

 

Even better - allow user to define the cue distance

 

Suggest Fitbit provides something more useful in next upgrade

Best Answer

‎02-07-2019 04:26

‎02-07-2019 04:26

I agree - the 0,4 Km is useless.  What make sit even more useless is that it is not 400 meters but rather about 403 meters which causes bigger annoyance.

 

But there is another issue that I need someone to advise me on if it is a software issue or a hardware issue.

 

As said before, the laps tick over at just over 400 m - i.e. the 20th lap  should be at 8 km, but it happens at about 8,07 km.  Even worse - the display on the screen when the lap finally occurs shows total distance as 8,00 km - while the distance shown on the watch face is shown as 8,07 km. 

 

Surely this should show the same distance run ?

 

Some one will answer that the screen takes a few seconds to change but that is rubbish.  I have proved this by actually stopping at exactly 8,00 km on the watch face and standing there for a minute - and the lap does not show.  I then moved forward to 8.02 km and stood.  Then moved  to 8.04 km and stood  for a further 2 minutes and still no lap indicator.  when I got to 8,07 km according to the watch face, the lap indicator suddenly appears and shows the lap time and the total distance as 8,00 km.

 

Again the same thing happened at 8,48 km - that should have been 8,40 km

 

Why is this so ?  Is it a software problem or a hardware problem ?

 

How can this be fixed ?

Best Answer
0 Votes