Related
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

Upgraded to V 12, route calculation stops at 39% and crashes device

pertti_s
over 3 years ago

Updated 1030 to v12, and after that I am not able to "ride" any routes.

I have enabled only standard garmin map, also tested with custom OSM map.

Routes were created either RWGPS (IQ app for sync) or Strava.

Every route will fail at 39% calculation and also crashes whole 1030 so it needs be started again.

  • 0 over 3 years ago in reply to hotdogpartysausage

    I had Turned both those popularity options off and might helped to solve crashes with Garmin own maps, but had no effect with 3rd party maps in my case. 

  • 0 over 3 years ago

    I have the same problem, after 39% calculating a route created in Komoot, my device crashes. Disabeling the new feature “Trendline Popularity routing”, same problem. I use OpenMTBmaps. When I disable the “omtb_europe_03_07_2020_NU_Local” map, calculation went 100% with no problem. I will try to reinstall a new recent omtb map. Hope that will fix the issue. I was wondering should I leave all those Garmin maps active when using omtb? Could they conflict?

    Edit 13/7/2021: After disabling all the Garmin maps, leaving only the OpenMTBmaps enabled, Routing calculation worked very fast, without any crashes during calculation anymore. It seems that some different enabled maps are causing these issues.  Need to experiment some more and I will put results here as soon as I have more info on this.

  • 0 over 3 years ago

    I had the same though disabling OSM maps seems to solve the problem, but I like OSM

  • 0 over 3 years ago

    It seems to me the issue is an error in memory management by one of the processes introduced in firmware 11.19 and newer.

    Using a fresh new profile, disabling CIQ or other random changes on the device may in appearance fix the issue (at least temporarily) for a specific route at a specific time, but one should certainly not rely on this before a race or as a "workaround".

    The only way to ensure the issue is not triggered is to revert back to firmware 11.10. Fortunately, it is still available at:
    https://forums.garmin.com/sports-fitness/cycling/f/edge-1030/253669/new-edge-1030-and-edge-1030-bontrager-version-11-10-now-available

    Garmin is apparently aware of the issue. It is really appalling there is no better communication from Garmin about this.

  • 0 over 3 years ago in reply to romain.w
    romain.w said:
    disabling CIQ or other random changes on the device may in appearance fix the issue

    This is quite a in depth description of how to reproduce or avoid the original error.

    romain.w said:
    It seems to me the issue is an error in memory management by one of the processes introduced in firmware 11.19 and newer.

    And with that really focused and great analysis this is the only viable source of error.

    romain.w said:
    Garmin is apparently aware of the issue. It is really appalling there is no better communication from Garmin about this.

    I think they are aware of the issue, but there are quite more factors to be taken into account than your error analysis did.
    I don't even understand how one can suggest this as an answer to the OP.

  • 0 over 3 years ago in reply to bw

    Wow. That is a lot of sarcasm.
    I focused on the solution because I’m about to race. You need a memory debugger to diagnose the issue at hand. My point is that the suggested fixes above may work under some circumstances but are not actually systematically working around the problem. People should not rely on them. 

  • 0 over 3 years ago in reply to romain.w

    Sorry if it seems sarcastic. My day to day job is actually about designing, developing and maintaining large complex software systems. So please forgive me if I am a little pedantic about descriptions that are "doing some random stuff that may or may not have influence" to a problem.

    Also from time to time I dislike Garmin's way of communication, but this is mainly a user to user forum with some Garmin mods in here. Official bug reporting and also beta testing communication is via Email.

    This error has quite some input variables, what area you are routing in, what source maps you are using, other route weightings (popularity based routing). I do not have insight to the implementation, but if there was a problem with memory management the symptoms would be - at least in my experience - much more undifferentiated.

    [edit] for example using official Garmin maps in Germany, I am not able to trigger this bug [/edit]

    As for your search for a stable Edge for your race: on the other thread I offered you stables and betas as backups starting from 11.10...

    In the end, sorry if I sounded that harsh