Re: Tread Changes Exisiting Routes - Shaping Point Issues
Posted: Wed Mar 04, 2026 8:56 pm
@smfollen As you know, I largely agree with you.smfollen wrote: Tue Mar 03, 2026 2:03 pm Trying to figure out why all this is happening, and exactly where the problem(s) are, is an interesting puzzle, but the bottom line is that we users have only a single choice - either let the Tread App sync or don't.
Only Garmin can fix the The Tread App's shortcomings and the issues it causes.
...
To be honest, I don't want to try anymore, even though I had so much hope.
Wireless is and remains my dearest wish.
So, I've been testing a lot over the last two days, again.
With my zumo XT2, with my Tread 2 also.
All results were comparable, with one exception: the Tread 2 can also synchronize directly with the Explore cloud via Wi-Fi, and the zumo XT2 cannot.
The rest is more (or less) comparable.
So here are my findings edit: for the moment.
- Tread 2 and Explore Cloud
No problem, after device-cloud synchronization, shapes remain as planned, in Explore cloud also
- zumo XT2 and Tread 2 synchronization with the Tread app offline (Wi-Fi and mobile data disabled)
No problem, after Tread app-device synchronization, shapes remain as planned
Note: the Tread app cannot calculate this.
- GPX import with the Tread app offline (Wi-Fi and mobile data disabled edit: , bluetooth disabled also)
No problem, after synchronization between the Tread app and edit: (not the device), shapes remain as planned
Note: the Tread app cannot calculate this way
- edit:
GPX import with the Tread app offline (Wi-Fi and mobile data disabled, bluetooth enabled, zumo XT2 is connected)
Well-known problems, shapes are moved
Not Always, in my tests with the Tread 2 and Chatham Loop GPX i didn't saw those issues in such test case
But yet, with my WK 3B Route for the zumo XT2 and tread 2 also, Shapings are shiftet like before with tread app
The Tread app cannot calculate this way, but the zumo XT2 can
- Use of routes with only VIA points
No problems, regardless of the configuration, VIAS remain as planned
- Use of routes with VIA points and shaping points, but the routing algorithm must be direct (no faster, no shorter, and no ADV).
No problems, regardless of the synchronization configuration,
VIAs and shapers remain as planned
These shapers are then also final in the Explore cloud, with all shapes unchanged
- But then,
Tread app online (Wi-Fi and/or mobile data enabled)
Well-known problems, shapes are moved
I don't think it's the synchronization. I think it's the route calculation method of the Tread app itself.
Conclusion:
If the Tread app can optimize the shapes, it does so, but it does it the way it thinks is best, which unfortunately isn't really optimal.
edit:
May zumo XT2 and or Tread 2 does changes also, sometimes? if routes comming from Tread app?
It's a nightmare. Whenever I think I've understood something, I start all over again shortly afterwards.
PS
@smfollen
by the way is that your noted deviations have roughly the same effect as my own examples.
What confused me at first was that it looked like an 8 to me at the beginning, but after the Tread app “optimization,” it no longer did. But that was probably due to the route selection, and if the northeastern section is avoided, it looks a little less like an eight.
I also think that the Tread app has improved at least a little. Not significantly, but marginally.