I did find that TD app permissions for Health, fitness and wellness was set to “Off”, have now alo toggled to “Allow all” (and below it shows that it is allowed to read the hear rate), but unfortunately I am still not getting the HR in the TD app.
Make sure and start your HR broadcast from your watch before starting this (just to be safe) I have 2 forerunners and it connects to all my devices perfectly but I have done some many resets and permissions over time. To me it seems like their is some strange caching that happens on android. You can also try resetting bluetooth and wifi globally to see if my theory is correct.
I found this bug with it not showing HR/Power in your second workout, just change zoom and it fixes it and I have it resolved in a new version coming next week (not the next build but the one after that).
Thanks.
After finally getting HR to display, I started pedaling and it immediately disappeared. Very frustrating.
Ok hopefully the next version coming Sunday or Monday solves this. We worked very hard to remove any potential cache corruption. It’s really strange that it works so perfectly for us with both samsung and pixel on A16 and 2 forerunner watches and other people able to resolve theirs… It’s not you for sure, but it’s just bizzare.
New version is out for Android
Thanks.
Does it work? Please say yes even if it does not
Kiddling…
Yes, the HR works great. Thank you. I did notice that at least 4 times, the power got stuck and I had to press either pause or the increase button to unstick it. Notice after the 15-sec threshold interval, after the 4th 75% threshold interval, and a couple more times after that.
What trainer do you have? I see you leave stuck at lower target longer than stuck at higher target
This should be pretty easy to resolve. We stripped out a lot of our complex code to simplify our ble is part of these types of issues but now we are better position to add some protective cases when target updates fail.
Cycleops Hammer
Hello Alex, sorry for the delay. Happy to report that the HR is now showing. Thank you.
From bad to worse. We keep trying to fix some unique devices and break other devices. We are really getting into mastering bluetooth for the first time. It is shockingly complex to understand how the wide array of devices work differently. Sorry, the next version should resolve this. We will stop touching this ble stuff very soon.
If you wouldn’t mind recording 30 seconds of data here with windows/mac chrome browser
https://trainerday.com/ble-testing.htm
I want to specifically look at your device as it seems a bit different than other issues. I don’t me unique to you specifically but to some more rare group of devices that works a bit different so getting this data will help make sure our automation tests reduce the chances of errors and still fix this one strange lingering one you saw. Todays issue was bigger and affected more devices. Send email to support@trainerday.com
Ok I got your data. Thanks. I fully understand and this issue won’t happen again. Fix should be approved today (hopefully). Submitted it yesterday. Then we can focus on the target not always being set correctly.
I am going to dig deep with my developer to solve this problem. All these different devices have so much interdependencies and all work different.
Yet it worked perfectly up until a few weeks ago.


