@sky-runner You’re right… ! I see it similarly… it is certainly very difficult not to overload the Maps… POI like water points would certainly be useful on larger zoom levels… But they don’t care about trash cans at all…

@maszop sometimes you realise at the moment to download maps and … Yeah, otherwise this is just a discussion.

@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

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 :/*

@matram there is: /Fusion/Ddfa

@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.

@Łukasz-Szmigiel Like I said, I avoid apps on my watch.

@sky-runner Hello yes I know the Strava segments but there the idea is to compare it with an outing already made and to know if you are early or not Garmin has been doing it for a long time you select your activity it offers you to measure yourself against another outing already made and you just have a ghost runner and a time that tells you if you are early or late

@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.

@matram We’re still eagerly awaiting the custom watch face functionality!

@Danny-poleg I’m not the right person to tag, especially on dive, but I transmitted this message. I’ve been told that feedback is monitored, and the issue is acknowledged. I would expect this to be improved in the future updates, but as usual dive updates are taking time to be released.

@Manta Hello Manta, glad you are using my RestTimer App! I made the numbers as big as possible and positioning the heart rate under the ring was a design choice. you can still read your heartrate although it is cut off a little I did update the appstore-image, but it is still showing the old (first) version. Also check out my other app Biggies, which also has big cut-off numbers. Hope you will still use it! Kind regards, Markus

@Squirrel - thanks for the tip. I rebooted watch and iPhone a couple of times, and the watch faces now show on the store when they didn’t before. Back in business. Phew!

@łukasz-szmigiel thanks for the information will try to add - hope it will fit into a sportmodie cell. have a nice day vinc

@Egika no, you totally understood my question, and I was hoping the answer would be what you said… Thanks!

@Łukasz-Szmigiel No I do not think so, there is only a single output in the manifest and three inputs. It seemed more load related as staggering canvas refreshes removed the problem. Worth nothing, on at least one occasion the canvas went black first then as a consequence of the load resulting in handling of that exception (we think) we got the pool full.

@matram the HRM DUAL got its last firmware a couple of years ago…

@Steven-Hambleton These are the font sizes available. There is plenty of options for larger size … f-d-xxxl: data field font, 85px for medium, 155px for large display f-d-xxl: data field font, 65px for medium, 118px for large display f-d-xl: data field font, 57px for medium, 103px for large display f-d-l: data field font, 50px for medium, 91px for large display f-d-m: data field font, 42px for medium, 78px for large display f-d-s: data field font, 35px for medium, 65px for large display f-d-xs: data field font, 25px for medium, 46px for large display However there is not much room for fine tuning at the lower end. I tried rendering text on a canvas and displaying that. It works but takes a bit more effort to program.

@2b2bff I think there may be some confusion between the standard running dynamics already available on the watch and the additional metrics provided by the Suunto Spark. The Race series can already record metrics such as cadence and some running dynamics. However, one of the new metrics provided by the Suunto Spark is Ground Contact Time Balance (left/right balance), which shows how evenly you load your left and right foot while running. As far as I know, this specific metric is currently only supported within the Suunto ecosystem when using the Suunto Run. I have not seen it being recorded or displayed in the activity summary on the Race 2 yet. So if Ground Contact Time Balance is the data you’re looking for, that may be the reason it is missing rather than a connection problem between the Race 2 and the Spark.