Here we go again! Today while i'm coming at home from the sea, i tried for the first time navigation and voilà: altimeter was totally wrong! When i was near my home that is about 110m asl, altimeter reported 75m! I tried to calibrate it but when i set correct altitude, it started to count slowly to calibrated altitude like my Fenix 5X did; altimeter was set on continous calibration. More info here: https://forums.garmin.com/forum/on-t...on-fast-decent ! I can't believe it! Luckily this time i bought it on Amazon, so if things don't change quickly, i'll return it and i'll stay with my Spartan Ultra that never had this bug!
Altimeter works better for me when I use the appropriate mode for Barometer: --- Changing from default: > Settings > Sensors & Accessories > Barometer > Watch Mode > Auto to > Settings > Sensors & Accessories > Barometer > Watch Mode > Altimeter --- Maybe also changing the recording period could help: > Settings > System > Data Recording > Smart to > Settings > System > Data Recording > Every Second
Maybe you don't want to understand... it's a bug that was solved only few days ago for forerunner 935 and Fenix 5 with latest beta that it isn't release yet for Fenix 5 Plus line and Fenix 5 X
No, I understand. I do not argue with you. I just mentioned what can lead to better results for me EVEN AS the bug is there. Also I think we should be as specific as possible. So I consider even our "arguing" as good for that. So if we could be more specific, it goes here: BUG is FIXED for Forerunner 935 as described below in Change History. --- Forerunner 935 software version 9.73 Beta - as of July 24, 2018 Changes made from version 9.72 to 9.73: ... * Fixed an issue that could cause elevation graphs to be smoothed and total ascent and descent values to be inaccurate. ... --- Hope the bug will be resolved for fenix5Plus series soon as well.
No, I understand. I do not argue with you. I just mentioned what can lead to better results for me EVEN AS the bug is there. Also I think we should be as specific as possible. So I consider even our "arguing" as good for that. So if we could be more specific, it goes here: BUG is FIXED for Forerunner 935 as described below in Change History. --- Forerunner 935 software version 9.73 Beta - as of July 24, 2018 Changes made from version 9.72 to 9.73: ... * Fixed an issue that could cause elevation graphs to be smoothed and total ascent and descent values to be inaccurate. ... --- Hope the bug will be resolved for fenix5Plus series soon as well.
Yes, sorry but i'm not so good in english so what i write could be different from what i would like to write... ;) .
However, i think that the delay is due to maps feature: 9.73b was released for 935 and Fenix 5, both haven't map feature, Fenix 5X and Fenix 5 Plus have... I hope they will fix as soon as possible because since i bought it, I have not been able to use my 700€ watch as i want yet!
A little update, I have done some tests with a brand new out of the box Fenix 5 Plus and an updated Fenix 5 Plus . Both have 3.2 system firmware but the stock one has 2.00 sensor hub firmware, updated one has 2.10 sensor hub firmware. That with 2.10 fw hub firmware exhibit this bug , that one with 2.00 sensor hub firmware works flawlessly! So here you are the proof that 2.10 sensor hub firmware is the cause of this bug!
renton82, will you look at what GPS firmware and sensor hub firmware you have on the stock watch that works? I am having the same issue and I have GPS: 2.20 and sensor hub: 2.10 with Software version 3.10
renton82, will you look at what GPS firmware and sensor hub firmware you have on the stock watch that works? I am having the same issue and I have GPS: 2.20 and sensor hub: 2.10 with Software version 3.10
