Latest XT2/Tread software version

[Oop North John]

If anyone else has their XT2 refusing to be seen by Garmin Express / the PC as a drive?

Tried different cables, different ports on the laptop, a soft reset on the XT2, turning off the laptop, but the XT2 refuses to go past the bright screen with the "Garmin and garmin.com/express" screen.

Took out the micro SD card I had installed and instantly it connects.

I had to replace the original cable because I suddenly couldn't connect it to my PC. This was very strange because it had always worked for over a year. However, after replacing the cable with a regular one I used for my smartphone, everything worked fine.

Weird isn't it, sometimes the one of my laptops USB ports doesn't allow a connection. Maybe there was a butterfly in Japan starting to flap its wings when I tried

[jfheath]

Could someone confirm for me if the reboots continue with version 6.10 of the XT2 and the Tread with version 2.12.33?

In my case, they continue, and it's necessary to stop the Tread app so that the XT2 doesn't keep rebooting.

I would try:

Reset Explore Database (Hidden System Menu / Developer Tests & Tools)

Roll back system software to previous (v5.40) and then reinstall 6.10
Delete the Tread App and reload / reinstall it.
Clear out data that might be synching for the Tread App from the Explore database at explore.garmin.com

Not that I know anything about this particular fault. I just know that mine doesn't do it, but if it did, that's what I would do. No particular order.

Beware that resetting system software or resetting the device will lose you Active Track Logs in CurrentTrackLog.gpx and in the Archive folder.
Save anything that you want to keep.

[turbo19]

I tried to do that today, nothing, it doesn't work.

When the explore cloud is empty, both on the XT2 and in the explore.com cloud, there are no restarts, but as soon as you start syncing some tracks or routes, the restart party begins.

I've deleted everything again and installed Tread without syncing. I'll have to wait for an update after 6.10 for the XT2 to work properly.

Poor engineering in Garmin after almost 3 years of this device. I don't understand what engineer came up with the idea of making a program in which all wireless transmission has to go through the crappy Tread App. The XT/Drive app combination was much better.

[turbo19]

New Tread version for Android:

2.12.35

It seems that version 2.12.35 fixes the constant reboot issue. I'm testing, and despite having the route active, playing music, and requesting the weather forecast on the XT2, it still won't reboot.

It's the biggest update they've made this year (at least in size 171Mb)

Fingers crossed.

[jfheath]

Im still on 2.12.33 on my ipad. I just updated it.

I've just noticed an improvement to the Tread App. I have been testing a 8 point route that has 7 shaping points to prevent the route from jumping onto the M6 Motorway between junctions 36 and 42. I want to stay on the superb old main road, the A6.

So previously i have created a route with 8 Via Points. I do not use shaping points because they are relocated. So 8 via points numbered 01 to 08. Save the route.

When I change a via to a shaping point, eg 05 sometimes it plots the point on the M6 and calls it Shaping Point.

When I change an adjacent Via Point eg 06 , sometimes it moves that onto the M6 and also takes 05 with it.

On occasions, no movement is observed until I change a third Via to a Shaping Point, then all 3 move onto the M6 !

The behaviour is not predictable. Different things happen each time I try it. It behaves differently if i start changing at 02 instead of at 07.

However, I have noticed previously that if I use the undo button, and then repeat the operation, it doesn't do the same thing.

Today I checked this behaviour again and noticed something curious:

If when changing a via to a shaping it moves the point onto the M6
Undo puts it back as a Via in its iriginal location
Change it to a shaping point again, it puts the SP in a different place on the A6. Not the M6
Undo and repeat, it changes it to a shaping point in exactly the same location.

Furthermore, after getting to that stage, change any via to a SP, and the SP remains in exactly the same place.

Which is what it should have done in the first place.

I think this is new behaviour. Maybe they have been working at it ?

[Oop North John]

The inconsistency of results of doing x or y, and then trying it again and getting differing results makes it extremely frustrating for me trying to work out if I'm going mad / forgetful / senile, and then I remember that I'm dealing with Garmin software, and the world is happy again, in my brain!

[Lanso]

So, premade GPX routes no longer get modified by the tread app?

[Oop North John]

So, premade GPX routes no longer get modified by the tread app?

I tried a route from BaseCamp where I made a "via" into a "not announced" which BaseCamp calls a shaping point. Transferred the gpx route into Tread via an e-mail, and the shaping point is no longer on the via points position. And as usual moves it onto a "faster" road, rather than the one it was originally in BaseCamp.

[Lanso]

Still broken and unusuable then

[jfheath]

So, premade GPX routes no longer get modified by the tread app?

I didn't say that - if it was my post to which you were referring. This behaviour was observed purely by using the Tread App on an Ipad to create a route using first via points and then changing them to shaping points.

There are two reasons for wanting to do it this way:

1. If you try to build your route with shaping points from the outset, you have to know where they will be placed. That isn't the way that most people add shaping points. You tend to plot a route and then put a shaping point mid-way (ish), and see how the route calculates. Then add a couple more either side of the first. So think of a route going from left to right. You put in point M in the middle, then decide it needs more, so you add Point L to the left and point R to the right. The map shows them in the correct position reading left to right Start, L, M, R, End.
But the route list puts the shaping point between Start and End in the order in which they were created - ie Start, M, L, R, End - and it is impossible to spot becasue theya re all called 'Shaping Point'.

2. Moving a shaping point is really problematic with the Tread app - with the fact that they are all called shaping point, and that when you pick up a shaping point to move it elsewhere, the place where you intend to put it in the list has moved because it has already removed the point you have juts picked up and redrawn the list. I complained about all of the Tread App behaviours to Garmin. So far this is the only one that they have fixed - and they did it by making it impossible to move a shaping point at all !!

So creating a route with only Via Points solves both of those issues. But I only want Vias at my stopping places - that way I can display the time/distance to arrival at the next stopping place for my pillion to see.

The last time I checked, it is the Synching of the route via the Tread App to the Cloud Database at Explore.Garmin.com that creates the moving route point problems. If you do not allow synch to take place, it does not happen.