XT2 turns off and restarts

[lkraus]

where do you get all that code from?

This PC\zūmo XT\Internal Storage\Garmin\GarminDevice.xml, near the end.

[proofresistant]

Hello @FelixHauser,
First of all, I find your experiences very interesting.

I also gather that the restarts occur during the routing of a track.
I would assume that this does not overload the XT2 and that calculations or system limits are therefore not the cause of the crashes

Nevertheless, I would ask which maps were active during this time
- CityNavigator?
- TopoActive?
- Adventure & Roads & Trails?
- Digital Elevation Map (DEM)?
- other OSM maps?
Here, I would try to limit the maps to the minimum you need, but as mentioned, I don't really suspect that this is the cause


Regarding:

I was especially surprised by your statement (I quote): “we do not perform tests with third-party planning software.”

and

Meanwhile, I just got off the phone with the gentleman from Garmin.
He was really polite and nice, but the conversation was just a vicious circle. Me telling him that it cannot be that the Zumo cannot handle 3rd party gpx data and he telling me they cannot proofcheck everything.

Yes, this is a serious problem.
The Garmin support team may has a problem of its own it seems that their hands are tied by Garmin headquarter. What I think basically is, officially, no other route programs are supported by Garmin, not even BaseCamp.
“Presumably,” only their own new modern planning tools (Tread App, Explore, etc.) are supported.
However, the fact that GPX can also be imported and that GPX can also come from other sources somehow doesn't fit in with Garmin's strategy.



So, enough of the generalities,
I would like to refer you to the following post from @turbo19 and ask you to consider it.

... I was going crazy because the same thing you're describing was happening to me: it rebooted every few minutes and was unbearable. I managed to fix it by disabling Bluetooth on the XT2 in the phone's connection menu.
You can sync whatever you want by turning on Bluetooth, and after syncing, turn it off again.
This way, no problems on several long routes completed this month.

Garmin is already aware of the problem, and will surely update the XT2 software soon (it's taking too long). As @multirider says, the synchronization system is very poor, slow, and bad.

As I wrote above also, I don't think the XT2 is causing problems because of track routing.
I would also suspect that it is the Tread app synchronization, what causes the problems
Try disabling Bluetooth, at least during navigation, as a test. (Turn off/deactivate the Bluetooth connection.)


Larger files could also be a reason here.
The Tread app and zumo XT2 don't just exchange data, they probably also perform calculations in the background.
It has been observed and criticized that shaping points are shifted (sometimes significantly) and, as an example, this negative behavior is probably not caused by pure data exchange.

Please let us know what further experiences you have.

[jfheath]

That is an interesting thought (disabling BT) and would immediately eliminate the possibility of phone/XT2 incompatibility. Although disabling BT doesn't necessarily stop it from trying to communicate and then being prevented.

If you find that works, then the next step is to re-introduce BT but make sure that Tread and XT2 cannot use BT to synchronise. The process happens about once per minute - just checking to see if anything new needs to be sent somewhere else. And the synch with the Tread app is know to create other routing issues. That's how I run mine - BT link, but no synch allowed. Without being allowed to synch, it doesn't even try - which gets rid of a whole lot of little issues.

To do that, you need to reste the XT2 to factory condition. And deleted the Tread App from your phone. Then re-pair phone and XT2, but do not allow it to synch (or save data).

Regarding the GPX files. They tried that comment with me, but I had pre-empted it by proving that the same fault exists with gpx files created by the Garmin Tread App.
"Why would you want to do it that way"
I don't - but I needed to prove that it wasn't foreign GPX files that cause the problem: these have come from the Tread App. I use GPX files because they are the only way that I can reliably share routes with friends who don't have the XT2. All devices use the GPX file format.

They had no answer to that. Mind - they haven't produced a solution yet either.

I did have a Samsung phone that caused issues with the XT2 after a phone call had been made. The call kept open the BT channel so that nav instructions stopped. Music stopped. The call was shown as being still in progress. I couldn't call out again, but I could break out of it if I reached round the back and pressed the off button. Not a full shut down - just go to sleep. And then press again to wake it up. It restarted quickly, still running the same route and BT was back to normal.

If I left it for 5 minutes or so - it did that itself. It would go blank re-start (not a reboot) and all would be OK.

I was due to replace my phone anyway - and that phone didn't display the same problem. Garmins response was - so it was an issue with the phone.
No. I pointed out that there had been no such issue with that phone and the XT1 software. So it is an issue with the XT2 software not behaving with the slightly older generation of phone. They accepted that point. I still have the phone, so I can dig out the Android version number of the old and the new if you want it.

[FelixHauser]

Hello fellow Zumo users,

Yesterday I ran into some more strange behavior with the Zumo. This time it wasn’t while riding, but just at home doing some trip prep.

In about a month, I’ll be heading to Morocco for two weeks. I’m not the type who preplans every track in detail, but I do like to prepare a bit. For this trip, I created:

4 GPX files with POIs

2 GPX files with one route each

For context: Garmin’s official explanation for the issues I experienced earlier this summer was “tracks too long,” and their solution was simply “keep them short.”

Here’s what I had this time:

Each route: ~160 km

POI file 1: 17 POIs

POI file 2: 17 POIs

POI file 3: 3 POIs

POI file 4: ~2500 POIs (a list of all petrol stations in Morocco — file size under 1 MB)

I imported these files into the Tread app, then powered on the Zumo. It started syncing right away — and promptly entered its infamous restart loop. After reboot, the screen froze and was unresponsive. Even once the files had finished uploading, the problem continued.

I deleted the petrol stations file from the Tread app, and it disappeared from the Zumo. But the restarting still persisted — until I turned off Bluetooth. With BT off, the device stabilized. Later, after renaming some files directly on the Zumo, I saw the sync icon pop up. I re-enabled Bluetooth, and surprisingly, the sync completed and the device stayed stable.

Takeaway:
The Zumo seems to have two related problems:

Large POI files (even when the file size is under 1 MB).

Syncing with the Tread app via Bluetooth.

It’s baffling that in the 21st century, a tech company can’t reliably handle BT transfers of sub-megabyte files.

I’ll be opening another ticket with Garmin in the hope they eventually take this seriously and fix it. I’m also attaching the petrol station GPX file in case anyone else wants to test it.

[proofresistant]

@FelixHauser Thank you for sharing your observation.
It confirms the assumption that synchronisation problems can be a reason for restarts.

Once your device is working properly again,
try reloading the POIs via the Tread app.
I wouldn't be surprised if everything remains OK then too.

[FelixHauser]

I've decided to keep the gpx file on my phone and, if I need to find gas urgently I will just look it up with gpx studio or some other app, find a gas station and just input it on the zumo manually...

I will try it however, but I don't have much hope

[Oop North John]

I too am becoming convinced that the XT2 hates having to look at lots of data, especially if it's new. And new data = old data that's had a minor change.

Today was just like the SP2 days of having to be patient with the technology

[proofresistant]

Hello @FelixHauser ,

I took a closer look at the ‘gas_stations’.
Unfortunately, I can't see anywhere near 6,000 petrol stations in there
How did you arrive at the figure of approx. 6,000?

Anyway, I found 1,624 petrol stations in the form of waypoints and 800 (mini) tracks (which, for whatever reason, each delimit a building area).

The 1,624 petrol stations in the form of waypoints don't seem to be the problem; I imported them (more or less without any problems) via the Tread app and now have them in my zumo XT2.

However, the 800 petrol stations in the form of tracks seem to have an extremely negative effect on synchronisation.
I also imported these (more or less without any problems) via the Tread app. They were then all on the zumo XT2, but from then on I could hardly use the zumo XT2 at all and the constant reboots followed quite soon after.
The problem was solved by switching off the Tread app by deactivating Bluetooth or deleting all 800 tracks in both the Tread app and the zumo XT2.
Without the Tread app connection, the zumo XT2 works perfectly, as I had suspected.
So in your case, too, it is a matter of the already recognised problems with synchronisation.


Question:
What are the 800 petrol stations (mini tracks) for?
Are these petrol stations that are not included in the POIs, or only partially included?

In any case, I see the following two approaches to your problem:
a) Before your trip, transfer everything you need for your travels to the XT2, including the 800 petrol station (mini) tracks, and then deactivate the Tread app connection. Of course, this is not recommended.
b) Import ‘only’ the 1,624 petrol stations in the form of waypoints. These are most likely the petrol stations you actually needed.

