Related
Options

25.11 does not fix the navigation crashes! When is this problem finally addressed???

7606241


Just installed the new update on my Fenix 7 Pro, went to walking, navigation and then first clicked "Around me", went back because I did not find what I wanted, clicked favorites and picked a restaurant about 3.3 kilometers away.

I get the usual "Not enough memory" error, which is funny, because the watch was freshly restarted after the update.

Afterwards I got an immediate crash and reboot.

My hopes were not that high that anything changed as I haven't seen anything in the changelog.

Navigation with route calculation is totally unusable at the current state, so when will this be fixed?!

 

https://www.reddit.com/r/GarminFenix/comments/1my3ura/not_enough_memory_available/

https://www.reddit.com/r/GarminFenix/comments/1ktdojf/what_causes_this_not_enough_memory_error/ 

https://www.reddit.com/r/GarminFenix/comments/1i9pc1j/garmin_fenix_no_memory_to_recalculate/

Seems even Edge devices are affected, luckily I did not buy one yet! 

https://www.reddit.com/r/GarminEdge/comments/1hj6f0e/not_enough_memory_to_reroute/

  

  

  

  

  

  

  • 0

    I think I have fixed it by coincidence.

    What I did (and some steps are random, possibly not in exact order):

    1. Connected Fenix 7 to PC and deleted all maps except Europe Central

    2. Went into"Walking" and tried navigation, same issue again

    3. Disabled "Worldwide Basemap DEM NR" an rebooted

    4. Disabled "TopoActive Europe"

    5. Enabled both again

    6. Another manual reboot

    Now the navigation works again and I had no crash anymore so far! and not "not enough memory" error.

    I've even managed to re-enable all layers again which I had turned off in the hope to save memory, and set the map resolution/quality from low to standard again.

    It even works for a 15km route, while it failed before even for routes with a few hundret meters!

    So this must have been some kind of bug, not sure by what it was caused.

    In case any of you is interested in a memory dump file (RAM.txt) which I exported after the last occurance of this issue, feel free to contact me

  • 0

    Today, the out of memory issue appeared again. I've disabled the topoactive map in isolation and tried again, with no effect. It even caused a reboot again.

    After the reboot, starting the navigation worked but it drew a straight line without topoactive maps.

    Then I've activated TopoActive Europe again (no reboot afterwards) and started the navigation with success!

    So I guess the short version of my hotfix would be:

    1. Disable TopoActive Europe

    2. Reboot

    3. Enablel TopoActive Europe

    Yesterday after I've managed to get it working I did one Treatmill workout in the evening and one normal gym workout, nothing more. So I've started both training programs just right now and tested the navigation afterwards, just to make sure it is not related. It isn't.

  • Former Member
    0 Former Member in reply to 7606241

    I had the same issue shortly after I asked the watch to "route back to start". It crashed shortly after the route was calculated (route back was around 10km on some fairly complex trails)

  • 0 in reply to Former Member

    just recently? What happens if you start it right now, would it work?

    The thing is, I have that no matter how long or short the distance. it could be even a few meters down the road and it crashes or at best shows it has no memory. It could even be just searching for POI's around me to make the watch crash

  • Former Member
    0 Former Member in reply to 7606241

    No I can definitely search for and navigate to POIs just fine. I am however using the Australian maps which probably has a smaller set of POIs than you may be using.

  • 0 in reply to Former Member

    Might be a reason, but I'm at the end of a smaller city, so one side is forest/mountain, the other is city. But I'd assume if you navigate to a point, it does only load relevant chunks of the map, not the entire map. So if I navigate 200m down the road, I'd assume everything beyond that and next to it is out of the loading scope.

    I guess this is a stupid bug. Maybe totally unrelated to the routing itself. I mean switching off the map and on again fixes it for a while, even for much longer routes

  • 0

    Ever since the newest update I can't use navigation features on the fenix 7. It always says "Route calculation error. not enough memory available". I still have enough memory on the watch and it's ever since the update.

    So far I've tried to reinstall the maps which is Central Europe, anyone else with this problem?

  • 0 in reply to 5607421

    Yes. I'm having this issue. Factory reset helped but did t solve the issue completely. It will now do 1 or 2 route calculations, then crash or error out.

  • 0 in reply to 5607421

    Yes indeed, but found a workaround and have not faced it anymore for weeks now.  

     25.11 does not fix the navigation crashes! When is this problem finally addressed??? 

    But I have other navigation issues now.

     Walking in opposing direction causing "Route calculation error. Missing routable roads in this area" 

    I face the same error occasionally when starting an activity. Only works again after restarting the watch.

    And sometimes the route calculation finishes immediately and just draws a straight line through the air to the target, ignoring all streets.

    Are you using topo active Europe?

  • 0

    Solved my main navigation problems using an alternative map from here:

    https://alternativaslibres.org/en/downloads.php

    Download OSM Base Map and Contour.

    TopoActive needs to be disabled. 

    Worldwide DEM Basemap, NR should stay active

    Reboot might be required after disabling TopoActive

    Route calculation is a lot faster (20s for a 15km route)! Recalculation works when you leave the route, and it took only 1-2 seconds!

    So the conclusion is, something is really messed up with the TopoActive (Europe Central at least) which makes it unusable for the Fenix 7 Pro.