Zumo User Forums

After driving myself crazy without being able to sync some Basecamp collections with Tread App over Bluetooth, I think I've managed to avoid Bluetooth disconnections caused by syncs.

I am going to differentiate 2 types of synchronizations, those that come from things drawn in Tread App (WP and routes) and those that come from outside (Wikiloc, Basecamp, MRA, etc.).

Tread App synchronization directly with the XT2 via Bluetooth:
with version 2.09.58 (2024-12-04) I have not encountered synchronization failures when sending directly from Tread App to XT2 (all elements synchronize quickly and without creating interruptions or bluetooth blocks).

Syncing external collections to Tread App:
When we want to synchronize external collections that have tracks/routes/wp, in my case Basecamp, if we try to synchronize them via Bluetooth with the Tread App, the problems begin. The only way I have found to synchronize these collections and prevent Bluetooth interruptions from occurring later on the XT2 is to introduce them via MicroSD or internal memory. We will put the collections in the "GPX" folder in our XT2's memory, and then we will import the material into a new collection. Nothing new so far.
What I have discovered is that when the collections are quite large (about 15Mb) it is convenient to disconnect the phone's Bluetooth. In this way, we first import the collection from the internal memory of the XT2 and leave it unsynchronized. Once it is imported to the XT2, we will turn on the mobile's Bluetooth and wait for it to synchronize with the Tread APP and the Explore cloud. This way I have had no interruptions and the Bluetooth connectivity between Tread App/XT2 remains stable, even during calls or music.

I have also discovered that it is better to create the collection that we will send our .gpx to, this way it syncs both the XT2 and the Tread App faster.

I have done 1000 tests and I think it is the best way to import material from Basecamp, MRA (when there are multiple files in the same .gpx), Wikiloc, etc. It is unfortunate that any external .gpx cannot be imported directly from the phone's bluetooth into the Tread App, but for now until this is resolved, I think it is the best way.

Many thanks to Edwin from the XT2 Facebook group for the tip

Excellent stuff. Well done you and Edwin !

So the reason for the disconenctions is to do with so much data having to be synchronised and constantly breaking other BT connections in order to do so. I had noticed that it repeatedly synchs - at least one per minute - both ways - when it shouldn't really need to. I also noticed that route points get sent to the Tread App first and then other information - like the actual route come later.

Another alternative of course is to not let it synch at all. Don't have the tread app set up so that it is saving your data. This option exists when first installing tread (unless they have removed it in the two recent updates), but it is easy to miss. You can still have tread connected to the phone, to receive traffic, weather, fuel info. But it doesn't even try to send route data between the XT2 and the Tread Database.

I thought you had tried that though ?

In my case - having the system set up like this still causes phone disconnect issues. Now narrowed down to - if the caller disconnects first, my XT2 doesn't recognise this and thinks the phone call is still active. If I disconnect first it doesn't. And it only does it on one phone. Not on my cheap emergency phone. Neither does it do it if Tread is not installed. Guess which reason Product Support went for ?

jfheath wrote: ↑Sun Dec 08, 2024 12:37 pm Excellent stuff. Well done you and Edwin !

So the reason for the disconenctions is to do with so much data having to be synchronised and constantly breaking other BT connections in order to do so. I had noticed that it repeatedly synchs - at least one per minute - both ways - when it shouldn't really need to. I also noticed that route points get sent to the Tread App first and then other information - like the actual route come later.

Another alternative of course is to not let it synch at all. Don't have the tread app set up so that it is saving your data. This option exists when first installing tread (unless they have removed it in the two recent updates), but it is easy to miss. You can still have tread connected to the phone, to receive traffic, weather, fuel info. But it doesn't even try to send route data between the XT2 and the Tread Database.

I thought you had tried that though ?

In my case - having the system set up like this still causes phone disconnect issues. Now narrowed down to - if the caller disconnects first, my XT2 doesn't recognise this and thinks the phone call is still active. If I disconnect first it doesn't. And it only does it on one phone. Not on my cheap emergency phone. Neither does it do it if Tread is not installed. Guess which reason Product Support went for ?

"Another alternative of course is to not let it synch at all. Don't have the tread app set up so that it is saving your data. This option exists when first installing tread (unless they have removed it in the two recent updates), but it is easy to miss. You can still have tread connected to the phone, to receive traffic, weather, fuel info. But it doesn't even try to send route data between the XT2 and the Tread Database.

I thought you had tried that though ?"

