I assumed I smoothed out all the issues, but nope.
I don't road-ride that much in the UK so, unfortunately, all the gremlins are noticed when I travel abroad, so that makes it worse.
Anyway, in a couple of shortish rides in the UK, I noticed that the Zumo would try to route me away from the intended route (fairly standard, and I place shaping points every few miles just to be sure it follows + I always have the underlying track for reference if it veers off) and along the way every once in a while it tries to force you off the main road taking some secondary road behind some housing, just to rejoin the main road a few hundred yards later.
In a couple of multiple clustered roundabout it wanted me to do a "pinball" pattern instead of following the route (I could see the track) for no reason.
No biggie.
In Spain (.gpx file you have on my trip report) I encountered a few issues:
1st segment (Bilbao to Potes). Despite me having created two or three waypoints in case we had to restart the route midway, in order to have them as potential starting points, they didn't appear on the selection screen at the start.
Additionally it wasn't able to calculate at all if I selected "closest entry point".
Apart from this, when we started the route and it was navigating us to the beginning of it, it kept trying to push us across side roads, doing some nonsensical detours.
Even during the route it would give spurious indications here and there in between shaping points.
Had to stop/restart routing a couple of times because of this weird calculation, and the fact that it wouldn't find closest entry point it made it more difficult an frustrating (hence the "launch").
It is set to "fastest route" and the only avoidance is gravel roads.
Maps are updated. Latest firmware update.
Again when around Potes on the second day, it would try to send us up single track roads more than once instead of following the main road (that was the shortest and fastest route to the next point).
I've noticed some signs around Potes over GPS issues so I assumed this was mapping errors.
Third or fourth day, we had to detour from our route and retreat to the hotel we booked because of heavy rain.
A to B navigation. We just selected the hotel waypoint and pushed go. Keep in mind both bikes have a Zumo XT. Same gpx files used, same firmware.
I check the proposed route (I always do) and, as logic dictates, it's mostly motorway and then B roads for the last 15/20 miles to the hotel.
I get on the motorway and start riding.
After the first motorway junction, correctly indicated, I keep going and see that the next exit is in 60km. Seems a lot but I don't give it much importance.
After a few miles my mate start closing up to me and, via the intercom asks me why I skipped the exit.
At this point I check the route and notice that the Zumo changed its routing and is sending me all over to the coast, then criss-cross on some very small (not visible on the map at that zoom level) roads all the way to the hotel. The total mileage for this is about 4 times what the initial route was.
We stop. I stop the routing. Re-start it and it's correct again, we manage to get to the hotel without riding 5 hours in the rain.
On the last day I had the usual straight lines across shaping points, but to be fair those would recalculate while approaching the shaping point itself.
But... bottom line is, I don't find the XT a trustworthy device.
I have to second guess every turn it tells me to do. In Italy more than a few times and made me get out of a motorway, just to go around the roundabout after the exit and rejoin the motorway.
The shit it pulled on the rainy day above alone was infuriating.
Last year I had to ride 100 miles on the bike while fairly sick before reaching an hotel (and spend the next 24 hours in knocked out in bed) and a trick like the one it pulled above would have not been appreciated.
I'm reading and asking on Zumoforum as well. And it seems like the XT has some flawed calculation algos... and has some issue calculating stuff "behind you". Maybe the reason why the XT2 is a completely different device software-wise?
At this stage, I'd rather "navigate" tracks. Something the Montana would do.
I already use the sat nav as an improved paper map, sort of...
I don't mind losing the bluetooth integration too much.
I use a Cardo. Command the music from my phone via Siri, answer the (rare) call with a button.
All of Zumo does in the picture is mess up the volume levels and - somehow - hang up calls when they happen (work fine without the zumo in the picture).
I'd miss the data integration (traffic, weather) because that one seems to work more than ok.
Also: I wouldn't mind profiles. I regularly use a GPSMap 64s and I'm quite used to the logic of the "standard" sat navs from G.
I don't road-ride that much in the UK so, unfortunately, all the gremlins are noticed when I travel abroad, so that makes it worse.
Anyway, in a couple of shortish rides in the UK, I noticed that the Zumo would try to route me away from the intended route (fairly standard, and I place shaping points every few miles just to be sure it follows + I always have the underlying track for reference if it veers off) and along the way every once in a while it tries to force you off the main road taking some secondary road behind some housing, just to rejoin the main road a few hundred yards later.
In a couple of multiple clustered roundabout it wanted me to do a "pinball" pattern instead of following the route (I could see the track) for no reason.
No biggie.
In Spain (.gpx file you have on my trip report) I encountered a few issues:
1st segment (Bilbao to Potes). Despite me having created two or three waypoints in case we had to restart the route midway, in order to have them as potential starting points, they didn't appear on the selection screen at the start.
Additionally it wasn't able to calculate at all if I selected "closest entry point".
Apart from this, when we started the route and it was navigating us to the beginning of it, it kept trying to push us across side roads, doing some nonsensical detours.
Even during the route it would give spurious indications here and there in between shaping points.
Had to stop/restart routing a couple of times because of this weird calculation, and the fact that it wouldn't find closest entry point it made it more difficult an frustrating (hence the "launch").
It is set to "fastest route" and the only avoidance is gravel roads.
Maps are updated. Latest firmware update.
Again when around Potes on the second day, it would try to send us up single track roads more than once instead of following the main road (that was the shortest and fastest route to the next point).
I've noticed some signs around Potes over GPS issues so I assumed this was mapping errors.
Third or fourth day, we had to detour from our route and retreat to the hotel we booked because of heavy rain.
A to B navigation. We just selected the hotel waypoint and pushed go. Keep in mind both bikes have a Zumo XT. Same gpx files used, same firmware.
I check the proposed route (I always do) and, as logic dictates, it's mostly motorway and then B roads for the last 15/20 miles to the hotel.
I get on the motorway and start riding.
After the first motorway junction, correctly indicated, I keep going and see that the next exit is in 60km. Seems a lot but I don't give it much importance.
After a few miles my mate start closing up to me and, via the intercom asks me why I skipped the exit.
At this point I check the route and notice that the Zumo changed its routing and is sending me all over to the coast, then criss-cross on some very small (not visible on the map at that zoom level) roads all the way to the hotel. The total mileage for this is about 4 times what the initial route was.
We stop. I stop the routing. Re-start it and it's correct again, we manage to get to the hotel without riding 5 hours in the rain.
On the last day I had the usual straight lines across shaping points, but to be fair those would recalculate while approaching the shaping point itself.
But... bottom line is, I don't find the XT a trustworthy device.
I have to second guess every turn it tells me to do. In Italy more than a few times and made me get out of a motorway, just to go around the roundabout after the exit and rejoin the motorway.
The shit it pulled on the rainy day above alone was infuriating.
Last year I had to ride 100 miles on the bike while fairly sick before reaching an hotel (and spend the next 24 hours in knocked out in bed) and a trick like the one it pulled above would have not been appreciated.
I'm reading and asking on Zumoforum as well. And it seems like the XT has some flawed calculation algos... and has some issue calculating stuff "behind you". Maybe the reason why the XT2 is a completely different device software-wise?
At this stage, I'd rather "navigate" tracks. Something the Montana would do.
I already use the sat nav as an improved paper map, sort of...
I don't mind losing the bluetooth integration too much.
I use a Cardo. Command the music from my phone via Siri, answer the (rare) call with a button.
All of Zumo does in the picture is mess up the volume levels and - somehow - hang up calls when they happen (work fine without the zumo in the picture).
I'd miss the data integration (traffic, weather) because that one seems to work more than ok.
Also: I wouldn't mind profiles. I regularly use a GPSMap 64s and I'm quite used to the logic of the "standard" sat navs from G.
Last edited:





This is testing Myroute app against the XT but you get the idea. No judgement of my 1980's music preference 







