Navigation

FAQ: what are the bugs in the current (2.70) Quest 2 firmware?

Every computerprogram has bugs, MS Windows, Linux, your car's electronics and thus the Quest firmware. Here you will find a list of all bugs that I know of. If you know more, please report them to Garmin and also mail the to me: .

SERIOUS? After loading some topo maps to the extra 512MB of memory on the Quest2, it seems like I can't search for addresses any more... which I would expect from topo maps, but CN8 NT is still loaded and enabled. I can however still search for cities on CN8NT or for POI's. Only the address search is always giving "No Matches Found" even without entering anything. When searching for an address, the search starts at the "in what city is the address" instead of the region selection. This also indicates that the Quest2 is looking in the loaded Topo maps, instead of in the CN8 NT maps. Update: reloading the Topo mapset resolved the problem... but this should never happen anyway. The same error happened after the firmware update from 2.40 to 2.50.

Annoying. Map screen redraws are somtimes very slow (5 to 10 second range!), using less custom POI's or disabling the proximity alarm does not speed things up (much).

Annoying. While geocaching with the Quest the rounding of the distance above 15 meters is annoying. Up to 40 or 50 meters it is no problem, since you are guided by the compass arrow. Below 30 meters the compass arrow is either too slow to update (logical, since the position is averaged) or does not point in the right direction at all for some time. You thus need the distance to the geocache/waypoint, so you can move around and see in what direction the distance decreases. This is almost not possible until you get below 15 meters and the distance is not rounded, but is shown per meter. My suggestion would to either not round the distance below *30* meters in general or not round the distance at all in off-road mode.

Annoying.The only way to use a track downloaded from the internet (for a motorbike tour as an example) is to rename it to ACTIVE LOG and do a trackback. You can also only trackback the most recent track. This is a clear disadvantage over other units... Is it possible to upload tracks with other names to the Quest and select that track for trackback? See HOWTO: converting tracks into routes and use them as tracks for a nice work-around.

Annoying. Making a U-turn while driving on-route (of an active route) initiates a non-prompted recalculation, even if it is set to ask before recalculating. Going off-route on the same route will prompt as usual.

Annoying. The mapping between the custom waypoint icons on the Quest and in Mapsource is correct, but the actual waypoint symbols are not transferred. You still need xImage and some renaming to do this... otherwise you will not see your custom symbols in Mapsource.

Annoying. Uploading a waypoint with the Garage symbol to the Quest 2 from Mapsource (6.9.1) will reset the symbol to the default black dot. Downloading a Garage type waypoint from the Quest 2 to Mapsource will retain the correct symbol.

While searching an address, the list of countries has two entries for each country... one in english and one in the local language. It doesn't matter which of the two names of one country you select though. Could be intentional though.

The background of the zoom indication and mapsource/overzoom indication remains the land color, even when that piece of the map actually is water. The user would think there was a piece of land there, but ofcourse could never reach it. =8-)

When 'Hide above' is set to 'Auto' (in Map Setup, Point tab) for My Locations, the My Locations are never hidden, no matter how much you zoom out.

All my Garmin devices were obtained from / al mijn Garmin toestellen werden geleverd door:

Waypoint Notter

MySQL: 0.0039 s, 6 request(s), PHP: 0.0151 s, total: 0.0190 s, document retrieved from database