As i expected, nothing changes... the 8.20 (as the 8.10 and 8.00 and previous ones) still contains the SAME bugs what i wrote down many times here (too):
#1: GPS LAT/LON position duplication due to bad low priority coding (the cpu doesnt get back new GPS position within 1sec due to bad low priority coding and in this case it is using the latest known position which makes duplication...), i have 33pcs duplicated positions during a ~140mins ride (sometimes more, sometimes a little less but not ZERO), these duplications mostly happened this day (again) within a 4mins window ( between 27min - 31min, 29pcs, 4pcs a few mins later a bit), there is no active BT connection during the ride, no route, no segment, no workout, so nothing started in the background. GPS+GALILEO setting but the GNSS setting is irrelevant as i experienced.
#2: Record skipping bug , always there is 1 skipped record in the FIT file, today at the ~105mins:
| ID | Timestamp | TimeRelative |
| 639200 | 2021. 07. 26. 15:08:28 | 6285 |
| 639300 | 2021. 07. 26. 15:08:29 | 6286 |
| 639400 | 2021. 07. 26. 15:08:31 | 6288 |
| 639500 | 2021. 07. 26. 15:08:32 | 6289 |
#3: Comm chip (ANT+) resetting, dropped my powermeter and speed sensor's signal after ~25mins (disconnect and reconnect message on 830):
i pedaled continously (so the power and cadence values should be non-zero...), the source of the speed and distance was changing from [4] (speed sensor) to [2] (GPS) and back to [4]
| ID | Timestamp | PosLat | PosLong | Altitude | Distance | GPSDistance | HeartRate | Cadence | Speed | Power |
| 149700 | 2021. 07. 26. 13:48:13 | 47,82116965°N | 9,05812486°E | 430,4 [1] | 13,08702000 [4] | 13,03444000 | 90 [3] | 25,36 [4] | 246 [3] | |
| 149800 | 2021. 07. 26. 13:48:14 | 47,82120930°N | 9,05804783°E | 430,6 [1] | 13,09407000 [4] | 13,04169000 | 89 [3] | 25,36 [4] | 242 [3] | |
| 149900 | 2021. 07. 26. 13:48:15 | 47,82124844°N | 9,05797273°E | 430,6 [1] | 13,10113000 [4] | 13,04881000 | 89 [3] | 25,36 [4] | 250 [3] | |
| 150000 | 2021. 07. 26. 13:48:16 | 47,82128809°N | 9,05789880°E | 431,0 [1] | 13,10816000 [4] | 13,05588000 | 89 [3] | 25,29 [4] | 250 [3] | |
| 150100 | 2021. 07. 26. 13:48:17 | 47,82132656°N | 9,05782454°E | 431,2 [1] | 13,11517000 [4] | 13,06290000 | 88 [3] | 25,19 [4] | 241 [3] | |
| 150200 | 2021. 07. 26. 13:48:18 | 47,82136437°N | 9,05774860°E | 431,2 [1] | 13,12225000 [4] | 13,06997000 | 88 [3] | 25,46 [4] | 260 [3] | |
| 150300 | 2021. 07. 26. 13:48:19 | 47,82140234°N | 9,05767140°E | 431,4 [1] | 13,12934000 [4] | 13,07713000 | 88 [3] | 25,46 [4] | 0 [3] | |
| 150400 | 2021. 07. 26. 13:48:20 | 47,82144802°N | 9,05758289°E | 431,4 [1] | 13,13642000 [4] | 13,08548000 | 88 [3] | 25,46 [4] | 0 [3] | |
| 150500 | 2021. 07. 26. 13:48:21 | 47,82148892°N | 9,05750938°E | 431,6 [1] | 13,14355000 [2] | 13,09262000 | 0 [3] | 25,46 [2] | 0 [3] | |
| 150600 | 2021. 07. 26. 13:48:22 | 47,82153779°N | 9,05744442°E | 431,6 [1] | 13,15082000 [4] | 13,09991000 | 0 [3] | 26,13 [4] | 0 [3] | |
| 150700 | 2021. 07. 26. 13:48:23 | 47,82159126°N | 9,05739882°E | 431,8 [1] | 13,15778000 [4] | 13,10677000 | 90 [3] | 25,06 [4] | 258 [3] | |
| 150800 | 2021. 07. 26. 13:48:24 | 47,82163418°N | 9,05738784°E | 432,0 [1] | 13,16455000 [4] | 13,11161000 | 88 [3] | 24,35 [4] | 300 [3] | |
| 150900 | 2021. 07. 26. 13:48:25 | 47,82168816°N | 9,05738826°E | 432,2 [1] | 13,17107000 [4] | 13,11761000 | 90 [3] | 23,48 [4] | 261 [3] |
I cant believe that the programmers cant debug it...
Isnt any debugging feature for users in the 830 with a secret/hidden settings? Garmin-Matthew i read somewhere on the forum there is method for certain models....
I'd like to run it in the background to find out what's causing it.
FIT file attached 7192973608.zip
