Ionic - Inaccurate automatic run cues!

[Jonathanbaker]

Hi all

My automatic run cues on my Ionic are not accurate. I set the automatic cues at 1 mile intervals and the readings I am getting during my run are not accurate. They have been up to 45 seconds out! They correct themselves when I complete the run and review in the workout summary on the Fitbit & Strava App. But, this is very frustrating as I use this feature to manage my pace whilst running. My Surge was rock solid in this respect.

What is everyone else's experience with automatic run cues?

I live and run in London.

[marlamcg]

Having same issue this morning.   Florida.

[shipo]

Hmmm, my Ionic has been dead on accurate with the exception of the last two mile points of an 8 mile trail run last Friday.  During that run my cues came on schedule through the first six miles and then the tracker got lost and showed me running in place for a mile or more starting at about the 6.5 mile mark.  In that instance, I got the 7-mile cue and the 8-mile cue never sounded.

Said another way, of the 39 miles I've run with my Ionic, 37 of them have had the 1-mile run cue occur on schedule.

[Rich_Laue]

With the Surge the user had to auto start the run tracking,  you say your using the auto detection of tye run. Hqve you tried manually starting the run?

[marlamcg]

Hi, I was using manual start.  Ionic was preset to cue at 0.5miles, buzzed as if it was cueibg but I was only .10 miles from home.  Also, paused while I was moving.  Interstingly, I tried the interval workout with GPS and it worked great.  The ultimate would be to have the interval timer be able to be embedded into the run tracker.  


Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

[shipo]

---

@marlamcg wrote:
Hi, I was using manual start.  Ionic was preset to cue at 0.5miles, buzzed as if it was cueibg but I was only .10 miles from home.  Also, paused while I was moving.  Interstingly, I tried the interval workout with GPS and it worked great.  The ultimate would be to have the interval timer be able to be embedded into the run tracker.  


Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

---

Ahhh, turn off auto-pause, that seems pretty buggy at this point.

[Jonathanbaker]

Thanks Shipo although sounds like we are experiencing different issues. My Ionic knows when a mile is complete, but it is giving me incorrect data as to how quick I ran that mile!

[Jonathanbaker]

Thanks Rich_Laue

I have tried manually starting the run and I am still experiencing accuracy issues with the automated cue timings.

[Jonathanbaker]

I have turned off auto pause as I did have it on! 

[SunsetRunner]

Maybe there's some misunderstanding. Ionic doesn't show your cue time. I found that alert screen after every cue shows your current pace (Yellow) and metrics you chose as a "Top Stat" (white). Of course alert screen should show stats related to recent cue...

Correct me if I'm wrong.

[Jonathanbaker]

Maybe I have misunderstood and if it does indeed show current pace rather than cue split time, this would explain why the readings have appeared to me to be inaccurate!

I have to say, showing current pace at the end of a cue is a pretty pointless metric. Clearly I want to know what time I have just run that particular split in. My Surge does exactly that!

I also have to add that the fitbit manual for ionic does not cover this area in any detail at all.

Very frustrating that it isn't clear what we are looking at!

[marlamcg]

I ran my long run yesterday using interval timer and gps setting.  Ionic did pretty good.  I lost signal at 5.5 miles but it picked me back up somewhere after 6 miles.  Total mileage seemed correct.  Also, I was running a rail to trails so there was lots of tree cover.  

Today, I turned off auto pause and set cues to 1.0 mile interval on run.  Short 2 mile run and all seemed accurate.   

[SunsetRunner]

---

@Jonathanbaker wrote:

Maybe I have misunderstood and if it does indeed show current pace rather than cue split time, this would explain why the readings have appeared to me to be inaccurate!

I have to say, showing current pace at the end of a cue is a pretty pointless metric. Clearly I want to know what time I have just run that particular split in. My Surge does exactly that!

I also have to add that the fitbit manual for ionic does not cover this area in any detail at all.

Very frustrating that it isn't clear what we are looking at!

---

I can now confirm that you can see last lap pace (white) on the alert screen if you choose "lap time" as a top stat. 

[Jonathanbaker]

Thanks Qwerty098, I will give that go!

[megsellner]

How do you make all these adjustments? 

[Jonathanbaker]

@megsellner

Hit the bottom right button to open the exercise app.

Scroll to your exercise eg. run

Press the gear icon at the top left of the screen 

This is where you can make the adjustments 

[hzn68l]

I am having the same problem with split times on the momentary split screen that appears automatically at the splits. The number given does not correspond to the actual time or pace of the interval. The GPS function appears to be accurate. The split times in the summary  screen are accurate but do not correspond to the observed times displayed at the split. The result is worthless information during the run. Obviously, I want the split data to reflect the actual time or pace of the split.

[Jonathanbaker]

@hzn68l the main reading on the summary screen at the end of each split appears to be the pace that you were running at the end of the split eg a point in time as opposed to a period of time. As you say, this metric is actually useless.

I have got around the problem (based on advice from @qwerty earlier in this thread) by setting the bottom stat (in the customize stats menu) to lap time. 

If you do this, the main reading (yellow) on the summary screen is still pace (moment in time), but the bottom stat (smaller white reading) displays your split for the individual lap / cue.

Hope this helps!

[hzn68l]

Thanks! I will try that. However, the issue still needs to be resolved.

Sent from my iPhone

[Flol]

Hi guys,

I just suggested to had the split times of each cue in the run summary display (in addition of the pace, which is worthless, I agree).

Vote for the suggestion if interested: 

https://community.fitbit.com/t5/Feature-Suggestions/Ionic-Exercice-add-display-of-split-times-in-app...