945 Latest Firmware Bugs, Issues and Missing Features

This is exactly what I'm referring to tess.

4338288 said:

No, you're wrong. This is not a settings issue on my side

I said is was probably your setting, not that it was definitely your issue.  No need to get worked up over nothing.

Agreed. I'm sorry. I'm just really frustrated that this watch is not at all living up to my expectations when compared to how it is marketed by Garmin and considering how expensive it is. This after using it since July 2019. Too many issues and bugs. This issue was just the limit for me.

I just came in after another run. Before the run I double checked that my maximum heart rate was set to 204 in both the watch and in Garmin Connect on my Android phone. I also double checked that "auto detect" was off for maximum heart rate in both the watch and the settings in Garmin Connect Mobile. Everything (heart rate zones as a percentage of maximum heart rate of 204) was correct during the run. Then after the run is saved (and automatically synced to my mobile), the maximum heart rate in the watch is again reset to 178. This, even if my maximum heart rate during this particular run was 192. But then again it should not matter since 1. the heart rate should never be updated to something less than input manually according to the manual and 2. "auto detect" is off.

I now double checked in Garmin Connect Mobile AND Garmin Connect Online and in both places it still says "Maximum heart rate" 204. So after the run the watch has reset its value to 178 while the value is still 204 in Garmin Connect Mobile and Garmin Connect Online.

The problem is, as stated by other users in the linked thread, that if I forget to set the maximum heart rate back to 204 before the next run the watch will report totally inaccurate heart rate zones and load and save totally wrong statistics about my training effect and my training status saying that I've been in heart rate zone 5 for e.g. 95 percent of the run. Very annoying.

Thanks for the suggestion tess. Please see my latest answer to "who knows", but yes, the "Max HR" settings value is 204 in both GCM and when I check under "User Profile" for my 945 watch in Garmin Connect Online.

I actually change the setting to 204 in the watch before each run (since it is reset to 178) and after a sync that value is reflected in the GCM app and Garmin Connect Online. But again reset to 178 in the watch after the run.

I've been using Garmin watches for 10 years.  This has happened to me about 4-5 times in that time period.  For some unknown reason, Connect online has reset my HR based on 220-age.  This will then change the settings in GCM.  I have to reset my maxHR and use % of heart rate reserve, save and then sync GCM and my watch for it to take affect.  I'm not sure why yours keeps changing then.  Do you have more then one watch on your account and have the other set to preferred device?

Yes, the thing that has happened to you 4-5 times in total over a period of 10 years is happening to me after every run at the moment. But exactly the same symptom (220-age). Note that this started sometime after Christmas, if I remember correctly, (used to work correctly before that) most probably after an update of the 945 firmware and/or an update of Garmin Connect Mobile for Android. It could actually be an update of the Android app that introduced this issue since that is reported in the 245-thread linked to above (he/se used synced to the Android app). Are you and your neighbor using Garmin Connect for Iphone or Android? 

No, this is my only device and naturally set to preferred device.

Ok. I have a Samsung Galaxy S10 and update all apps every night. I have version 4.26 of Garmin Connect for Android right now (latest for me), updated 6 January (could actually time when the issues started quite well but doesn't have to). Which version do you use? It is common that you don't release new versions to all users at the same time and developers also perform A/B testing for different markets, i.e. different versions. But we should use the same version by now since it was released almost a month ago.

Yeah I know, I could test what you suggest and a lot more. But unfortunately I don't have neither the time nor the motivation as a consumer in this case, having paid for the product, and really just wanted to add this issue to @Roland 's list of known bugs above. 

So as a software engineer I will concentrate on the software I am developing and will leave the fault tracing to Former Member and his development teams so they can diff the code and maybe use git bisect to find out which commit caused the error. Then add automatic regression tests for this and hopefully fix the bug in the next sprint as a high prio task in their sprint backlog. At least they have a lot of information in this thread now to be able to solve the issue.

For the record: Yes I have tried a hard reset (holding power button down for like 15 seconds). No change.

I'm also on 4.26.  You may be on to something though about the GCM version and the type of phone used.  Last year I had to revert back to a previous version of GCM Android on my LG because my text messages stopped after an update.  I use Verizon Messages + as my text app and it stopped working on my LG, but it was working with the new update on my work phone which is a Galaxy S9.  Best of luck.

I have updated the first post and gone through all the mentioned issues and the corresponding threads. According to the them, the issues are still present or there hasn't been any feedback from users. Please let me know if any of the listed issues should be marked as resolved.

What about backcountry skiing ?