S9B reboots at activity start screen when a particular route is loaded
-
I loaded a route with waypoints (turn-by-turn directions from plotaroute.com) onto my S9B and activated navigation at the starting point of the route. The watch showed a few navigation pop-ups right on the activity start screen (before pressing the start button), then rebooted (screen went black for a couple of seconds, then the watch face appeared). Tried once more, the same happened. After the second reboot I started the run without navigation and enabled route navigation later, there was no reboot. But in the last few kilometers of the run, at each POI the watch notified me that I’m at the end of the route, while the navigation screen showed the continuation of the route properly. Attaching the particular route: Szőlőskislak-23k.gpx
-
@halajos does this happen all the time? App you synced the route with ?
-
@halajos could you also send logs via SL ?
-
@dimitrios-kanellopoulos I’ve sent the route to SA through runalyze, then synced to the watch from the mobile app (on Android). This has happened me only with that route on that place, but then it crashed consistently on the start screen. Should I send logs from SA or do a sync with SL and then send logs, perhaps both?
-
@halajos if its possible just after the crash… The logs do not survive long
SL and passing the ID here would be preferable
-
@dimitrios-kanellopoulos I can’t reproduce the crash, as that route is far from my home. I recorded one more activity since the one with the crashes, and synced that as well with SA. Not synced with SL for long. Do you think it’s still worth to send logs from either SA or SL?
-
@halajos I think after half a day they are rotated …
-
@dimitrios-kanellopoulos I can think of two contributing factors to the crash. It may contribute to the crash, that the route had waypoints near the start/end of the route (it’s a loop) causing notification pop-ups on the start screen. It doesn’t explain the repeated “end” notifications in the last few kilometers. Another factor could be non-english alphabet characters in the waypoint names (?) which I had in the route.
I tried loading the same route at home, far from the actual place where the route starts, and it doesn’t cause a crash.
If it helps in the thought process, I can tell that my fiancée had the same route loaded on her SSU, which didn’t crash, but showed the same “end of route” notifications. -
@halajos for notification issue: in my case with an Ambit3, if I add waypoints to a route and I don’t add at the end of the route an “End” type waypoint, then my watch will pop-up end of route notification at the last waypoint near to the end. Can that be for your case too? Did you marked point A/B as Start/End waypoints?
-
@andrasveres routes downloaded from plotaroute.com used to work. The last waypoint in the route is this one:
<wpt lat="46.737305" lon="17.668048"> <time>2021-03-01T07:49:59Z</time> <name>FINISH</name> <cmt>FINISH</cmt> <desc>FINISH</desc> <sym>Flag, Blue</sym> </wpt>I loaded the route data into excel to check, all waypoints have a corresponding trackpoint (by coordinates).
-
@halajos it is strange that if I manually import your route into:
- Suunto app: there is no waypoints loaded.
- Movescount: all waypoints are loaded.
If I look at Start on and FINISH waypoints they are imported into Movescount as Waypoint type (I’ve tried changing them to Begin and End type, but Movescount export didn’t include <type> info into GPX file).
When in Suunto app I added Start on as Begin and FINISH as End type waypoints and exported the GPX file, then it contained correct <type> info for both points.<wpt lat="46.73737" lon="17.667992"><name>Start on</name><type>Begin</type></wpt> <wpt lat="46.737305" lon="17.668049"><name>FINISH</name><type>End</type></wpt>This is what I was referring to with my previous post.
If I didn’t had these type of waypoints added to my route then my notification would not work properly for both start/finish points.
However note that I’m using an Ambit3, not sure how Suunto 9 handles this.
