FW 4.8 same ggz issue as in FW 4.7

Discussion related to the Garmin GPSMAP 66s/st GPSr
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

Had the exact same problem as in FW 4.7 in FW 4.8. The device bricked up on start up just like described here:

https://www.gpsrchive.com/Discussion/vi ... f=36&t=814

I think it is a problem with the new proximity alert feature. Without it turned on, the device boots up just fine multible times after ggz is copied to device. Once the proximity alert is turned on, it freezes on next boot. Could reproduce this twice and remembered, that I actualy could boot the device once after loading the ggz with FW 4.7, at which point I activated the proximity alert. Bricked up on next boot. Can anyone confirm?

Cheers,
UglyTim
User avatar
gpsrchive
Site Admin
Posts: 1378
Joined: Fri Jan 20, 2017 11:29 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by gpsrchive »

Please describe in more detail what 'Bricked Up' actually looked like:

• Was the boot screen visible?
• Was the progress bar visible?
• What text was displayed?
• Was the backlight illuminated?
• If not illuminated, does briefly pressing the power button activate the backlight?
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

As described in the FW 4.7 post, it is the screen where the Garmin logo is displayed with the copyright info below (and your personel startup text, if you have one, above), so before the 'loading tracks' and so on status bar is displayed. For the illumination I just had to brick it again, since I usually have illumination switched off. Worked perfectly, as soon as I switched on proximity alerts for geocaches, the device would not boot (Worked perfectly for multible reboots before). Illumination stays on, no reaction. Forced mass storage mode with deleting .ggz file and sql folder gets it to boot again. Putting the .ggz on the device again lets you boot it up as often as you want, as long as you do not activate proximity alerts again. As soon as you activate proximity alerts again, the device freezes on next boot (before you reboot, proximity alerts actually work). It is a rather big .ggz file with almost 9000 geocaches, created using GSAK.

BTW: I did a hard reset after FW update to 4.8.
Last edited by UglyTim on Sat Oct 03, 2020 6:55 pm, edited 2 times in total.
User avatar
gpsrchive
Site Admin
Posts: 1378
Joined: Fri Jan 20, 2017 11:29 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by gpsrchive »

Thank you!

Your description sounds like the device was completely frozen, and not indexing data.

This information has been forwarded to Garmin software engineers!
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

Just did another test with a .ggz only containing 30 geocaches with proximity alerts on. The device booted, but it took a little bit longer than booting with a newly copied .ggz with 8000 geocaches without proximity alerts on. .ggz also generated with GSAK.
User avatar
gpsrchive
Site Admin
Posts: 1378
Joined: Fri Jan 20, 2017 11:29 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by gpsrchive »

What about a GPX with 100 or 4000 caches? Is it only GGZ?
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

Was hoping to get some experiences from other users here to get input on exectly that, since it is actually really time consuming to do those tests... Well, hang on, I will look into it.
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

Ok, with 1000 geocaches the device hangs for over 20 minutes now. When I first encountered the problem with FW 4.7, nothing happened for over 1,5h on the trail with the 8000 caches file. Going to take out the batteries now and reset it deleting the ggz and sql and try with 200 again.
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

200 worked fine, tried 500 next, worked fine as well. With 800, booting took significantly longer (about 3 minutes, compared to less than half a minute for 500). The screen was only a couple of seconds on the copyright, the loading bar was fast as well. Most of the loading time was displaying 'loading maps'.
UglyTim
Posts: 9
Joined: Fri Sep 18, 2020 7:36 pm

Re: FW 4.8 same ggz issue as in FW 4.7

Post by UglyTim »

1000 as .gpx hangs an copyright screen as well. What I noticed with all the last tests was, that when hanging on the copyright screen the 'could not find sat.' message was displayed after some time (did the tests on my desk, while before I mostly was on the balcony or near a window).
Last edited by UglyTim on Sat Oct 03, 2020 9:56 pm, edited 1 time in total.
Post Reply

Return to “GPSMAP 66s/st”