Garmin have F**ked the Drive app.

Ok. So: context.
I haven't used my XT since the Spanish trip in April. Used it today to ride in Surrey. Battery was so dead that it took a while for the Zumo to power on after being on its powered mount.
When it came to its senses, it was almost as it got reset, as all the "soft" settings were lost: icon, sounds, map (back to shitty 3D), etc.
I assumed all these config were write on memory, but looks like not.

Apart from that, it turns out it would still connect to Drive on my phone. So some settings are kept.

I know the battery of my Zumo is on its way out (quite some way out already) and this is ok. I'm just surprised it loses the config. ANYWAY...


I just updated Garmin Drive on my iPhone to the latest version.
I am on iOS. iPhone 13.

My Zumo is not paired with the Explore account.

I airdropped a random track from my Mac to my iPhone, and then opened it via Drive (selecting from the "share" overlay, same steps we went through with Berin in another thread a few weeks ago).

Drive asked me immediately to share the file with Zumo. I did, and it got sent immediately via Bluetooth. So, still works.

drive.jpg

zumo.jpg


Wouldn't surprise me if Garmin borked the procedure for people who have the Zumo paired with their Explore accounts.
 
This one then! I'm using an iPhone. I seem to have the same update and it is still working for me. Perhaps its because I binned explore and the link to my xt

This may be a difference with the I-Phone version, maybe they will fuck you over at a later date?

I also binned Explore as soon as I got my XT, so it has nothing to do with that, quite the opposite as it is actually insisting you use Explore now, probably trying to capture the market in route planning, and have all of the data on everywhere you plan to go, do go, how you get there, and how fast you go on the way etc.

If you use gpx 1.1, the XT will recalculate the route between shaping points as per your device setup, if you use loads of shaping points it should be ok.

I have been trying gpx 1.2 and although it doesn't show the shaping points, it does show the waypoints and it follows the track without any recalculation as long as you have auto recalculation switched off.

Now I will admit I am not as "expert" as some on here, so take the above with a pinch of salt, that is what I have found researching the differences and this is only true with the XT apparently
Be very careful, I had major issues with 1.2, it was a very frustrating and lengthy journey, quick summary:

I started getting odd directions, detours, constantly asked to "turn around" for no reason, I tried all sorts of things with settings and placed support cals with Garmin and My Route App.....

...And this is where it got weird, as I use MRA for route planning as it is 1000 times quicker and easier than basecamp (and I can zap routes straight from phone to XT) this was how I made the routes, however I then discovered that using basecamp my test route worked OK.

Not sure on the technical specifications of GPX file, but MRA and Basecamp create them differently, and they behaved differently on my XT.

Be very interested in how you get on, if you are using basecamp then probably fine, if not you may get some weirdness, please do keep us all informed on your findings ;-)

One other point to note, because the "shaping points" using GPX 1.2 are not shown when you go into the route on the device it means you cannot edit them on the fly, sometimes I will want to shorten a route slightly when on tour due to weather / time / mood and I can open the route and remove a few points (as waypoints and shaping points show up and can be deleted) but with 1.2 you only see the Waypoints, making this impossible.
 
If you use gpx 1.1, the XT will recalculate the route between shaping points as per your device setup, if you use loads of shaping points it should be ok.

I use 1.1 for exactly that reason. I also follow MyRoute’s advice / best practice of having a shaping point every 5km / 3 miles. The transfer and any subsequent recalculation on import onto the device’s screen is then minimal. I also try, whenever possible, to create the route in Here maps. All that aside, I also check the route(s) before using them. Small discrepancies over estimated time / distance I ignore. Anything meaningful I investigate and fix. Five minutes spent, is better than half an hour on the roadside.

But we digress…..

:beerjug:
 
I use 1.1 for exactly that reason. I also follow MyRoute’s advice / best practice of having a shaping point every 5km / 3 miles. The transfer and any subsequent recalculation on import onto the device’s screen is then minimal. I also try, whenever possible, to create the route in Here maps. All that aside, I also check the route(s) before using them. Small discrepancies over estimated time / distance I ignore. Anything meaningful I investigate and fix. Five minutes spent, is better than half an hour on the roadside.

