Time out by 10 seconds

comparing to what? to other's flyby on Strava for example? or to GPS time by a mobile app ?

Yes using Strava flybys on a group activity I'm around 10 seconds behind everyone else.

yes, it is an ancient known bug (by me), i reported it to Garmin 2 or 3 years ago (under gps time offset bug or similiar name), but they didnt fixed it and didnt reply to me. i didnt test it fully but this is my theory: you need to turn off the unit completely (so not the short power button press, that is the sleep mode only) after You got a good gps lock, then turn it back on, wait for a lock again and start an activity and in this case it will be good (probably the sleep only mode is the problem, i dont know). and what i noticed that the clock (top right corner or the time of the day datafield) is accurate , no offset difference (it could be anything between ~1-15secs as i experienced, i assume it is the internal quarz clock's slowdown as time goes day by day) but when it is recording, there is delay in the FIT file, so something wrong in the code for sure. i have many comparisons (i record with 2 or 3 devices simultanously) day by day where this bug is exist and good shown. (530 and 830 is affected for sure, maybe the 1030 too)

btw, what is the gnss setting in your device? gps, gps+glonass or gps+galileo? i'm using it always with gps+galileo and my 1st idea was that this is the problem somewhy (the old Edge 820/1000 never had such a time offset issue) and if the gnss setting is different , it is good (i never tested it longer so this is why i asked).

Garmin-Matthew any update from Edge coding team about this since 2 years?

here is my old thread: forums.garmin.com/.../1137369

I do notice some others are experiencing the lag in the same group activity as me using Garmin devices as well.

I always switch the Garmin off (not standby) after every ride. 

These past two days I've done what you have suggested by switching it on, wait for GPS lock then switching it off then back on again and the time seems to be correct! 

I'm using the default GPS setting - think its GPS + Glosnass from memory 

lowenhart  "great news!" (and such a big shame for Garmin... but it is not the only one bug what they couldnt fix since many years in Edge family... lots of bug is coming from Edge 510, i bet Garmin never rewrite the code from base, they reuse a core from older models and if this contains bugs, it will be in never models too...)

btw, do You have the Bluetooth phone connection enabled or disabled? Because probably if the BT is enabled, the time may be synced via GC app as with newer wristwatch and this issue doesnt happen with others, only with BT Off, i dont know, i dont use BT phone connection , it is switched off 

I had a 520 for 7 years before the 530 and never experienced any 'time lag' issues.

I have the Bluetooth enabled all the time, I always pair my phone so I can see messages etc

Btw I checked the 530 and the GPS setting is indeed GPS + GLONASS

I wonder if just having it on GPS will solve the time lag issue...? 

lowenhart yes, the time lag bug is only on the x30 series, the old x20, x10 series had/have another bugs which is still in the newer models too. (gps position duplications in FIT file, skipped data records, or the bad "distance" field values which cause weird jaggy speed chart on Strava for example if you dont use speed sensor... ) Yeah, then there is no time sync via BT. i cant imagine why cant code it right , the unit gets the accurate time from sats, but somehow this variable not copiing to the another timer which is the source of the time in the FIT file for recording (probably there are more variables for it and only copy it before you turn the device off  and not immediately after the gps lock is done and the gps time is present)

let's try it but i dont think that the only GPS setting will solve it.  (i cant do it , i dont ride outdoor now , it's winter now... )

Luko79I never really had any issues with my old 520 actually and I find it was better built. The buttons on the 530 feel flimsy. Also the screen doesn't seem as bright as the 520. Cost cutting?

Anyway, I tried the GPS setting this morning to GPS only and on flybys I'm around 5 seconds slower than my friend (who is using a 520)

Might have to keep on doing your method of turning it on and wait for GPS lock and then switch it off and back on again (if I can be bothered ) 

Check that you are using 1 second recoding. The Flyby is using the data points available. If you are using smart recording them there can be up to a 5 second data between data points.