deleted routes reappear in XT2 (as long as trip duplicates are present)

[proofresistant]

Strange behavior

It has been reported before that routes reappear in XT2 devices even though all routes were previously deleted (XT2 and or Tread app and or Explore).

I've just noticed it more as my experience with tripmanager grows.
I'm not saying it's related to Tripmanager, quite the opposite, thanks to Tripmanager I noticed it the quickest which could be the reason.

The reason for the routes reappearing is probably that the XT2, for whatever reason, perhaps creates duplicates of the “trips” when synchronizing (sync. issues).
Found in:
zūmo XT2\Internal Storage\.System\Trips\1234567890.TRIP
There were some copies of trips, different file name, different number of copies, may different route sources but recognizably the same content per route source.
(For me, the *.trip copies from the same route source all look the same, even the Tripmanager CSV export does not show me any different content).

If I then restart the XT2, supposedly without existing routes, the first trip file found always comes back as a route in the XT2 visible in the Explore routes library.

What is still strange is that I can then see the trips as a route in the XT2, but not in the Tread app, even after synchronization.

Then I can also edit the route in the XT2.
But then, as if by magic, the route in the XT2 disappears again and there is one less file in the Trips folder.

If I then restart the XT2, the first trip found appears again as a route until all trips in the folder zūmo XT2\Internal Storage\.System\Trips\ have been removed, which can of course also be deleted on the PC.

Has anyone observed this?

Anyway, the knowledge about the trip copies now helps me to clean up the XT2

PS
@ @FrankB : Could you think about, displaying an additional column with the trip name (mTripName) in the TripManager table with the trips?
(I personally find the trip name more interesting than the file name anyway)

[smfollen]

@proofresistant In Trip Manager, Functions -> Rename file will, by default, rename the file to the trip name.

[proofresistant]

@proofresistant In Trip Manager, Functions -> Rename file will, by default, rename the file to the trip name.

Yes, I have seen the function, but it may not be necessary for some people to run it if it is already in the table anyway

[FrankB]

@proofresistant
I understand your question, and why it would be useful.
The problem, for me, is that the same list is used for all file types, and only for trip files the mtripname can be displayed. Besides getting the tripnames requires copying the file to your computer first, because a program can not read files directly from an MTP device. So it would probably take much longer just to display the list. Will keep it in the back of my head though,

For now you can rename the trip files, as @smfollen pointed out, or you can look in the green bar.

trip info.jpg (24.99 KiB) Viewed 2062 times

Frank

[turbo19]

Strange behavior

It has been reported before that routes reappear in XT2 devices even though all routes were previously deleted (XT2 and or Tread app and or Explore).

I've just noticed it more as my experience with tripmanager grows.
I'm not saying it's related to Tripmanager, quite the opposite, thanks to Tripmanager I noticed it the quickest which could be the reason.

The reason for the routes reappearing is probably that the XT2, for whatever reason, perhaps creates duplicates of the “trips” when synchronizing (sync. issues).
Found in:
zūmo XT2\Internal Storage\.System\Trips\1234567890.TRIP
There were some copies of trips, different file name, different number of copies, may different route sources but recognizably the same content per route source.
(For me, the *.trip copies from the same route source all look the same, even the Tripmanager CSV export does not show me any different content).

If I then restart the XT2, supposedly without existing routes, the first trip file found always comes back as a route in the XT2 visible in the Explore routes library.

What is still strange is that I can then see the trips as a route in the XT2, but not in the Tread app, even after synchronization.

Then I can also edit the route in the XT2.
But then, as if by magic, the route in the XT2 disappears again and there is one less file in the Trips folder.

If I then restart the XT2, the first trip found appears again as a route until all trips in the folder zūmo XT2\Internal Storage\.System\Trips\ have been removed, which can of course also be deleted on the PC.

Has anyone observed this?

Anyway, the knowledge about the trip copies now helps me to clean up the XT2

PS
@ @FrankB : Could you think about, displaying an additional column with the trip name (mTripName) in the TripManager table with the trips?
(I personally find the trip name more interesting than the file name anyway)

I observed the same problem.

The problem is that by staying in the "unorganized" folder from time to time the XT2 restarts because the XT2, the Tread App and the Explore Web are not well synchronized.

The only solution I've found is to manually delete the route from Explore website.

[smfollen]

For what it's worth, I do not use the Tread app at all, so no sync to the Explore database, but I have seen deleted routes reappear.

The key here may be, as proofresistant points out, "as long as trip duplicates are present". The XT2 can have multiple .trip files with the same trip (aka route) name. You can see this with Trip Manager.

It may be that when a route is deleted on the XT2, not all of the .trip files associates with that route are deleted?

[proofresistant]

The only solution I've found is to manually delete the route from Explore website.

Although a bit late,

The safest solution is to delete content from four locations.

• a) Tread app

• b) Explore cloud

• c) Zumo XT2 internal collection (or ‘Favourites’ on newer devices)

• d) Device internal storage: .\System\Trips\*.Trip

It is often sufficient c) to delete files from the Zumo XT2 internal collection and d) the corresponding .\System\Trips\*.Trip files.

What has always helped is to delete all routes from the device:
e. g.:
Delete everything from .\System\Trips\*.Trip
And use the hidden menu to delete the Explore database.
The Tread app and Explore Cloud were usually already ‘cleared’ beforehand

PS
Recommendation:
Even after several months, I have to say, ‘Thanks, Frank’ – TripManager has more than proved its worth, as it did here when sorting out the ‘chaos’ with the duplicate routes