S9 reboot in activity
-
@chris-hebet there is some discussion in this issue in “Software update”
-
Happened to me in June, never happened again. One thing I could suspect is that I kept SA running with my phone during activity.
-
@lexterm77 Hmmm… interesting fact.
Every person who had this reboot experience had Suunto plus screens and/or navigation selected if I read their posts. Putting a lot of stress on the CPU and memory of the watch.
Could it be that a notification from SA is pushing the watch over it’s limit? -
Yes, only with S+ it was very slow to react even for a manual lap button and interval timers were lagging more than 5s when I turned off S+ everything was fine.
-
@chris-hebet io lo stesso problema dopo l’ultimo aggiornamento. anche se uso la funzione ritorna alla partenza
-
The S+ and navigation memory issue was solved with June update if I’m not wrong, so not sure what’s wrong now. But I’ll test this (hopefully tomorrow, I’m battling with a cold that does not go away for two weeks now).
-
Tried this morning with S+ burner and activating “back to start” mid route, no crash.
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi Grazie per la Tua risposta. Questa sera farò un altro tentativo, e se dovesse andar tutto bene, dovrei presumere che ci sia qualche problema con Koomot, visto che gli ultimi itinerari li ho creati da lì.
-
@ivan-de-rasis continuerò a provare anche io.
-
Hello, anyone actually have this problem with the S9 (non baro)? I have a friend that suffered few exporadic reboots on mid-activity on the last weeks. He associated this to the screen lock during the actitity but I don’t know if have some sense. These days we try to replicate it without success. Thank you!
-
it happened to me a couple of times while navigating a track and with Suunto + climb, the last last week … S9B
-
@flypg
it seems to be a rare case and happened to me recently, too. the watch did not actually reboot, it crashed partially. no screen available, not possible to stop the activity, only access the options menue.
I think it is known. If it happens to users frequently, please report with sending logs and provide mail address with time logs sent.
If it happens rarely, as it happened to me only once, I would recommend just to wait for a new firmware to be released. Maybe soft-resetting the watch improves the situation, but I don’t have experience with that. -
@gambacorta @freeheeler Thank you!
Exactly this behavior @freeheeler It’s not reboot on some cases but it’s the only way to recover the normal function.
Yes, I already recommended him trying to replicate and send logs inmediatelly, as lucky, without success until now.
