That sounds good at first glance.Dutchgixxer wrote: Sun Mar 22, 2026 6:10 pm I have loaded a track to the tread app. I have converted the track to a route and both are present in de XT2.
Just a thought, at first glance, it’s faster to turn a track into a route in the Tread app.
But ultimately, it might work better if you first convert the route into a track in the navi device, using the device maps.
Hmm, that sounds a lot like synchronization issues to me.Dutchgixxer wrote: Sun Mar 22, 2026 6:10 pm If i start the route calculation of the route taken 10 minutes or more. Very dissapointed.
When the Navi is busy synchronizing, I notice similarly long processing times, among other things.
That, in turn, sounds to me as ifDutchgixxer wrote: Sun Mar 22, 2026 6:10 pm If i try to start the route while not on the route, calculation is done directly to the end. What a waist of time
a) the route path got corrupted during synchronization, yes, I’ve observed exactly that before.
Or
b) as if that route line is vulnerable to the CEP problem.
Maybe try this approach again:
- import the track into the Tread app
- wait sync transfered track to the navigation device is done
- turn off Bluetooth
- convert the track to a route in the navigation device
By the way,
I've also tested the new version. Unfortunately, I haven't found anything particularly positive to report; everything related to synchronization is still, (at the very least) questionable





