Suunto app Forum Suunto Community Forum
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Suunto Race 2 constantly rebooting — firmware 2.56.18, confirmed via device logs

    Scheduled Pinned Locked Moved Suunto Race 2
    9 Posts 4 Posters 357 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V Offline
      viduc
      last edited by

      Hi all,

      My Suunto Race 2 has been rebooting constantly — roughly every 10–40 minutes, sometimes as often as every 7 minutes. I pulled the diagnostic logs off the watch’s internal storage to investigate, and the cause is clear and consistent.

      Findings:

      29 crashes recorded in a single 17-hour period
      Every crash is the identical firmware hard fault: HardFault (task:ui), unaligned memory access, at the exact same code address (PC 0x004A0A38) every single time
      Currently running firmware 2.56.18, HW version 1428B4
      A full factory reset did not resolve it — the crashes resumed with the same signature afterward, which rules out a settings/data corruption issue
      A firmware update/rollback attempt around the same time also triggered a separate one-time crash (an internal assertion in the update flasher)
      Given the identical crash address across every occurrence, this looks like a reproducible bug in firmware 2.56.18 itself, not a hardware fault or something caused by my settings.

      Has anyone else on 2.56.18 seen this? Suunto support — happy to share the full log files if useful; I have detailed timestamps, fault codes, and stack traces ready to send. I tried through the app, but I have been sending since the last firmware but they appear to not be fixed so I suspect the ticket is not monitored there.

      Thanks.

      Suunto_Race2_Reboot_Report.pdf

      isaziI T 2 Replies Last reply Reply Quote 0
      • isaziI Offline
        isazi Moderator @viduc
        last edited by

        @viduc I would contact support and ask for a replacement.

        Watch: Suunto Vertical 2 Titanium Black

        Blog: isazi's home

        1 Reply Last reply Reply Quote 0
        • T Online
          Thorlap71 @viduc
          last edited by

          @viduc Hi,

          I got my Race 2 4 days ago and I had two crashes as well. On getting the watch I updated it to 2.56.18 immediately. I had my first crash on Friday just before my 100km race therefore I was worried it could happen again med race, but it didn’t. The second crash happened today. In comparison with your crashes they are not so frequent, but there must be some kind of issue here to resolve. I have yet to see how the watch will be behave in the future and am a bit worried and I shouldn’t be for the watch of that price tag.

          Regards.

          V 1 Reply Last reply Reply Quote 0
          • V Offline
            viduc @Thorlap71
            last edited by

            @Thorlap71 I looked at the logs myself, in my case it’s to do with the Always-on-Display function in conjunction with the numbered watch faces, how every minutes the time is rendered at a different position to save the OLED panel burn in. Solution for now until they recognise there is a problem, either turn off AoD function or use a different watch face with hands/needles instead of number. I sent many logs but still they replied in the email that they received none. idk but I hope it helps you

            E 1 Reply Last reply Reply Quote 0
            • E Offline
              elbee @viduc
              last edited by

              @viduc said:

              I sent many logs but still they replied in the email that they received none.

              Did you send the mail from the same account as is configured in your suunto account?

              Suunto matches logs on email account. It would be so more convenient if you got a reference number after you sent in a log.

              Suunto t3c | Suunto Ambit 3 sport | Tomtom runner 2 | Garmin forerunner 935 | Garmin forerunner 965 | Suunto race s
              Stryd | Bryton Gardia R300L | Polar H9 | Polar oh1+ | Wahoo bolt v2 | 4iiii precision 3

              V 1 Reply Last reply Reply Quote 0
              • isaziI Offline
                isazi Moderator
                last edited by

                @viduc @thorlap71 are you both using always on display? Which watch face?

                Watch: Suunto Vertical 2 Titanium Black

                Blog: isazi's home

                V 1 Reply Last reply Reply Quote 0
                • V Offline
                  viduc @isazi
                  last edited by

                  @isazi
                  So far I have tested Vector Classic, Outback Adventure, Race 2 (default watch face), and lastly Modern Analog. With the exception of the Modern Analog which has run 16 hours without any crashes, all other numbered watch faces I tested have been crashing every 20-30 minutes.

                  Here’s what can be inferred from the logs:
                  The bug is most likely in the shared low-power/AOD rendering component (“c-helper-lowp”) used by multiple of Suunto’s stock watch faces — specifically in the native code that looks up a glyph from the packed bitmap font asset at the randomized (x, y) position computed by aodMove(). Because the position is randomized every minute via Math.random(), only some resulting offsets are byte-misaligned, which explains why the fault is frequent but not constant, and why different watch faces (different eW/eH/tarDis parameters and different font assets) produce different crash rates without eliminating the bug.

                  1 Reply Last reply Reply Quote 1
                  • V Offline
                    viduc @elbee
                    last edited by

                    @elbee yes, it’s from the same email address with suunto app

                    Here’s the excerpt
                    “At the moment, we have not received any confirmed reports regarding this specific issue with firmware version 2.56.18. It is still recommended that you update your watch to the latest version. To help us investigate this further, could you please submit the device logs through the Suunto App?”

                    E 1 Reply Last reply Reply Quote 0
                    • E Offline
                      elbee @viduc
                      last edited by

                      @viduc suunto support isn’t the most professional support organization.

                      Suunto t3c | Suunto Ambit 3 sport | Tomtom runner 2 | Garmin forerunner 935 | Garmin forerunner 965 | Suunto race s
                      Stryd | Bryton Gardia R300L | Polar H9 | Polar oh1+ | Wahoo bolt v2 | 4iiii precision 3

                      1 Reply Last reply Reply Quote 0

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      • First post
                        Last post

                      Suunto Terms | Privacy Policy