I haven’t read through this whole thread but I’m not a fan of AMOLED, hence why I’ve not upgraded my original Vertical. IMO there’s absolutely nothing wrong with MIP and hopefully we will always have an alternative to the eye-burner that is AMOLED

@Dimitrios-Kanellopoulos yeah, @sky-runner always provides valuable input. The problem is no time to read all feedback

@Nikolai-Simonov I have intense jungle training this weekend; I’ll be testing both Vertical 2 and the update.

@gkaempfer Same here

@suzzlo watch being the bottleneck makes sense. I did go ahead and test my V1 with the Scotland map download and it took just under an hour. So I still think there is more to it than the watch.

@Egika Yes, different colours make no difference unfortunately

@Highlands These are great! Thanks

@maszop Thanks. And weirdly it has now synced correctly some 20+ hours after finishing the activity. That’s what usually happens an hour or two after I’ve grumbled about it on here. I’m inclined to suspect some sort of Bluetooth issue but whether it’s the phone or the watch I can’t say. It’s annoying.

@Egika this was exactly the bug I referred to in my post. Anyway my point is that there is a difference between fixing watch breaking busy and niggles, so it would be good to know what to expect…

I’m probably buying the Spark to use with the Vertical 2 Ti. Since both products are already in the market, with these headsets, I think Suunto has a very good oportunity to go a lot further. The combo of the heatsets when paired with the watch, could be used to improve several things: I.E: Voice notes while in activity Ability of making phone calls without taking the phone of the backpack when you are in a trail run. I.E, click button and say something like: call sister. Improve the pedometer features (no other brand has a product in the market which such a nice feature). I.E: When the GPS signal is lost because you are running indoor or in a treadmill. I think there are many more use cases that would make an instant buy probably for many people.

@Egika Thank you.

@aiv4r no worries. I think the current way is not bad at all. It just need to be consistent. Having a 5km run as PB for 5k - great, Having a 10.xkm run as PB for 10k instead of the 9.95km race I did last time - accepted Having a 20.4km run as PB for the half marathon - what? And nothing I can do to decline that half marathon PB and go back to the one before… support hasn’t been that helpful with that, yet…

Received the Spark today after a weekend order. Paired & updated quickly and have supreme sound. Haven’t tried them in action (on the bike trainer or out for a run) but are quickly becoming my favorites in spite of owning multiple sets of Sonics. [image: 1776298642069-sonic.png]

@Tieutieu Not for me. I’m still seeing 20% drain per day.

The watch and phone are connected via Bluetooth, and I’m receiving notifications, but the app shows no connection. I turned Bluetooth off and on on the phone, but it didn’t fix the problem. What else can I do? [image: 1776097483350-a11.jpg]

@Brad_Olwin It will be great for Suunto Coach AI !

@Gunnar said in Map Design Update 2.53.42: memory is not storage Unfortunately, I can’t find any information anywhere about the difference in RAM between the Race and the Race2.

@Pe-Ter Thanks for the feedback! A couple of questions to better understand your use case: Would you still use the PREV INT panel, or is it not really useful to you in this scenario? How long would you expect the temporary screen to be displayed? Would it be acceptable if it disappears after a short time and you then rely on the PREV INT panel? What I like about PREV INT is that it’s always accessible. For example, I often check it once I’ve caught my breath a bit after an interval, rather than immediately.