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

Headphone and Chest HRM keep disconnecting

Former Member
Former Member
Had this for a few different firmware now and it’s getting frustrating.

Have reset the watch to factory settings and still an issue. Did a six mile run today and cut off four times so I gave up. The HRM reconnects in a few seconds but you then have to go into the watch to get the headphones reconnected.

Any one else had these issues?

Having already sent the Garmin back once for a dodgy Altimeter (which is the same on the new device), prefer not too have to send another back.
  • My TickR X HRM connection is also quite unstable :(
  • Quick update. Been off running for a couple of weeks but did a couple over the weekend a 7km and 16km. I decided to not use the Bose headphones to see if the issue is isolated to the use of headphones (or a device that demands a lot of transfer of data). Across these 2 runs I had zero dropout of bluetooth for the extenarl HRM and Stryd footpod. I don't have any dropout of the headphones on my phone or Apple TV so I'm guessing it is an issue with the software on the 645M and not the headphones.
  • Former Member
    0 Former Member over 6 years ago
    I'm still having issues. Can do a run and no disconnections but then other days cut out 4/5 times.

    When I run with just the heart rate monitor and no headphones the heart rate monitor never drops out.

    So something is not right. Never had this when I first had watch so has been introduced in later firmwares.

    Time to contact support I think. Ridiculous how a watch bought for music just not fit for purpose.
  • Same, I've totally given up on using headphones until a new firmware or bluetooth/ANT drivers are released cos it's just too frustrating with all the drop outs/reconnects/reboots.
  • Same for me more and more recently - stryd dropping out on too many of my runs. 10 mile road race on Sunday and it dropped after roughly 3.5 miles, this morning dropped after 3.5 miles again. Not sure if the distance is a coincidence. On Sunday I had no other Bluetooth devices connected, today I had headphones. When pace comes from STRYD it means that the split when it drops is slightly off. Any solutions? I am guessing this is a Garmin issue and not a stryd issue, Apart from this I really like everything else about the watch!
  • Former Member
    0 Former Member over 6 years ago
    Garmin support have confirmed this is a problem they are working on. Have sent them my watch data to help.
  • Garmin support have confirmed this is a problem they are working on. Have sent them my watch data to help.


    Good to know, thanks.
  • Former Member
    0 Former Member over 6 years ago
    Anything new on this in the last week? Have only had the watch for a couple weeks and this has happened twice now. I suspect something related to the Garmin Running Power data field -- both times my unit croaked, it knocked that field off my running screens. Anyone have similar experience?
  • I also observe simultaneous dropouts of HR-recording and blutooth music connection on my 645M. Both reconnect after a second or so, happened once in an hour in the last runs (both, HRM and FR are quite new, so not too much statistics yet).
    I am not using power data field. HRM is a Garmin HRM-Run (the recent version, with the red transmitter).

    Odd: dropout during my last runs with HRM and BT-music was also after ~3,5miles, like in the report #16 of joewillgoss ?!
    Speculation: could there be some kind of data-buffer being full after ~3,5miles that need to be moved/cleared whatever, keeping the watch too busy to process the datastream?
    I have no special IQ-apps or fields installed, except for Spotify and a battery widget.

    Good to hear Garmin's aware of the issue and working on it.
    Apart from that: I love this watch !
  • Garmin support have confirmed this is a problem they are working on. Have sent them my watch data to help.


    Any news from Garmin concerning this issue?