Zumo User Forums

jfheath wrote: Sat Aug 16, 2025 2:41 pm @FelixHauser - do you have Tread installed on you phone to synchroise with the XT2 ?

Allanashley wrote: Sun Aug 17, 2025 12:55 pm The thing is, does the Zumo reboot because of memory issues, or is this a hardware issue.
If it’s the latter, then is there any hope other than replacement?
I keep the files in memory to a minimum but the unit still reboots, 20 times in a 2 hour ride, even when not following a route.
Can’t believe that there isn’t someone at Garmin who knows all about this issue and the reasons for it.
They are sending me a replacement next week so will let you all know what happens.
If it reboots again I will be selling it and getting a Chigee.

Thank you very much for your inquiry.

There is no specific information, such as a maximum length for tracks.
This always has to be considered individually from GPX to GPX.
In most cases, the issue lies with a particular GPX file.

We generally recommend keeping the devices “clean” and only transferring the necessary tracks.
We usually cannot make concrete statements about individual sample routes—among other reasons, because we do not run tests with third-party planning software.
Based on experience, using tracks on the zumo usually provides the best results. The reason is that the calculation or conversion of the route takes place directly on the device. The procedure is as follows:
Export the planned route as a track (.gpx) → import it into the Tread app → synchronize with the zumo XT2 → calculation/conversion of the track into a route on the device.

Each new route or track may behave differently. We therefore definitely recommend checking the route on the device after calculation to ensure it matches your requirements and expectations. Adjustments afterward may also be necessary.

FelixHauser wrote: Tue Aug 19, 2025 4:55 pm

Thank you very much for your inquiry.

There is no specific information, such as a maximum length for tracks.
This always has to be considered individually from GPX to GPX.
In most cases, the issue lies with a particular GPX file.

lkraus wrote: Tue Aug 19, 2025 7:09 pm I would have to object to this response as being unresponsive to the issues you are having.

Dear Garmin Support Team,

Unfortunately, your response was of absolutely no help to me. The suggestion to keep the device “clean” is particularly amusing, since I already mentioned in my original request that I only keep the necessary files on the device.

In addition, you did not address whether Garmin is even aware of this problem and whether any steps are being taken to resolve it. Just to be clear: I am very well aware that I am not the only one experiencing this issue. For example, here:

viewtopic.php?t=2315
and also here:
https://www.advrider.com/f/threads/garm ... s.1643705/

I was especially surprised by your statement (I quote): “we do not perform tests with third-party planning software.”
Allow me to follow up here: Why did Garmin even implement the function to import GPX files in the first place? If you neither test how GPX files from third parties behave, nor clarify what limitations exist regarding storage or route length, then what exactly is the purpose of importing them? And from which source?

At this point, I would really appreciate some more clarity—or at least that my ticket be forwarded to one of your software developers. I am more than willing to provide the GPX files that cause my device to crash.

I must also say that I am rather disappointed. I already spent more than €600 on a BMW Navigator 6, which became unusable after two years due to display ghosting—and now I am facing similar problems with the Zumo XT2.

I look forward to your reply.