Thanks all for your responses. It definitely seems like something is wrong with the way calories are being recorded in the App, and also that it’s not super clear what is referring to what. Hopefully both things can be fixed (or clarified in the laters case) in a future version of the App.

[image: 1781033297573-img_8023.jpeg] ![image: 1781033353523-img_7995.jpeg] [image: 1781033362263-img_7996.jpeg]

@Mouse-Cruiser THANK YOU!!" Finally worthy advice - skatebording works perfectly. So the guy from support was a little bit out with zones and so on

@Stefan-Kersting maybe more then 1000 ?

@Petr-Manek yep It is the same on Android. Although the help talks about total calories as well…

@Egika said: 22542 I am on 22542 and the behaviour is like posted above.

Have you enabled the previews for the Notifications on the iPhone? https://forum.suunto.com/post/191802

To get notifications on the watch there is also a parameter that has to be enabled on iPhone: Settings / Notifications / Show previews: must be Always or When unlocked. If you keep this setting on Never, the notifications won’t show on the watch

@OutdoorMan said in Time in ZoneSense zones seems to be off: @sky-runner if you don’t count 10 minutes which ZS needs to calibrate, then it’s about 22%. No. The total duration was about 62 minutes. If we discount the first 10 minutes - the remaining time is 52 minutes. The total duration of the red part is is about 5 minutes. That is not 22%. Just to be clear, it claims I spent 11 minutes in the VO2max zone but the graph doesn’t show that.

@Tieutieu it honestly doesn’t make sense 🧐

@Emelyanovich profile - feedback - send roasted to Suunto / Профиль – обратная связь - отправить журнал в Suunto

Just want to chime in that I also came across this today while preparing for an upcoming mountain trail 100k race. This is my first race using a Suunto watch instead of COROS or Garmin. It’s disappointing to: a.) not have an elevation profile in Suunto when importing the official GPX file (from UltraPacer, in this case) b.) not be able to use turn-by-turn guidance With COROS and Garmin, both of these things are non-issues for their users. I understand the bits about the GPX file not containing the elevation data itself, how I can find a workaround, etc., but this should not be my problem, and it never was before. And I don’t know of any fix to get myself turn-by-turn guidance, which would be great when running in the mountains at night, other than to spend hours completely recreating the route myself.

Update after field test (May 2nd): I have now confirmed that the real-time ZoneSense gauge on the watch itself (Vertical 2 / firmware 2.53.42) frequently shows Yellow (Anaerobic) during an easy run at avg 122 bpm — well below my Aerobic threshold (S1 = 130 bpm). This rules out a pure app-side recalculation bug. The issue appears to originate in the firmware 2.53.42 DDFA computation, which was the first version to include ZoneSense as a native function on Vertical 2. The app 3.9.1 seems to faithfully reflect these erroneous watch-side values, whereas the previous app version was apparently applying post-sync correction/smoothing that masked the problem.

@VoiGAS said in SA beta 3.8.1: Strange that there are different translations between the operating systems Yes, indeed. I always wondered why.

@Bigb0zz Thank you! I made two new attempts and I suppose that the problem is linked to a corrupted track I tried to upload. Thank you for the attention and help.