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

+1 same issue with my HRM-Run and with RD POD (I tested each of them separately)

Extra info:
- iPhone SE, connected via Bluetooth with the watch and with headphones (I haven't tried a run without it)
- The HRM-Run and the RD Pod reconnect and disconnect multiple times
- In my case, the time when it loses the connection is not consistent (as some people reported here)

Examples:
- https://drive.google.com/open?id=1Vg3hqUFgNbxGAnMzCCk5LTJtZHpNyJh6
- https://drive.google.com/file/d/16zbv1toBDm3n0U1ahUgmQFDF82z3q0gr/view?usp=sharing

Do you guys think it will be solved with a firmware update?

The support is informed about this issue and I mentioned the support case (PSC-23192) as previously mentioned here. I’m not an engineer, but as far as I know the connection to the phone is just bluetooth, the connection between HRMs is an ANT+ connection, nevertheless both working on same frequency band (2.4 GHz). Maybe both antennas create interferences towards the other. The funny thing is, that for two minutes it works perfrectly - within these two minutes there must certainly be the one or the other ping or transmission between phone and watch, which makes me think it can be solved by a firmware update.

I just spoke with tech support regarding our original tickets from 2 months ago. As of yesterday, the ticket was updated with comments that they had identified the issue as being between the Cypress Controller (garmin 5 Plus and FR645M) and phones using BLE 5 controller used in a long list of phones, including the iPhone X. It's moved to a engineering to come up with a solution. No eta, but good to know that they've finally identified the source of it and are able to replicate it.

I wonder if that issue will end up being the root cause of the very unreliable connection between my 5X Plus and iPhone X as well.

Well there is a list of firmware patches for the broadcom chip aka cypress hardware if they need to use, noting a higher risk installation than a normal update...definitely one to do with battery charged imho

https://community.cypress.com/community/linux/blog

i hope this actually gets fixed soon because my bluetooth connection still suffers even with the past public update .

Bluetooth connection with FW update 4.61 (beta) seems a bit better in connection with iPhone X, but after a 10K run I still experienced the same issue with the drops after 2min. FW 4.61 is no solution so far, although there has been a BT/ANT+ update included (2.80).

Has anyone found any resolution to this? I just spent way too much of my day on the phone with Garmin and it is looking like this is going to be a product swap, but I am still wondering if there is a specific issue. I had luck with the disabling the phone connection on 3.1 and 3.56; however, since upgrading to 4.2 or trying the 4.xx beta versions, I have not had any luck with the work around. I am getting extremely frustrated and desperately want the watch to just work. I am wondering if this is a hardware issue, due to it not being universally experienced. I am trying to upload some of the fit data I have from this mornings run. I just grabbed a few snap shots of where it dropped the connection (pg 1), the initial connection that happened at the beginning of the run (pg 2), and where it seemed to be re-establishing connection (pg 4+). This happened multiple times on my run.

Some good news and some bad news.

Good news is UPS delivered my brand new replacement watch from garmin today, yah, and it's on 4.20, all setup, and linked to my new stryd as well.

Bad news, same issue as here, data disappears at 2mins 8 seconds, at least I now have stryd data to replace some of the lost garmin data fields. . .

So fin.pimlico, have you talked to support again? If so, what did they say? I just began initiating an exchange and they swear up and down this is not an universal issue; however, to me, it appears to be pretty damn consistent.