This heart rate problem is critical. It's breaking all other metrics. These days in a race my frequency was 210BPM, I think I was dying, lol.
That is correct derek87. Once the beta is either replaced by a newer production/live sw (with a different sw #) or once it has been rolled out to production/live sw (as the same sw #), we ask that new…
Now that Fenix has all forerunner feature why not just do firmware replacement on 955 and upload both betas and updates to both Fenix 7 and forerunner 955 using same firmware
Unfortunately for us, it loks like they are only focused on Fenix series for now. Like if they will only release new features for the forerunner when it's all finished testing in the Fenix.
They should…
Unfortunately for us, it loks like they are only focused on Fenix series for now. Like if they will only release new features for the forerunner when it's all finished testing in the Fenix.
They should at least keep fixing the many bugs.
Now when we try to report a bug in 12.27 in the beta forim they reject it cos it's not beta anymore. Well but the bugs are still there.
i guess. you are right in that there is an upside to the Fenix series bug testing for us.
i *think* that if it's still a bug in 12.27 we report it here unless there is an active thread already. it's not consistent, but perhaps Garmin-Kevin can comment.
That is correct derek87. Once the beta is either replaced by a newer production/live sw (with a different sw #) or once it has been rolled out to production/live sw (as the same sw #), we ask that new threads be started here (or that you contribute your experience in the existing threads) in the main forum app for all devices.
Additionally, the bug reports should only be for when a new issue is realized in or caused by the new beta software. If a previously realized bug continues in a new beta, there should already be a thread started in the main forum app and we ask you to contribute there instead of subitting a bug report.
My apologies if I have not disclosed this information in enough bug reports when closing them or changing their status. I have tried to draw as much attention as I can to existing threads in the main forum apps for all Forerunner devices.
From what I see in the main thread (https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/311787/fr955-heart-rate-reading-errors-during-an-activity) for that report, this looks to be (for now) isolated to you and one other user. At this point, I'd encourage you to reach out to your local Garmin Product Support Team directly.
Hmm I think I recall that DCraimaker talked about similar problems a few years ago. I think his conclusion was that in dry whether with low humidity in combination with some types of training clothes you get HR spikes. So if Im remember correct he is nowadays usually use OHR on upper arm.
I did not see that you have a h10 that’s is working on another device