Altimeter bugs or broken because systematic pool swimming activities?

I saw a lot of complains about altimeter.

In my case I think is related to the regular pool swimming activities:

  • Software version 20.60 (may 2022) was the last version with Temperature info during pool swimming activities. Reason:  "The intention is to improve reliability of your temperature sensor along with other sensors" see details here.
  • Since September 2022 I started to experienced strange behavior of altimeter: indicating completely out of range values but still sensing the differences of elevation - still indicating correct nr of floors
  • Since last  November my altimeter starting to indicate crazy values ex: changing from +10000 to -300 in a minute! No more floors counting. The behavior is similar with this one.
  • I tried to calibrate all methods: manual, gps or dem. It behaves like is not recording the new value obtained by calibration.
  • I swim weekly 5-6times/week about 2000m/activity.

I trend to think that my altimeter/barometer sensor is broken and the cause is related to this systematic exposure to pool water. Garmin please give as some more info&recomandation? Shell we announce the competitors that Garmin Fenix 6 series sensors (altimeter) was not designed to resist to systematic pool swimming activities?

  • I don't swim and similar (though less extreme) craziness is observed from FW update to update. It seems that they're trying to fix things but don't get it right :( 

  • Fenix 7, software v11.28, swim 4 rimes a wk with it for the last yr.

    My altimeter was not having any issues until after my last swim this week.  And now it has been bounching from -20k feet to a +70k feet.  Which is beyond what the sensor is ever capable of reading.

    i have tried each calibration method and none have an effect if the sensor is turned on, if I turn off the alt and set it to baro only the calibration will take and it will hold for about an hr or so before going haywire again.  

    On my last run it said I climbed over 100k ft in a hr, which impacting the whole workout file when it was exported to other platforms.

    At this point I'm not sure if the sensor is just damaged, software bug just now showing up, or if there is water in the sensor?  My hope is there is just some water in the sensor and it will dry up in a few more days