@dreamer_ I’m built similarly to you so glad I stuck with the Race 2. Maybe you’ll change back after the update! I didn’t want to pay an additional £100 for a torch and bigger battery, neither of which I need. This would also come with more bulk and omission of the scroll wheel which I like for zooming the maps. I wonder whether this update will be included in the next quarterly one or a separate earlier fix…

Scusate ma non capisco il voto negativo!!!

@Highlands said in Suunto Vertical 1 – A Few Questions About the Future + Questions About the Vertical 2 and a Comparison with the Coros Nomad / the New Vertix 2026: @dreamer_ I hope they put a sapphire crystal on R2S. About this, I think my wife’s 46mm Run could fit a 1.4 inches screen. Perhaps they could fit that screen aize in the Race 2 S playing with the bezels and making you think the watch is not that “S” but something comparable to a Fenix 8 47mm . That simple change would make a lot of noise for marketing in my opinion and very likely much better sales (just for that)

@Mff73 always nice when someone else has done the work! Thanks, I didn’t know about that post, or Sonny’s work.

@2b2bff well well well … if you tell to someone who is doing a diet that he lost 5000 g and to his wife that she lost 5 kg … you are right … this is not the same … the wife will be super happy but the man wearing a suunto and for who 43 and 43.0 make a difference will start to question himself about the precision of instrument … how it could have been possible that he arrives preciselly to exact 5000 Joking !!!

@2b2bff said: @stromdiddily there is no universal “This is a workout file, deal with it watch” format. If you are pushing a workout to Garmin, you define the steps. If you push the workout to Suunto, you define a SuuntoPlus Guide. I don’t know how Coros or Apple Watch does handle it. So, Training Peaks - or any other platform for that matter - has to include the respective framework for each brand individually… The other way around, if you read the finished activity from the watch, there is a format that has been widely adopted: Garmin FIT files. I see, this makes sense…thank you