But we digress…..

:beerjug:
I noticed this, I was with a friend who had the route I did passed to his garmin in gpx 1.1, here maps and I used 1.2 on my XT, there were slight changes to the route on his device, because the route had been recalculated. My fault as I didn't use enough shaping points
 
This may be a difference with the I-Phone version, maybe they will fuck you over at a later date?

I also binned Explore as soon as I got my XT, so it has nothing to do with that, quite the opposite as it is actually insisting you use Explore now, probably trying to capture the market in route planning, and have all of the data on everywhere you plan to go, do go, how you get there, and how fast you go on the way etc.


Be very careful, I had major issues with 1.2, it was a very frustrating and lengthy journey, quick summary:

I started getting odd directions, detours, constantly asked to "turn around" for no reason, I tried all sorts of things with settings and placed support cals with Garmin and My Route App.....

...And this is where it got weird, as I use MRA for route planning as it is 1000 times quicker and easier than basecamp (and I can zap routes straight from phone to XT) this was how I made the routes, however I then discovered that using basecamp my test route worked OK.

Not sure on the technical specifications of GPX file, but MRA and Basecamp create them differently, and they behaved differently on my XT.

Be very interested in how you get on, if you are using basecamp then probably fine, if not you may get some weirdness, please do keep us all informed on your findings ;-)

One other point to note, because the "shaping points" using GPX 1.2 are not shown when you go into the route on the device it means you cannot edit them on the fly, sometimes I will want to shorten a route slightly when on tour due to weather / time / mood and I can open the route and remove a few points (as waypoints and shaping points show up and can be deleted) but with 1.2 you only see the Waypoints, making this impossible.
I assume you know about the importing issue with MRA into the XT. You have to import, then start the route from the trip planner, then go to the active route and save it. The route then becomes a saved route instead of an imported route and works ok.

Never used Basecamp, have been using MRA since they started. I've used 1.2 on my XT for a couple of years with no issues, but I do not tend to change waypoints on the fly. If I wanted to do that, I would open the route on my phone, change it and then send a new file to the XT, but I've never felt the need, but good points as to why to use gpx 1.1
 
It shouldn’t. Not dramatically at least.

Assuming the route was created and sent from MyRoute’s Routeplanner:

How many shaping points did the route have? MyRoute recommended one every 5km / 3 miles, for transfer to a Garmin device.

Which GPX version did you save and transfer the route in? I find 1.1 very reliable for transfer into my XT, as it transfers with it the blue shaping points and the orange flag way points, which are then displayed on the route on the XT.

Which map was it created in? Here? TomTom? OSM? Something else?

What preference settings are there on the XT which might have forced a recalculation?
It was sent from Basecamp. I still use basecamp for a number of things because the waypoint handling on MRA is still very poor.

I tried it with a few different maps, nothing changed.
 
Back to topic, running the new app:

1. My main iPhone refused to connect with my XT.

2. My sacrificial iPhone (with very few app’s) connected perfectly with my XT. It also transferred routes perfectly, too.
 
Back to topic, running the new app:

1. My main iPhone refused to connect with my XT.

2. My sacrificial iPhone (with very few app’s) connected perfectly with my XT. It also transferred routes perfectly, too.
My phone is an iPhone 12, so nothing new or fancy. Got loads of apps on it though.
 
My phone is an iPhone 12, so nothing new or fancy. Got loads of apps on it though.

I think it is because my main iPhone phone was previously linked to two XT’s and a camper van device, it has always struggled.

The new app maybe also struggles, not least as the phone told me it was connected to the device but the XT reported that it wasn’t.

Anyway, my sacrificial iPhone connects to the new Garmin app, and the new app to my XT. I haven’t yet tried my sacrificial Android phone.
 


Back
Top Bottom