This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Hangs on "Wait for GPS", Still Works

Former Member
Former Member

Watch: Vivoactive 4

SW: 5.1.0

GPS: 4.6.0

With a recent software update, I started a Run activity, waited an abnormally long while for GPS signal, and the screen seemed stuck on "Wait for GPS" but with the status bar at full red as though signal was acquired. After waiting at least 5 minutes or more, I went ahead and started the activity and ran for a while. As soon as I started the run it looks like GPS was working just fine. The activity summary has an accurate log for my position throughout the run.

It seems like GPS was working just fine, but the firmware was stuck in this "Wait for GPS" state as though there's a flag that's not properly getting set to as to display that the activity is Ready to begin. Everything worked fine yesterday, today with new software I get this odd behavior.

  • Hello! Are you able to test this today and tell me if you experience the same issue when trying to connect to the GPS? Did you update the device using the app or through the computer?

  • Former Member
    0 Former Member over 4 years ago in reply to Garmin-AmberD

    Yes, I'm planning on heading out again today. The software update was prompted on the watch itself, so this update came through the app.

  • Former Member
    0 Former Member over 4 years ago in reply to Former Member

    Tried again, and the first attempt got to the Ready state, then kept bouncing back and forth between "Wait for GPS" and Ready. After going back to the home watch face and starting a fresh Run activity, it finally worked ok and made it to the Ready state in usual fashion.

  • exactly same behavior on mine and I have same firmware and gps. There is a separate thread on the gps 4.6.0 firmware. For me it only seems to happen with the 'run' activity but not walk. Left it 20 mins last week (outside) before run and 'wait for gps' message never went so ran anyway and all seemed to be OK with the track. Going out again today so will report back

  • I find the watch frequently takes a long time to say the GPS is ready.  I usually give up after a minute or so and start the activity anyway.  Most of the time the GPS data looks okay, sometimes the beginning location of the activity is off a bit.  In my case I am mostly interested in the distance I cover, not the exact location. 

  • Updated firmware to beta version. Just been out waited 3 minutes for a gps fix but didn't happen, so set off anyway - data and distance looks accurate, so that's the main thing

  • Do you notice a difference in kcals burned when “gps ready” compared to starting prematurely? I did a 7km run the other day before gps was ready and it logged total 55kcals Open mouth Impossible unless I was floating RoflI wondered if it was due to heart rate not being detected in getting ready or whether just a glitch? 

  • I have the exact same situation. Start a walk activity, and wait an abnormally long time for signal acquisition. Usually the red bar is full and still it has "Wait for GPS". I start the walk and its tracks ok, but its clearly not right. I've used all the combinations of GPS with the same results. The tracking in some parts of the walk is way off what it should be, and compared to my old VA HR, the GPS is poor on a good day.

    SW: 5.6.0

    GPS: 4.8.0

    Does anyone have a fix for this ?

  • HI there! Can you hold the power button for 45 seconds ignoring power off. Then turn it back on and try again. If this does not work can you let me know. 

  • OK just been outside to try it. Sunshine and clear day. Took a time to become Ready so I would say no, its no better. Its a shame as my VAHR would be slow to connect if I was in another location, but thereafter it would only take a few seconds. The VA4 might take a couple of minutes from a location it always uses and earlier today it was cycling between ready and waiting..... I mean it clearly tracks from the start but it look like a SW issue that its not updating the watch face that it is in fact Ready.