@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

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

@gsaff I am sorry for you, but there is no exception, Garmin too has very faulty units…

@9peekrf0 Raw data from watch are going to app, you can update in the app and see other metrics. But it can’t invent data, if the used mode was without GPS for example, then, no GPS. Etc… And update in app won’t be synced to watch.

@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

@fondueaufromage Regarding the touchscreen issue, I sent my watch to the service center for inspection. Surprisingly, they were able to resolve the ghost/phantom touch issue simply by performing a soft reset and hard reset. I had already tried both resets myself multiple times, but did not solve the problem. The service center then sent the watch back to me. They only charged me for the courier fee, while the inspection and troubleshooting were provided free of charge. However, about 3–4 days later, the ghost/phantom touch issue returned. I contacted the service center again regarding the recurring problem. As an alternative solution, they offered me a trade-in option. They are offering a 60% discount on a new SV1 Titanium Solar if I trade in my current watch, SV1 Stainless Steel. I accepted the offer.

@krad801 said: @Egika how do we get this issue to Suunto to be fixed? I agree with Sebastiano in that the watch should be reporting accurate elevation gain. This is why we purchased and wear the thing - report back the accurate numbers (same as distance and duration). Credo di averlo risolto. Però ancora non sono uscito in bici. Sulla corsa ora mi dà dei valori moooolto verosimili. Appena esco in bici ti faccio sapere. In sostanza ho fatto il downgrade del firmware ma non è cambiato nulla. Poi e reinstallato l’ultimo firmware nuovamente e ora per lo meno durante la corsa mi dà gli stessi identici valori del mio vecchio coros. Prima di allora l’altitudine sulle corse era completamente sballata. Ho la bici a riparare. Appena esco in bici ti faccio sapere.