Fenix 5/5S - 4.16 Beta Release

My fenix 5 gets itself into and interesting state every now and then... the following conditions exist in this state:

1. Move and Connection alerts do not auto dismiss, the back button is needed to dismiss them.
2. Vibration stops working with alerts.
3. Heart Rate widget doesn't show history, only the current Heart Rate.
4. The watch doesn't go into "Do not disturb" mode automatically, has to be done manually.

I' have reported this to the beta team, but was wondering if anyone else sees this behaviour? I've noticed this since 4.02

This beta has proved disastrous for me. The barometer was working just fine with 4.1 except it was thrown by swimming. The beta suggested a fix for this, so I gave it a go. The result: the barometer is now entirely useless. It varies by 100s of metres when I walk a short distance. For example, I calibrated it earlier today at 113 metres, the elevation of my house. After walking half a mile to the shops and back it now reads 427m. I've seen it drop to -200 and go up to +800 from this same calibration with no more than a few metres actual change. So the beta *might* have solved the swimming issue, but the cost is that the barometer doesn't work at all.

Moreover, I tried downgrading back to 4.1, but the problem now persists. Really disappointed.

Have you tried cleaning out the barometer port with some warm water?

This beta has proved disastrous for me. The barometer was working just fine with 4.1 except it was thrown by swimming. The beta suggested a fix for this, so I gave it a go. The result: the barometer is now entirely useless. It varies by 100s of metres when I walk a short distance. For example, I calibrated it earlier today at 113 metres, the elevation of my house. After walking half a mile to the shops and back it now reads 427m. I've seen it drop to -200 and go up to +800 from this same calibration with no more than a few metres actual change. So the beta *might* have solved the swimming issue, but the cost is that the barometer doesn't work at all.

Moreover, I tried downgrading back to 4.1, but the problem now persists. Really disappointed.

Have you tried rinsing out/soaking the barometer port with some warm water? There might be some debris trapped in there causing the altitude issues.

I sent this to the beta feedback email, but i'll mention it here. I believe there is some oddness in Vo2 Max calculation on the new firmware. I switched from a Fenix 5 to a Sapphire edition and when I did the switch i decided to try the beta. My first activity i tracked was a pretty lazy mtb ride with my wife and i noticed that the new watch showed a crazy high Vo2 max of about 8 points higher than i'd established on a few runs with the old Fenix 5. I ran this morning and it came down 2 points but it is still probably way higher than what i deserve.

I also didn't get a notification of a new value on either Vo2 Max change. So i believe there might be a bug related to this.

Otherwise the beta seems solid. My Tickr x works fine (connected via ANT+), GPS worked well reasonably well on my ride last night and my run this morning. I do notice that it has me drifting into some of the yards in my neighborhood instead of showing on the sidewalk, but this behavior also existed in 4.10 on the old watch.

My only issue is that i *think* that the Vo2 Max score is probably a bug.

I sent this to the beta feedback email, but i'll mention it here. I believe there is some oddness in Vo2 Max calculation on the new firmware. I switched from a Fenix 5 to a Sapphire edition and when I did the switch i decided to try the beta. My first activity i tracked was a pretty lazy mtb ride with my wife and i noticed that the new watch showed a crazy high Vo2 max of about 8 points higher than i'd established on a few runs with the old Fenix 5. I ran this morning and it came down 2 points but it is still probably way higher than what i deserve.

AFAIK vo2max is calculated only: 1) on "normal" bike activities 2) only with power meter
Thus, 2 question - do you have power meter on your mtb? Did you use the MTB activity on your Fenix?
If you don't have Power Meter and/or you used the MTB activity type, them vo2max shouldn't be calculated at all

I sent this to the beta feedback email, but i'll mention it here. I believe there is some oddness in Vo2 Max calculation on the new firmware. I switched from a Fenix 5 to a Sapphire edition and when I did the switch i decided to try the beta. My first activity i tracked was a pretty lazy mtb ride with my wife and i noticed that the new watch showed a crazy high Vo2 max of about 8 points higher than i'd established on a few runs with the old Fenix 5. I ran this morning and it came down 2 points but it is still probably way higher than what i deserve.

I also didn't get a notification of a new value on either Vo2 Max change. So i believe there might be a bug related to this.

Otherwise the beta seems solid. My Tickr x works fine (connected via ANT+), GPS worked well reasonably well on my ride last night and my run this morning. I do notice that it has me drifting into some of the yards in my neighborhood instead of showing on the sidewalk, but this behavior also existed in 4.10 on the old watch.

My only issue is that i *think* that the Vo2 Max score is probably a bug.

AFAIK Running and Cycling have separate VO2 Max scores, cannot confirm since I did not track any cycling activities.

AFAIK vo2max is calculated only: 1) on "normal" bike activities 2) only with power meter
Thus, 2 question - do you have power meter on your mtb? Did you use the MTB activity on your Fenix?
If you don't have Power Meter and/or you used the MTB activity type, them vo2max shouldn't be calculated at all

I used the MTB activity and I do not have a power meter on my bike. I basically pulled the watch out of the box earlier that day and charged it up. Before the MTB ride I didn't have a vo2 max score shown on the widget. After the ride it showed 52. My old watch had pegged me at 44 after 2 runs. I didn't get a performance notification for the new Vo2 max even with the watch set to notify me.

I went on a run the next day and after saving the run my Vo2 max as reported in connect and via the watch widget showed at 50. I still didn't get a notification on the watch (i did get PR notification for a few different distances and a new LTHR)

I went on a super slow recovery run today and after saving my widget shows 49 for Vo2 Max. I did not get the notification on the watch.

I also know there are 2 different Vo2 Max scores for cycling and running. I do not have a cycling vo2 max score in connect.

So two issues
1. The notification of new Vo2 max score appears to be broken in the beta
2. It is odd that my widget on the watch started showing Vo2 max info after an MTB ride. Did it think i was running? This seems like a pretty big bug.

I have reported both issues and sent .fit files to the beta team.

I believe you only get VO2Max notifications for new high VO2Max numbers. If you have seen 52 then you would need 53 to be notified

I believe you only get VO2Max notifications for new high VO2Max numbers. If you have seen 52 then you would need 53 to be notified

That may be true, but I was never notified of when the 52 value popped up either.