Is latest GPS Firmware Update Corrupt

3181237

I just updated to latest firmware and now the map screen just shows Acquiring Satellites.  It shows a GPS firmware update is starting (even though I jus just a firmware update) and a minute later that it is successful.  However, the Acquiring Satellites message remains.  I power off and power on and the same cycle starts over again.  I have seen messages from other users in a Facebook group mentioning the same thing starting 4 days ago.

  • 0

    If you go to the system about page what version doe sit show for the GPS?

  • 0 in reply to aweatherall

    Have the same issue, started with 31.18 now on 31.23 still not working properly. at startup it GPS Firmware i 0.00. A few minutes after start up i displays "updating GPS firmware" after updated successfully GPS Firmware is 16.01. But it takes another 10 minutes to 2h before it acquires satellites. Workaround has been to leaving it in sleep mode after acquiring satellites, then it acquiring instant after wake up. Now on 31.23 that doesn't seem to work either from time to time.

    Been in contact with the Swedish support who want me to send them the unit for troubleshooting. 

    I'm deep in the garmin ecosystem, 970, 1050, Scale S3, Connect data for 14 years,  but thinking of getting a Hammerhead Karoo for back up...

  • 0 in reply to aweatherall

    Software version 31.22B, GPS Version 16.01. Unlike Jonas comment, at start up, I show GPS 16.01.  But like him, about  a minute after start up I get his 2 screens. Note that this behavior started immediately after installing the most recent GPS Firmware update. It had downloaded recently but I ignored installing it for a few rides. After finally accepting it and installing, I get this issue with the constant "Acquiring Satellites" issue.  The rest of the device works fine - it picks up my speed sensor so I get distance and the altimeter is working so I get elevation gain. I also get data from my power meter and heart rate monitor.

  • 0

    I chatted with support. This is apparently a known issue that is being worked on and is separate from the boot loop issue. So the solution is to wait.  In the mean time, my device is useless.