[solved] Reboot during activities
-
@inkognito - do you know if a soft reset will also flush the AGPS?
I had an issue with a Sports App properly starting ( blank screen or no data fields in the Sport App screen ) this morning. After two or three false training starts, I soft-reset the watch ( no phone sync ) and the next training started the Sports App correctly.
The only downside of the soft-reset is that GPS lock took more than 5 minutes, possibly 10 minutes. After all of that delay, I had no issues in the 3+ hour training ride.
-
@Bradleyd said in Reboot during activities:
do you know if a soft reset will also flush the AGPS?
yes it does
-
@SimonHumm I provided all logs to Suunto, and I would assume that the bug has been identified as more logs are not necessary. I have no idea what the bug is, as my watch never crashed.
-
@SimonHumm I also walk on thin ice every time I start a training too
Have to constantly watch the watch during the first few minutes, if the watch survives this period, then I can continue the exercise with a calmer mindI hope the issue is identified by Suunto now and a fix is released soon (if it’s a software issue). At my place it’s cold in the morning this period, it’s not funny to wait in the cold for the watch to catch GPS signals again after a crash
-
@chargerunner and others experiencing this frustration, it appears like there is an issue with GPS state and SuuntoPlus apps on my watch that is leading to the reboot on training start.
I spent a little bit of time playing around with different configurations on an S9 and landed on the following experiences with my Polar H10 HRM and a bluetooth CORE body temp sensor for the SuuntoPlus Sports App.
-
multiple successful exercises, including run and unspecified indoor, whenever I disabled GPS and used the Sports App.
-
two back-to-back crash followed by watch restart, when I tried a run training with good GPS. In both cases, no Summary data for the Sports App was written ( suggesting the app initialization didn’t complete ) and no HR data was shown on screen before crashing.
-
immediately after the 2nd crash, I turned off GPS and completed a 20 minute run successfully. After the run, I did a quick check to confirm that a GPS enabled training without a Sports App would start.
-
immediately after the successful run, I tried two back-to-back runs with GPS. The training started, but the Sports App screen data was empty ( – on the screen field ) and no summary data was written at the training end ( again, suggesting the app initialization failed ).
-
immediately after, I soft-reset the watch, waited 12 minutes for GPS to lock, and successfully completed a 20 minute run with good GPS and a Sports App.
In my case, the watch doesn’t have an AGPS file, so I have manually seeded location using the Navigation “Your Location” before starting a training. If the reboot during activities cause is state based, then either soft-restarting your watch before training -or- turning off GPS -or- not using Sports Apps may help with stability.
-
-
@Bradleyd
what GNSS combination do you and all you guys experiencing this issue use?
GPS only or a combo of GPS and others?
I’m using external HR always with S9B, and most of the time S+ climb, burner or zones. I’ve never had a crash with the latest firmware. I’m always using GPS and Galileo.
If it was GNSS related, maybe it’s worth a try to switch system combo or go for GPS only, over avoiding using S+ or soft-resetting and waiting 15min in the cold on a daily basis. -
@freeheeler I had crashes with GPS+Galileo and GPS+BeiDou. Didn’t try the other…
I had perfectly fine exercises with various SuuntoPlus apps without any crash, only to find it crashing next time with the same setup…
I also had crashes when I didn’t use SuuntoPlus at all…
I had crashes with external HR monitor and with watch OHR…Instead of trying crazy things like rebooting the watch on daily basis or hoping that hard reset will save us (it does not), the best would be if someone from Suunto would tell us what their analysis showed
Well and provide some fix asap… -
@inkognito
Suunto does not communicate much, but as I understand @isazi 's statement they seem to be on it
-
Suunto sent us a message, we need some information from people having crashes, please contact me with a DM for more info. Thanks.
-
I had another reboot today… In fact, I went like “let’s combine many functions together and see if it crashes”
So I used:
- Sport mode: Walking - custom with ETE/ETA fields
- SuuntoPlus: Burner
- Navigation: Route
- I set target HR zone to Zone 1
Watch crashed and rebooted around 26 minutes after start… I was stationary at that moment (taking a photo with my phone), I looked at my watch and saw a black screen and then, several seconds later, the watchface…
But this made me realise one thing! This was not the first case my reboots happened like this. In fact, I had multiple crashes just after I stopped for a while! Usually due to photos, road crossings etc… I did not use pause or autopause…
I tried to replicate this immediately after with no luck… I went on for another 40 minutes with the same setup without any problem…
Anyone with similar experience (crash happened when you stopped for a while)?
-
@inkognito
I did groceries today and didn’t stop the activity when I was inside the building. navigation, hill climb, external HR etc… no crash at all. but I never had a crash with the latest firmware.
I recommend @isazi 's suggestion -
@freeheeler I’m in contact with @isazi
I was just currious whether I might have found some pattern in those reboots or not… To me, it happened multiple times exactly after I stopped for a while. It is becoming hard to believe that this is just a coincidence But I am definitely not saying my watch rebooted everytime I stopped…Anyway, when you stop without pause, many things happen at the same moment, like:
- Sony GNSS chip probably recognizes that you don’t move and triggers some clever algorithm to filter the data
- your HR decreases, you probably go from higher zone to lower, this affects the Burner app calculations…
- ETA/ETE values are changing rapidly
- Navigation starts using compass… etc.
I can imagine that these many simultaneous things that are going on might bring better chance that something goes wrong
-
@inkognito From what I experienced myself and from the other users, I think each one has faced a different “pattern”, so various that there can’t be a single pattern for these reboots
For me it’s nearly always at the beginning of a running exercise (only once at the beginning of a cycling exercise). At first I noticed that the hear rate didn’t show up on the watch face before the reboot, so I thought it had something to do with the HRM (I use the watch’s HRM), and I always waited for the hear rate to appear at the beginning of the activities to be sure there wouldn’t be a reboot. Then later I found out that sometimes the heart rate also showed up before some reboots, and I don’t know what is the pattern of those reboots anymore
-
@chargerunner said in Reboot during activities:
@Reiner Glad to hear it @Reiner . How long has it been since you downgraded? I would wait at least one week before being a bit more sure about the issue not coming back
After the hard reset (still not downgraded), my watch went on for one week without error before the crash came back…No more crashes after downgrading to previous firmware since 10 days - 5 “running” workouts. Before it crashed on every workout 1-2 times. Unusable.
It looks like the right decision.The “process” and suunto statements for a quick solution are not satisfying. -
@Reiner It’s encouraging. Could you keep us updated after maybe 10 more days?
I didn’t downgrade my watch. It went through a hard reset, imposed by Suunto Link, and still stays with the latest software version. It’s been more than 3 weeks since the hard reset now, and the crash happened already 3 times. The encouraging sign is that it didn’t crash as often as before the hard reset, and also didn’t crash during the last 10 days. I think in the end I will also downgrade the software as you did.
-
@chargerunner I’ve also downgraded the version from 2.23.20 -> v2.20.30.682 cause that bug and lack of reaction from Suunto are pissing me off. When I reported the bug on live chat they told me to hard reset and if it is not working then send the watch to the service
Will let you know after week or two if its okay. -
@fecek
just as a general reminder. Suunto does not seem to be inactive. @isazi has sent us a message about that.
I don’t have crashes fortunately (and unfortunately).
if you do have crashes and some patience, before you downgrade it would be helpful in long term for all to get in touch with @isaziliving sideways
-
@freeheeler no disrespect meant to anyone but I’d rather have an official statement from suunto for reassurance. Comes across as sly if I’m completely honest.
-
@ADHDMonkey
I know what you mean. Suunto does not comment on issues, improvements or roadmaps.
my observation is that the issue came up slowly. at first only one or two users reported crashes and now reports are becoming more frequent.
it still seems to be a rare case and Suunto can only investigate with feedback and reports. let’s hope it gets solved, soon -
@freeheeler
I’m sure there are still a large number of other affected users. Very most of them are not registrated here in Suunto forum.
They will probertly contact official support, when i read supports answer “send the watch to the service” oh no… The distribution of the buggy firmware has not been stopped until today.
