New Garmin Zumo XT Review - Updated

#82
"OSM maps"? Do tell... My 478 is stuck at 2019.2 because Garmin determined it was at its "end of life" and my "Lifetime" maps will no longer update.

Although it only caused minor irritations during the '21 IBR, that was only because I was also running Waze and Google Maps side-by-side on a 7" android tablet. (When there was a disagreement, I went with the majority)

I would love to be able to get more current maps on the 478, even if they are occasionally inaccurate for speed limits (which are not displayed on the 478)....
openstreetmaps.org

I was going to use them for a planned B2B ride starting in Matamoros, MX. Mexico is not part of the installed maps of the ZumoXT. Since Matamoros is not known as a friendly area I wanted to be sure to get in/out as quickly as possible. Downloading that small area of routable streets is well within OSMs ability. But from what I saw of their routability I am a little skeptical of using it on a large scale. YMMV

Hope this helps.
 
Last edited:

WY88

Premier Member
#83
I currently run a Garmin 660, 2 actually, guess they are the "horse and buggy to modern day GPS units", since I just purchased a Fire Creek Aux Tank for my Wing, the Zumo XT will be a little down the road, but not too far. I've learned a lot from this thread, thank you all.
 
#84
Although it only caused minor irritations during the '21 IBR, that was only because I was also running Waze and Google Maps side-by-side on a 7" android tablet. (When there was a disagreement, I went with the majority)
I had some disagreements with some of the routing choices of the ZumoXT a few times and ended up using Waze to resolve the issue. One incident of great note was when she wanted to route me 40+ miles out of the way to avoid a road closure. Mind you that that road closure was the I-40 bridge across the Mississippi River at Memphis, TN. Another incident was in Washington DC when all traffic was diverted off of the Beltway for some reason. Garmin didn't understand why I diverted to surface streets and wanted me to immediately get back on the Beltway. Waze immediately understood what was happening and routed me to another part of the Beltway (after allowing me to bag the Bonus). In both instances Garmin finally got the gist of what was going on and followed suit. My main issue with Waze is that I am running it on a 1st Gen iPhoneSE so the 4.0" screen is very small.

I like the idea of the SmartDevice based navigation aids due to their ability to receive updates from other users in near realtime. But I don't have a large enough screen on my current device nor do I have touchscreen friendly gloves for that not-large screen. Maybe in the future I could have nice things but for now the XT is 'da bomb'!
 

Stephen!

Flivver Flyer
Premier Member
IBA Member
IBR Finisher
#85
I like the idea of the SmartDevice based navigation aids due to their ability to receive updates from other users in near realtime. But I don't have a large enough screen on my current device nor do I have touchscreen friendly gloves for that not-large screen. Maybe in the future I could have nice things but for now the XT is 'da bomb'!
A 7" WiFi Android tablet can be had pretty cheap, relatively speaking. Unlike apple devices, you do not need the more expensive cell-enabled version to get a GPS chip. Use your network enabled device as a hotspot for connection to the interwebs. A tethered stylus makes manipulation pretty easy without removing your gloves, when safely parked alongside the road, of course... :p
 

Greg Rice

Premier Member
IBR Finisher
#86
Follow-up to mapping issues in the Big Bend area of Texas:

Garmin Tech Support suggested that the Aftermarket maps I had installed might be causing the issue. (I had OSM maps of Mexico installed for a potential trip there.) Since I had not planned on revisiting the Big Bend area in the near future for testing they marked the ticket Closed with the option to reopen it at a later time.

During the IBR I did have the chance to revisit the Big Bend area so I tried Garmin's troubleshooting of disabling the OSM maps. When I did that the mapping issue went away. Reenabling the OSM maps brought back the issue. So Garmin's Tech Support was correct that the OSM maps were the issue.

I have disabled the OSM maps for now and will probably remove them as the trip to Mexico is on hold now.

I hope this helps anyone else that may have this issue.
Thank you the update. I was a little curious as to why you was having that issue.
 

kerrizor

Premier Member
IBR Finisher
#87
A weirdness that I've seen.. I run with the "Cities Ahead" panel showing, which shows not just cities but rest areas (along interstates, mostly..) Sometimes it seems to get "stuck" showing "Rest Area" as the next "city" on the list, refusing to update the list without restarting the unit. It seems to happen most often along stretches where rest areas/waysides aren't explicitly named - as a software engineer, I assume there's some name collision bug happening, but either way, a minor annoyance, for sure. It doesn't happen often, but when it does I roll my eyes and think "oho its doing THAT thing again.."
 

Marc11

Premier Member
IBR Finisher
#88
My XT just went back to Garmin for replacement, the screen would automatically select options, cancel routes or route to new places in the rain. Seems the rain drops caused ghost inputs.
 

biquer

Premier Member
#89
Mine has reacted to raindrops since the start, others on the Zumo forums have reported this as well. I don't think a change of screen will help. I tilted mine slightly more forward and its ok now. 2 of us were out recently and were routing point to point for a photo rally. 2 XTs. At one point in a maze of narrow roads both XTs literally took us round in circles, back to where we started. We had to resort to a Tomtom to get us out. Both XTs were set to fastest route. At one point farther on it routed us on motorway (interstate) which we knew was not our original plan, but we assumed the motorway would be faster. When we reviewed it that evening it had added over 40 miles to a 110 mile trip. There's no way that was a faster route, it was just wrong. The XT is a great tool, but it's not the Nirvana in GPS we all seek!
 

rneal55555

Premier Member
IBR Finisher
#90
So it seems as though an plastic bag is in order. Although it's been out long enough now you'd have thought we'd have heard of this before now. (or maybe I just wasn't paying attention)
 

