Related

Issues with Pacing and Step Count on Forerunner 965 After Latest Update.

1805625
9 months ago

Hi everyone,

I’ve been experiencing issues with my Garmin Forerunner 965 since the latest update. Specifically:

1. The pacing is inaccurate during my runs. When I increase speed, the pace shown on the watch doesn’t adjust in real time and sometimes freezes.

2. The step count during runs is noticeably lower than usual, which wasn’t an issue before the update.

Here’s what I’ve tried so far:

Resetting the watch to factory settings.

Re-calibrating GPS and ensuring it’s set to Multi-Band.

Updating the software to the latest version.

Restarting all connections with my phone and the Garmin Connect app

Unfortunately, none of these steps resolved the issue. Has anyone else experienced this? If so, were you able to fix it, or is it likely a bug with the latest firmware?

Looking forward to hearing your thoughts!

  • 0 3 months ago

    I had the same issue with incorrect distance/pace data while running. The faster I run the slower pace my watch would show. It was frustrating especially during interval sessions. 

    The issue for me was that my HRM-PRO would be the main pace counting device. So I had to disable pace and speed readings at Settings - Sensors for my HRM-PRO. To so, you'll have to wear the HRM so it would be connected to the watch and disable pace and speed readings  at Settings. 

    This helped immediately and pace is now adequate because it is being provided by GPS and not by chest strap.      

  • 0 8 days ago in reply to 3205092

    since i used the HRM pro ive been through that problem about my pace too

  • 0 5 days ago in reply to 3205092

    Just to clarify, the setting has the options: alway, never, indoor.
    Mine is set (by default I guess) to indoor, which makes sense for me since no GPS data available.
    So what was it set to in your situation?
    Always- which of course would not take the watchs gps.
    Indoor- would mean that there is a bug and for outdoor runs it took the HRM pace and distance by failure.

  • 0 4 days ago in reply to Marc

    When you set Use HRM-Pro Plus for Pace/Distance = Always

    • The Garmin watch will prioritize pace and distance from the HRM-Pro Plus (the chest-strap accelerometer) instead of GPS.

    • HRM-Pro Plus measures pace/distance based on acceleration + stride length → it’s not GPS, so:

      • It is very stable (pace won’t jump around when GPS is weak).

      • But it needs to be properly calibrated (via outdoor GPS or manual calibration).

    Red circle Why you see differences compared to your friend’s GPS?

    1. Auto Calibrate not accurate yet

      • If you haven’t run enough outdoors with GPS for the HRM-Pro Plus to “learn” your stride length, the data will be off (e.g., running faster/slower than usual changes stride length → pace shifts).

    2. HRM measures based on your individual stride

      • Different people = different stride lengths → so even if you run side by side, results may differ.

    3. GPS vs Footpod (HRM-Pro)

      • GPS outdoors has its own errors (depending on route, trees, tall buildings), but usually matches the actual distance covered.

      • HRM-Pro Plus is generally more consistent (especially when GPS is weak), but if calibration is wrong, the entire distance will be off.

    4. You set it to “Always”

      • Meaning even with good GPS, the watch still takes pace/distance from HRM → so it won’t match your friend’s GPS.

    Gear️ Solution

    • If you run outdoors with good GPS:
       Point right Set Use HRM-Pro for Pace/Distance = Indoor Only (recommended). That way, the watch uses GPS outdoors and HRM only for treadmill runs.

    • If you still want to use HRM outdoors (Always):
       Point right Do a few outdoor runs with good GPS and keep Auto Calibrate on, so the HRM can learn your stride length. After a few sessions it will become much more accurate.

  • 0 4 days ago in reply to 6303236

    Thanks for the detailed explanation. However, my question was more about whether there was a bug (in case  had it set to "Indoor Only, but it was not working outside) or if he had set the setting "always", which, as you explained, would never use GPS.