@cosme.costa said: Rearding the OFF ROUTE alerts when you are on track, check what I said. Is the route created with SA or imported? I think I’ve seen it both ways - both when it is created in SA and when it is imported. This has never happened before but started happening regularly after the last update. What the new implementation doesn’t take into the account that the map may not be accurate enough, so it may think you are off route because the trail on the map is slightly off from the real trail.

@Euan73 Never had that behavior after 6 months of intense use. In the first weeks I had a couple of restarts but those never appeared again after the latest 2 updates. I would try a hard reset to see if it solves the issue. Last months the watch has been super stable, both on trails and road running and I’ve been racing a lot averaging around 7-10h of weekly training.

@matram pm me with your GitHub name, I’ll add you to my S+ skill repo. I’ve already done the digging.

@pavel.samokha First of all, thank you very much I’m sure you know who to refer the issue to and I know it will be addressed

@Markus-Hornof cheers mate! Thank you very much

@DonTomGot I am no JS expert myself. But some tips. The watch runs Duktape JS engine, which is only ES5.1 compliant. The simulator runs QuickJS I think. So code that will work OK in the simulator may silently fail on the watch. There is a pinned thread on the difference between simulator and watch, you can check there for advice on some of the typical stumbling blocks. For instance the missing semicolon on the return statement will work in the simulator but likely fail on the watch. I would also use “View system events” in the “Suunto watch view”. A lot of the failures are silent or not easy to decode, but you may find something. You can also insert your own systemEvent statement to “print” to the event log and get a traceback that way.

@Rasser Hello, I use the drill mode personnaly. I count the number of turns and when I put in pause, I add the distance. Like that I know each distance between each pause.

@Tommy85 I’m working on something similar, an S+ app showing most available weather data the Suunto platform provides at the moment, meaning current weather + 7 hours in the future. I have a POC but need to work on design some more because there’s plenty of data and it’s hard to visualise it all on the small screen. I’m also thinking about incorporating a kind of moving widget that will react to users heading (fused compass and GPS) in order to show headwind and tailwind. So it’s plenty if data

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

@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

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

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

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

Have you tried to connect the Eon Core to a computer ?