I got a GH625-XT a couple of weeks ago to replace a GH615B which had served me well for the last 6 years. In general I'm pleased with the new watch (I mean to write a fuller 'report' in another thread soon). There is one serious problem I've run into, though, which is potentially a show-stopper, and I'm surprised no-one else on here has been affected by it. Once in a while, when I get back from a run and upload the data to SportTracks, I find that the track is wildly inaccurate, all over the place - and by inaccurate, I mean maybe even hundreds of metres from where I was! It's happened 4 times now, and with the latest one just now, it actually records my start point as a point over 200 metres from my house. The rest of the time, on all the other runs, it's incredibly inaccurate.
Three of the times the problem has occurred with a run starting at my house, and the other time was after leaving another building, so in each case this has in effect been starting the watch from 'cold' having just turned the watch on, and getting a satellite fix afresh. It's not occurred at all when I've reset my watch while out running, so this may give a clue as to where the problem lies. On each occasion the watch has indicated that it has a proper satellite fix and is ready to go, so it's the not the case that I'm starting to run before the watch is ready.
Just to be clear, the problem is with the watch, not the data upload, because I've noticed a clearly inaccurate distance reading on the watch before doing the upload.
I thought (and hoped) that it might be a firmware issue because the watch had version 1.0 firmware on it when I got it, so I upgraded it to the latest firmware last week. But the problem has occurred again today with the latest firmware.
Could it be a fault with this particular watch? It doesn't seem likely to me given that 9 times out of 10 the accuracy is spot on - I would have thought it would be wrong all the time or not at all.