Tread - Option not to transfer data

[Oop North John]

I know that you can not have the XT2 and Tread set up not to sync, and so anything in Tread is only there, and vice-versa. Or, you work in Tread and don't switch on the XT2.

Sometimes though it would be helpful for me to look at routes / waypoints only in Tread, and them not to be synched across to the XT2. I could have a "work in progress" collection, but then any routes etc will get transferred across and contaminate what I want on the unit. Is there a selectable option to "hold" items only in Tread?

[jfheath]

I know that you can not have the XT2 and Tread set up not to sync, and so anything in Tread is only there, and vice-versa. Or, you work in Tread and don't switch on the XT2.

Sometimes though it would be helpful for me to look at routes / waypoints only in Tread, and them not to be synched across to the XT2. I could have a "work in progress" collection, but then any routes etc will get transferred across and contaminate what I want on the unit. Is there a selectable option to "hold" items only in Tread?

Yes - ish. In order to set Tread Up on the phone - or ipad, it has to be able to synch. Which sounds like a complete gocha.

But I have had my ipad able to access the routes while my XT2 was set up to synch with my phone. I just set up the ipad to synch first, and then turned off the Bluetooth connection. Without BT, it cannot synch. I'm unsure whether something like that will provide a solution - eg if you set it up to work on a different device and then stop any form of synching between the phone and the XT2.

I think that did work for me at one time - but I was actually working on something else at the time and I have been installing Trread and destroying Tread synch repeatedly over the last few months. I cannot be certain. Certainly if you destroy the tread link to the XT2 and the phone it is currently working with - it is going to know about it. But if it was set up on the ipad and you leave it set up but turn off BT - and then destroy the Tread on the phone and on the XT2, while the phone is off - the Ipad is just going to think that the XT2 isn't turned on - it cannot communicate to find out anything different.

I did have the XT2 syching with the phone and the ipad synching with the Tread Database all at the same time. So my Ipad could pick up the routes from the Explore database and send them back again. The phone could read these but it didn't synch them with the XT2 unless the phone changed them in some way - eg by adding a full stop to the name. Then the route is deemed to have been created on the phone, and that would synch.

It's a little vague in my memory - but I'm pretty sure that the answer is no - if you are talking about a phone and the XT2. But yes (probably) if you set it up on a different device, turn the device off and then resintall on the XT2 and phone so that those two cannot synch.

[Oop North John]

Thanks, that's what I was thinking.

Somehow I had my tablet sync'd to the XT2 and it made Tread on my phone only to want to synch the audio, which was confusing to start with, and then irritating. I suspect that if you have Tread on a phone and tablet then more than one on will try to update the other, which then when the XT2 is on will cause all sorts of mayhem.

I find route planning on the tablet not too bad and the phone a little less easier, certainly much easier than on the XT2. Going away it's convenient to have the tablet as it's less weight and size to carry. Pity that Garmin couldn't make a 590 with a bright screen.

[jfheath]

I suspect that if you have Tread on a phone and tablet then more than one on will try to update the other, which then when the XT2 is on will cause all sorts of mayhem.

I think that I turned BT off on the ipad, so that it couldn't communicate with the XT2. It just stored the route in the Explore database. The phone app could pick this up, but it wasn't the owner of the route, so it didn't synch.
You need the phone BT link to the XT2 for all sorts of reasons, so the phone has to take ownership of the route. I was trying to work out how to do that. Was the route on the XT2 coming from the phone, or from the ipad ? So I changed the route name on the phone's Tread App. As soon as I did that, the phone synched the route to the The XT2.

So to get the tablet able to use the tread app, it needs to be installed with full BT and synch connection.
Then you can destroy the BT link, and the Tread app will still allow routes to be created.
It can still send routes to the Explore database by wifi (and that works even if you use the phone as a wifi hotspot !)
Once the Explore database has the route, the phone can see it.
The Tread App wont synch the route with the XT2 unless the phone has edited it. Adding a full stop to the name forces the synch.


I was quite pleased when I found that out, but then I found that putting additional shaping points in was a pain. it always adds the point to the end of the segment in the trip list, and reordering them is difficult because they are all called Shaping Point.

(So if you have a segment with shaping points A B D, and you realise that you have missed out C, so you add point C on the route between B and D. It looks ok on the map, but the route list reveals that they are in the wrong order. They are shown as A B D C. Dragging the points in the list is possible, but it is very easy to get the shaping points mixed up - mainly because the display moves half way through dragging the point, so you have no idea where to drop it !)

So I started using Via points, and then changed them to shaping. But Tread then often moves the point onto a faster road.
I reported it, gave them video evidence. Nothing so far. So I gave up with Tread. Pity I really liked the idea. It has a lot of good features. Tech support make all of the right noises, but nothing ever happens.

I find route planning on the tablet not too bad and the phone a little less easier, certainly much easier than on the XT2. Going away it's convenient to have the tablet as it's less weight and size to carry. Pity that Garmin couldn't make a 590 with a bright screen.

Totally agree. A 590 with a brighter screen and better battery life or better connections so that it could charge properly was all that was required. It was a brilliant satnav apart from that.