Latest XT2/Tread software version

[Oop North John]

New Tread app version for Android,

3.00.06 (2026.02.17)

8.76 Mb

Seems they've added features, but can't get the basics right again. Waypoint showing and place name behaviour is "frustrating" once more

[Oop North John]

New Tread app version for Android,

3.00.06 (2026.02.17)

8.76 Mb

Seems they've added features, but can't get the basics right again. Waypoint showing and place name behaviour is "frustrating" once more

And tried to add a shaping point into a route in Tread (which seems to be a fairly stable way of doing it) but now that route and all others has the spinning wheel of doom for "recalculating".

Bonus point to Garmin, I can't report it as the spinning wheel of doom prevents the feedback being submitted

[smfollen]

Product.Support@garmin.com

[Oop North John]

Avoidances now can be accessed from the routing screen.

Any one any idea what "Avoid area C" is? Congestion charging??

Google suggests that the Avoid Area C is something to do with roads in Israel.

[turbo19]

New Tread Version for Android:

3.00.09 (2026.03.05). 127Mb

[Oop North John]

New Tread Version for Android:

3.00.09 (2026.03.05). 127Mb

Any idea on how they've improved its many "features", aka bugs?

[smfollen]

I just checked the latest release notes, and then asked Garmin Support about this.

Support Center Chat
Session started between Dan and Steve Follen
Steve Follen:
The latest version of the Tread App (Android) is 3.00.09 (2026.03.05), but the Release notes only go up to version 2.12.50 (1/8/2026) (https://support.garmin.com/en-US/?faq=O ... eRK7Hlfe08)
Where can I find what has changed in the current release?
Dan:
Thank you for contacting Garmin Chat Support. Let me ask around and see what I can find out
Steve Follen:
Thank you
Dan:
The release notes are This version includes bug fixes to improve app and device functionality
Dan:
I am putting in feedback to get that site updated.
Steve Follen:
Well thanks, but honestly "bug fixes to improve app and device functionality" don't really say anything useful. Not your fault, of course.
Dan:
I totally agree with you
Steve Follen:
I understand! Maybe you could also provide that feedback to whoever owns the release notes.
Steve Follen:
Have a good day.
Dan:
Will Do!
Dan:
Thanks for choosing Garmin. Have a great day!

After many interactions with Garmin Support, I have come to the conclusion that the support people are generally not to blame. Rather, the problems are beyond their areas of responsibility and influence.

[Oop North John]

Just opened up Tread this morning on my Android phone and it's at 3.00.11.

[proofresistant]

My Android device Tread app has now also been updated to version 3.00.11.

Personally, I don’t see any improvements regarding my main issues—the shapings being moved or the synchronization loops—it’s behaving exactly the same as before.

And it still grumbles when the magical 10 shapings are exceeded

[Regain]

iOS is on v3.00.09 updated three days ago and still current. I’ve checked with several of my routes built on and imported from MRA. The routes calculate without error and my shaping points are in the same place. I’ve not checked lat/long for extreme accuracy but looking at the routes on MRA and Tread, the points appear about right. I display my track underneath so I know the routes are as planned.

I promise I’m not a Garmin plant but it seems to work for me. Faster roads do appear to have a magnet in them for Tread calculated routes but easily nailed on to side roads with strategic shaping points.

Oh, and multiple shaping points, way more than 10 despite the pop-up reminder. Strange but good.