Very long startup-time [Bug 41]
- GPSrChive
- Site Admin
- Posts: 3925
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Very long startup-time [Bug 41]
Interesting results....
-
- Posts: 26
- Joined: Sat Sep 05, 2020 1:08 pm
Re: Very long startup-time [Bug 41]
I experience exactly the same effect. I tried analysing the correlation between the number of progress bars and the numbers of Geocaches/Tracks/Routes but I have no clue at all.
Garmin GPSMAP 65S | Garmin GPSMAP 66SR | Garmin GPSMAP 66ST | Garmin Extrex 30
-
- Posts: 29
- Joined: Mon Oct 05, 2020 12:47 pm
Re: Very long startup-time [Bug 41]
In a previous post, I wrote:
I think I can confirm the behaviour. Since my last post some weeks ago, I notice that the number of progress bar cycles increases for each update. When I updated today, It took 1 hour and 10 minutes before the map showed up. This is frustrating, and I hope this is fixed in a new firmware release shortly.
- GPSrChive
- Site Admin
- Posts: 3925
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Very long startup-time [Bug 41]
For clarity, when you say 'each time I update', are you are referring to
A) adding + removing GPX/GGZ files, or
B) replacing existing GPX/GGZ files, or
C) adding + removing + replacing GPX/GGZ files?
And which firmware version?
A) adding + removing GPX/GGZ files, or
B) replacing existing GPX/GGZ files, or
C) adding + removing + replacing GPX/GGZ files?
And which firmware version?
-
- Posts: 29
- Joined: Mon Oct 05, 2020 12:47 pm
Re: Very long startup-time [Bug 41]
B) Replacing existing GPX/GGZ and POI files using the GarminExport macro in GSAK.
FW 6.40
-
- Posts: 29
- Joined: Mon Oct 05, 2020 12:47 pm
Re: Very long startup-time [Bug 41]
After upgrading to FW 7.10, I can see that there is no change with regards to the very long startup-time
-
- Posts: 29
- Joined: Mon Oct 05, 2020 12:47 pm
Re: Very long startup-time [Bug 41]
After hours and hours of testing with different combinations of GGZ, GPX and POI files and file sizes, I find that the very long startup-time is related to child waypoints. When child waypoints are included in the Geocache GPX files or as a separate GPX file in addition to Geocaches in a GGZ file, the number of progress bar cycles is high, thus the startup-time is very long.
With Geocaches only in a GGZ or GPX file and child waypoints as POIs, no matter of file size, the GPS starts up as expected with only one progress bar cycle.
With Geocaches only in a GGZ or GPX file and child waypoints as POIs, no matter of file size, the GPS starts up as expected with only one progress bar cycle.
- GPSrChive
- Site Admin
- Posts: 3925
- Joined: Fri Jan 20, 2017 11:29 pm
Re: Very long startup-time [Bug 41]
Thank you Catch, we have an inquiry in at Garmin and are awaiting a response.
-
- Posts: 29
- Joined: Mon Oct 05, 2020 12:47 pm
Re: Very long startup-time [Bug 41]
One more test: When adding the child waypoint GPX file separately, the GPS do also start up with only one progress bar cycle.Catch wrote: ↑Fri Dec 04, 2020 7:02 pm After hours and hours of testing with different combinations of GGZ, GPX and POI files and file sizes, I find that the very long startup-time is related to child waypoints. When child waypoints are included in the Geocache GPX files or as a separate GPX file in addition to Geocaches in a GGZ file, the number of progress bar cycles is high, thus the startup-time is very long.
With Geocaches only in a GGZ or GPX file and child waypoints as POIs, no matter of file size, the GPS starts up as expected with only one progress bar cycle.
- GPSrChive
- Site Admin
- Posts: 3925
- Joined: Fri Jan 20, 2017 11:29 pm