I've had the 830 for about a month and it's mostly good but has a few annoying bugs that I've found so far. Does anyone else have an issue with the Live Track not starting automatically? This was never a problem with my 520 but the last few rides the Live Track never initiates despite ensuring that my phone is connected and I have the settings correct. Also, I had it trigger an emergency message to my wife last week using the incident detection "feature". I was unclipped and standing still. Then it ignored the fact that I cancelled it before the timer expired and sent the message anyway.
Triathlon Forum
Login required to started new threads
Login required to post replies
Re: Garmin Edge 830 issues [TH3_FRB]
[ In reply to ]
Livetrack has been an issue for almost a year now (maybe longer) with all Garmin devices. It was hit or miss on my 520 and it didn't automatically start on my 830 this past weekend. I just did it manually. The 830 did just get a firmware release to 4.10
I get the same thing with incident detection as well but that happened all of the time on my 520 as well when I come to a rather abrupt stop. It looks like there was an issue with hitting cancel and the latest firmware should fix it.... I hope.
Made visual improvements to ClimbPro, including more granular coloring on the ClimbPro chart and the ability to preview future climbs.
Made ClimbPro a separate screen in the timer loop, so the elevation screen is still available during a climb.
Fixed issues with ClimbPro that caused the climb or list screens to display improperly.
Added new ClimbPro messages to activity FIT files.
Changed the Incident Detection setting to be set for each activity profile, and defaulted the setting to OFF for Mountain and E-Mountain profiles where false positives can be more likely due to terrain and riding style.
Fixed an issue where Incident Detection could get re-enabled if the user has emergency contacts listed in Garmin Connect.
Fixed an issue where prompts could appear over the Incident Detection alert, so it could not be acknowledged by the user.
Added the ability to disable the ForkSight page that appears when you stop during a Mountain activity.
Added the ability to turn off Grit, Flow, and Jump recording in FIT files for Mountain and E-Mountain activity profiles.
Added the ability to turn off jump alerts in Mountain and E-Mountain activity profiles. Jumps will still be recorded in the FIT file but you will not be alerted during your ride.
Improved the MTB Navigation interface to utilize the new Riding Area and parking lot data available in the 2019.10 Trailforks map.
Fixed an issue where the map zoom and orientation were not properly returning to their original values after the ForkSight page was displayed in a Mountain activity.
Fixed some map drawing issues with the latest 2019.10 Trailforks maps.
Started using 7-day GPS ephemeris data instead of 3-day data, to improve positioning when new ephemeris data is not available.
Added protections against injecting bad GPS ephemeris data that could come from older versions of Garmin Express.
Fixed issues with popularity routing.
Fixed an issue that could cause the device to generate large activity files and freeze during navigation.
Fixed an issue where the battery would not charge to 100%.
Increased the minimum sharp bend warning speed to 15mph.
Fixed an issue causing erroneous FTP values.
Modified the FTP test to lap at the end instead of stopping the timer so the ride will continue to record when the test completes.
Fixed incorrect automatic gear selection for Di2 shifters.
Fixed an issue where Di2 battery empty was improperly reported as eBike battery empty.
Fixed issues with the cycling dynamics page.
Added the ability to choose between two different radar tones.
Fixed a display issue with the power zone chart.
Fixed some display issues with the lap summary data screen.
Improved the interface for editing data fields on the map screen.
Added extra layout options to the map page to support a larger elevation profile.
Made improvements to the elevation profile for segments embedded in a course.
Fixed an issue where Connect IQ data fields could only be added to the current activity profile.
Improved LiveTrack reliability and added better user feedback to convey the LiveTrack status.
Improved overall device stability.
blog
I get the same thing with incident detection as well but that happened all of the time on my 520 as well when I come to a rather abrupt stop. It looks like there was an issue with hitting cancel and the latest firmware should fix it.... I hope.
Quote:
Changes made from version 3.50 to 4.10: Made visual improvements to ClimbPro, including more granular coloring on the ClimbPro chart and the ability to preview future climbs.
Made ClimbPro a separate screen in the timer loop, so the elevation screen is still available during a climb.
Fixed issues with ClimbPro that caused the climb or list screens to display improperly.
Added new ClimbPro messages to activity FIT files.
Changed the Incident Detection setting to be set for each activity profile, and defaulted the setting to OFF for Mountain and E-Mountain profiles where false positives can be more likely due to terrain and riding style.
Fixed an issue where Incident Detection could get re-enabled if the user has emergency contacts listed in Garmin Connect.
Fixed an issue where prompts could appear over the Incident Detection alert, so it could not be acknowledged by the user.
Added the ability to disable the ForkSight page that appears when you stop during a Mountain activity.
Added the ability to turn off Grit, Flow, and Jump recording in FIT files for Mountain and E-Mountain activity profiles.
Added the ability to turn off jump alerts in Mountain and E-Mountain activity profiles. Jumps will still be recorded in the FIT file but you will not be alerted during your ride.
Improved the MTB Navigation interface to utilize the new Riding Area and parking lot data available in the 2019.10 Trailforks map.
Fixed an issue where the map zoom and orientation were not properly returning to their original values after the ForkSight page was displayed in a Mountain activity.
Fixed some map drawing issues with the latest 2019.10 Trailforks maps.
Started using 7-day GPS ephemeris data instead of 3-day data, to improve positioning when new ephemeris data is not available.
Added protections against injecting bad GPS ephemeris data that could come from older versions of Garmin Express.
Fixed issues with popularity routing.
Fixed an issue that could cause the device to generate large activity files and freeze during navigation.
Fixed an issue where the battery would not charge to 100%.
Increased the minimum sharp bend warning speed to 15mph.
Fixed an issue causing erroneous FTP values.
Modified the FTP test to lap at the end instead of stopping the timer so the ride will continue to record when the test completes.
Fixed incorrect automatic gear selection for Di2 shifters.
Fixed an issue where Di2 battery empty was improperly reported as eBike battery empty.
Fixed issues with the cycling dynamics page.
Added the ability to choose between two different radar tones.
Fixed a display issue with the power zone chart.
Fixed some display issues with the lap summary data screen.
Improved the interface for editing data fields on the map screen.
Added extra layout options to the map page to support a larger elevation profile.
Made improvements to the elevation profile for segments embedded in a course.
Fixed an issue where Connect IQ data fields could only be added to the current activity profile.
Improved LiveTrack reliability and added better user feedback to convey the LiveTrack status.
Improved overall device stability.
blog
Re: Garmin Edge 830 issues [stevej]
[ In reply to ]
Thanks for the confirmation. I actually had a 510 previously, not 520, and never had a problem with Live Track. I can obviously start it manually as a work around but sure would be nice if the feature worked the way it is supposed to.
TH3_FRB wrote:
Thanks for the confirmation. I actually had a 510 previously, not 520, and never had a problem with Live Track. I can obviously start it manually as a work around but sure would be nice if the feature worked the way it is supposed to.Fully agree. But it is what it is.
Have you read this?
https://www.dcrainmaker.com/...are-instability.html
blog