Page 31 of 40
Re: Latest XT2/Tread software version
Posted: Tue Jan 06, 2026 2:11 pm
by FrankB
@jfheath
Look on the bright side (of life). All the hours of puzzling how to make it behave.
Re: Latest XT2/Tread software version
Posted: Tue Jan 06, 2026 6:58 pm
by jfheath
I'm just not letting them think that we don't matter. Not that it will bother them one bit.
Re: Latest XT2/Tread software version
Posted: Tue Jan 13, 2026 1:09 pm
by turbo19
New Tread version for Android:
2.12.50 (2026-01-08)
Re: Latest XT2/Tread software version
Posted: Tue Jan 13, 2026 1:32 pm
by Dutchgixxer
Thanks release notes available ?
Re: Latest XT2/Tread software version
Posted: Tue Jan 13, 2026 7:24 pm
by Gelo
Has anyone noticed any improvement in how routes transferred from the Tread app to the XT2 are handled? Does it still mess them up?
Re: Latest XT2/Tread software version
Posted: Wed Jan 14, 2026 8:54 am
by Oop North John
turbo19 wrote: Tue Jan 13, 2026 1:09 pm
New Tread version for Android:
2.12.50 (2026-01-08)
Looks to have deleted the "generic restrition" warning about where there might be a traffic jam

Re: Latest XT2/Tread software version
Posted: Fri Jan 16, 2026 9:52 pm
by proofresistant
Tread app 2.12.50 (2026-01-08)
I observe the same synchronization issues I've had for the past two years.
My test examples haven't really shown any positive changes.
Endless back-and-forth synchronization in seemingly endless loops, route calculation (sometimes) not possible, and multiple identical trip files for one route in the device.
Re: Latest XT2/Tread software version
Posted: Sat Jan 17, 2026 7:27 am
by Oop North John
proofresistant wrote: Fri Jan 16, 2026 9:52 pm
Tread app 2.12.50 (2026-01-08)
I observe the same synchronization issues I've had for the past two years.
My test examples haven't really shown any positive changes.
Endless back-and-forth synchronization in seemingly endless loops, route calculation (sometimes) not possible, and multiple identical trip files for one route in the device.
Have you tried deleting Tread and removing the BT links, and re-pairing the phone and XT2? Apologies if you already have, not trying to teach grandma how to suck eggs!
Re: Latest XT2/Tread software version
Posted: Sat Jan 17, 2026 8:29 am
by jfheath
Oop North John wrote: Sat Jan 17, 2026 7:27 am
proofresistant wrote: Fri Jan 16, 2026 9:52 pm
Tread app 2.12.50 (2026-01-08)
I observe the same synchronization issues I've had for the past two years.
My test examples haven't really shown any positive changes.
Endless back-and-forth synchronization in seemingly endless loops, route calculation (sometimes) not possible, and multiple identical trip files for one route in the device.
Have you tried deleting Tread and removing the BT links, and re-pairing the phone and XT2? Apologies if you already have, not trying to teach grandma how to suck eggs!
You have to delete and reinstall the Tread App on your phone as well.
Start with a clean phone and XT2. Then install Tread, and link to the phone - but do not give permission to store data or to synch. That allows data - weather, traffic, up-ahead, fuel on route with prices etc. But you have to transfer routes using the SD card or by USB cable. Best to store on the SD card with the XT2.
Re: Latest XT2/Tread software version
Posted: Sat Jan 17, 2026 5:19 pm
by proofresistant
Oop North John wrote: Sat Jan 17, 2026 7:27 am
Have you tried deleting Tread and removing the BT links, and re-pairing the phone and XT2?
Hi
@Oop North John ,
Thank you for reminding me.
To rule out this such kind of problems completely, I reseted the Bluetooth connections (zumo XT2 and Android smartphone), deleted all Tread App data and uninstalled the Tread app, and rebuilt everything from scratch.
As expected, the result is disappointing and unchanged: I am still observeing endless synchronizations and multiple Trip files on my divice.
Then there's the tip that a reset can help, especially if inexplicable problems arise despite all checks. This applies to operating systems, software, smartphones, navigation systems, or whatever.
But, and this is the key point, in most cases (maybe less than 10%), a reset doesn't really help and “only” creates a lot of unnecessary work to restore everything to how it was before. Ergo, reset yes, but really only when nothing else helps.
I should also mention here that I hate such “modern” tips, which are far too easily given “just like that” by the manufacturers' support staff.
But thank you for mentioning the reset tip anyway, it kept me entertained, busy and allowed me to rule that out for us
