Page 2 of 3

Re: Very long startup-time [Bug 41]

Posted: Wed Nov 04, 2020 8:24 pm
by GPSrChive
Interesting results....

Re: Very long startup-time [Bug 41]

Posted: Thu Nov 05, 2020 7:23 am
by rgschmidt
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.

Re: Very long startup-time [Bug 41]

Posted: Fri Nov 27, 2020 4:16 pm
by Catch
In a previous post, I wrote:
Catch wrote: Tue Nov 03, 2020 2:26 pm I have a feeling that the number of cycles increases each time I am updating the GGZ/GPX files.
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.

Re: Very long startup-time [Bug 41]

Posted: Fri Nov 27, 2020 5:08 pm
by GPSrChive
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?

Re: Very long startup-time [Bug 41]

Posted: Fri Nov 27, 2020 5:15 pm
by Catch
gpsrchive wrote: Fri Nov 27, 2020 5:08 pm 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?
B) Replacing existing GPX/GGZ and POI files using the GarminExport macro in GSAK.
FW 6.40

Re: Very long startup-time [Bug 41]

Posted: Tue Dec 01, 2020 6:18 pm
by Catch
After upgrading to FW 7.10, I can see that there is no change with regards to the very long startup-time :(

Re: Very long startup-time [Bug 41]

Posted: Fri Dec 04, 2020 7:02 pm
by Catch
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.

Re: Very long startup-time [Bug 41]

Posted: Fri Dec 04, 2020 10:35 pm
by GPSrChive
Thank you Catch, we have an inquiry in at Garmin and are awaiting a response.

Re: Very long startup-time [Bug 41]

Posted: Sat Dec 12, 2020 6:44 am
by Catch
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.
One more test: When adding the child waypoint GPX file separately, the GPS do also start up with only one progress bar cycle.

Re: Very long startup-time [Bug 41]

Posted: Sat Dec 12, 2020 1:01 pm
by GPSrChive
Catch wrote: Sat Dec 12, 2020 6:44 amOne more test: When adding the child waypoint GPX file separately, the GPS do also start up with only one progress bar cycle.
For clarification, are you referring to adding the 'additional_waypoints.gpx' file?