Firmware 13.13: 6 crashes during a 35km ride...

When I got the offer to update my Edge 1050 to firmware 13.13 I made the mistake to update Disappointed

During a 35km ride this evening I had 8 freezes: after about 5 km, 10 km,  20 km, 30km, 34 km, 34.2 km, when saving at 34.5 km and a minute later when I wanted to switch it off.

The device is with this firmware completly unuseable. The freeze happend on all screens and in all modes. Never had that before.

  • there's a way to force downgrade. Problem is you have to have firmware package for specific version. When I've tried to share v11.24 update file and description how to flash it my post got immediately deleted by moderators. I'm not risking my Garmin account getting banned by posting that again.

  • We have released SW 13.14 to a 100% public release. The announcement can be found here

    To download this immediately, please ensure you have a wi-fi network added to your Edge, then navigate to the Main Menu > System > About > Check for Updates. 

    We sincerely appreciate everyone's patience as we worked toward this fix. We understand the inconvenience this has caused, and understand the frustration expressed by many who felt there was a lack of communication.

    We investigated this to find the root cause as soon as we could, and wanted to ensure the fix worked as intended over the weekend in the beta release. (there were site errors that kept the beta community Closed for feedback)

  • Thx for that. Just installed and looks good. I will test tomorrow on my next ride. Could you please let us know about the details of the root cause. 

  • On the release page it is now called 27.13 to 27.14. Is that correct?

    Isn't it 13.13 to 13.14?

  • You are absolutely right, and this has been corrected. Thank you. 

  • First of all - THANK YOU. It works as expected again White check mark  No more freezes however I (probably other Users affected) have some final questions. I‘d appreciate if you could comment on that. That would also be a strong signal to stengthen confidence in garmin products in future and would be the least of gratitude for all those guys who helped to debug this error.

    What was the problem?How do you assure this does not happen again?

    THX