Reboot when checking alti/,baro?
-
Sometimes happened to my watch S9P too. watch will reboot when see Baro graph
-
@babychai the bar graph indeed does that to me also
. Another similar thing that happens to my watch is the following:- setting the watch in energy saving mode
- move the screens to altimeter/barometer
- set-correct the altitude manually
the watch reboots
-
This should not happen (it happened at some point during testing and was fixed). If it happens, can you please sync your watch (immediately after) and send logs? And then send me a message?
In this way we can send it to the developers.
It never happened to me on my production watch. -
@babychai My wife has the same problem with the S9P. Sometimes.
-
@isazi Sure. Let me know how I can do that lol.
-
@mikekoski490
sync immediately is self explanatory
for android (?): after sync, go to the watch icon in SA, press the 3 dots and then select “send logs to Suunto”… then private message with your email adress mentioned that is connected to SA account and the time (and timezone) your logs have been sent
-
@babychai My S9P has become moody as well recently, crashed twice in the middle of a run (had done a soft reset after the first time), then one day (or night rather
) when looking at resources - but that was exactly at midnight, so maybe a bit of a corner case… -
@isazi Hi, please check your message. My S9P reboot again just now. thanks.
-
@isazi I have exactly the same issue. New watch that unfortunately reboots on various occasions. Also sleep tracking is not working so my guess is that the watch also reboots at some point during the night?
-
@LaurA-0 it could be, but if your watch reboots this often it is a good idea to call support, because there may be something wrong with the watch itself. Mine never rebooted.
-
@isazi I talked to Suunto Support. They told me to either return it or send to Suunto for repairs with about a 3-4 week turn around.
-
@mikekoski490 I’m convinced it’s a software bug. When I get back from vacation, I’ll write the details
-
@Pavlas said in Reboot when checking alti/,baro?:
@mikekoski490 I’m convinced it’s a software bug. When I get back from vacation, I’ll write the details
Except that I have two S9P models and never had this happen. It may require something unusual to be set in the watch.
-
@Brad_Olwin I tried it on my wife’s S9P and this is what I noticed:
I have the watch on my wrist, the HR sensor is active.- I scroll down to the altitude screen.
- I switch to the next screen with an altitude graph
- I switch to the next screen with the pressure graph
- I switch to the first altitude screen and this is where the watch gets stuck. A soft reset takes place.
If I put the watch on the table and the HR sensor is not active, the watch is not stuck.
Unfortunately even so the watch freezes not every time.
-
@Pavlas I reported this to Suunto, thanks to all people that sent logs, and a fix is planned. Still, it never happened to me, so it may be something that affects some watches (or watch configurations) and not others.
-
@isazi Thank you! If you’d like, I can send the log from my wife’s S9P too. Unfortunately, the problem only happens sometimes. As I tried over and over again, the watch restarted about 4 times. The fifth reset was already hard and the watch reset to factory settings. Then it seemed fine for a while. But after a few tries, the watch got stuck again.
-
@Pavlas no more logs should be necessary for this. As for the hard reset, I think that if the watch detects a series of soft resets it assumes something is wrong with the firmware and performs a hard reset.
-
@isazi I have suffered that issue some times, it’s very reproducible (S9P).
The issue happens when you switch from the watch screen to the alti-baro screen very fast touching the down buttom switching screens.
It seems like if you don’t let the heartrate screen and data appear comepletely and switch to another screen very fast the watch get stuck and reboots (soft reboot but you lose alti/barometer and heartrate info graphs) -
@jjpaz there should be a fix for that in next firmware, thanks to people that sent logs.