@isazi yes. I think we mean the same. I only use manual waypoints when creating a route and rarely have TBT on. But I never used „official“ POIs. Maybe I should try it out once ️

@Mff73 yeah- my comment was based on those surveys. I don’t know if something about this is actually cooking

I also have run out of upvotes Thanks @Łukasz-Szmigiel will give it a go

@wmichi Exactly, here is what happens after a long run:) [image: 1700844332136-img_0599.jpeg] [image: 1700844332156-img_0590.png] [image: 1700844332163-img_0589.png]

@Egika Unless a device follows at least the specification for usb 1.0 (which includes power negotiation for up to 500mA @ 5v) it isn’t allowed to use the USB logo or branding. A chip to handle the spec costs no more than a few pence these days so it’s highly unlikely you’ll buy a charger carrying the usb branding that doesn’t follow the spec. You could pretty easily test whether a charger does actually do the handshake by sticking a little tape over the 2 middle pins of the USB-A plug or socket as these are the D+ and D- data pins needed for the handshake. If your device doesn’t start charging or takes days to charge you can, I think, conclude it’s only receiving the default 150mA.

@Mads-Hintz-Madsen I’m hoping so too!

@jjorgemoura Typically I just need to connect in the BT stack. If the watch will not connect toggle airplane mode off then on from the watch not the phone, that will reconnect. No need to forget anywhere or repair from scratch at least in my hands.

@helgonet12 I have had the vertical on my wrist recently but the values are different at the moment. I’ll be watching this week.

@pavel-samokha i saw the map and it’s demarcated incorrectly, however the real problem when navigate using SV maps these lines go though the map incorrectly and the result you get it’s a visual complex …a mix with paths ,roads, lines with a black bold ridge lines in screen in zoom 50m What i understand here is luckily it’s not watch manufacturing problem eg. Processor, memory , screen issues etc… so im COOL -It’s topographic issue maybe I use the navigation very often in my training and different mountains, in general i don’t remember anywhere else same black line issues so far.

@Tieutieu it’s a mad world

@Retired-Assistant can you post photos of HRV? Are you seeing any values in sleep summary on the app? Can you post photos for that as well? Make sure sleep tracking is on with hours, sleep target is set, 24/7 HR tracking is on and HRV tracking is on.

@isazi ok

@wheeler fantastic news! …but I am going to freak out once they add this: [image: 1712685441535-bfd22d2e-c41d-4b91-b09b-1f002943a44f-image.jpeg]

@GiPFELKiND perhaps the apocalyptic response isn’t necessary. Firmware does go through testing prior to release and while all bugs are not found, many are and maybe not all have been fixed yet.

@thailon PM me and I should be able to help you. I am in US so it may take a bit of time. Sorry this happened but there may be a simple fix.

I have these thoughts too after the update

@Tieutieu said in Vertical all black or titanium: I like the grey titanium color much more than black I second that

@isazi another data point: today’s ride was 7 hours, I was on the map for maybe 4 of those hours. No problem there. Either because of the recent soft reset, or because I wasn’t always on the map screen. shrug I’ll be doing this for the next several days, let’s see…

I’m experiencing the same issue with a new Race S watch. I was tracking a kloofing exercise as a trail run and it god submerged a couple of times during. Ended up with something like 9000m elevation gain. We did 8.8km downstream. The GPS data on Strava shows a realistic 200m odd of gain.

@Ze-Stuart thank you, I tried the s+ app today as a trial and i did a manual sync int eh Stryd app - I ended my with duplicates - is this normal and I just delete the one with the least data in it ? Also is I don’t use the S+ app and I do the same, save and sync run in Suunto app and then do a manual sync in Stryd - will I end up with duplicates ? Cheers