7.60 bug in barometer

The barometer is sensitive to pool swims. In the F3 there was some masking that caused these huge changes not to affect either the altimeter or barometer, but it looks like similar functionality hasn't been ported to the F5(x) yet.

See attached for the effect of an open water swim in the ocean. Altimeter remained constant throughout. ciq.forums.garmin.com/.../1299074.jpg

0 AllanOlesen67 over 7 years ago

Are you sure about the Fenix 3? I use the F3 for sea kayaking, and my altitude dives for some hundred meters when I do a greenland roll where the watch get submerged. So there does not seem to be any masking going on there, at least.

0 Former Member over 7 years ago

There was a patch a while ago that took care of the issue but it doesn't always work. There've been times I swam and found the altimeter at the same altitude as before swimming and times it went totally upside down afterwards. All surpassed, two baros dead in a row... one only lasted 2 months and I'm past the second week without watch now.

Please those of you who do pool swim check on the "missing length" bug fix Renton and I reported. I can't... watch still at tech service (2 weeks).

0 MDGr over 7 years ago

Are you sure about the Fenix 3? I use the F3 for sea kayaking, and my altitude dives for some hundred meters when I do a greenland roll where the watch get submerged. So there does not seem to be any masking going on there, at least.

So when the watch _isnt_ in a swim mode I had the behaviour you described. But the F3 was excellent and preventing those spikes when activity was logged as a swim.

0 MDGr over 7 years ago

Please those of you who do pool swim check on the "missing length" bug fix Renton and I reported. I can't... watch still at tech service (2 weeks).

How is this related to spikes in the recorded barometric pressure caused by swimming?

0 Former Member over 7 years ago

I know he's looking but we can't type in the beta thread since it's locked.
(sorry I know it's OT)