upd/04/25: most of this review gets outdated as old issues get fixed, which is good. What is not so good is that routing (with TrafficTrends on) became way too conservative. At nighttime on local streets it's not uncommon for for the unit to give a 20-minute estimate on a 12 minute route. It looks as if the "trends" are not granular enough to separate day and night. Time estimate is also very conservative on highways. I am not an aggresive driver, but even for me highway travel times are way too pessimistic. HD traffic coverage is still virtually non-existent outside of NYC and few other areas. Just to give an example, there is no traffic coverage pretty much anywhere on I-87 from NYC to Canadian border. To be fair, things are much better on I-91 in Connecticut and quite good in NYC.
All in all, after using 3490 for >6 months now I am still holding to my initial opinion: this is is the best thing Garmin has done since 25x and 75x series since everything in between was just a sad joke. On the other hand, I still find that those older models do a better job in many situation and the software is definitely way more stable on older units. Other than that, 3490 is cool and fun, unless you want to sacrifice some screen resolution but get a bigger screen with 2595
upd 01/18: it looks like after 3 months of delay, "Unable to calculate route" error was finally fixed with firmware version 4.4.
Also this update introduced something called "smartphone link".According to description, it connects to Android phones and brings Live traffic for $20/year and fuel prices for $10/year. Tried it once so far - very easy to set up, just have to download the app and connect via bluetooth. Traffic data seemed to different from what is coming through HD and showed a some highways as closed while they were not. One annoying "feature" is that when smartphone link is in use, all calls are forwarded to the Nuvi, which is sort of redundant.
The rest is the review as of November.
"Best Garmin" doesn't mean perfect. It's a new model, so bugs are visible every day. It fails to calculate pretty much every route from Brooklyn to Manhattan due to (what it seems to be) a mapping bug on one of the highways. So I have to drive up to the critical point and navigate from there. I've seen people having similar problem in other parts of the country and this also is an issue with other models from the new line-up (tested on 2495). My expectation is that this will be fixed soon as it's not really acceptable. Upd: as I've said - fixed in firmware v 4.4
Update to 3.6 also introduced a curious bug where the unit occasionally reboots itself if I miss a turn.
I also had problems registering it because Garmin communicator plug-in couldn't see it on my PC. If you have the same problem, it should be easily solvable, see comments to this post.
Sometimes it also restarts during voice recognition. No big deal, really.
Map detail is still inadequate. In 2D view most highways will not be labeled, which makes selecting a point on map a very painful, if not impossible task. Old pre 1xxx Garmins have better map detail and I still much prefer 255W for long-distance drives. Especially given that it has better traffic coverage.
That said, I actually like 3490 way more then I expected and I think it's a great unit. The UI has been re-worked and simplified compared to the chaotic mess that Garmin has been doing for the last 2-3 years. It's almost as easy to use as old Nuvi's from 200, 600 and 700 series, but has a much richer functionality. (Ok, the UI might not be immediately straightforward and I had to explain customer service rep how to turn GPS simulation mode on, but once you get used to it, it feels great and gets better with time)
One of the best features of 3490 is the ease of input. You don't have to suffer through entering the state and the city anymore. Just type the street and the house number and it will search for the address in nearby cities and states, will give you a list of choices , and only if you don't see the one you're looking for, you can type the city and state. For someone who has to commute between two states (like NY and NJ) that would be a nice relief. Also, while you type, it offers several matching street names to choose from. The only strange thing is that the matches don't seem to depend on your prior searches, e.g. if you recently searched for "Broadway" and start typing "B", you'll have to type all the way until "Broadw" before "Broadway" shows up. TomTom (I own 2535) would give it right away.
POI search is also simplified (even though it's hard to imagine that POI search on Garmin can be made simpler). Many weird GUI solutions made in earlier versions are now re-worked into something that gives you a very pleasant experience. POI categories are even more clearly defined, restaurant types have even more sub-categories and you can also search POI by simply typing (or saying) the name. Also what's important, POI search is very fast, great improvement compared to older versions.
You still have an option to choose "poi near destination", "poi near active route", etc, and selecting those options is also much easier than on units released in the last couple of years. "Poi near active route" option was re-worked and it feels like it's integrated with the new "exit services" feature. If in the past you would get a list of, hotels, with distance, now it would group them by highway name and exit number and for the nearest ones will give the distance to the exit too. I have to note here that I had at least one case where with all the bells and whistles and the new UI, the closest gas station it could offer along the route was 10 miles away and required additional 10 minutes of travel time, while my pre-historic 255W with same map version offered a gas station that was 1 mile away and required a 2-minute detour.
Another item that was re-worked significantly is adding a via point. It now seems to be integrated with trip planner, so when you try to add a new point to your route, you can re-shuffle the order of destinations. The downside of it, as some people complained, is that if you browse a map, it might only show you the first leg of the route (as always, not clear why). This doesn't seem to be a big issue and if while planning you select "routes" you will be able to see the whole route on map during the planning stage.
Speaking of this, yet another awesome feature of 3490 is that it offers you several routes to your destination and you can pick the one you like. Not just "route A, route B" as it showed up on 3790 and others, but more like Google maps or Navigon. A grain of salt is that when displayed on the map, the colors for alternative routes do not take into account current map scheme, so in some color schemes they are pretty much invisible as their color may be very similar to the colors of highways and interstates. There is also no way to see the alternatives in text format.
Now, the most important piece - the routing. They made really a quantum leap and a great break-through there. For the last 3 or 4 years Garmin was way behind TomTom in terms of navigation in big cities and failed to account for historically congested roads and delays due to traffic lights. Last year Garmin rolled out TrafficTrends as a response to TomTom's IQRoutes. It's been a complete disaster as you can read in multiple reviews. After all this time I was surprised to see that TrafficTrends actually do work on 3490. The estimated arrival time and routes in NYC have been improved dramatically. I am driving with 3490 alongside TomTom 2535 LIVE and I can't really say that one unit is much better than the other. It's pretty much a tie where TomTom probably maintains slight lead. Route calculation times on Garmin are not bad, but recalculation while driving is sometimes much slower than on TomTom. There may be situation when recalculation takes a while. It's mildly annoying as you might miss an exit or a turn, but doesn't happen too often.
Just to give you some idea how the routing works in NYS.
On my test routes that includes Manhattan, Queens and Brooklyn I've got
1) estimated 35 min, actual driving time - 45
2) estimated 28 min, actual driving time - 43 (7 minutes unreported bridge traffic + 6 minutes traffic lights)
3) estimated 36 min, actual driving time - 41
4) estimated 17 min, actual driving time 15.
This timing is with enabled TrafficTrends (TrafficTrends are by default disabled on this unit)
Traffic. I see a lot of people complaining about it. In New York and around the city everything works pretty well. There doesn't seem to be much traffic signal out of the city and when I approach a city it seems to get the signal later than either TomTom or my old Garmin. Outside of NYC I've seen virtually no traffic coverage on this unit. Haven't gone far enough, at most 6-7 hour drives. Regular FM does a much better job.
On a positive side, in the city traffic acquisition is immediate, thanks to HD radio traffic. Feels almost like Live units, but requires a cable to be plugged in.
Of course, initial acquisition is only a part of the picture and mostly matters when you start driving. While on your way, it doesn't matter too much if update frequency is 30 sec or 2-3 min like on devices with FM receivers. What matters more is the quality of information your traffic provider gives you. I've seen a case when TomTom's HD Traffic correctly indicated that there is an 8-minute traffic on a local street in Manhattan while 3490 tried to route through this street. I've also seen my old 255W (with double Navteq + TTN subscription) showing a better highway traffic coverage.
Read more ›