Zumo User Forums

jfheath wrote: ↑Sun Jun 14, 2020 5:07 am It managed to show my current position, but that didnt change so I am not sure how it obtained that.

I just read it on Garmin's site that the position in Explorer updates every 10 minutes if data connection to the XT via your phone is available. Never tested it though, I'm not using live track.

Done it with iPhones, but never tried with Android.

Basically if you have the Garmin Drive app running, you can share your route file to it (Garmin Drive) from your choice of routing app and it will be loaded in the correct directory on the XT.

mzeist wrote: ↑Fri Jun 05, 2020 6:25 pm

Ray N. wrote: ↑Fri Jun 05, 2020 11:45 amAnother difference is that the audio out on the XT is only bluetooth or internal speaker.

but the internal speaker is not loud enough on a (my) motorcycle (ST1300 Pan European, so no loud pipes)

The internal speakers were never designed to be heard ON the bike. It is for car use.

Tac wrote: ↑Tue Jun 09, 2020 4:18 pm I think this problem started with the 2.7 firmware update. I'm sure the change of speed limit alarms could be turned off before the update.

Not with Australian maps. The issue was there out of the box, as it came from Garmin.

Iris wrote: ↑Sun Jun 07, 2020 9:11 pm Maybe I missed it somewhere...

Yup, you have, page one of this thread. I have a full list of all audio settings.

Roundabout design speeds vary a little but 30 kph is actually about right. It’s not Garmin making it up, it’s highway design standards so, there doesn’t have to be an actual sign for them to apply the warning. This may well be the case, but I can tell you that in Australia, the XT does not warn for...

Yeah, same here. I used yesterday a modified theme too for a 370 km ride without any issues. The bit about not finding the XT is a worry, but the USB port change advice is good. Let us know how you go.

I was one of the first ones in Oz to upgrade. No regrets at all.

Just checked it for the oz shop. 6 to 8 weeks processing time. Looks like you are not alone in Canada with this.

In your case the fact you had to use MS Fix It points to an issue at your end. Even after a fresh install of Win 10 on my Surface Pro, the issue still existed with every update version going back at least 5 years. Fixit seem to suggest that the problem was with a corrupt uninstaller, so assuming th...