Software 2.9 Issues

I've had the nuisance alarm reset issue with 2.4 and 2.7, not holding out much hope for 2.9 it seems

I had the same problem with the default software that shipped with my watch (I think it was 2.40). Then, I tried the beta hoping that would resolve it. I previously posted that the beta software didn't fix it and my settings would revert with the GC sync. When someone else reported that it was fixed for them, I did a completely wipe of the watch and reset it. I also removed GC from my iPhone and reinstalled.

Lo and behold, the problem went away. The settings would stay between syncs with 2.72 and, I am happy to say, still work after upgrading to 2.90. They did revert back after the initial install of 2.90, but once changed (and after doing a GC sync), the settings stayed as I set them.

Hope this helps.

I rescind my comment. My problem with settings changing back after a sync persist.

I rescind my comment. My problem with settings changing back after a sync persist.

I'm also seeing the issue of alarms being over-ridden on my F5. After some further testing, it seems that both on 2.72 and 2.90 the alarms survived initial BLE syncs with GCM, but as soon as a sync had happened that ended in the 'Updating' splash screen with the swirling border, then the alarms previously set on the watch were gone.

If this is the worst issue I think we'll be OK going forward...:p

If this is the worst issue I think we'll be OK going forward...:p

I absolutely agree. The Fenix 5 range has released with substantially more 'mature' software than has previously been the case with many Garmin watches; but some still seem to think the Fenix 5 series will be riddled with horrendous bugs for months to come, which I just don't think is correct https://forums.garmin.com/showthread.php?373283-I-m-happy-with-my-3-HR-looks-like-5X-is-having-new-product-pains

All that said, there are still some minor bugs/issues that should be highlighted to the dev team (contact email details on the beta thread) so that they can be quickly eliminated.

Just ask them to let the ability of insert the correct MSL pressure for barometer because mine is off of almost +3/4mb... It's a feature that takes only few minutes to implement... Correct pressure reading is much important for hiking and camping... after all is an outdoor watch...

Various Issues

Following the update to 2.90 - my F5 will no longer detect my Garmin chest HR strap, my edge 1000 still picks it up but the F5 not only won't connect but won't even find it. The reason this is a huge problem is down to the watch learning about you because it now will not account for today's 50 mile ride and hence think I should be recovered tomorrow after a day off that I clearly haven't had, this renders a lot of these metrics useless and certainly means I do not get what I was wanting from this watch.

Also most of my sensors were wiped out from the update but at least I was able to reconnect.

In other news I have the following big issues with the F5 which potentially means I'll have to send it back (hopefully not and someone can help)

Calories will randomly be crazy high and I mean 1,300 per hour for very easy exercise 105 bpm - again the edge corroborates the issue as I have kj to use as a rough measure when cycling. I can give links to burning 370 cals in 6 minutes at around 100 bpm on my 2 mile commute. All user settings inttact and correct

It will not connect to my stages power meter via ant+ (at all) and when connecting to it via bluetooth there are frequent dropouts so data is unreliable

It will not hold a signal to my jabra HR earphones again other devices do not seem to have a problem including a Suunto Spartan (not a huge problem if it will pick up the chest strap again in the future)

Optical HR when cycling is pointless but not really an issue for as I'll wear the chest strap when I can get it to reconnect.

Any advice is very welcome or even someone sharing same issues would at least add some weight to my case.

thanks, Vince.

Quick update

My alarm is now working and GC is not resetting the times set. Not quite sure how or why it's now working.

One other issue I have found is that the Heart Rate Variability Stress records are not shown in GC, so I will advise the beta team on this one.

I have the same problem with my HRMRUN. After upgrading to 2.90 it no longer shows up under sensors and I am unable to re-pair it.