@far-blue No problem. I made research and found interesting solution All is here: https://youtu.be/a_LR1oula_0?si=WlHVB7TmKjmmyJZm I found proper link to calculators described in movie (web page has changed): https://www.8020endurance.com/80-20-zone-calculator/ Today after running test with 3 and 9 minutes intervals I had all data and adjusted all. Should be OK.

I managed to resolve it without reset to factory and without clearing cache and data of the Bluetooth app. I did (not sure of the exact order): Remove old Suunto watch (Spartan Trainer) from the device list in the App Delete Suunto App data/cache (I wanted to unpair the watch from the phone but did not find it in the Bluetooth list(?). Maybe it unpaired when clearing the App data or I misremember.) Turn off Bluetooth on the Phone Unpair (forget) MobileApp on the watch (Settings - Connectivity - Paired devices) Turn off discovery on the watch (Settings - Connectivity - Discovery) Log into app Pair watch again (turn on Bluetooth and Discovery first) Most likely not all of those steps are required but I would rather not have more opportunities to figure out which ones are.

@Brad_Olwin I think you’re right. I also doubt many people are that bothered by it, it’s quite a niche thing. It’s just really useful for hitting specific paces on a track, for example, ave lap pace is super useful for this sort of thing.

@localful watch and version?

I had the same issue on my Race S… HR stop working few second after starting the activity (while green sensor was still active) Strange thing, I noticed that before the run the 24 HR had detection failure on the 12h monitoring and the HR was taking more time to display in the watch menu. I had to soft reset my watch to get back to normal behaviour. 1st time I saw this issue, was ok before the update.

@VoiGAS said in Race S - Customize battery mode: @Brad_Olwin You get 40h on Race S without maps in Performance Mode? 31h is my maximum with dual band. Or do you mean 40h if you switch to endurance and sacrifice the maps option then Correct, Endurance with no maps but you still get breadcrumb track climb guidance etc.

@Sixeela29 en tout cas ce n’est pas Suunto qui bloque puisque les segments strava sont une fonctionnalité strava. Je n’utilise pas strava. les infos pour mettre en œuvre sont dans le manuel.

Its not so much to snap it to track on a Satelite image that might be offset but rather for pace stats and distance

@aiv4r I thought the same thing at first, but then I wore my apple watch and it showed the exact pace at the end like the Suunto was showing during the workout. When I check each of the intervals in the suunto app (graph) I clearly see that the pace was under 4:20 the whole time, then I go back to the normal workout summary and it shows 4:30‍️

@sky-runner totally agree I have returned my suunto bands and buy 2 ultra fit they are way more comfortable and a bit more discreet to wear

@dreamer_ I’ll receive mine tomorrow. I’ll test it on known trails.

Street Names would be great, and the ability to turn off etc. But for me the most important thing is the response and clarity of the maps. On the Suunto Vertical (I haven’t tried any other Suunto watch) the maps are fantastic for responsiveness.Extra data may slow this down.

I somehow prefer the black stainless steel still, but i do find this watch strap really nice!

@Buntmans At this point I would contact support as @isazi suggested

@DianeB Write to this address support-en@suunto.com But be prepared that they take a long time to answer your question. Don’t stop and ask a lot. Although they are very nice haha.

@Tami999 This should also be veritical

@SvenSchroeter just like how geologists can tell the difference between clay and silt by tasting

Hello, I calibrated the compass and now the setting is there.

I have similar issue but looking at the graph I see sporadic drops in altitude of about 100m here and there, of course no wind no clothes or anything that might cause external reading problems. Haven’t found a way to solve it, but watch worked correctly the first 3/4 months. It’s quite a problem since it’s one of the few information that really interest me. Could it be a hardware problem?

@Brad_Olwin Today i updated to 2.40.44 and exactly the same happend with Error 1301. There was also written that something was repaired on the watch.