Hi Sarah Boudon, sorry, no updates at the moment. I’m keeping this bug open as a way to communicate back to you if anything changes. Unfortunately, there’s nothing we can do about it at this time, as it seems to be some sort of communication issue between your phone and your watch.

Hi Valeriy Kovalenko, I suspect that might be the issue. Because I’m in the pool and let my arm falling, so the 2 devices might not always be able to communicate real time. And if your design expect it, that could be the cause. Instead the companion app on the watch could buffer the data and sync when the comm is re-established? Or at the end of the activity like it’s the case when I’m swimming: the watch store it all, save it and then sync to the phone when the 2 sync

Sarah Boudon, if you’re experiencing this issue during static in a pool, then this is definitely the reason—Bluetooth connections don’t work underwater. Some sort of on-device cache could be a solution, but to be honest, I want to keep the companion app as simple as possible to avoid diverting resources from the main development.

There is a task to create a stand-alone Garmin app (an app that will let you run exercises on your watch without needing your phone nearby, similar to the Apple Watch app): https://feedback.getstamina.app/device-compatibility/p/garmin-stand-alone-app. Once it’s done, you’ll be able to use it in the pool and sync your exercises back to your phone when a connection is available.

Understood, thanks Valeriy

Valeriy Kovalenko unfortunately I see it all the time. And both the app and watch have been restarted in between

To be noted, I don’t those gaps on the garmin app or apple app tracking the heart rate, so I suspect it’s either the companion or the stamenia app

hi, just to let you know it keeps happening. It seems it stops capturing the measurement at the start of the hold each time and then restart at the start of the recovery, tracing a line between the 2 points during the hold.

Interestingly, it captured when I tapped for the contraction

And also, I’m sure it’s not because of the water, because to experiment, I set the last hold longer than I planned to on the app, and the time I was already out continued not to have any heart rate (while for the same duration when in recovery phase on the app, it captures it)