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

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

KUKUK
2 months ago

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.

  • 0 2 months ago in reply to 1454717

    What I found out: most people use the "--gmapsupp" flag with mkgmap to build the gmapsupp.img for the device. But opentopomap is using the img for BaseCamp for the device. I have no idea what the differences in the format are, but the opentopomap cannot be loaded e.g. in QMapShack, it just crashes.

  • 0 2 months ago

    I updated my firmware last night before a big ride. That was a mistake. I had 7 freezes during my ride today where I had to fully restart my device by holding the power button for a long time.

    I don't have any custom maps on my device. I did have to run with battery saver on because the battery was unexpectedly fully drained during the night after starting the update. I read in another post that running with battery saver enabled also might be a cause for all the freezes.

    After each stop of a few minutes I had a freeze. But also while riding the device would freeze up completely.

    I didn't have any issues with the previous firmware and would like to downgrade.

  • 0 2 months ago

    Yep, mine froze tonight, very frustrating for a now mature product. It needs an urgent update

  • 0 2 months ago in reply to cream17

    Since their initial response early in the thread, Garmin have been completely slient on this marvellous cockup of theirs. Multiple users, for example, have asked how to revert to the previous FW so they can continue using their maps, but nothing but silence...

  • 0 2 months ago in reply to AuldNik

    Emailed garmin support.
    They replied, that they are working on a software solution and that disabling popularity routing would solve the problem for now.
    I don't think this can be correct, because I've never had that option enabled.

  • 0 2 months ago in reply to NicoKossen

    Neither did I. But I had a small OSM "test" map without DEM data on it when it crashed.

    ( it is weird that the community has to do the debugging for closed-source software )

  • 0 2 months ago in reply to NicoKossen

    I always disable popularity routing at first, so this will clearly not help. All my crashes was with all of this options disabled.
    Only Climb Pro was enabled, but since the custom OSM maps don't contain any data for it, maybe they mean that?

  • 0 2 months ago in reply to NicoKossen

    I also have ClimbPro and popularity routing disabled and I'm getting plenty of crashes regardless. The only thing that helps is to delete all non-Garmin maps.

  • 0 2 months ago in reply to 1454717

    I don't have any custom maps installed and had many freezes during a long ride yesterday so it appears the freezes are not just limited to having custom maps installed.

    I was following a GPX track and had freezes after each stop and also during riding. I also had battery saver enabled.

  • 0 2 months ago in reply to woutlepelaar

    I'm the same. I am not using any custom maps. Just stock.