SSU 2.5.18 - ON AIR

[suzzlo]

Sure, create new bug, and use [Translation] in subject and tags!

[sartoric]

@suzzlo said in SSU 2.5.18 - ON AIR:

Sure, create new bug, and use [Translation] in subject and tags!

Where ?
In App / bug even if it’s a watch “bug” ?

[suzzlo]

Upssss sorry…

This forum is for SA, but we know Suunto is reading. Perhaps they are taking note of your comment/bugreport. Other option is to send and email to Suunto Customer Support

[A Former User]

@sartoric lol. Just happened to click and see this. The thrill of Discovery!!

[Markus Fischbacher]

I have the feeling that the watch is reacting a little bit worse since the update. What does the community say?

[gerhardusvb]

im on the Trainer , and since the update, when pressing the top left button during a workout it no longers brings up the current time …

am i missing something or do i now have t0 add it as a datafield??

[Dimitrios Kanellopoulos]

@gerhardusvb use lower button long press

[gerhardusvb]

Thanks! i missed that one, tried all buttons this morning but did not try longpress…

[suzzlo]

I feel all things in FW a bit better, but it’s just an impression (no stress test done), but I actually cannot find something that works worse that before, so

Now we have more more configuration options, that I assume are going to appear in the next SA versions, so I expect improvements in one of the most asked features in this forum Full watch customization

Best regards

[ianshowalter]

I think I just found a bug in the 2.5.18 firmware. At least, that’s what I’m assuming it is since I’ve had my Spartan Ultra for almost a year and this had never happened until about an hour ago.

I just finished a 15 minute stretching session, selected my feeling on the watch after ending the workout, and the watch displayed it’s usual “Saving” screen with the spinning circle. After a short while I noticed my watch still said “Saving” and the circle continued to spin. I let it go for another few minutes, and it still said “Saving” and the circle was still spinning. At that point I assumed it had somehow gotten stuck, so I held down the upper right button for 12 seconds and rebooted the watch.

Here’s where it gets weirder: I was fully expecting to have lost the workout at that point, since the watch had given no indication that it ever finished saving it. But after rebooting, I found the workout in the logbook. It had in fact been saved. Not only that, but during the time it appeared frozen, the watch had also connected to my phone over Bluetooth and uploaded the session to the Suunto App. Everything in the background had continued to work exactly as it should; it was only the watch’s display that had gotten stuck on the “Saving” screen.

I’d completed and saved several other sessions earlier today before that last one without incident.

[Dimitrios Kanellopoulos]

@ianshowalter question… Did you have also MC app? Installed and logged in?

[ianshowalter]

@Dimitrios-Kanellopoulos No. I only connect my watch to Movescount using the USB power cord. I’ve never done anything like make routes in SA that would mess with that, either.

[Dimitrios Kanellopoulos]

@ianshowalter I had once before 2.5.18 in August an activity that took ages for the activity to save and then the watch rebooted after stuck.

Never again.

Can you press with Suuntolink send logs and pass me the ID ?

[ianshowalter]

Here’s the ID number: 634161718076659

In the meantime discovered something else: immediately before that stretching session, I did 36 minutes on a crosstrainer. That workout saved to the watch without any problem, and it’s fully intact in my logbook, on the Suunto App, and on the Movescount web site. But, I’ve noticed that the recovery time I accumulated during that workout and the calories burned from that workout are both missing from my watch’s current recovery time display and today’s active calories burned total. So whatever caused the problem looks like it must have actually begun with that previous crosstrainer workout.

[stromdiddily]

Odd behavior setting an alarm…random numbers appear dashed out on the S9

[A Former User]

@stromdiddily said in SSU 2.5.18 - ON AIR:

Odd behavior setting an alarm…random numbers appear dashed out on the S9


Your files did not finish uploading

[stromdiddily]

@Yannis-Belouris said in SSU 2.5.18 - ON AIR:

@stromdiddily said in SSU 2.5.18 - ON AIR:

Odd behavior setting an alarm…random numbers appear dashed out on the S9


Your files did not finish uploading

Thanks! Edited above

[Jonathan Newby]

@Yannis-Belouris thanks just got it.

[ianshowalter]

After today’s run I can confirm that measuring altitude during a run after the watch has gotten thoroughly soaked in the rain is vastly improved over what it used to be in that circumstance. I used to get some wild variations when that happened; it looks like the update fixed that.

[stromdiddily]

Sample size of 3 but tracking has been great post update. Noticeably better than the trusty A3P on two of the three runs