Attached are two separate GPX files based on your gas_stations.gpx file, 1,624 POIs in "gas_stations_(POIs)_(Marokko).gpx" and 800 Tracks in "gas_stations_(LocationTracks)_(Marokko).gpx".
When splitting the files, I thought it would be useful to add a petrol station symbol to the petrol station POIs and assign a green colour to the tracks.

Next, I will look into how POIs work in the Garmin .GPI format.
I have already prepared the "gas_stations_(POIs)_(Marokko).gpi" with Garmin POILoader.

[FelixHauser]

Thanks @proofresistant for all your work and efforts.

The file gas_stations was generated using the "overpass-turbo" website, which I found using the Perplexity search engine. I have no idea about the structure the generated gpx file has and why there are tracks and waypoint.

The number of 6000 comes from having a look at the file on Visual Studio Code and sucking at recognizing patterns. So let's pretend this didn't happen. The Zumo showed around 2400 uploaded items, which is in agreement with the 1600+800 you found.

What I am now wondering is the difference between "Waypoints" and "(mini) tracks" and, even more important, how did you find them and separated them.

Yesterday I tried the "Garmin POI Loader", and I converted some other files to gpi files. Although the Zumo recognized there were gpi, it failed to save them into the internal memory and, once I zoomed into morocco, I didn't see anything at all.

Anyway, I will keep investigating but time is running out. In a few days my bike and my stuff is being shipped to Malaga

[jfheath]

I've been looking into this little problem. I first used BAsecamp to split the rectangular tracks from the Waypoint flags.

That is easy to do. You load the gpx, set the filter to just the waypoints and export them.

Trouble is, a lot of them are called simply nod followed by about 10 digits. I didn't count but It involved using the fingers on more than one hand !

So instead, I downloaded the maps for N Africa, then turned off the satellite and placed my position at one of the wapoint fuel stations.

Where To ? -> Category -> Petrol Stations - displays a list.

If you tap the tear drop icon in the top left corner - you can tell it where to search - Your ACtive Route, A time ahead, my destination, upcoming exits, where I am now, A different town, a recent destination (I assume it means Via point), A waypoint.

You can also turn on Settings -> Map Display -> Map Layers -> Up Ahead Places That gives you 3 options. Select Petrol Stations for one of them.
Thes clutter up the screen so I tap each of the other two and let it search for xxx and yyy - that stops the screen being filled with more icons thatn you want. But the box has to be ticked in up ahead places.

On the view Map page, the bottom right corner 3 bar display - seelct Up ahead That will populate as you move, but if you tap Petrol stations you get the same view as before - relative to the tear drop search criteria.

With you Tread app active (but it doesn't have to be set up to synch), it will also show the prices.

Yell out if you need more info on this.