@Brad_Olwin and to the rest of the community, Thanks for your inputs. Looks like I just have to hope and trust that the watch is able to self correct. BTW how can we tell if the watch had already self-adjusted it’s altitude? TIA!

@stromdiddily or we keep it… someone interested in a pair of telemark skis?

@Dimitrios-Kanellopoulos Just a small update/test after the latest firmware update: I exported the FIT files of two moves from Runalyze and used GPXSee to analyze the fit files. The tool has 2 ways to calculate the speed: “By distance/time” or “Recorded by device” Unfortunately the speed with GPS only didn’t improved very much after the latest firmware update if I calculate the speed by distance/time: [image: 1572558979770-1.png] If I calculate the speed by “Recorded by device” it started to look a bit better: [image: 1572558883557-2.png] The move with GPS+GLONASS however looks much cleaner if the speed is recorded by distance/time. Especially the second half [image: 1572559017704-3.png] Is this because of a better/stronger signal if I combine GPS+GLONASS? So it looks like the firmware update solved the speed wobble a little bit, but not quite like the Ambit 3 Peak. The speed spikes are also visible on the watch screen during the move, so it isn’t only the FIT file.

@vimegar sorry… GPS only… this also effects FusedAlti of course

@TELE-HO said in Reminder in Suunto 9 BARO ?: @zhang965 he takes a beer then, too… problem for rehydration solved wanted a bigger one …!!!

@vimegar On the HR side I agree

« Flattening » 3280 feet is quite a big issue for me ! I’m very disappointed !

@slaine It should not take 5 min, mine occurs much more quickly than that. It is possible you missed one. I find the vibration is not very strong and typically have both tones and vibration turned on. If you have the intensity screen available it will be grey outside of the specified zone and if outside of the zone you did receive a notification.

How much cooler does this look compared to the original. I haven’t tried the blue one yet, but it’s just refreshing to see some new color. [image: 1570823712996-img-20191009-wa0002-resized.jpeg] [image: 1570823731194-img-20191009-wa0006-resized.jpeg] And I kept the original black buckle ecause the replacements came with a silver one and this just looks better with the Titanium Black model. [image: 1570823742617-img-20191009-wa0012-resized.jpeg]

@Egika interesting! and thanks for your info! I noticed with my today’s “walk in the park”, I’ve manually adjusted alti to what I THOUGHT is the right alti (at around 11 am) then I went by train to the start point and selected “auto adjust” (around 12:30 pm). before auto adjust it showed 411m, after 422m. 5minutes later I started the activity and the summary the showed lowest point 411m… how does that happen? I only moved uphill after my start at the lakeside.

@sartoric said in Suunto 9 Baro Watch Face ??: Maybe, just guessing, you’re tapping on the touchscreen … maybe … on the unlocked watch face …

Reset works perfectly Thanks

The reason Strava shows correct elevation profile and elevation gain is that for non-baro devices it ignores altitude data from the uploaded FIT file and instead uses its own elevation database. In contrast, Movescount uses GPS elevation from the watch in this case, which is known to be fairly inaccurate. If you care about accurate elevation you should have gotten a baro model.

As a result, received following reply from Suunto Customer Support: " … Please be advised that for the information when mm Hg unit will be added to the watch’s option is still uncertain but rest assure that your suggestion will be sent as a feedback to our developer. We do not want to make promises that we can’t fulfill we will just keep you updated via Suunto app. … "

@Dimitrios-Kanellopoulos thanks.

@sartoric tried that. so far so good. will try a few more times to see if it keeps acting “normally” or whether the problem recurs

@silentvoyager I’ve read again your post and checked your solution about pressing the middle button enough to not change the screen but before entering the menu and I think that’s not bad. You have to get used to press about 1 second and you have to press about 4 seconds to enter the menu, so you have a 3 second range, which is not bad at all. For me now all the mentioned solutions are good enough, depending on the situation.

If I remember well, all the sport modes related to mountain (not only “mountain mode”) should have the barometer automatically set to “altimeter” and FusedAlti ready to kick in, to give priority to altitude changes measurement

@Darjan-Savšek yes it is possible and perhaps its worked on

@silentvoyager there is for sure room for improvement. I created an issue for this btw. I don’t leave these stuff undocumented.