I’ve discovered that when general watch brightness is set on high it makes raise to wake low screen is brighter than general brightness low & raise to wake low. Just a bit but enough for me! Didn’t know that its affect each other. I thought that general brightness affect normal use only. Now raise to wake is perfect for me, but when surf menu, checking stats its too bright Maybe this info will help someone.

@Brad_Olwin Aha!! That did it! Perhaps it was a corrupted initial sync? Thank you!!! I’ll relay this feedback to customer support as well. Appreciate you all.

Yes, I had the same problem. It was uploaded to strava incorrectly.[image: 1746112024151-img_20250430_234812.jpg] [image: 1746112024162-img_20250430_234747.jpg] [image: 1746112024173-screenshot_2025-04-30-23-47-09-69_3bb53944894d9646ec5754b62cc2584b.jpg]

Pimped my watch [image: 1746022105556-img_9548.jpeg]

@ilker enjoy your watch : )

After soft reset and another run the Vo2max now appear on the watch…

@Maryn Actually the only thing I did was that I have uninstalled the Beta Suunto App and installed the official App from app store. This issue might be related to the iOS app itself - maybe try to delete, install the app again and test if it helped.

@SnowSailor what data ?

@Sven-Grossenbacher said in Wind added 60% extra elevation: Has anyone else experienced this? Yes, many of us. Is there a known fix or workaround? No. Most manufacturers have a built-in algorithm or threshold to disregard sudden and dramatic changes in elevation that would be impossible for the given activity. Suunto doesn’t seem to employ this. There’s a general unwillingness by some to admit that this is an issue, but there are enough examples in this forum and elsewhere demonstrating that it is, in fact, a problem. Both wind and sudden submersions in water will give false elevation readings. I posted a clear example of the latter before that related thread was locked. (Just guessing here) I’d imagine Suunto is aware of this and working on a solution. Like many of the issues we run into, it seems like it would be an easy fix that other companies have somehow figured out. But who knows. Until then, the general advice is to go back into your affected activities and edit the elevation data manually.

@isazi I started the activity in a different mode, nothing helps, are these update errors? For some reason, I have all the user mode, I can’t change to Performance mode

@2b2bff I’ve reported it to Suunto

I have the same problem. After updating to firmware 2.40.38, the watch does not recognise my breaststroke style. Before it was no problem to recognise and count breaststroke, freestyle, backstroke. Now only freestyle and backstroke. I have also tried various swim breast to see if some adjustment of the style can achieve recognition and recording but without success.

@sartoric Indeed, you’re right. “POI (Point of Interest)” seems the right terminology for what I want to do. Thank you very much. [image: 1744120724518-baedf0c7-d4f3-4583-8acd-58a517773cbf-image.png]

@martintrail said in weather display: I had the same problem this morning, but it’s fine now. I synchronized a few times and then somehow it was fine. 200 / 5.000 right. I was having this problem too. As you said, it works after 2.3 synchronizations. but the problem here is that BEAUFORT is used differently in each country. we use km/hour but the watch gives me m/s

@thanasis The S+ screen will show a pointer and green if you are in the zone for the interval. Red if you are outside the zone. I find this quite helpful. However you are correct. For me, I would rather not have a buzz or other notification and I realize this is highly personal. For my intervals I always am running and typically use power, which can fluctuate. The buzz or sound would just distract me as I often use RPE to gauge effort and glance at the pointer to ensure I am somewhere in the correct zone. the missing feature is a lap counter!

@Lawrence-Kuracina Is Strava counting lifts as runs as well?

@inkognito I’ll try that. And let you know. Thanks!

@Loïc-Fracheboud I have experimented that too : If you want to modify the current route you’re navigating on, it crashes the activity. The only way : create another route in the app and charge it in navigation settings.

Finaly I did it!!! I just deleted the app and reinstalled again!!! It was the same version, but it works!! Thanks for the answers!!