This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Edge 830 Version 8.00 Bugs

As i expected, the 8.00 still contains the previous 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 19pcs duplicated positions during a 140mins ride (sometimes more, if somebody needs i can check the previous activities with 8.00fw), these duplications happened today within a 4mins window ( between 49.5min - 53.5min), 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 123mins: 

751800 2021. 06. 16. 15:18:02
751900 2021. 06. 16. 15:18:03
752000 2021. 06. 16. 15:18:05
752100 2021. 06. 16. 15:18:06

#3: Comm chip (ANT+) resetting, dropped my powermeter, hrm and speed sensor's signal after ~35mins: 

Timestamp PosLat PosLong Altitude Distance GPSDistance HeartRate Cadence Speed Power
2021. 06. 16. 13:49:35 47,73636265°N 9,07911315°E 449,6 [1] 17,55112000 [6] 17,61077000 132 [4] 98 [5] 51,83 [6] 228 [5]
2021. 06. 16. 13:49:36 47,73623952°N 9,07915740°E 449,2 [1] 17,56558000 [6] 17,62485000 132 [4] 98 [5] 52,00 [6] 211 [5]
2021. 06. 16. 13:49:37 47,73611337°N 9,07918481°E 448,6 [1] 17,57992000 [6] 17,63903000 133 [4] 98 [5] 51,66 [6] 217 [5]
2021. 06. 16. 13:49:38 47,73598588°N 9,07919663°E 448,4 [1] 17,59433000 [6] 17,65323000 132 [4] 98 [5] 51,83 [6] 0 [5]
2021. 06. 16. 13:49:39 47,73585605°N 9,07919051°E 448,2 [1] 17,60873000 [6] 17,66767000 132 [4] 98 [5] 51,83 [6] 0 [5]
2021. 06. 16. 13:49:40 47,73572722°N 9,07916159°E 448,0 [1] 17,62312000 [6] 17,68216000 132 [4] 0 [5] 51,83 [6] 0 [5]
2021. 06. 16. 13:49:41 47,73560015°N 9,07911155°E 447,6 [1] 17,63773000 [3] 17,69678000 132 [4] 0 [5] 51,83 [3] 0 [5]
2021. 06. 16. 13:49:42 47,73547945°N 9,07903771°E 447,2 [1] 17,65222000 [3] 17,71130000 132 [4] 0 [5] 52,20 [3] 0 [5]
2021. 06. 16. 13:49:43 47,73536763°N 9,07894132°E 446,6 [1] 17,66658000 [3] 17,72568000   98 [5] 52,20 [3] 208 [5]
2021. 06. 16. 13:49:44 47,73526789°N 9,07882498°E 445,8 [1] 17,68068000 [3] 17,73979000   98 [5] 51,96 [3] 218 [5]
2021. 06. 16. 13:49:45 47,73518004°N 9,07869388°E 445,6 [1] 17,69454000 [3] 17,75365000 132 [4] 98 [5] 51,12 [3] 218 [5]
2021. 06. 16. 13:49:46 47,73510377°N 9,07854812°E 445,2 [1] 17,70795000 [6] 17,76749000 132 [4] 92 [5] 48,27 [6] 218 [5]
2021. 06. 16. 13:49:47 47,73503722°N 9,07839088°E 445,2 [1] 17,72115000 [6] 17,78141000 132 [4] 96 [5] 47,53 [6] 205 [5]
2021. 06. 16. 13:49:48 47,73498558°N 9,07822626°E 445,0 [1] 17,73423000 [6] 17,79503000 131 [4] 97 [5] 46,82 [6] 222 [5]
2021. 06. 16. 13:49:49 47,73494175°N 9,07805745°E 445,0 [1] 17,74705000 [6] 17,80859000 131 [4] 96 [5] 46,39 [6] 224 [5]

when is the fix expected? still in this century?

  • I did the reset 3 times. The same all the time. I noticed that this happens while the gps is running. when GPS is turned off, activity profiles can be switched.
  • I have the same. The load focus and 7 day training load have both been wiped. I hope they will return after a few rides.

  • +1 on the ant+ issues. It seems packers get lost on powermeter more often. On varia radar it signals as disconnected, I believe that’s because of the safety nature of the system, no error message on powermeter. Also sometimes all sensors get disconnected, sometimes just the remote for instance. 

    very bad experience in this matter, first versions did not have this issue. Maybe as software matures is gets bloated and hangs? Shouldn’t the ANT+ comms take priority on development/debug?

    My Wahoo friends have no ANT+ issues at all, so maybe when it’s time to upgrade I really consider switching sides on this one. 

    I once wrote that Garmin risks to be the new Nokia, I hope I am wrong. 

    BicyclistOn

  • " I did a factory reset via buttons and restore only thru connect app. So now it's working..."

    Do factory reset via button command: 

    To perform a master reset:
    1. Power device off.
    2. Press and hold Lap and Start/Stop.
    3. Power device on while still holding both buttons.
    4. Continue holding buttons when Garmin “splash” screen appears.
    5. Release buttons when Garmin “splash” screen disappears.
  • How do I get a report like this?

  • May be related to training status resetting: I've done 2 rides in 2 days where I allegedly did a personal best 40km. Only the second ride, was 7 minutes slower than the first! And neither were anywhere near a PB for me anyway. Edge 830 on v8.10. New issue to v8.x.

  • Another new bug to v8.x on navigation: Twice I've been following a route, bluetooth audio via my Android has said "take the second exit as the roundabout", yet shown a graphc of a staggerd crossroads (not a roundabout), that directed me left! I followed the graphic, only to be told I'd gone the wrong way, the audio was correct, graphic was completely wrong.  I'm also now frequently being told to take the n'th exit on a roundabout, that disagrees totally with reality and the graphic.  This is in the UK, but even accounting for a reversed direction, the count is still wrong.
    On that point (not new to v8.x), the "coming-up" graphic for roundabouts in the UK, is frequently (always?) the wrong direction, we go anti-clockwise... You'd think with Garmin's global presence and historic products, they'd be able to get that right lol.

  • Have had an 830 for almost 2 years now, worked flawlessly up until the latest 8.10 firmware (thats the only thing i can think has changed) Lost Satellities popping up constantly on the device, km's not recording, ride going into pause mode. Nothing and i mean nothing else has changed on the device. Out for a ride this evening, it was 2k before the sats picked up, then said i was doing 63kph, down to 22kph and kept bouncing up and down speeds for the next 3 or 4 k. Stabilised for a while then started acting back up. Kept pausing and restarting mid ride. Getting very annoying, and am hoping this is a software issue that can be fixed. Any help appreciated.

  • Anything changed for the better since 8.10?

  • Looks like everything is GPS.  You did restart? Think unit has to rebuild its satelites 'priority list'.