Page 1 of 1
Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sat Sep 20, 2025 9:58 am
by bonstetten
I can reproduce following freeze on the device which I can only solve by pressing the power button for a longer time.
Stays freezed even the display goes into screen save-mode and awakes again. In one case the device then restarted without pressing the power button just after touching the sleeping display.
How to cause the issue:
- Load a GGZ-File with 36'000 Geocaches
- Select Geocaching -> Menu top right ("Hamburger-Icon") -> Search -> Select one Geocache from the list -> FREEZE
- After removing (deleting) the file using "Android file transfer" on the Mac, the GGZ directory is empty, but the caches are still there after a restart of the device --> I had to delete the "Geocaching live data", even this are not live data and it also unregistered my device as there is an other already known issue
The same ggz file works on the Oregon or GPSMAP 66st
As a geocacher with this issue the GPSMAP H1 is currently almost unusable.
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sat Sep 20, 2025 11:50 am
by JungleJim
Loading 36000 caches seems like quite a lot to me (but I don’t do geocaching…). Does the issue also occur if you load a smaller file?
And of course, in case you haven’t done so yet, report the issue to Garmin support.
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sat Sep 20, 2025 1:58 pm
by GPSrChive
What is the firmware version on your device?
We are unable to duplicate the crash using our own GGZ files. However, your crash has been added to the Common Issues page. Out of curiosity, what program was used to create your GGZ?
We are also unable to duplicate your 'Geocaches still present after deleting GGZ files' issue. This type of complaint has been a very common MAC related issue in the past, and we suspect your issue may also be related to how MAC computers do not always delete items, instead 'hiding them from the user'.
Please verify all geocache data has been removed from the device and/or microSD cards (check all directories for hidden files), and retest again.
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sat Sep 20, 2025 3:22 pm
by bonstetten
I use icaching to generate the file and 'android file transfer'' to connect to the gps and I can't see invisible files there. As the mac does not recognize the GPS it also does not can create files there.
Just to repeat: The same file works on the 66st and other devices, but they can be recognized as USB drives by the Mac.
I can provide you the file for test purposes. Just contact me.
I'm aware of the effect with the invisible mac files. I informed other users long long time ago in my GPS related podcast and blog.
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sat Sep 20, 2025 3:41 pm
by GPSrChive
We would like to test your GGZ files.
Please send to:
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sat Sep 20, 2025 6:01 pm
by javawa
GPSrChive wrote: Sat Sep 20, 2025 1:58 pm
This type of complaint has been a very common MAC related issue in the past, and we suspect your issue may also be related to how MAC computers do not always delete items, instead 'hiding them from the user'.
"MAC" as in "
Media Access Control" or "Mac" as in a computer made by Apple? A Mac keeps the trashed files on every attached device, emptying the trash will remove them. They are not hidden from the user, the files are clearly visible in the trash folder. However, this doesn't apply to devices using MTP (as does the GPSMAP H1). Files are immediately deleted.
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Sun Sep 21, 2025 6:11 pm
by GPSrChive
bonstetten wrote: Sat Sep 20, 2025 9:58 am
I can reproduce following freeze on the device which I can only solve by pressing the power button for a longer time.
Stays freezed even the display goes into screen save-mode and awakes again. In one case the device then restarted without pressing the power button just after touching the sleeping display.
How to cause the issue:
- Load a GGZ-File with 36'000 Geocaches
- Select Geocaching -> Menu top right ("Hamburger-Icon") -> Search -> Select one Geocache from the list -> FREEZE
- After removing (deleting) the file using "Android file transfer" on the Mac, the GGZ directory is empty, but the caches are still there after a restart of the device --> I had to delete the "Geocaching live data", even this are not live data and it also unregistered my device as there is an other already known issue
The same ggz file works on the Oregon or GPSMAP 66st
As a geocacher with this issue the GPSMAP H1 is currently almost unusable.
Thank you for sharing your GGZ file for us to test!
Good news (maybe), your GGZ file loads OK on our H1i Plus, and we are able to view and navigate to geocaches contained within the GGZ file, all without issue.
Caveats: We are not near their location, so we had to choose 'Search Near > Use Map > Your Location' to test. We also are using all English settings on our device.
Perhaps you can retest with all language settings in English to see if this helps anything?
Re: Device freezes/restarts when selecting a Geocache loaded with GGZ-file [Crash 2]
Posted: Mon Sep 22, 2025 9:57 am
by bonstetten
Thank you GPSrChive investing time in this issue. It still exist, but I can deliver more information as a did what you recommended:
First:
- GPX-file with the same data (Geocaches) works.
- My device is since I set it up on english as language
If I select the geocache as you did over the
Find-option it works. Eve i seacht using 'Use Map' or 'Geocache'
It still freezes/crashes when I select the cache using the
Geocaching-App
Geocaching-App --> select one of the caches (loaded by the GGZ-file) --> Freeze
(pressing [Quit] does not work. I need to press the power button for longer time to restart the device)
Addition:
- It looks like this happens only when I select my own caches (theese are close to my current "test position")
- Video to demonstarte what happens availabe on request