2024 bug: pace/distance wrecked, footpod not working either

Fenix 7s SS: So yeah. since this year all my runs have a massive problem: They are too short and slow. Which is great if you do a running programme with a target time.

Last night at 1km into my run I was 80m behind (route I know and have measured many times with watch and phone app). This got even worse when I switched on my footpod, which has a calibration factor of 1 but makes a very subtle poor signal correction on distance in some parts of my route that makes me 'slow down' in these parts without. By 2km though I was 300m behind and my pace was 2min/km slower than on my phone. Basically, the footpod seems to have slowed me down even more. Have not changed anything on my watch, also not the gps settings. Oddly, the track looks good as always, gps set to auto select still. Changing the calibration factor to 1.05 didn't change much, still too slow. 1.1 finally did the trick. Firmware is still 14.68 as it seems stable for me. Satellite configuration checked with further app: all looks good as usual. I have no idea what might be going on here. Any idea?

  • Former Member
    0 Former Member over 1 year ago in reply to 6928399

    Did you try a soft reset?

    Hold the upper left button until it powers down, wait a minute, then turn back on.

  • Trying it now. Will run again tomorrow thus will see if it did anything.

  • Ok, some things have improved with the soft reset. The gps is giving the usual 50m off over 1km distance again. The HR is still messed up and cannot be correlated with cadence, the footpod integration to correct for the small difference is also still a problem. Hmpf.. it's annoying if you do a running programme with a pace goal and the watch constantly complaints that I'm too slow (which I'm not but Garmin undermeasures the distance)

  • Hi, I've got a Venu Sq and I'm having the exact same problem - it might be since the latest update. All the last few runs I have done have been off pacing, gps and HR... really hoping they address this quickly!

  • So I found another problem. I exported the TCX and uploaded it to smashrun and the pace is about 1min/km too fast at any given time compared to what I saw during the run and what ended up on the garmin website but average pace and distance are correct! Use the .fit file. Same. Tried the same with the GPX file and got a much shorter run, average pace is fine, pace at any given time is kind of ok but the whole pace track looks somewhat different. There's something seriously messed up going on here.

  • This reminds me about many threads I've seen and participated  in on the Fenix 6 forum. The symptoms are the same - the distance is too short, the pace is too slow.

    My wild guess that the satellite CPE data on the watch has expired and for whatever reason isn't being updated. Because of that the watch can't properly lock to satellites so the quality of the GPS reception is poor, and the watch increasingly relies on the accelerometer to measure the pace.

    Go to the System -> About system menu. There is one screen that tells the status of CPE. Does it show Current or Expired? 

  • I did. The CPE data is up to date according to the system info. But yeah, it does remind me of the Fenix 6. But the Fenix 6 was always shite while the 7 (s) was fine from the beginning and only started to become shite just now. I'm almost tempted to update to the latest firmware, but seeing the problems still reported here I'm hesitant.

  • So getting a bit closer to the HR problem. It looks like the measurement is dodgy when I don't breathe regularly. With that I mean 3 steps inhale, 4 steps breathe out. Same with 2/3. All is fine with 3/3 or 2/2 for some reason. Been using garmin watches for quite a few years and this one since it came out. Never had this problem before.

  • Former Member
    0 Former Member over 1 year ago in reply to 6928399

    Have you tried totally un-pairing your foot pod from the device, doing another reset, and using just the device on it's own?

    I tried the stryde foot pod a couple times, and it did weird stuff like this, so I returned it.

    Also, you say you are using your phone as a point of reference for distance. Are you 100% sure your phone is giving the correct distance?

  • Yeah, I unpaired it. I also don't constantly use it. It really depends on the route I use. I'm certain about some routes on my phone because they've been measured for a race and the phone is prettySweat smileuch spot on every time. The watch is always short, but the amount of short differs. On good days it's about 50m/1km. Lately it differs a lot between 50m/1km and 300m/1km. And no, the route doesn't Sweat smileddenly change it's length Sweat smile So yeah, phone is consistent, watch is not.