looks like IOS 26.1 solved the issue. my watch is now finally synching the data

@Brad_Olwin Okay, good. I’ve figured something out: After reinstalling version 2.44.52 on the 9PP, I verified that the NGP values ​​reappeared in the app (for new activities). Then, when I downgraded back to 2.40.44 and I do a new activitie, the NGP value ​​it is not shown again. Finally, I updated once more to 2.44.52, I did an ultímate test and it confirmed that the NGP data was indeed present. So, I haven’t fixed anything, but I’ve found the source of the problem. Now, the thing is, I don’t really like 2.44.52, but going back to 2.40.44 and losing NGP isn’t appealing either.

@2b2bff, oh thanks for that clarification - I missed that , i am going to try that next time

Someone on Reddit posted an image of 48000+ hour recovery time after 130 km race. That is over 5 years! This becomes an embarrassment for Suunto and should be fixed as soon as possible!

Follow-up on my experience doing the actual race. Summary: I’ve used navigation with multiple waypoints during the entire 16 hours of the race After some considerable effort I managed to have the right set of waypoints at exact distances where aid stations were supposed to be on the race course. Two of the aid stations were visited during the race 2 times each. Other aid stations were visited once. Once I’ve had the correct preview of the waypoints in the app (see the picture above), the navigation was working mostly correctly, as expected during the race. The battery usage was exceptional - better than expected despite using navigation for the entire 16 hours and looking at the map and elevation profile most of the time. My Race 1 watch used only 27% of the battery in 16 hours, which makes the projected battery life over 59 hours. I used the High Contrast map theme. Also, I used an external HR sensor. I ran two S+ apps I was using Climb guidance 2.0 with all aid stations on the profile. That worked generally well and was useful. I could track both the remaining distance to each next aid station and the remaining ascent/descent. However I’ve run into two known issues that I’ll mention below. Both of these issues have already been reported in separate threads. [Issue 1]: The navigation route reversed twice during the race - both times when reaching the ends of out-and-back sections. This is something I’ve actually anticipated based on my prior experience - see https://forum.suunto.com/topic/12994/suunto-navigation-tendency-to-auto-reverse-route-when-it-shouldn-t.-bug-or-misguided-feature [image: 1760409898910-screenshot-2025-10-13-at-7.41.59-pm.png] This resulted in the watch showing incorrect profile and incorrect distance to next aid station until I was out of out-and-back sections. [Issue 2] The climb guidance profile could not be zoomed to the desired level of details at the end of the route. This is covered by https://forum.suunto.com/topic/13601/climb-guidance-2.0-issue-not-all-zoom-levels-are-available-at-the-end-of-the-route-see-picture. This was especially bad considering the 100 km distance.

@Brad_Olwin @Miroslava I tried to restart everything, unfortunately HRV is out of sync. Funny thing is that recovery did match for a few seconds (both 79%), then after a few seconds it went up to 81% on the watch.

@Egika looking forward to it I just stumpled upon this oddity: [image: 1760181015173-c41a7a66-154c-4169-8c35-3aa701a682b9-image.png] If you go with “Tritt” as one leg before the other and “Schritt” as the cycle of both legs hitting the ground then you should be consistent. So, it should be “Trittfrequenz” in the first row alltogether, “Schittfrequenz” in the row below, as it currently is. Then it is “Trittlänge” and “Schrittlänge”. The number of steps that is called “Schritte” above - is this number of “Schritte” or number of “Tritte” in that regards?

I have the beta version and it’s happening to me as well.

@Mff73 said in [BUG] Alternative old/new trails are shown in Suunto App route editor depending on the map zoom level: Probably a map caching issue. Maybe try delete app cache and check again? Potentially uninstall / reinstall. These trails changed 4 years ago. I haven’t had my devices for so long. Also, deleting the cache didn’t help. [image: 1759761213654-screenshot-2025-10-06-at-7.32.25-am.png]

@gogapo update: there are more translations issues as you can see in the link I provided. If I change it to English it works fine

@Tieutieu said in Suunto app crashes when filtering summery by tags: I have also reported it several times through beta app (, iOS 24.00 sa version) On my phone (iOS) it crashes so after I tried to filtrered I can’t enter the main menu of the app (recap/activity…) and I also needed to reinstall the app. On my MacBook Pro, reinstalling the app even didn’t solved => app keeps crashing every time I try to access to the menu. [image: 1734414791180-img_3606.jpeg] Update the app to the latest version. If poosible, the best option is Delete the current app and reinstall its latest version. Now, try filtering single tag instead of multiple tags.

@Tieutieu problem solved thanks

Sounds like this might become possible in iOS 26.1 https://www.macrumors.com/2025/09/23/iphones-third-party-smartwatch-features/

@brave_dave my recovery on the app is ALWAYS 90% Watch on the other hand fluctuates

@dankcushions ok so it would not require a watch update but an app/api update. This is probably a good news, hopefully they can fond out how to fix it… Thx for tout insight