S9 Baro crash in altimeter menù
-
Hello!
I have the same problem. Already talked to Dimitrios about it. It seems to happen while entering Altitude menu too fast (enter menu straight after scroll). I usually wait those white up and down menu arrows to disapper before entering.I have avoided any crash that way.
I saw this topic and tried to crash my watch. Took only three times and boom, reboot. In 2 hours two times more.
Which watchface are you using? I use the one with barometer on outer ring (with baro trending and altitude). I use yellow color. Reboot issues started after installing firmware with new watchface. I tried other watchfaces also but they seem to be stable.
Could other people try with mentioned watchface if it causes crashes?
-
@Jugger I can’t reproduce it.
I scroll all the way down to the altitude and then as fast as I can to altiude graph->barometer->altitude->altitude graph but it keeps working. Both with touch and buttons -
@surfboomerang And you did use that certain watchface? It happens seldom.
-
@Jugger yes, I will try some more.
You mentioned yellow color. That means you have a green baro outer right right? -
@surfboomerang That’s right.
-
@Jugger Can you post a video? I can’t make it crash. Maybe I’m reproducing it wrong.
-
Hey guys, can you send logs via the Suuntolink and give me the ID ?
-
Here’s my log 2093490669333900. Few minutes after crash.
-
@Jugger and @Dimitrios-Kanellopoulos I have tried to crash the watch like you described (about 15 times) and it has had one crash (ID 282087109534000).
Usually I use the watchface like you said (with barometer on outer ring with baro trending and altitude/hPa - red colour). In the last crash has that with the outer ring with sunrise/sunset/moon phase - yellow color but maybe the colors aren’t the problem (…only watchface?!?).
I check often baro info on the watch because I’m passionate about meteorology. If the problem is only the fast access to alti/baro menu, I will check/access more slowly…
@Dimitrios-Kanellopoulos this is the logs list sent with Suuntolink:
636599218900 (crash around 20:40*) 31/12/20
6823202005300 (crash around 14:09*) 01/01/21
282087109534000 (crash around 18:42*) 04/01/21
(*) local time; GMT+1Thanks to all.
Matteo -
Finally I got video uploaded to Dropbox. This time I got lucky and my watch rebooted on my first attempt. Total crashes today: five times.
And to @matteo_000 wait for white menu arrows to disappear then it should be fine
Video is around 50mb. Hopefully it works.
https://www.dropbox.com/s/5s6ue6nhdzdwcvk/Video 4.1.2021%2C 20.06.23.mov?dl=0
-
@Jugger I did exactly what you did a dozen times, but I’m still unable to let it crash.
Does the watch also crash if you do this with touch instead of the buttons?@Dimitrios-Kanellopoulos Could it be production year related? My s9b is 2 years old.
-
@surfboomerang I tried and after a while it happened also with touchscreen. Just going in and out to alti menu. Don’t have to scroll to watchface.
-
I’ll forward this to the sw team, but imo as others don’t have this issue and since I have seen these type of issues getting a watch replacement new , I would recommend the same.
It can be hw fault that crashes this! Ie not isolated component.
In regards to that, can it be clothing, place etc ?
Ie electrostatic
-
@Dimitrios-Kanellopoulos I doubt that static electricity has anything to do with it. Crash can happen anywhere. With different clothes and temperatures. I would like to replace my watch if possible.
Like I’ve said reboot happens random. Not everytime like on video.
-
@Jugger ask support and pm me the case ID to try to speed this up and bypass the support scripts
-
Dear all,
in these days I have tested much time the function ALTI-BARO and I found:- the crash can happen ONLY with the watchface with barometer on outer ring with “baro trend” and altitude/hPa info;
- it NEVER happened with other watchface;
- with others watchface the access to submenù (ALTI->GRAPH ALTI->GRAPH BARO) is much faster than with watchface with “baro trend”; with this the slide/swipe it seems more slow…someone could try it ?
- touch or bottons use is the same; there isn’t difference;
- my S9B is new (less than a month…arrived to me 19th last december) and if @surfboomerang has had the same problem with his watch two years old…maybe insn’t hardware problem… I think;
It could be a bug of the new watchface or last FW update ???
@Dimitrios-Kanellopoulos I tell you others new ID log sent immediately with Suuntolink after the reboot:
446884534921400
452235984552900I think that I will waiting to replace the watch to understand if the problem can resolve (maybe with new FW update ?!?) because all the others functions seems ok. In case I need it I will advise. Thanks for your support!
So this is my little experience that I hope could help.
Matteo
-
@matteo_000 said in S9 Baro crash in altimeter menù:
my S9B is new (less than a month…arrived to me 19th last december) and if @surfboomerang has had the same problem with his watch two years old…maybe insn’t hardware problem… I think;
Small correction.
I can not reproduce the problem with my watch. I tried many times, with the baro trend selected, to let it crash but I failed to reproduce the issue.Also I haven’t noticed that the menu is much slower with that particular watch face. I will pay more attention to it.
-
Ok sorry for my mistake…so @Jugger how old is your watch ??? Do you have detected the same difference between the watchface “baro trend” and others??? Thanks
Matteo
-
@matteo_000 I just tried and baro watchface is bit more slower when swiping alti sub-menu all the way to left and back to main menu. I also tried to crash my watch with other watchfaces with no luck. Only baro is causing that. I’ve had all firmware updates but problem was always there. So it’s not related in software.
I bought my watch in May 2020. Everything else is working just fine.
-
@Jugger it doesnt mean SW is always related.
The memory / CPU usage can increase and thus the “capacity” needed can cause this.
Similar lets say (not the same problem though) with phones that their batter is going kapot and while they show 50% when you do an intense work they shutdown/reboot.
There are also memory errors and many other stuff.
