@Johan-Ulijn yes, maybe parse them with fitfiletools or gotoes will solve this

@sky-runner On my watchface: Weather, Sunset Distance Moon I use: Weather to estimate quick what clothes I should put on. When in doubt, I’ll check it on my phone. Sunset/-Rise to plan my run (it’s forbidden to run in my forest when the sun is not up) Distance since I keep recalculate my cumulative distance during the week. It’s conveinient for me to see it on my watchface Moon because I like the moon. It’s just for fun, but also: I love a moon-run in, especially in this snow; I love the ash-grey crescent moon. I do want to know when to look up The same could count for the CTL and TSB metrics. I haven’t been using this much since the TSB hasn’t been 0 till yesterday since I’m only 2,5 months at Suunto. I could imagine I won’t look it on my app every week. But I would like some estimation on my watch. When it’s off I would analyse in my app. The only real reason to use the app is for the route planning

@yadihinz I need to move this topic, which watch and which phone os?

@suzzlo It shouldn’t be - tap watch icon, choose watch, make changes. I don’t know how settings are stored on the watch but my assumption it’s some kind of xml or JSON which should be really easy to back up and restore granularly.

@AYHAN-YILDIZ if your headset can accept a call, it should also be able to reject a call. At least all headsets I know can. Ignoring a call is always safer than rejecting while riding IMHO.

I use this regularly and considering it is a 3rd party developer/app I am not sure how/when/if it would become a “Suunto” app/feature. Great solution to a missing function in the Suunto platform and kudos tot eh developer!

@Simon-Rasmussen I agree. That would make it much easier to categorize notifications at a glance. Right now, it feels a bit outdated.

I’m still in need of this one. Or the “remember the last 5-10 used timers” and present it as a list. Like the short list of the sports modes…

@OutdoorMan I also find the existing limit of 3 data screens limiting, and there is absolutely no good reason why this limit exists. Keep in mind that older users with declining eyesight want fewer larger font fields per screen. I try to not exceed 4 fields per screen, and if I want to use a graph data field, that limits that screen to two fields. For example, on the main screen I have elapsed time, distance, HR, average pace. Then I always have a screen dedicated to vertical stats - current elevation, ascent, descent, vertical speed. That leaves me with only one data screen for everything else, and I have to think hard what I have there. Also, I like to have a screen focused on the current performance including pace, HR, cadence, etc. But then I also want fields like the battery level, sunset/sunrise time, etc. Also that leaves me no way to use any lap specific fields, which are sometimes useful when racing. I end up using some S+ apps as a workaround to have additional fields. But that is a rather poor workaround.

@hschwaiger I wonder If the TSSp is not based on the normalized power (instead of the “standard” power), which means it’s already accounting for uphills in the TSS score (but not how technical the trail is of course)? At least I can see that my runs with ascent get more TSSp than flat runs with same distance and pace…

@Piiipmatz Tracks visible when zoomed out like it used to be would be a good start…