Suunto 9 Peak Pro 2.44.48 Beta Test
-
Have you been able to check if the touchscreen function is fully operational on the navigation screen (breadcrumbs)?
There was a bug in the last update that caused me to revert to a previous software version. I hope it’s been fixed.
-
@enriqueescoms Nope, same problem. Using touchscreen on the navigation screen just moves the little hamburger menu icon around.
-
@duffman19 said in Suunto 9 Peak Pro 2.44.48 Beta Test:
@enriqueescoms Nope, same problem. Using touchscreen on the navigation screen just moves the little hamburger menu icon around.
Don’t bother me! I can’t believe it… ugh
-
Took a few tries before I figured out Brave didnt know what to do with the app link (com.etc…) using Chrome worked. The update went smooth, no resets, no settings changed noticed, zones untouched. I’m a light user (walking, hiking, sleep tracking, pool swim) and mostly looking to test the swim stroke detection… give me a couple days.
-
@duffman19 Totally agree with you about map page and buttons, I prefer the SV version. I don’t understand if there is a reason that suunto did the functions differently.
S9PP
Upper button- Short press : n.a.
- Long press : multisport
Center button
- Short press : next page
- Long press : activate zoom function
Lower button
- Short press : navigation options
- Long press : n.a.
SV
Upper button- Short press : zoom in
- Long press : zoom out
Center button
- Short press : next page
- Long press : previous page
Lower button
- Short press : navigation options
- Long press : n.a.
There is also another bug that appeared since the Q1/2025 update : missing icons to indicate what the top and center buttons are for in relation to the SV.
As I already wrote in a comment following the Q1 update, this is not a serious problem but it could be annoying for someone who is not familiar with the functions.
-
@fondueaufromage Yes, you’re right. I’ve never understood why the function assignment on that screen is different between the 9PP and SV
-
Please, I’m making a plea from here, so someone at Suunto can respond: Fix the touchscreen bug on the navigation screen. Because if it’s not fixed, it’s impossible to go back one screen at a time (with the touchscreen because of the bug, and with buttons because of the function layout).
-
Having been for a run or two this morning, GNSS accuracy is still pretty good, correct side of the street, can see crossing over roads properly, did reasonably well in deep forest with only minor wobbles. So not a great difference to before, in so much as it still works. Didn’t test any other features, I’d agree on the comments changing 9PP nav page to vertical setup, as only way to go back is locking the screen and long pressing still, which is awkward if you want to use the zoom feature at any point.
EDIT: I actually just ran a test activity at home, tried to use the touchscreen in nav mode and it crashed the watch. Mildly amusing. It didn’t actually have GPS lock yet so maybe that had something to do with it. Sent logs as of 14:23 CEST.
Then I restarted it, got GPS lock and saw that the touchscreen only moves the burger menu off the page, and back on it. So I guess the bug is with the burger menu interaction at the bottom of the nav screen.
-
2h of road cycling yesterday, me with SV, my wife with S9pp updated with beta.
No issue, everything was ok ; gps accuracy perfect.
Only OHR on S9pp was completely out of whack : but as usual for her => it’s bike, and she has very small wrist (even tightened to the maximum, watch is still a bit loose)1h trail running this morning . All good, and gps accuracy seems slightly better than before update
-
Did the update today without any problems. All settings kept, just the sensors needed to be paired again (but that’s because of the new multi sensor support, right?)! Tomorrow I will test if the Stryd issues are gone…
-
Connected 2 HR-sensors (Polar Verity Sense, Polar H10). Both are shown correctly in the settings (connected devices), both show the battery status. BUT: When starting a running workout no HR-sensor could be selected, only wrist-HR! StrydX ist the only sensor that appears here.
-
@jschmidt Started a cycling session. Here the HR-sensors are working as expected. I think the devices are wrongly related to a special kind of activity only.
-
During the night between Saturday and Sunday, actually, the second night after the watch update, the OHR sensor crashed.
I’ve lost the count for this issue…
Firmware after firmware, this bug is still present: how is it possibile that no Suunto tester, still, never report this issue?I’ve already downgraded the watch to 2.40.44, the only firmware free from this bug: all the software updates are good, but I can’t accept every two mornings to soft-reset the watch to bring back all the functionalities!
Anyway, I’ve sent logs Sunday morning, at ~5:10/20 (CEST).
Suunto 9 Peak Pro Titanium Slate
Suunto Spartan Sport#swatt
-
@jschmidt Back from my first test run with Stryd. The only good thing here is: Stryd is connecting, the zero drops are gone. Beside this nearly everything failed:
- power value still shown from wrist instead of Stryd
- calibration has gone, so pace and distance in my case is way too short
- no chest hr strap is possible, so ZoneSense is not working
-
@Matúš said in Suunto 9 Peak Pro 2.44.48 Beta Test:
During the night between Saturday and Sunday, actually, the second night after the watch update, the OHR sensor crashed.
I’ve lost the count for this issue…
Firmware after firmware, this bug is still present: how is it possibile that no Suunto tester, still, never report this issue?I’ve already downgraded the watch to 2.40.44, the only firmware free from this bug: all the software updates are good, but I can’t accept every two mornings to soft-reset the watch to bring back all the functionalities!
Anyway, I’ve sent logs Sunday morning, at ~5:10/20 (CEST).
I’ve had a similar experience as @Matúš except it was the first night (Sunday night) after the update. I woke up to the watch turned off and had to restart it. No overnight data of course.
Monday morning went on a 1.5 hour hike and all worked as advertised (having previously reset my zones back to where they should be and linking my H10 again).
No issue last night, but when I synched the watch with SA this morning, despite overnight HRV having been registered on the watch SA told me it didn’t register. About an hour later the watch froze up and I had to do a soft reboot. This random freezing up, while sleeping, while watching TV, while training has been an ongoing issue for me since the FW 2.43.12 update. 2 months ago (9 July to be precise) I reported this issue in an online chat with tech support. As you can see in the following screen grab, they already knew about it and supposedly fixing it was a priority for the engineering team:
Since this continues to occur I guess it wasn’t much of a priority for the engineering team
So, after doing the soft reboot this morning I resynched my watch to app again just to be on the safe side. I had a longer 4+ hour hike planned and set out. 3h50m into the hike the watch stopped recording the exercise and either a) rebooted on it’s own, or b) just got tired and went back to being a plain old watch. I can’t say for sure because I only noticed it about 3 minutes later. So I restarted recording (a new session) and it worked until I got back home (about 20 minutes).
After synching the 2 activities to SA the app told me the whole 3h50m was in zone 1, yet while hiking I had been following the zones and the watch reported (the last time I looked) that I had been just over 2 hours in zone 2. So once again the data from the watch and SA didn’t jive. I checked the zone settings on my watch and they were correct, yet SA had randomly set my zone 2 limit 40 bpm higher than what I have set on the watch. Interestingly enough, that 2nd shorter 20 minute session after the hiccup registered the correct zone settings. Go figure!
As such, I too am going to revert back to FW version 2.40.44 since the issue from version 2.43.12 has not been fixed and has just carried over. The new functionalities added to the last 2 FW updates show potential, but I value RELIABILITY over bells and whistles and Suunto is seriously dropping the ball.
UPDATE:
Surprise, surprise! I went into debug mode => Select OTA package and what do I find? 240.44 is not available. I can only go back to 243.12 which is where the problems started to begin with. It’s a damned if you do, damned if you don’t situation.Does anybody know if there’s a way for me to get back to 240.44? Or is my only option to choose between the lesser of the two evils?
-
- Since restoring my settings no new problems
- Battery Usage since 15h 9% with all sensors on and high brightness when lifted, everything else according to light set to low/off, no activity recorded during that time. Seems a bit high to me but normally I don’t use that high brightness when lifted.
- Had no sensor issue so far but did have it once in a while
-
@pavel.samokha I’d say anecdotally the step tracking is much lower this update, but I don’t know if it has actually been changed. It just feels like it undercounts more since the change, but I’m basing this on a trip to IKEA being suspiciously low and now some oddly low days doing tourist stuff on holiday.
-
Went on walk yesterday and forgot to stop the activity when going on by car.
I didn’t get a reminder to stop the activity as usual.Today I went to my guitar lessons by bike, stayed there for 50min and pressed the pause button after arriving. After the lesson I continiued my tour and just realized after 15min that there was no warning about the acitvity still being stopped.
Has somebody tested it yet?
-
@Dareo said in Suunto 9 Peak Pro 2.44.48 Beta Test:
Does anybody know if there’s a way for me to get back to 240.44?
In the following thread, some users have experienced your same problem: https://forum.suunto.com/topic/6836/firmware-collection/96.
Also, there are links to download some past firmwares, but it seems that the 2.40.44 one is not (directly) present.
Suunto 9 Peak Pro Titanium Slate
Suunto Spartan Sport#swatt
-
New weird one. Used the send to watch navigation option, to follow a route in town. When I was zoomed into 50m zoom level, watch vibrated constantly at one second intervals, but not at 100m or higher.
Repeated it by going to the compass widget on a different route and navigating again.
