10-02-2017 04:30
10-02-2017 04:30
Unfortunately the default cue for the Run exercise is .5 miles. On the Surge, it was 1 mile. Most people want to see their pace per mile, not 1/2 mile. I went in to the settings gear for Run and changed to 1.0. This worked for that run. However it resets back to .5 mile for the next run. It doesn't save the cue setting for me. My runs automatically transfer to Strava. Strava picks up .5 mile cues as Lap Times. Not usable. Please fix to allow permanent save of cue default. Or change default to 1 mile. Thanks!
10-03-2017 07:19
10-03-2017 07:19
I'm having the same issue! It's so frustrating.
10-03-2017 17:23
10-03-2017 17:23
Same problem here. A little annoying to have to remember to change every time
10-27-2017 04:03
10-27-2017 04:03
I am having the same issue. Even though I have specified 1 mile intervals directly on the watch, the phone app, and Fitbit.com, the interval resets to .5 miles. Please fix this!
10-27-2017 04:34
10-27-2017 04:34
Same thing here, very frustrating. Has to be a bug, hopefully this will get fixed!
10-27-2017 05:00
10-27-2017 05:00
10-27-2017 06:50
10-27-2017 06:50
Agreed, I find it annoying I need to set the cue prior to every run.
10-27-2017 23:57
10-27-2017 23:57
How silly! Does it do the same in km? I know it needs fixing, but in the meantime, is that an option? As a runner I prefer to use miles but I understand kms so that would perhaps work for me. Seriously considering purchasing this to replace my flagging TomTom Multisport and upgrade from my Charge 2 in one hit, so would like to know if this works.
10-28-2017 05:28
10-28-2017 05:28
I figured out how to do it through the computer and it works fine for me now. Trying to adjust it on the watch is the only place it doesn't stick.
10-28-2017 06:08
10-28-2017 06:08
@Cantryboy wrote:I figured out how to do it through the computer and it works fine for me now. Trying to adjust it on the watch is the only place it doesn't stick.
Awesome, thanks for the tip; I just reset mine to a mile. 🙂
10-28-2017 09:43
10-28-2017 09:43
Ah, thanks for the update. I think I probably will go for it ☺️
10-28-2017 10:21
10-28-2017 10:21
Hey!
I had this problem for a while - what worked for me is that I amended the settings via the Fitbit dashboard via the website on my laptop. After, it seemed to sync up to my tablet and then to my Ionic and has worked since.
Might be worth giving that a go - seems it has worked for others 🙂
10-28-2017 10:36
10-28-2017 10:36
The cue is your pace for the mile, so you get one at 0.5 and 1.0 mile....but both are your mile pace.
The bigger issue is that the pace is horrible ly inaccurate and needs immediate fixing. The pace shown is a snap shot of your pace at that moment, not your average over that 0.5. What a munumental screw up right now.
10-28-2017 12:25 - edited 10-28-2017 12:25
10-28-2017 12:25 - edited 10-28-2017 12:25
@racertempo wrote:The cue is your pace for the mile, so you get one at 0.5 and 1.0 mile....but both are your mile pace.
The bigger issue is that the pace is horrible ly inaccurate and needs immediate fixing. The pace shown is a snap shot of your pace at that moment, not your average over that 0.5. What a munumental screw up right now.
I still don't understand why folks are so hung up about the pace cue; one's pace varies throughout the course of a run, fact of life.
10-28-2017 12:50
10-28-2017 12:50
I'm looking for a reasonably accurate pace whenever I look at my wrist (appreciate there may be a little lag when I speed up it down) and a fully accurate record at the end of my run. Is this what the Ionic achieves? I want to replace a running watch with it, but only if it's up to the job. My Charge shows my pace as faster than it is due to the lack of accuracy in the connected phone's GPS. I guess what I'm really asking is, is the GPS in the Ionic on a par with a TomTom or Garmin device? Appreciate any feedback. Thanks
10-28-2017 13:13
10-28-2017 13:13
10-28-2017 16:06
10-28-2017 16:06
@hzn68l wrote:
Are you certain that the 1 mile interval is holding? Everything will look good for a while but it eventually turns back to half mile. This includes the watch, the app, and Fitbit. com. In the app, even though the summary says 1 mile, the selection wheel below will read .5 mile. Check it out.
Sent from my iPhone
Mine held, I went on two runs today and both triggered the alert at 1-mile intervals. 🙂
10-28-2017 16:32
10-28-2017 16:32
10-28-2017 17:04
10-28-2017 17:04
@Troutking wrote:
You are correct! I just checked my watch and you're right. It is back to .5 miles. Only worked for a little while. I'll change to not fixed.
Hmmm, just checked mine and it is still at 1.0 miles. As a side note, I synched my Ionic from my laptop shortly after I changed the setting instead of synching it from my phone. Don't know if that made a difference or not.
06-22-2018 16:38
06-22-2018 16:38
Can you tell me where you you went to changed it on the computer...