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

Update 2.33.16: GPS Precision

Scheduled Pinned Locked Moved Suunto Race
11 Posts 5 Posters 607 Views 5 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.
  • S Offline
    sartoric Moderator @Rodrigo Lima
    last edited by 27 May 2024, 22:28

    @Rodrigo-Lima
    did you check if agps is up to date ?

    SVTS - 2.40.38
    SSSWHR BARO Amber - 2.8.32
    Samsung A5 2016 - Android 7.0
    Samsung A33 2022 - Android 14 - One UI 6.1
    Suunto App Android 5.2.5 beta
    Suunto App IOs 2.45.0 (19123) beta on MBP M1

    R 1 Reply Last reply 28 May 2024, 09:00 Reply Quote 0
    • R Offline
      Rodrigo Lima @sartoric
      last edited by 28 May 2024, 09:00

      @sartoric
      Yes, the AGPS is with date: 2024-05-28T00:00:00Z

      Here you have pictures of the exactly same course, a good one before the update and a bad one after the last update.

      Before Update:

      Screenshot_20240528_095052_com.stt.android.suunto_edit_230863995471540.jpg Screenshot_20240528_095038_com.stt.android.suunto_edit_230875280671539.jpg

      After Update:

      Screenshot_20240528_094957_com.stt.android.suunto_edit_230897223437681.jpg Screenshot_20240528_095013_com.stt.android.suunto_edit_230886783352266.jpg

      Even the Altitude went completely wrong.

      Wrong Altitude:

      Screenshot_20240528_095256_com.stt.android.suunto_edit_231006332730373.jpg

      Correct Altitude:

      Screenshot_20240528_095222_com.stt.android.suunto_edit_231018387269954.jpg

      S G 2 Replies Last reply 28 May 2024, 09:12 Reply Quote 1
      • S Offline
        sartoric Moderator @Rodrigo Lima
        last edited by sartoric 28 May 2024, 09:12

        @Rodrigo-Lima
        Same wrist ?
        Same weather ?
        Did you have always the same bad result ?

        It could be just a bad gps day.
        Did you try a soft reset (and sync again) ? Just don’t do it right before the run

        SVTS - 2.40.38
        SSSWHR BARO Amber - 2.8.32
        Samsung A5 2016 - Android 7.0
        Samsung A33 2022 - Android 14 - One UI 6.1
        Suunto App Android 5.2.5 beta
        Suunto App IOs 2.45.0 (19123) beta on MBP M1

        R 2 Replies Last reply 28 May 2024, 09:15 Reply Quote 0
        • R Offline
          Rodrigo Lima @sartoric
          last edited by 28 May 2024, 09:15

          @sartoric
          Yes, the conditions were the same.
          I never had any problems with the GPS. It was always very accurate on the GPS track until this last update came.
          Both runs I did after the update, the track has problems.

          1 Reply Last reply Reply Quote 0
          • R Offline
            Rodrigo Lima @sartoric
            last edited by 28 May 2024, 09:41

            Is there a way to revert the watch to the previous version?

            1 Reply Last reply Reply Quote 0
            • G Offline
              GiPFELKiND Silver Members @Rodrigo Lima
              last edited by 28 May 2024, 10:55

              @Rodrigo-Lima whaaaaaatttttt the hell 😲😲😲😲😲

              If it doesn't challenge you, it doesn't change you. #lifewithasthma #runwithasthma #nevergiveup #pushinglimits #adventurestartshere Suunto D9, 9 Baro, 9 Peak, Vertical Ti, Race , Race s Courtney, SA (Beta) Android🏃🏼🧗⛷️🚵

              H 1 Reply Last reply 28 May 2024, 11:17 Reply Quote -1
              • H Offline
                halajos Bronze Member @GiPFELKiND
                last edited by 28 May 2024, 11:17

                I don’t think it’s related to the last update, no GPS firmware change in that. And my Race produces just perfect GPS tracks also with the latest FW.

                R 1 Reply Last reply 28 May 2024, 11:20 Reply Quote 0
                • R Offline
                  Rodrigo Lima @halajos
                  last edited by 28 May 2024, 11:20

                  @halajos mine also used to produce perfect GPS tracks.
                  What could be the solution for this?

                  H 1 Reply Last reply 28 May 2024, 11:53 Reply Quote 0
                  • H Offline
                    halajos Bronze Member @Rodrigo Lima
                    last edited by halajos 28 May 2024, 11:53

                    @Rodrigo-Lima you could try this:

                    1. ensure you’re using performance mode
                    2. soft reset the watch using 12s upper button press (AFAIK this clears the AGPS data cache)
                    3. sync the watch with the Suunto app to download AGPS file
                    4. wait a few minutes to ensure AGPS data is unpacked and processed by the watch
                    5. before starting the activity wait until the GPS indicator turns yellow and wait a couple of minutes more to let the watch connect to as many satellites as possible (do this preferably in an open area)
                    6. start your activity with GPS

                    If this consistently leads to bad GPS tracks, then your watch may be faulty.
                    FYI: It may happen, that an AGPS file on a given day is faulty or there’s a faulty satellite. These events are rare, though.

                    1 Reply Last reply Reply Quote 1
                    • L Offline
                      larrybbaker
                      last edited by 28 May 2024, 12:39

                      No issues noted here - had the update since the beta. A week worth of runs without issue. SV Ti.

                      SV Solar
                      iPhone 16 Pro

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

                      Suunto Terms | Privacy Policy

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