- Yes, that option is good and I have tried it. It is the most solid for Basecamp routes. But you lose the option of having everything synchronized with your phone, and being able to draw the routes on trips, and you also lose the option of sending the .gpx via Bluetooth. If you only put the .gpx at home it can be a good option.

"In my case - having the system set up like this still causes phone disconnect issues. Now narrowed down to - if the caller disconnects first, my XT2 doesn't recognise this and thinks the phone call is still active. If I disconnect first it doesn't. And it only does it on one phone. Not on my cheap emergency phone. Neither does it do it if Tread is not installed. Guess which reason Product Support went for ?"

- I've had those same problems these days, when someone calls you and you don't pick up the call, the pick up/hang up screen remains on the XT2 screen. The same thing happens when waiting calls come in.

Did see some video's about this problem.

so on old phone no problem and new phone you have that problem.

What I did see in that video was that phone was disconnected via Call Hold.
Can you see if you have "call waiting" option in you're new phone is active and if so turn if of and test again !?

would be interesting to see if problem is then gone. ?

and are both phones on same phone operator network ?


Herman

Before I even got my XT2 I hade already imported al my 300+ Basecamp waypoints and routes to Garmin Explorer on the web. From there it synced over to Tread on my phone.
When the XT2 arrived and during set up, al the waypoints etc synced to the gps with no problems at al.

New routes or waypoint created in Basecamp are easily transferred to the XT2 with in Basecamp when connected with cable. Or exported from Basecamp as gpx files and then imported to Garmin Explorer web.

Niro wrote: ↑Sun Dec 08, 2024 10:00 pm Before I even got my XT2 I hade already imported al my 300+ Basecamp waypoints and routes to Garmin Explorer on the web. From there it synced over to Tread on my phone.
When the XT2 arrived and during set up, al the waypoints etc synced to the gps with no problems at al.

New routes or waypoint created in Basecamp are easily transferred to the XT2 with in Basecamp when connected with cable. Or exported from Basecamp as gpx files and then imported to Garmin Explorer web.

Yes that is as it should be.
Routes, tracks and waypoints can be sent to the Zumo XT2 by USB cable and stored in the GPX folder in Internal Storage, or in the SD Card/Garmin/GPX. The XT2 will pick them up and load them.

However - routes transferred from any GPX file may be subject to change. We are used to the route being recalculated - choosing different roads to get from one route point to the next. That is Ok. Just use a few more shaping points, or place your shaping points with a little more consideration about what he satnav might do if (say) you plot a shaping point just after a junction. You see that as an instruction to turn off and continue along that road. The Satnav sees it as an inconvenient detour - it takes it and then goes back to where it was.

But the XT2 is different. Once the route is loaded and checked and you can see that it is OK, it has to synchronise with the Explore App on your phone and then with the Explore Database. One of those (and I suspect that it is the Explore App, has changed the routes beyond all recognition. Because it has changed, it then gets synch'ed back to the XT2 - via your phone. This takes a little time, so you may not notice it immediately. If you create a track of the route (eg in BAsecamp), put that in the same collection on the XT2, set it to a nice bright red or black - you will be able to see where the route has deviated.

The Via points tend to stay in place, but the route and the shaping points that formed the route are both moved onto faster roads.

We've had a few Tread updates since I tested and reported this fault. I have a video of the behaviour that I sent to product support. I must go back and see whether or not this has been fixed.

Niro wrote: ↑Sun Dec 08, 2024 10:00 pm Before I even got my XT2 I hade already imported al my 300+ Basecamp waypoints and routes to Garmin Explorer on the web. From there it synced over to Tread on my phone.
When the XT2 arrived and during set up, al the waypoints etc synced to the gps with no problems at al.

New routes or waypoint created in Basecamp are easily transferred to the XT2 with in Basecamp when connected with cable. Or exported from Basecamp as gpx files and then imported to Garmin Explorer web.

"Or exported from Basecamp as gpx files and then imported to Garmin Explorer web."

I have already done many tests with this method, and with the tracks (not routes) that come from outside (Basecamp, Wikiloc, etc.) it sometimes causes problems after Bluetooth. Don't ask me why. Garmin magic. Something that should be the simplest in the world, importing some gpx to your Tread app on your mobile or a website, can become something very complicated.

That's why I opened this post, in case anyone was having those same problems when importing their most valuable data from Basecamp to Tread.

A couple of months ago I bought a Xiaomi Poco Pad, 12 inches, and together with the mouse, it makes it quite easy for me to draw routes with all the imported Basecamp data. Via Michelin + routes most used by motorists, along with my synchronized lists of beautiful towns or places of interest, make it very easy to draw routes in the Tread App.