Software update 2.39.20 (2024 Q4)
-
@Knigge said in Software update 2.39.20 (2024 Q4):
@Łukasz-Szmigiel “Why should Suunto continue to support older devices?” Well, there’s a simple reason (for me): To retain customers. I will eventually buy a new watch, and my decision in the future will depend on the experiences I’ve had in the past. My experience now is that my S9P is no longer supported. If I buy such a high-quality and expensive watch, I (personally) expect it to be supported for more than 2–3 years. If that’s not the case, I’ll look for another provider that supports its products for a longer time.
With this approach, Suunto has lost a potential future buyer and a (former) advocate of the brand. I used to recommend Suunto to my friends…
You continue to incorrectly say that the 9P is no longer supported. You have ZoneSense in the app from the 9P. You have been informed many times in this thread and others that the hardware will not support the calculations for in watch ZoneSense. How do you know this is not true? At any rate Garmin Fenix 7 is not capable of running the current Fenix 8 firmware with all of its new features and is much newer than the 9P. I hope you are happy when you switch brands. Please refrain from beating this topic to death, we have all heard what you have to say in multiple threads and have been more than patient.
-
@GiPFELKiND Ich glaube du verstehst @sartoric falsch: Er weiß dass du keine Höhenlinien in Bayern über 500m hast. Ihn nervt nur dass du das immer wieder postest
Posted in German since I think there is a misunderstanding here
-
@Pavlas said in Software update 2.39.20 (2024 Q4):
Since the last update 2.39.20, my watch sometimes disconnects from SA and won’t reconnect. Restarting the phone doesn’t help. A soft reset of the watch helps. It has happened to me with both Vertical and Ocean. My wife had the same problem with the 9PP. Has anyone experienced this?
I also noticed this weird behaviour. my watch disconnects for no reason few times now. I would say once every two weeks.
Suunto Vertical: software 2.39.20
SA: 4.106.3 -
@ChrisA Danke Chris ja ich habe ihn wirklich falsch verstanden
-
@Brad_Olwin As I wrote yesterday at noon: “The argument ‘The old hardware is simply too weak for this calculation’ is one that I can understand and accept.” I’m aware that four years is a very long time in the world of electronics. I also had no intention of disturbing or dragging out this thread in any way. I was/am simply a bit frustrated, that’s all. It’s just my personal feeling. If I used any terms incorrectly, I’d like to apologize for that.
When I said, “The S9P is no longer supported,” I meant that there will be no more updates for this watch. I thought I had specifically referred to the watch and not the app. And I never said that “it’s not true” that the hardware can’t support ZoneSense (or other features). At the beginning, it was always about “the operating system of the watch” and the fact that the old operating system will simply no longer be developed.
In my understanding, there is a difference between a feature not working because it isn’t implemented in the software (the operating system) and a feature not working because the hardware can’t handle it. Saying “The feature doesn’t work because it hasn’t been implemented in the software” also means “We could make the feature usable in the software.” But as I said, if the hardware doesn’t allow it, I fully agree with you that it is what it is.
Actually, I wanted to send you, Brad_Olwin, a personal message with this content to avoid holding up this thread any further, but I couldn’t find that option. And I couldn’t just leave your words as they were. So, please excuse this wall of text, which has no relevance to the current update. I won’t comment any further. I meant no offense to anyone.
-
Found idly something useful out today - when using button lock in activity, you can hold the middle button on the map page and it cycles to the previous page like with every other one, where the default behaviour with button lock off is to adjust zoom levels.
Given that I very rarely actually adjust zoom levels I guess I’ll have button lock on by default now to save me skipping forward all the way to get to the page before the map one.
I’m sure other people have already noticed, given this was the case on the previous FW apparently.
-
I have the impression that the battery drain problem is back… a few days ago I looked at the map during an activity, since then I lose 5-6% per day… I send logs (16.57) and then do a soft reset.
-
Another data point.
New Suunto Vertical, purchased on 16.01.2025, latest software version v2.39.20 claiming to have fixed the HR issues in release notes. It worked ok for past week and today the HR sensor stopped working, didn’t record my sleep. After rebooting the watch it went back to normal.How is your experience with latest software version? Is HR really fixed?
-
@bbartlomiej Did it stop after having charged the battery? In my case HR and sleep tracking stopped after first charge with the new FW.
-
@bbartlomiej FW 2.39.20 (latest one for Vertical) introduced the HR and sleep tracking bugs that you see discussed in many recent threads. Currently, the problem is “solved” only for 9PP (the most affected by this problem) with a downgrade to a previous FW. A fix for all watches should hopefully be released this month according to statements reported in this forum.
-
Does the red dot in SuuntoApp next to the firmware version mean anything or is it there just like that? When I click, it says that the firmware is anyway up to date.
-
@kriskus interesting. I have never seen that dot before. It has appeared for me also.
-
I would like to report a new crazy behavior of my SV which I see since the last update. As for me the battery drain issue is not solved yet, I had to charge my SV today after only 17days… when I put the watch to the charger, the charging screen appeared on the watch display, but there was no change of the charging level for about 5 minutes… normally I could see the first increase of the charging level after max. 1 minutes! After a soft reset, everything was normal, and the watch is charging as expected. I recognized this behavior some weeks before, I think I charged 2 times since the last software update… and as it seems to happen every time I charge, I now report it here. I never recognized that this behavior was reported here…
-
@SuperFlo75 I can confirm I have had this behaviour as well. But not every time. It seems to me it happened when I was charging with lower remaining battery (under 30%) but I am not sure about that.
-
@Zdeněk-Hruška @SuperFlo75 I’ve seen this behaviour with previous firmwares too, mainly if I was downloading maps.
I charged mine 2 days ago without issues, battery level was 17%.In my case battery drain has been solved, 29days with 4/5 hours of GPS per week, 1 per week without GPS and around 6/7 hours of maps in total. Backlight, 24/7, sleep and notifications off. No sun either, so no solar charge.
Since I have the watch this has been the best battery consumption that I ever have had.
-
@Zdeněk-Hruška I recognized this behavior the last 3 times I wanted to charge… not before. I always charge from a level of about 5-10%… so I can’t give a statement if the behavior is different when charging from a higher level
-
@SuperFlo75 I always charge below 30%, otherwise the alarm clock no longer works.
-
Having some issues with my SV recently. No apparent reason. Last update was in December (2.39.20).
Last Friday, did a Treadmill session. Watch totally failed to track that. Usually there are some differences between the watch and the treadmill (maybe 1Km difference in a 10Km run).
However, this time, watch was tracking 30min/Km pace, when I was running around 6:30m/Km. Mega fail.The next day, Saturday, for first time, HR stoped working. It seems the issue is not only affecting the S9PP.
This required a soft reset to have HR working again.Two days after, yesterday, another treadmill run and another 30min/Km session. I stoped the session and started a new one, hoping that might solve it but nothing, continue tracking my session at around 30min/Km.
At the end, I manually adjusted the distance. However, that doesn’t have an impact on TSS.
Thus, one of those sessions is now a 6.05Km distance and 40 min long, with 477Kcal, 7585 steps and 2 TSSr!!!Can’t see why this has started happening now, again, no recent watch updates.
Maybe next time I would take my old S9B as a backup and comparison!