and another crash/restart today - no HR strap or ZoneSense fields this time Reddit comment here *yep have had 4 or 5 of these glitches on 7 week old Vertical 2 so far - on only some runs, after a long while it seems to get slow to respond, then freezes, then restarts the watch (except for 1 time when it just exited the activity). Generally most of the run GPS/HR data is still there, except maybe the last 400-500m when the slowness started. What’s missing is the total ascent/descent calculation and some other calculated data. have submitted support ticket & logs thru app each time. no response so far. I first thought it was something to do with ZoneSense, because they only happened when I was using an HR strap & ZoneSense fields in custom Running mode, but today’s glitch/restart was without the HR strap & ZoneSense fields… so that leaves… touch screen, media controls, or 2 other basic S+ apps (HR Zone Duration and Last km/mile)… or it’s just the whole watch OS … maybe it needs a more regular reboot than just at recharge time Trying a more basic Custom Run Mod with none of the above (touch screen, media, S+ apps) to see if it still eventually fails Getting less happy with my purchase :/*

@Stefano-M64 darn it, package got lost somewhere… still waiting

@withManish On iOS there is rungap for datamigration. And I use strava and intervals.icu. It collects data from multiple sources (I had different brands in the past). But most importantly, data of 5 or 10 years ago hardly has any relevance. But I’m no hardcore data collector.

@Ze-Stuart it’s really a pity. I really hope they can push an update soon to improve the user experience.

@cosme.costa I firmly believe that a navigation route is not open for interpretation by the watch and must be followed as originally planned unless the user gives up and moves on the new direction for some distance. This must be unambiguous. The watch must not silently reverse the route direction or skip a part of the route without giving the user a chance to notice and correct the mistake. This should work within the tolerance of detecting off-route condition, of course. The algorithm should be straightforward and consistent. If there is any significant divergence from the route, which includes changing the direction or skipping a significant part of the route, there must be OFF ROUTE notification first. If user continues to move along the altered route for more than e. g. 100 meters, they the watch should snap to the altered route, which may be either reversed direction or skipping a part of it. If there is more than one choice, skipping a part of the route should be preferred over reversing. Ideally, once the original route has been altered there should be a clear notification about that. The above should not apply when the user is not currently navigating. For example, someone had a one way route and they have reached the destination point, so they have ended the navigation. In that case moving back on the route should not generate the OFF ROUTE warning and it should just silently lock to the reversed route. By the way, I sometimes see OFF route warnings even before I have reached the start point of the route, which is clearly a bug. Also, the light blue navigation arrows should not disappear when OFF route is detected. The arrows should continue showing where the route is supposed to go as planned. Only when the new route option is accepted, if user continues to move in a new direction, only then the light blue navigation arrows should confirm the new altered route. The same as above should work for detours. Even when getting completely off route, the route should retain the navigation arrows at a point on the route closest to the user position, showing where the original route is supposed to go. That is very helpful for merging back into the original route.

@Brad_Olwin Really? Very interesting as XC Skiing is my other Usecase for the Vertical. Sun and Snow together are so bright that the MIP really shines. Also the Solar power collection is welcome. For running I really like the Race S as it is much lighter and the OHR works perfectly since the last update. Waiting for an Ocean 2 Titanium in the Race 2 case. If the new display is that much better it would serve all my demands. But as long as RaceS (discounted), Vertical Titanium (used) and Mares Divecomp together cost less than the Ocean I will stick with this trio

I’ve been able to release a few updates oriented around lowering the hardware load of the app and yet even today I’ve received a feedback that the app is rebooting the watch - and it’s always Vertical 2. Are there any known issues or something that’s not specified in the documentation in relation to Vertical 2? @dimitrios-kanellopoulos , @suuntopartnerteam ? Can I help somehow in debugging the issue by adding extra logging, etc.?

Hopefully they’re able to fix it soon. It feels like with every update they just introduce more problems. Currently still experiencing the auto-update bug (can’t disable it essentially), and now the battery bug has gotten even worse.

@Joaquin Be careful not to chase perfection and in the end nothing is completed. The komoot route is a bit cumbersome and komoot is far from perfect (even if I tell komoot to not change the route, the route on my suunto race s is different than on my wife’s apple watch.) The garmin/wahoo way (select a gpx file and use the open with app) would be an improvement, even if not all tbt alerts are perfect. My first gps watch (a ambit 3 sport) only had breadcrumb navigation. Did I ever got lost? No. My watch after that, a forerunner 935, had breadcrumb and tbt alerts. (Which didn’t work well. A route could only have 50 navigation alerts and if you did your route reversed you lost all tbt alerts). Did I ever got lost? No. My first watch with maps (a forerunner 965) and having some context is nice. Eventually garmin fixed the 50 alert limit, but not the reverse problem and they introduced a timing bug (up to 10k the alerts are before a corner, after 20k alerts are in a corner, or after). And yes, on a twisty road you get alerts for every corner. Did I ever get lost? No. Now I have a suunto. Komoot is fine, but could be better. Autodetect of going reverse is good. No problem if I do a round route and the end is detected before the start (garmin has problems with this. Navigations stops when you reach the goal, which could be before you actually started). Autozoom actually works as one would except (garmin had autozoom, but that doesn’t work, or not as one should expect). But do I get lost ever? No. In the end, all are equally good in the “do not get lost” requirement. Is everything perfect? No. But don”t wait until everything is perfect. Release small steps. Get feedback. Improve some more.

@Elipsus no worries, I just shared the “why” : )

@GiPFELKiND What phone model? and what error? also on lates android build, knowing issue if you app swiped out from activity list, you probably could lost connection, fixed but not released yet. in general race for BTLE connection between suunto app and live.τ app still exist, but observation said that it’s not a big deal, and connection works in general well. personally i usually lost connection in some difficult areas near military objects, or radio polluted regions… not sure if it’s your case. you can try to the latest apk build here - https://artifact.fra1.cdn.digitaloceanspaces.com/live-t/apk/1.0.18/live-t.apk or if you use google play join internal builds here - https://play.google.com/apps/internaltest/4701596347369604163