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 820 new 10.00 firmware update

Any good feedback and general improvements on functionality?
  • [h=3]Physio TrueUp does not work. Record activity on 820 and Recovery Advisor does not update to FR935. This functionality worked with Beta 9.34. Training Load and activity summaries transfer as expected.[/h]
  • [h=3]Physio TrueUp does not work. Record activity on 820 and Recovery Advisor does not update to FR935. This functionality worked with Beta 9.34. Training Load and activity summaries transfer as expected.[/h]


    This is now working both ways. It must have been related to Garmin Connect instead of the 10.0 firmware.
  • The update has been working well for me:
    * Battery life seems significantly better
    * Strava segments working well
    * No "dropped and reconnected" ANT devices during the ride

    The one bug I have found is that it resets to miles units every ride (I have my speed/distance set to metric). Its strange in that the speed stays in k/hr but the distance switches to miles. I have to go to settings/units every ride to reset.
  • With Firmware v. 10.00 as for v. 9.0 bluetooth connection with Microsoft Lumia 950 xl fails. After many attempts I managed to connect the two devices but at the first activity the connection fails. I think it's a problem with GCM for windows because even if the two devices are connected, GCM sometimes does not recognize the bluetooth as activated. The only firmware that works with bluetooth is v. 8.70


    Now in the bluetooth settings of my Lumia 950 xl phone there are two entries concerning the edge 820 but only one is connected while the other is only associated. So even if GCM is connected, synchronization fails.
    ciq.forums.garmin.com/.../1398555.png
  • ^^^ there are supposed to be two BT associations. Note that the icon for each is different, one showing a tablet and phone and the other a computer monitor. I believe one is used for incidental communication with your phone during a ride and the other for transferring larger amounts of data, like up/down loading courses and activities. It might be normal BT vs BTLE, but I'm not sure of that.
  • I don't know why from fw 9.0 there are two associations BT, what I'm sure is that up to version 8.7 there was only one BT association and everything worked well, so I thought that the problems with GCM for Windows devices could derive from this difference between the two firmware.