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 1030 Strava Segment list corruption bug

I run Strava Segments on my Edge 1030 on Firmware 12.20 and the segment list gets corrupted over time.  I am running the same segments on my Edge 820 without any issues.

Once a segment is first synchronised, it displays correctly in the list.

When the list is opened again, the title of some of the segments can change and then the segment is corrupted. 

This seems to happen after my garmin has synchronised with my phone. It also sometimes happens after the garmin is turned on.

Corrupted segments have their title replaced with a single letter instead of the full segment title.  They also have what seems to be a random mix of the original segment details e.g. the length and elevation but a map and leader board from another segment in my list.

This corrupted segments sometimes get fixed after I have synchronised with my phone app but this is not always the case.

The corrupted segments also sometimes get fixed if you delete them on the garmin and synchronise again or unstar and star the segment again in Strava.

This bug is not totally random as the same segments in the list are likely to get corrupted multiple times.

www.strava.com/.../6697054 is one of my stared segment that keeps getting corrupted

Has anyone else noticed this bug?

  • Same here, corrupted files with a single letter name, and once they get corrupted I am unable to get them back. I remove them from the device but when it synchronizes again the corrupt segment comes back.

  • Even more, there seems to be a problem recently that the device hangs up during the boot phase when "loading courses, workouts, and locations". The only fix I found up to now is to delete all segments via USB using storage mode (and not allowing it to sync new segments next time it switches on.) - syncing a new segment immediately makes it break again.

    I wonder if this is related, i.e., this happens when segments corrupt that much that they won't even load anymore during booting?