There might have some reson to cause the situation:
- Antenna different; If it is real, we have to use firmware to compensative the weakness.
- Because of quality of the first sample production; Production guys told the 2nd run performance is something better than first. We can check this.
- Firmware problem??? GPS info seems a little lag, it is a clue.
I'm wondering, if it really makes sense to continue testing, when the beta testers have some kind
of proto-types, which are different from your normal production ? Is it really useful, when I'm posting
problems with GPS signal recieving, when you already modified something with antenna and anything
However - I will share one more finding about GPS problems:
Yesterday I made a run with 625 and 505 together. First result:
625 needed about 1 Min. to get the GPS fix.
505 needed didn't have a fix after 3 Min.. After GPS reset the fix was there in about 2 Min. (Sum: 5 Min.).
More important (and more terrible) was the result of the track recording.
Please have a look at the two screen shots (first: 625, second: 505).
I should mention, that I run exaclty the same round track 4 times.
As you can see, also 625 has some abreviations. However it is okay.
GH-505 is far away from being okay
Just to clarify: Both pictures are taken from the same run !
I could add, that finally the GH-505 showed about 600m more for the total distance of 10km,
but I think, when you have a look at the recording, this isn't the main problem.
I'm wondering, what could be the problem. Btw.: The weather was fine, nearly clear sky, no clouds,
sun shining. The track has some trees on the right side, but is open (water) on the left side.
It is complete nature there. No buildings, no technical equipments, almost no other people.
However - both watches had the same conditions. And GH-625 worked fine.