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

Data not updating on watch segments/laps + random hearth rate.

Scheduled Pinned Locked Moved Suunto 9
bugissue2.26.8
5 Posts 2 Posters 418 Views 2 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.
  • A Offline
    ADHDMonkey Bronze Member
    last edited by 10 Feb 2024, 18:37

    New Suunto ‘feature’.

    What it says on the title.

    Swimming/Running: segment/lap data during activity shows all zeros for distance and time. Intensity zone does not update from ‘blue’. Distance and time seems to be OK on log after the activity (both on watch and on app) but heart rate is random, as is PTE by consequence, and therefore ‘progress’ status on app.

    I blieve a similar bug has been reported on ‘race’ model.

    How and where do I upload logs for someone at suunto to maybe look at them before I ‘upgrade’ my watch to 2.23.24, or resetting it, with a hammer? 🤬

    I’m. So. Tired. Of. This. Company.

    B 1 Reply Last reply 11 Feb 2024, 13:13 Reply Quote 0
    • B Offline
      Brad_Olwin Moderator @ADHDMonkey
      last edited by 11 Feb 2024, 13:13

      @ADHDMonkey I have not used the 9 in awhile but I assume you have zones set on the watch for HR? We also need more information on the laps, auto lap or manual? Custom sport mode or standard?

      Vector/T6c/Ambit 3 Peak/S5 Copper/S3/S7 Ti/S9 baro Ti/S9P Ti/S9PP Ti/Vertical Ti/Race Ti/RaceS/Ocean/Wing

      A 1 Reply Last reply 11 Feb 2024, 14:57 Reply Quote 0
      • A Offline
        ADHDMonkey Bronze Member @Brad_Olwin
        last edited by 11 Feb 2024, 14:57

        @Brad_Olwin I still use it, like many others. Happens in custom sports mode and in standard. I’m talking about auto laps and segments. All settings were unchanged when the bug appeared so its not a change of setting causing the issue. Either wa,all this is pretty irrelevant as all the info should all be available on the logs, I would think.

        1 Reply Last reply Reply Quote 0
        • A Offline
          ADHDMonkey Bronze Member
          last edited by 12 Feb 2024, 10:36

          Log Id number:

          3876357451600

          1 Reply Last reply Reply Quote 0
          • A Offline
            ADHDMonkey Bronze Member
            last edited by 13 Feb 2024, 10:38

            Soft reset seems to have fixed the issue somewhat.

            Clearly a memory management issue, which seems to be a recurring issue with these watches. A bit surprising that there is no warning mechanism for this sort of thing.

            1 Reply Last reply Reply Quote 0
            4 out of 5
            • First post
              4/5
              Last post

            Suunto Terms | Privacy Policy

              This community forum collects and processes your personal information.
              consent.not_received