Suunto 9 Peak Pro 2.44.48 Beta Test

Matúš

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).

jschmidt

@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

Dareo

@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?

Ecki D.

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

The_77

@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.

Ecki D.

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?

Matúš

@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.

The_77

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.

Dareo

@Matúš Thanks @Matúš For now I’ve reverted back to 243.12. I saw in the thread that you provided that 2.39.20 is available, and if push comes to shove I’ll install it. Still going to try and get 240.44 since it was the latest release that didn’t cause reliability & stability problems on my watch.

@pavel.samokha Is there a link similar to the one that you provided at the beginning of this thread so that I can download and install fw 240.44 on my S9PP?

pomah86

This update works fine for me, heart rate tracking working, sleep tracking working, I do some running, climbing and gym workouts, all are tracked fine and battery life is good.

Only thing broken is VO2max, but that has been broken for over 2 years now, not sure it every worked for me…

enriqueescoms

Does anyone know for sure if Suunto developers are working on fixing the bugs mentioned about the beta, or will it just end up happening anyway? Because I don’t really have any faith in it.

Although, well, I hope I have to eat my words.

pomah86

@enriqueescoms I think the fact that we have a beta test here, is evidence they actually want to know what is wrong and have a chance to fix it. There is no point in doing a beta test and then just move on ignoring the feedback. That is just a waste of money and time. But dont assume everything will be fixed.

Elipsus

@pomah86 I think @enriqueescoms is referring to the previous beta that lasted barely a week before being pushed to everyone despite some significant issues raised.

But let’s be hopeful, Suunto did probably learn from this disastrous experiment and will be more thorough this time

pomah86

@Elipsus Ok, this is the first beta test that is open to the public that I see from Suunto, but with that history in mind I can see there is a lack of trust

Tieutieu

@pomah86 nope not the first one : there has been a few ones recently but they have been followed very quickly by public fw release

Dareo

@pomah86 If you look at my posts a little earlier in this thread you’ll see that tech support acknowledged that there was a known issue in the fw 243.2 release affecting stability. When they tell you “…rest assured this case is a top priority for us and most of our engineers are working hard to fix it”, then a couple of months go by, a new fw (beta) release comes out and you see the issue has carried over to the new release, it’s not difficult to become a bit cynical when it comes to one’s level of confidence that known bugs will actually be fixed.

That said, I’ve rolled back my fw and will wait until a final, supposedly stable, release comes out and continue to be hopeful that this issue will finally be resolved.

isazi

@Dareo which bug are you talking about? I can check if it is known or not

Dareo

@isazi S9PP freezing up and requiring a soft reset. It’s happened while watching TV, dining out, sleeping, and training. Up to 7 soft resets on a nordic walking course! I have no idea what event(s) can be triggering it. It’s intermittent and unpredictable. Sometimes the watch will go a couple of weeks with no problems then there will be a 2 day period where it’s nothing more than a bracelet due to it constantly freezing up.

This all started with the 243.12 release. Soft and hard reboots don’t help. A couple of times when rebooting there’s been a message on the watch saying “Returning the watch to a stable state”, then an hour later it will freeze up again.

I installed 2.44.48 Beta hoping to see it fixed but it wasn’t. Since the Beta also had some other issues I figured I’d just revert to 240.44 which was the last stable version that didn’t cause any problems on my watch. However, when I went to select an OTA package in debug mode 240.44 wasn’t available and it would only let me revert to 243.12 which is where the problems started.

isazi

@Dareo sounds more like a faulty watch than a bug, I would contact support if I was you

Highlands

@Dareo Hello. I haven’t experienced this behavior on my 9PP.