Marc11

Premier Member
IBR Finisher
#91
I cannot accept that rain triggering screen inputs is normal or acceptable. I'll see what happens with my replacement unit, but in my having owned Garmin units for years, including BMW branded units, as well as my current BMW VI unit this has never been an issue.

I won't accept it as normal nor will I cover the unit or tilt it down out of the rain. It's a design flaw for sure if it persists.

I agree something is off with the XT routing, on a recent trip the XT was off by over 100 miles compared to google maps. I was able to get it close by selecting shortest distance vs fastest route, but still at times it was a few miles different.
 

SteveAikens

Premier Member
IBR Finisher
#92
Hmm.
Trying to understand why I'm not seeing this problem with rain.
Recently here in NM, we've been having serious rains, and as luck would have it, our ride to Provo started in a real frog strangler for just under 100 miles.
My XT never even blinked in the rain.
 

biquer

Premier Member
#93
Its not just Garmin, my Tomtom Rider 550 does it also, however, you can adjust the sensitivity of the Tomtom touch screen. My XT is an early one, they may have fixed it? The last example I've read about was December 2020. The placement of the unit on the bike and the type of bike will of course determine each units exposure. There are also instances of water ingress and failure of the screen. All of the cases I've read have been met with immediate, prompt replacement by Garmin, so kudos to their customer service.
 

Marc11

Premier Member
IBR Finisher
#94
Its not just Garmin, my Tomtom Rider 550 does it also, however, you can adjust the sensitivity of the Tomtom touch screen. My XT is an early one, they may have fixed it? The last example I've read about was December 2020. The placement of the unit on the bike and the type of bike will of course determine each units exposure. There are also instances of water ingress and failure of the screen. All of the cases I've read have been met with immediate, prompt replacement by Garmin, so kudos to their customer service.
That was same for me. I contacted support for my unit purchased in early 2020 and with in 5 minutes I had an link to send in my unit for a replacement. Great service.
 

Shawn K

Professional Cat Confuser
Premier Member
#95
I thought I read somewhere that the Zumo XT now utilizes a capacitive touchscreen instead of a resistive touchscreen (like older models). If so, that would explain rain issues, as capacitive touchscreens can be affected by the conductivity of water.

Can anyone confirm? I may be wrong.
 

Marc11

Premier Member
IBR Finisher
#96
I thought I read somewhere that the Zumo XT now utilizes a capacitive touchscreen instead of a resistive touchscreen (like older models). If so, that would explain rain issues, as capacitive touchscreens can be affected by the conductivity of water.

Can anyone confirm? I may be wrong.
If true that would be an epic fail and render the unit useless to me, it would also surprise me with how swiftly Garmin arranged an exchange.
 
Last edited:

Shawn K

Professional Cat Confuser
Premier Member
#97
If true that would be an epic fail and render the unit useless to me, it wod also surprise me with how swiftly Garmin arranged an exchange.
I just confirmed that the Zumo XT does, in fact, use a capacitive touchscreen. Prior generations use resistive touchscreens.

To me, that goes a long way toward explaining wet performance. All those people bleating for years about how they "needed" a higher-res screen (why??) got their wish with the XT, but it came at a cost. You want high-res, you have to go capacitive.

From Garmin's website:

Screenshot_20210715-205358_Chrome.jpg
 
Last edited:

Steve Gallant

Premier Member
IBR Finisher
#98
I can confirm the rain definitely affected the screen for my new XT as well, during the IBR. Pretty annoying. That, plus the extremely flaky routing algorithm it is using (compared to 1. Google Maps, 2. My trusty Zumo 350, and 3. My own local street knowledge in my home area) has not inspired much trust for me in my very good-looking new toy. I ended up disregarding the XT routing more times during the rally than trusting it. I hope Garmin updates the routing software soon.

In addition, so far the excellent weather/traffic integration has been useless to me because the Drive phone app (on Android) completely takes over phone call voice routing, even if you disable that function in the app (I prefer to run the phone calls directly from phone to Sena). Calls are static-filled and hard to hear, forcing me to completely disable the BT connection between phone and GPS during the IBR.

All in all, so far the unit has been a functional disappointment. :(


If true that would be an epic fail and render the unit useless to me, it would also surprise me with how swiftly Garmin arranged an exchange.
 

Marc11

Premier Member
IBR Finisher
#99
My replacement will be here Wednesday. Hopefully Garmin has made a screen calibration change or something.

I've solved 99 percent of the odd routing issues and the phone and app issues are new just started happening during the last few days of the IBR. Hopefully that's a bug that Garmin corrects because it was a huge pita.

There is a mega thread on Adv about the XT and these issues aren't really being discussed, makes me wonder if they are isolated or if we are edge use case users.
 
Last edited:

SteveG

Premier Member
IBR Finisher
My XT also had some odd screen issues in the rain during the IBR - although by the sounds not quite as bad as Marc's. At the time I attributed the "ghost" inputs to my tank bag cover billowing in the wind and possibly brushing against the bottom side of the screen.
I concur with Steve though, that the connection of cell-to-GPS is worthless as it seemed to have connection issues and call quality was worse that direct phone to headset connection. I also use Siri voice commands which didn't want to work when connected through the GPS.
My final setup for the IBR was to connect the GPS to a cell-enabled tablet for the smart data (traffic) and connect my cell phone only to my headset. But even with the dedicated device (tablet) feeding smart data to the XT, the Drive app still needed restarted a few times.
For me, the screen is really the only redeeming quality and reason for keeping the XT. My old 595 has 99% of the same functionality, plus TPMS, if only the screen would be better.