Software update 2.39.20 (2024 Q4)
-
@Łukasz-Szmigiel You made my day
-
@Nicola-Fontana unique case/situation. I don’t think this is a majority feeling.
-
@sebchastang i have the same issue. Anybody know how to install previous OTA-packages on the vertical?
-
@Dimitrios-Kanellopoulos said in Software update 2.39.20 (2024 Q4):
Hi all S9PP’s people. Thank you for the logs and we have found the issue.
I ll keep you posted.
great job! glad to hear this good news
-
a fix for the HR issue is currently under testing
-
@Egika Do you know if a fix for bad “control panel” display when activated by bottom button shortcut is also under testing?
Even if it is probably less important than the HR issue, I think it deserves consideration from Suunto since it has been broken with latest firmware.
Thanks. -
@sebchastang sorry, I don’t know. Can also not reproduce this myself.
-
@Egika no problem.
Steps to reproduce:- set control panel as bottom button shortcut
- restart watch
- access control panel by long pressing bottom button > result is a bad display of control panel as described in @TrailEyes video
https://forum.suunto.com/post/158535
Sometimes Control panel displays well, sometimes does not.
I also contacted support to tell them about the control panel issue. I don’t know if this is going to be forwarded to dev team.
Anyway, I am happy for S9PP users who will soon have a fix thanks to Suunto responsiveness
-
@sebchastang said in Software update 2.39.20 (2024 Q4):
Steps to reproduce:
set control panel as bottom button shortcut
restart watch
access control panel by long pressing bottom button > result is a bad display of control panel as described in @TrailEyes video
https://forum.suunto.com/post/158535
Sometimes Control panel displays well, sometimes does not.Thank you!
I now could reproduce it on my S9PP. Seems to be a MIP device only issue.
Not sure if too much will happen regarding this one over the Christmas holidays though… -
@Egika Good to know you can reproduce!
I would be satisfied just by knowing Suunto will include a fix for this issue in the next update (Q1 2025).
Thanks again for your help