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 4.19 Now Available

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

  • 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 4.10 to 4.19:

  • Added support for Connect IQ 3.1.
  • Added support to control Garmin inReach remotely.
  • Made improvements to the indoor cycling user experience. 
    - Improved smart trainer discovery and initial setup experience when using an Indoor activity profile. 
    - Improved the Follow Course experience by enabling UI (map, ClimbPro, Elevation, etc) and data recording from the simulated course. 
    - Made improvements to smart trainer sensor calibration.
  • Made improvements to Workout user experience. 
    - Added FTP line to workout comparison displays. 
    - Allowed graphical workout data fields to be configured on regular data screens. 
    - Improved the display for open steps on the workout comparison graph.
  • Made improvements to the ClimbPro user experience. 
    - Made ClimbPro available for navigation to a location and for round-trip courses. 
    - Added a setting in the ClimbPro data screen setup to specify which climbs should be detected (All, Medium/Large, Large Only). 
    - Removed the ClimbPro page from the timer loop if there are no climbs left in the ride.
  • Made improvements to the Segment user experience. 
    - Fixed an issue where segments with slashes in the name would not be processed and would create subfolders on the file system. 
    - Fixed an issue where the segment leader could get reset during a sync. 
    - Added setting in the Segments menu to set a Default Leader Priority, which allows the user to set a default leader to apply to all segments.
  • Added pressure filter in order to improve elevation recording.
  • Improved Firstbeat heat acclimation by utilizing weather forecasts.
  • Added ability to render Hebrew text for incoming smart notifications. This requires additional font files. Follow instructions on separate forum post.
  • Fixed issues with the map zoom level not being set correctly.
  • Fixed an issue where Battery Save Mode could stop working mid-ride.
  • Added jump prompts for each jump in cases where there are multiple jumps in a row.
  • Fixed issues with the heart rate graph data field.
  • Fixed an issue that caused Auto Detect Max HR to always be enabled.
  • Improved the y-scaling on the elevation profile.
  • Added directional arrows for round trip courses.
  • Fixed cosmetic issues with Extended Display mode.
  • Added additional info to the nutrition/hydration settings page.
  • Turned backlight on when the user laps or there is an autolap during an activity.
  • Automatically sized the text in the elevation data field.
  • Improved overall device stability by fixing crashes and freezes.
  • in the Indoor Profil i can take no 

    additionally training site
  • GPS performance improvements, please.

  • Zoom issue in map field still preserve 

  • i've installed yesterday the 4.19 and did the first ride today. 

    I had a big surprise in the phone(android 9) connection status - after 15km it showed me "phone disconnected" - usual stuff, no surprise here for me. And I was thinking nothing has been changed. 

    But, after 10-20s, I saw a message "phone connected". This is the very first time the Edge830 re-connects to the phone while riding. Until now, to make the connection again I had to get my phone out of the pocket, start GC app and go to devices. 

    If this was a one time only behavior or not, have no idea. What is clear is that it did not disconnect again during the next 25km i was still riding.

  • Any news on fixing the wacky routing performed on-device? The 830 doesn't recognise known bike paths and produces huge detours where none are required.