I am asking for you why the price hike in the US. Lets see

@snow that would make sense

@snow Maybe, I could buy that for a very slow recovery run at 7 - 8 min pace. But 4:10 pace is very close to my absolute limit and it sure does not feel like I am speed walking. But it seems like I am in good company with other walkers It comes back to, if GCT is for one foot per step or for both feet per stride, the rest follows mathematically. I guess Suunto should provide an authorative answer to clear up the confusion.

@Mi_chael said: @Tieutieu It’s possible to skip a step of your interval workout on Run and Run 2 Then I hope It could be an improvement on other watches next updates

@isazi ahh I need a macbook with Apple M1 Chip or higher… My macbook is tooo old. Thank you!!

With version 2.44.52 of the firmware the watch does not vibrate after a successful compass calibration, it plays a sound instead. Also, at least from my experience, unintended calibrations are (almost) non-existent. Here is link to that version, in case it might be useful for your experimentations or if someone wants to downgrade to it. I never updated past this version as it was very stable for my needs and I remember later ones introduced the backlight-related problems, the vibrations, battery drain for some, etc. To be fair, I fave not actively used my 9PP since the end of November 2025.

@VoiGAS Vo2max on a watch isn’t that accurate. Do a coopertest. That’s more accurate. Or do a sport medical test. Then vo2max isn’t calculated but really measured.

@Egika to your point, some road runners like me love the new watch face, celebrating the 2nd fastest American in the marathon ever , with his iconic glasses 🥸

Worst for me is that there are still naps happening in the same time frame as sleep is detected. If you could go in and delete naps or adjust your sleep time (begin and end) like you can with Garmin and Coros, you could at least work around aggressive sleep detection.

@havupuumies That is great to hear!

Thank you for the suggestions. A reset fixed it.

@Egika Hi. So I left my Core 2 on my kitchen table in time mode for 24 hours. I took photos of the time of day/altimeter screen/baro screen yesterday morning and this morning if anyone is interested I’ll post them. At least with my core 2 running latest software: 24 hours later, the altimeter drifted by 46 meters, from 30m to -16m. The baro graph is flat as a pancake (on my other watch the 24 hour graph is a steep incline, going from 1021 to 1027 overnight) At least for me, the watch must be left in baro mode to track changes in air pressure as weather related and lock the alti from drifting. In either time or alti modes, it locks the barometer, so changes in barometric pressure impacts the altimeter and causes the alti to drift accordingly.

@klipowicz said: Your guess would be correct, except I live in Portland, Oregon, and that’s also the city selected in my watch settings. So, a 7-10 minute difference can’t be explained by the difference between my physical location and my phone’s location - unless Suunto has incorrect coordinates programmed into the firmware or incorrect formula to calculate sunrise/sunset. This is exactly the same for me. Live in Vancouver BC. In the morning, sunset on watch shows 15 minutes earlier approximately each day until I pair with app. For some reason sunrise is correct. (?)

Just to let you know - It started to work well 2 days ago.

@Steven-Hambleton said: @snow The Race 3S is Lithium-Ion according to the Suunto website. I see this on the product website: [image: 1792152480533-d7486b42-2018-4183-a854-e7d07c406dbc-image.jpeg] But anyway, I am looking not at the tech, but at the numbers. What we see here is 38h in multiband GNSS and 45h in singel band.