S5 2.18.18 crash during workout / no vertical navigation prior

[Łukasz Szmigiel]

Hi,

I had a watch crash into charging screen today. The only thing that was uncommon during the hike was vertical navigation (route altitude) missing from its screen. I also had S+ Burner loaded and multimedia controls were on (although there was no multimedia so it was standby).

The crash occurred when I wanted to change navigation to “find back”. The screen went black and then charging icon appeared. The watch was at around 30% charge during that time (I’ve started with 41%).

After plugging in the watch to my PC it booted up ok and continues to charge from 30%. It also did an activity sync up to a point when the watch died, although with no ascent / descent available. Also lowest / highest points make no sense (26m / 60m). There’s also some data missing but I suspect this is due to the workout not being saved properly.

I’ve sent logs to Suunto with ID: 886205577179900

Is there anything else I can do to help debug this issue?

[Dimitrios Kanellopoulos]

@łukasz-szmigiel thank you for the logs ! I’ll update you next week.

[Łukasz Szmigiel]

@dimitrios-kanellopoulos anything new about this one?

[Brad_Olwin]

@łukasz-szmigiel I will try to test this as well, you had burner running and media controls on as well as a route loaded?

[Łukasz Szmigiel]

@brad_olwin yes, and galileo - which may also be important as I believe the interface is somewhat slower when using this GNSS. But this may be as well placebo.

I was unable to reproduce it so far.

[Ivan De Rasis]

@łukasz-szmigiel Anch’io ho riscontrato gli stessi problemi e deduco siano dovuti all’ultimo aggiornamento eseguito

[Ivan De Rasis]

@ivan-de-rasis anche perchè il mio Suunto 9 Baro, fino all’ultimo aggiornamento, è sempre andato una scheggia!!!

[inkognito]

@Brad_Olwin @Łukasz-Szmigiel @Dimitrios-Kanellopoulos

I encountered the same with S9 non-baro. I used GPS+Beidou, S+ Burner and media controls. My watch didn’t crash. When I tried to choose different route, the issue remained the same. Sometimes when I was switching between screens, the altitude navigation chart appeared for approximately one second (and looked somehow strange) and then it disappeared.

[Łukasz Szmigiel]

@inkognito in my case the crash happened when I wanted to switch from navigation to find back. Generally the interface freezes for a moment whenever I do so but this time it froze and then died.

[Ivan De Rasis]

@łukasz-szmigiel Ho provato per tre volte consecutive ad accedere al menù Ritorna alla partenza e tutte le volte il mio S9B si è resettato da solo

[Łukasz Szmigiel]

The crash happened again today - same hiking profile, different route, same other settings.

Logs from right after the watch booted up after connecting to PC:
1229920506550300

I was anticipating it as there was no vertical navigation and the watch took like 5 seconds to start after pressing the middle button. So when I was approaching the end of my route, I recorded the video:

https://photos.app.goo.gl/maUgWAAk48ZxAcJr7

You can see that the watch crashes when switching from route navigation to find back.

My settings:
1. Screens (hiking):

As you can see - there’s plenty of data but I like it this way when I’m hiking. I’m moving slowly so I can switch between the screens when needed. Perhaps it’s crashing because there’s too much to process?

2. Watch settings

• HR 24/7 enabled
• Sleep tracking enabled
• Media controls enabled (no music was available during the navigation)
• Beep disabled
• Vibration enabled
• GPS + GLONASS (it was Galileo last time)
• Sun ring watch face

3. Workout settings

• Performance
• ~47% battery in the beginning
• Polar H10 connected
• S+ Burner enabled
• Route loaded

4. May be important or not

• Both last time and today I’ve created the route on location in my car with no internet connectivity - I know it shouldn’t matter as watch <-> SA sync is offline but those are the similarities I remember.
• In no more than 5 minutes after the start I already had ascent of ~80m (last time and today) which hardly ever happens with GLONASS - especially if I wait for a while before hitting the start. I don’t remember seeing such discrepancy when the bug doesn’t occur.

[isazi]

@łukasz-szmigiel thanks for the logs, I am reporting it.

[isazi]

@łukasz-szmigiel well, cannot say much about this but devs may be fixing this, your detailed report was very useful.

[Łukasz Szmigiel]

@isazi thank you. I’m happy that the report was useful! I’ll try the same settings next time without Burner and/or media controls.