Original post
I’m currently experiencing an issue with receiving my heart rate signal during an activity on my watch. Yesterday everything worked perfectly — I was able to send my HR data to the app while running without any problems.
Today, however, I’m unable to connect the watch during an activity. Standalone transmission (directly from the watch without an activity running) is still working fine, but that doesn’t help me during workouts like running.
The watch should be broadcasting the heart rate via Bluetooth continuously during activities, but it doesn’t show up anymore when I try to pair it as a new Bluetooth device.
Thank you for your help!
Community Member•2/27/2026, 11:36:26 AM
My phone is a android phone.
Community Member•2/27/2026, 1:00:18 PM
Just to make sure we’re on the same page 🙂
Are you running the HypeRate app directly on your Garmin Forerunner 965?
In that case, you don’t need to connect it to the Android app during an activity.
Community Member•2/27/2026, 2:06:01 PM
If I run the HypeRate app directly on my Garmin watch, it works fine for transmitting heart rate data. However, when I start an activity on my Garmin (for example running), I need to connect the watch to the HypeRate app on my phone via Bluetooth. The reason is that you can’t run two activities at the same time on the watch (e.g., running and the HypeRate app).
The Garmin watch still broadcasts heart rate data during an activity, and the phone app should be able to receive it. I did find a workaround: if I disable and then re-enable heart rate broadcasting on the Garmin watch, the phone app is able to detect and connect to it again. But only after restarting the broadcast of the heart rate!
So I am able to get the HR data during running activities!
Community Member•2/27/2026, 2:12:13 PM
Thank you, that’s extremely helpful information 🙌
You’re absolutely right: Garmin continues broadcasting heart rate during activities, and the phone app should be able to reconnect without needing to restart the broadcast.
The fact that disabling and re-enabling HR broadcast fixes it suggests this might be related to how Android handles BLE re-discovery or cached devices during activity transitions.
We’ll investigate this behavior on our side.
In the meantime, your workaround is perfectly valid and thank you for documenting it so clearly!
