In general, do not hesitate to contact me at lukas.the.coder@gmail.com. I will try my best to support you. Meanwhile, here are some known issues:
This is a history. In the past, Google disabled my application in the Play Store because the application didn't have an animated splash screen and there was no support for the rotary input. These problems were solved in the meantime and my application is back online.
Heart for Bluetooth works only on watch devices based on Wear OS 3.5 and above.
Tizen based watches are not supported (like Samsung Gear S3).
This application cannot be installed on phones, you can install it only on watch devices with Wear OS. To install it, open the Play Store on your watch and search for Heart for Bluetooth. If you try to install the application in the browser on your PC or on your phone, it will most likely fail.
Ensure in the [Configuration] menu that the 'Always on' mode is on and keep the 'Heart for Bluetooth' application active on the screen. This will ensure a stable data transmission.
When you swipe the application away into the background or the system puts the application into the background, the data is not transmitted. This is a known issue: a new version with a fix will be released soon. This bug is related especially to the Galaxy Watch 4 device. Galaxy Watch 7 keeps the application in the foreground without any interruptions.
There is no easy solution to this problem. This is a security limitation of the watch device. The watch generates with each new app start a random Bluetooth address and appears as a new heart rate monitor, so it has to be re-paired. As a workaround for this problem, I implemented a [Pause] button on the [Activity] screen. If you use the button, all services will shut down to save the battery, but the application stays active and keeps the same Bluetooth address.
The watch keeps showing 1/0 instead of 1/1 on the Connection screen? Make sure your watch has a stabilized Heart Rate value before you start pairing a client device. Sometimes, re-pairing or restarting your watch helps. Unfortunately, some device combinations are just incompatible and will never pair. You may try a factory reset of the watch, some users reported success after this step.
As a workaround, starting another native sports application on the watch in the background keeps the device awake and helps stabilize the connection. Heart for Bluetooth runs on top of that in parallel. Another workaround that might help is enabling the 'Always On' mode on your watch in the Configuration screen.
Garmin Edge 130 is supported, Garmin Edge 530 stopped working after an update of the Edge device a year ago. There is no solution to this problem yet.
Multiple users complained recently about connectivity issues and handshake with the client device will not succeed. There is no solution to this problem yet.
This is not a freeze, it works as designed. When you click the finish button, the background services shut down and a finish flag is shown. You can now end the application by swiping it away.
This behavior is confusing, I am working on a better approach.
Zwift supports two modes for connecting your Watch to PC: direct connection and a bridged connection via Zwift Companion app. If you observe problems, please try both variants, one of them usually works fine.
Google banned the old design because it missed a splash screen and black background. Additionally to that, Google blocked the old Android framework this app was based on. Unfortunately, it is not possible to distribute that version via Google Play Store anymore.
I wonder too this basic function is (was) missing. Actually, Pixel Watch 3 running WearOS 5 supports Heart Rate broadcasting natively, my application is not needed there anymore. See on Reddit.