This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

First Gen HRM-Run drops out after 2-ish mins

Former Member
Former Member
Second run with the new 5X+ and it did the same thing on each run - all strap related data; ground contact time & balance, stride length, vert oscillation, etc. stops recording at around 2 mins 14 seconds. My wife's new 5+ (not X) is doing the exact same thing. Still getting heart rate, cadence, etc, but that is likely coming from the watch when it drops the strap out. Battery changed in our HRM Runs a couple weeks ago.

We both just upgraded from 5X's which worked fine with the straps.
  • Former Member
    0 Former Member over 7 years ago
    I am not sure if this useful , but on my f5x+ I don't have this issue (yet) but I have in the watch configuration/system/save every second.
    please check if you have the same and do test


    Thanks, and yes we're using 1 second recording. The very first run was smart recording (default), but all others are 1 second.
  • You can add me to the 2:08 fallouts with HRrun 1st generation. (Mod. 1752 Garmin SW-V 6.60 Batterie o.k.)
    Today my first run with Fenix 5x+ (till then forerunner 935 without issues with HRrun)
    Fenix runs on 3.1, GPS+Galileo, 1 second recording, only Garmin running power combo Datafield installed.
    tempe and foodpod are connected as well during the run, livetrack was running.

    for a short test i disconnected HRrun from the strap shortly after KM 7, to check if the HR is comming from the strap or the wrist, and i noticed that HR blanked out for a short time.

    The running dynamics pages were gone at around 2:08 and the running power did stop „calculating“. I can see some ocasions with datapoints after 2:08 but running power did not catch up, nor running dynamics datafields came back on the watch.

    maybe this is usefull additional information for you.

    Hier ist meine laufen-Aktivität bei Garmin Connect. #beatyesterday https://connect.garmin.com/modern/activity/2817084335
  • Just wanted to share some findings. While i was experimenting with different settings / options while sitting stationary and wearing my HRrun, it seems that HR stays connected always but running dynamics drop out as soon as there is a bluetooth connection to my phone. I tried to do a run actvity with bluetooth disabled on my phone an i did not notice dropouts in running dynamics.

    If someone else can try and confirm.... or it was only good luck here. I will try without phone on my next run.
  • ......but running dynamics drop out as soon as there is a bluetooth connection to my phone...... If someone else can try and confirm.... or it was only good luck here. I will try without phone on my next run.


    I was intrigued by this, as I normally run without my iPhone, so wondered if this is why I’m not experienveing this issue. So I’ve just done a 5 minute test activity, using the Run app, walking around my garden for 5 minutes with the watch connected to phone throughout. I had LiveTrack enabled and checked the Notifications widget every minute, to ensure phone to watch connection was being maintained throughout. In my case I was still receiving Run Dynamics Data from my HRM Run after 5 minutes, so the phone connection doesn’t seem to “break” things for someone who wasn’t having the problem beforehand anyway.
  • For me it was pretty straight forward. I had a run on Friday, no problems at all. I installed the Garmin Power data fields and had a run on Sunday. Major disaster. Power data "froze" at the start, seems around the 2 minute mark.
    I uninstalled the data fields, will check tomorrow the result.

    It seems to me that one of the Power fields is hugging onto the connection to the Dynamics data and dies, locking the stream.ciq.forums.garmin.com/.../1370324.png
  • I can report the exact same thing. I had no issues with my HRM-RUN until I installed the Garmin Running Power data field last night, then I had consistent dropouts at right around 2 minutes. I took the field off the activity (I was using the Treadmill app) and restarted the watch and still had a dropout. I've uninstalled the data field now but have not had a chance to try another activity with the HRM-RUN.
  • For me it was pretty straight forward. I had a run on Friday, no problems at all. I installed the Garmin Power data fields and had a run on Sunday. Major disaster. Power data "froze" at the start, seems around the 2 minute mark.
    I uninstalled the data fields, will check tomorrow the result.

    It seems to me that one of the Power fields is hugging onto the connection to the Dynamics data and dies, locking the stream.


    Status update: yesterday I removed the data fields from the screens and uninstalled them as well. No reboot of the watch. This morning it still dropped at 2 minutes. Will re-try after reboot.
  • Today i had a run with bluetooth disabled on the iphone.
    The symptom changed. I had a long dropout and serveral short reconnects to the sensors, but it continued to record and the dynamics screen and power ciq were still active. Beside of me having a bad day and bad weather came up...

    here my run
    Hier ist meine laufen-Aktivität bei Garmin Connect. #beatyesterday https://connect.garmin.com/modern/activity/2825957012
  • Status update: yesterday I removed the data fields from the screens and uninstalled them as well. No reboot of the watch. This morning it still dropped at 2 minutes. Will re-try after reboot.


    Nothing changed for today's run so it seems once the power fields were there it gets "stuck" on the watch. Uninstall and multiple reboots (due to the charging percentage issue on the 5) did not help :(
  • Nothing changed for today's run so it seems once the power fields were there it gets "stuck" on the watch. Uninstall and multiple reboots (due to the charging percentage issue on the 5) did not help :(


    Further development: this morning, instead of "Trail Run" I had a "Run" and all was peachy again. RD data for an hour, no interruptions. Will do a Train Run over the weekend to see if the "mud" is stuck in that activity especially or now cleansed from the watch completely...