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

New Edge 830 Public Beta 5.68 Now Available

Garmin-Matthew
over 4 years ago

A new Beta software for the Edge 830 has been released. Full change log, instructions, and software for installing the beta can be found in the link below.

Edge 830 (5.68): https://www8.garmin.com/support/agree.jsp?id=14955 

  • For any issues that you encounter please fill out the form included in the download and attach it to an email to [email protected]. Please note that you may not get a response to the email unless we need more information on the issue you report.
  • Although this software is believed to be reliable, it has not yet been released for production and should be used at your own risk.

Changes made from version 5.66 to 5.68:

  • Fixed CIQ data field software update migration.
  • Fixed Di2 automatic shifting.

Changes made from version 5.51 to 5.66:

  • Segments:
    Fixed issue with detecting segments that were going in the opposite direction of travel
    Improved segment and ClimbPro UI cooperation
    Fixed issues when approaching a segment embedded in a course and other minor segment UI issues
    Fixed issue where segment virtual partners would claim to be finished almost immediately after starting the segment
  • ClimbPro:
    Improved estimated time to end of a ClimbPro climb
    Fixed ClimbPro page graph drawing
    Fixed issue where disabling 'Pop-up on Climb Approach' would disable ClimbPro completely
  • Improved sensor connectivity
  • Improved automatic FTP detection
  • Added Go Back, Pause, and Go Forward workout step controls to the workout tray
  • Added support for new GPS firmware. Sync your device to update to the new firmware
  • Added option to delete a data field in quick edit mode. Access by pressing and holding a data field on a timer page.
  • Improved grit and flow consistency between Garmin products
  • Improved bike light connection stability
  • Fixed bike alarm not turning off after correct password was entered
  • Fixed radar vehicle drawing temporarily not updating
  • Added a shortcut to the display menu by pressing and holding the Auto Brightness button on the status widget
  • Added a toggle for MTB map theme
  • Improved MTB trail search UI
  • Fixed issue where history line wasn't updated while panning in the map
  • Fixed issue with the number of power zones displayed post ride
  • Fixed dual sided power meter calibration factor reporting only one side
  • Fixed Firstbeat metrics for multiple rides during the same power cycle
  • Fixed Training Effect UI layout
  • Removed unnecessary beeps for notifications that don't need them
  • Fixed timezone map downloads from WiFi
  • Fixed issue with power targets in TCX workouts
  • Made various device stability improvements
  • 0 over 4 years ago in reply to Luko79

    i use vector 3 and 1sec recording!

    5318046527.zip

  • 0 over 4 years ago in reply to f|33tStA

    Unfortunately the bug (duplicated GPS positions due to low priority setting for GPS chipset and it cant give new position data within 1s and in this case the main code is using the last known position datas, so there will be a duplicated LAT/LON value in the FIT files and if You dont have speed sensor then the speed chart on graph will be jaggy) is still there just both of You are using speed sensor which is "hiding" this .  Maybe the code is better a bit because there are "only" ~50pcs duplicated datas in a 1.5h long file, /in 5.50 there was apprx  180pcs/ , but it is still unacceptable. I will send it to the beta team also, maybe they will be able to fix it at 2021... (it is a bug since 2016-17 from older Edge units and Fenix models are also infected.../but there it is not so serious and happen randomly on a given day, and not everyday with every activity/ so they are using common old code parts in "newer" firmwares / devices...)


  • 0 over 4 years ago in reply to Former Member

    did you open the files app?
    I don't have an adapter from lightning to usb so I can't try. 

  • 0 over 4 years ago in reply to Former Member

    Yeah, it wasn't clear from your oblique question whether your problem was that

    1. you knew what you were trying to do -- which, I guess, was to install the beta firmware from an iPad -- but the device didn't mount on the iPad, in which case I was mentioning that the iPadOS is still beta so YMMV, or
    2. you were completely clueless and were posting a bizarre question (which is endemic here) expecting somehow to use connect to deal with the device via USB.

    I guess if you had said "I have an iPad and I've already got the adapter and I have unzipped the beta file but the device isn't mounting on the iPad" then I would probably would have been able to answer better.   However, I don't seem to have the adapter so I can't test it on my iPad running iOS 13.

  • 0 over 4 years ago

    Radar (510) is not working/connecting in 5.68 and back to 5.50 is not working (loop).....anyone got the same problem?

  • 0 over 4 years ago in reply to sandersbenningme.com

    same problem with the loop on on 530 when trying to go back.

  • 0 over 4 years ago in reply to sandersbenningme.com

    My 510 worked fine with 5.68 -- I didn't have to change anything.  Do you have your 510 added as part of a light network (which is what I have), or strictly as a Radar device?   I guess I should add that my ride was done before I updated the GPS software, which might be another differenced between your setup and mine (if you did the 5.68 and the GPS at the same time).

  • 0 over 4 years ago in reply to vmojzisek

    But finally I found out, that I works but only once. When I switch off Garmin and start it again, remote doesn't connect again and I have to do new pairing. Each start, each pairing. With 820 I had been waiting for proper connectivity with remote control for two years. Now, I am afraid of the same with 830. 

  • 0 over 4 years ago in reply to vmojzisek

    It's the same remote issue with the Edge 1030 beta too. I don't have to re-pair but I do have to Disable & Enable it again the the sensor settings & it will connect. 

  • 0 over 4 years ago

    Two crashes, frozen screen for the first two-hour ride