Suunto 2.50.28 hot-fix Q4

mich heller

one more thing I noticed after this update - sleep summary is working again

Inge Nallsson

@Bastienhere said in Suunto 2.50.28 hot-fix Q4:

Before this update it was a nice smooth curve relatively mirroring my speed curve

But… That’s just the Suunto App presentation, not FW related. And the ‘smooth’ Pace curve in relation to Speed is due to a silly left side Pace graph going from 04:36/km to 46:17/km! You can hardly see the real variations there. The top image example you give has discernable pace variations between the 05:32/km and 07:00 extremes. Using 20.0 and 0.0 km/h for the right side Speed graph is not how I would present it, but still, all that is an App issue.

nseslija

@duffman19 Unfortunately you are right, the bug is still there.

Bastienhere

@Inge-Nallsson you’re making some fair points although the places where my pace dipped from 04:36/km to 46:17/km (and the others in the graph) was when I was stopping for traffic lights.

It’s just very inconsistent in the way it represents pace now, almost like I’m running like a drunk man lol. And to be fair I strongly think this is what is affecting my VO2Max readings.

Bastienhere

@GiPFELKiND hmm I checked my latest run and another back in December and the pace zones are the same

Likarnik

Am I the only one that has problems after this update? First time for me. Vertical1. Yesterday I was sitting at the desk and noticed that backlight is on and watch is in settings menu. Touch and buttons were not working, so I performed 12s reset. Later that day I wanted to check before my run if my zones were still ok and I couldn’t enter settings. First menu was ok, but then when I went to training, watch went back to watchface. I tried a couple of times and then went for a run. At night I woke up and the watch was again lit up and in settings menu, unresponsible. I performed soft reset and went to sleep. But the watch did not wake up. Now it looks like dead, it sits on charger but nothing happens. No button press is waking it up. Is there some special combinaton to wake it up?

helgonet12

@mich-heller for me it was the first time sleep and sleep summary didn’t work on this latest software. I did a soft reset and the sleep stats came but not summary

Highlands

@mich-heller For me the morning report reappeared out of the blue 1-2 days before my V2 got updated to the latest stable software.

Highlands

*@Likarnik

The issue you’re describing—freezing in settings, unresponsive buttons/touch, appearing “dead” or blank after soft resets and while on the charger—is a known recurring problem with the Suunto Vertical (original model), especially around software updates like the recent 2.50.26 staged rollout that started January 7, 2026 (Q4 2025 firmware). It often ties into deep freezes, partial boot failures, or battery/charging glitches post-update or after repeated resets. Many users report similar sequences: backlight stuck on, menu lockups, then blank/unresponsive screen that doesn’t wake easily.

You’re not alone; identical symptoms appear in Suunto forums, Reddit, and Facebook groups from 2023 through 2026, including after charging or resets.

Step-by-Step Troubleshooting to Try Right Now (Escalating Order)

Start with the charger plugged into a strong wall adapter (5V/1A+ recommended, not a weak laptop USB port). Clean contacts if needed. Leave it attached undisturbed for at least 30–60 minutes initially—deeply discharged or frozen watches can take 20+ minutes just to show any sign of life.

Extended upper-button hold (most successful for blank/unresponsive cases)
While on the charger:
Press and hold the upper button (topmost on the right side) for at least 20–60 seconds continuously.
- Many users say it reboots after ~12 seconds but keep holding longer (up to 60s) to force a full recovery from deep freeze or “service mode.”
- Release, wait 10–30 seconds, and see if the screen lights up, vibrates, or shows the logo/charging indicator. Repeat 3–5 times if no response.
Alternative button combos while charging
- Hold upper + middle buttons together for 15–20 seconds.
- Hold all three right-side buttons simultaneously for 15–30 seconds.
  These have revived “dead” screens for some after normal 12s reset failed.
Charge longer + periodic attempts
Leave it charging undisturbed for 2–4 hours total (even overnight if possible). Every 30–60 minutes, try the extended upper-button hold again. Some watches enter a recovery state only after sustained power.
If it wakes up at any point
- Immediately do a factory reset via watch menu: Settings → General → Reset settings → confirm (erases everything unsynced—try to sync to app first if it connects).
- Re-pair with the Suunto app, check for any pending updates (this firmware 2.50.26 includes bug fixes for crashes/button issues), and test thoroughly.
- Avoid rapid on/off or repeated soft resets right away to prevent re-triggering the freeze.

If Nothing Works After Several Hours/Attempts

This points to a deeper software lock (sometimes called “service mode” with blank or partial screen) or rare hardware/battery fault.
Contact Suunto Support right away: Use the in-app chat (if app sees the watch), their website support form, or email/phone your regional service center. Provide:
- Serial number (on box or under watch).
- Proof of purchase (for warranty—Vertical 1 is typically 2 years).
- Describe symptoms + what you’ve tried (including firmware version if known).
  Many users in similar “bricked after update/reset” situations got warranty replacements or repairs quickly.

No special “secret” recovery combination beyond the above is documented for the Vertical. Avoid draining it fully on purpose right now (as some battery-drain threads suggest), since it’s already unresponsive.

Try the extended hold first—it’s revived quite a few “dead” Verticals. Update me on what happens after attempting these!*

So sorry about your issue. Got this response from Grok. Hopefully, it helps you solve the problem.

Likarnik

@Highlands thanks, so far no luck.

Benjamin 0

I own a race Myself and I had to send it back 2 times because an import battery drain issue (whiching drifting over the time). @geoffwilli I think you are facing the same Issue, not sure it is SW…