Garmin Fenix 7 crashes when starting Track from Locus
Solved
Hi!
Since last weekend my Garmin Fenix 7 crashes, when I try to start a Locus track (could be new related to the new route planner)
Track download works as expected. Starting the navigation results in an immediate reboot of the watch
Samsung Galaxy Z Flip 5
Locus Version 4.2.2
Garmin Fenix 7, OS Version 16.22
Hello,
i have the same problem. After exporting the newly created route from the new version of the planner in LocusMap 4.22.2 to the FIT file format, and then importing it to the Garmin Epix Gen 2 watch, the watch restarts after starting the track. When trying again, the watch won't even boot, a hard factory reset is required. Tracks (FIT files) created before the planner update work without a problem.
Samsung Galaxy S22 Ultra
Samsung Galaxy Tab S9 Ultra X910 16 GB 1TB WIFI
Garmin Epix Gen 2, OS ver. 16.22
Hello,
i have the same problem. After exporting the newly created route from the new version of the planner in LocusMap 4.22.2 to the FIT file format, and then importing it to the Garmin Epix Gen 2 watch, the watch restarts after starting the track. When trying again, the watch won't even boot, a hard factory reset is required. Tracks (FIT files) created before the planner update work without a problem.
Samsung Galaxy S22 Ultra
Samsung Galaxy Tab S9 Ultra X910 16 GB 1TB WIFI
Garmin Epix Gen 2, OS ver. 16.22
Hi, that is quite nasty.. analysing.
Hi, that is quite nasty.. analysing.
Seems like Garmin crashes when loading track generated via in-app planner and the problem isn't necessary related with version 4.22 (new planner UX). Tested on Epix 16.22 - no factory reset needed after crash.
In-app gps-recorded tracks or track planned via web planner (https://web.locusmap.app) and exported via mobile app works fine.
That is what we know so far and continue in analysis of the issue.
Seems like Garmin crashes when loading track generated via in-app planner and the problem isn't necessary related with version 4.22 (new planner UX). Tested on Epix 16.22 - no factory reset needed after crash.
In-app gps-recorded tracks or track planned via web planner (https://web.locusmap.app) and exported via mobile app works fine.
That is what we know so far and continue in analysis of the issue.
Hi, we located the problem and resolved it in internal build. We expect to release it during next 2 weeks.
In the meantime workaround is to switch in-app planner to use Grapphoper for routing (or plan courses on web).
Hi, we located the problem and resolved it in internal build. We expect to release it during next 2 weeks.
In the meantime workaround is to switch in-app planner to use Grapphoper for routing (or plan courses on web).
Hello, great news. Thank you for the information and the initiative in solving the problem.
Hello, great news. Thank you for the information and the initiative in solving the problem.
Small update: For those who don't want to wait for next release, you can download our BETA APK installation file and test the fix in advance: http://bit.ly/lmVersionsTest
BETA builds are not stable versions and might contain also some other minor issues.
Small update: For those who don't want to wait for next release, you can download our BETA APK installation file and test the fix in advance: http://bit.ly/lmVersionsTest
BETA builds are not stable versions and might contain also some other minor issues.
Problem was resolved in the app version 4.23.
Problem was resolved in the app version 4.23.
Replies have been locked on this page!