Acquiring and losing satellites

Same here in Japan.
With my Edge 520 getting the 'Lost Satellite' warning about several hours into rides, but not always.
This annoying problem started happening about two months ago.

After I contacted Garmin Japan asking for repair, I received the following comment.
" Garmin is aware of this problem of GPS reception being unstable over time. We suspect that it could be related to the GPS software version and are now working on it to fix."

How frequently are people getting this issue (% of rides)?

I've had this problem repeatedly since I purchased a 1030 about two months ago. I contacted Garmin Australia support several weeks ago about the problem, and followed their instructions to perform a master reset and reinstall the firmware. Those changes made no difference - in the week following, I had the lost satellite problem on four of six rides, usually somewhere between the 30km and 50km point of the ride (the two rides where I didn't get the problem were short rides of only 20km). I sent all the requested information off the Garmin, but no fix has yet been forthcoming...

When the problem happens, if I go into the GPS settings and flip the setting (ie from GPS only to GPS+GLONASS or from GPS+GLONASS to GPS only), that gets rid of the problem for the next 30-50km, after which I need to flip the setting again.

Luckily I didn't sell my 1000 when I purchased to 1030. I've been on several rides with both units on the handlebars, and it's only ever the 1030 that screws up.

...

When the problem happens, if I go into the GPS settings and flip the setting (ie from GPS only to GPS+GLONASS or from GPS+GLONASS to GPS only), that gets rid of the problem for the next 30-50km, after which I need to flip the setting again.

...

Same problem with the 820. Same method to fix while riding.

Last Sunday new high speed record: 233km/h on a flat track. Thinking abour a career as a professional rider ...

Edge 1030 finds satellites way better now (new gps update installed). Have tested few days now and it founds satellites almost fast as edge1000.
My location is southern Finland.

Edge 1030 finds satellites way better now (new gps update installed). Have tested few days now and it founds satellites almost fast as edge1000.
My location is southern Finland.

I thought I glimpsed a GPS firmware update in the weekend. Will give it another shot. Thanks!

My 820 has never had this problem until a GPS firmware update today and throughout my ride home tonight it constantly kept loosing satellite connection. Very frustrating.

I'm in Australia also (Canberra), and I've noticed this problem as well - it doesn't happen until I'm about three hours into a ride, then the 1030 beeps at me fairly frequently for the rest of the ride saying that it has lost satellites. Running F/W 3.90. I haven't had the problem on shorter rides up to 60-70km. It happened to me today on an out and back 130km ride where I retraced my route over exactly the same road - no problem on the outward leg, but at about the 75km point on the return leg, I started getting the "lost satellite" messages at the top of the screen. After about 20km of this, I went into settings and changed the satellite setting from GPS+GLONASS to GPS, and I had no further problems with lost satellites for the remaining 30km of the ride. One of the other riders on this ride was using an Edge 1000, and he had no problem at any time during the ride with loss of satellite signal.

So it seems to me that there is some bug in the 1030 firmware that only manifests itself after several hours of recording a ride and only if the GPS mode is set to GPS+GLONASS.

Mine was already set to GPS and I'm having this issue constantly. And yes it gets worse as the ride goes on - today on a 3 hour ride it was constantly beeping in the last 30 mins. Drives the other riders mad so I've had to turn off sounds. My partners 1030 has exactly the same issue. Even after the v4.0 firmware upgrade I have this issue. So, I've changed it to GPS+GLONASS to see if that makes a difference in Sydney. This only started with the update to v3.8 of the firmware but I can't seem to downgrade like you could on the older Garmins.

Mine was already set to GPS and I'm having this issue constantly. And yes it gets worse as the ride goes on - today on a 3 hour ride it was constantly beeping in the last 30 mins. Drives the other riders mad so I've had to turn off sounds. My partners 1030 has exactly the same issue. Even after the v4.0 firmware upgrade I have this issue. So, I've changed it to GPS+GLONASS to see if that makes a difference in Sydney. This only started with the update to v3.8 of the firmware but I can't seem to downgrade like you could on the older Garmins.

The GPS firmware was updated about two weeks ago to version 4.4. Maybe make sure you have that. I havent updated the garmin software from 3.9 to 4.0 yet as I'm not seeing any benefits with fixes they report in the log (they didnt list anything about GPS), but my first two rides since the GPS firmware update and things are looking good for me. Time will tell though ...we do tend to be beta users for Garmin for the first few years of a products existence.

Unfortunately I cannot confirm that the issue is fully solved with the latest GPS-Update and Garmin Edge 1030 running 4.0. My device works fine for 50km rides but not when doing 80km+. Also switching GPS off/on or changing GPS only/ GPS+GLONASS does not fix the problem. This happened repeatedly and I was quiet upset on my last tour. Planned 115km and lost over 10km because I use the auto-stop function that interrupts recording when driving at very low speed. I set this to 5km/h in order to not record traffic lights stops. I noticed the speed jumped randomly. It never exeeded the actual correct speed I guess but very often went down to 10km/h or even 0 km/h even on a descend where you easily go 50km/h just by rolling. What is the expected behaviour when using an additional speedometer? Which one will "win"? I use a Bontrager DuoTrap as it comes integrated on my Trek road bike. Anyway on clear sky on open fields this is not acceptable for a device like that. Garmin please keep working on that or tell what additional data you will need to analyze.