3790t fix for slow route calculation.

Try a hard reset after any FW change, or map update. That's what seems to make the real difference.

It's what many here do.

I always do a hard reset after an upgrade or downgrade but that never fixed the slow route calculations. What I wrote up was a fix for me that others can try if they share the same symptom.

Well then, thanks for that tip!

Something is missing here, I have a 3760 and trends is working and I get a route in about 5 seconds unless I'm going from two big areas like inner city Baltimore and inner city DC. Then it can take 20-30 seconds.

Where I have a problem, and have always have with different nuvis, is that when I'm on a route and showing a traffic screen it fails...nothing...run out of RAM etc.

Sounds like a hard reset might clear your problem. Have you tried one?

Thanks for sharing that information. I'll keep in mind if I come accross any lagging in my calculation time for my 3790.

Yea, several, a few times on my own and one with Garmin customer support. It's not just me, I know a few others that have the same one, couriers and all. Please remember I mentioned routes with many turns. I'm talking about 15 or more, with less it works fine.

I think these PNDs are minimum deals as far as components,kind of why I wish Garmin would make an Android application.

I just returned today from Philadelphia to central Virginia through Baltimore and DC, and my Nuvi 2360 took to constant recalculations during the trip so much that it became unusable. A recalculation would start for no apparent reason, take 10-15 minutes or more to get to 99%, freeze there, finally finish and show me the route for a second or so, then start recalculating again. I finally turned it off, but then tried again later because of the usefulness of the traffic reports even without a working route (plus my wife was driving and I was getting bored!). I finally turned off trafficTrends and myTrends, after which it worked well (I did not delete the database). My theory is that these complex metropolitan areas along with active trends databases just becomes too much for the Nuvi, and results in program thrashing (an old IT term where if a processor has too much to do it ends up doing nothing at all). I haven't reset it yet, although I did after the last map update back in February. Any comments? Thanks, DaveD

Try clearing the log as well.

When I was finding long calculation times on the 3790 I found that turning trafficTrends off fixed the issue. Turning myTrends off had no effect on the calculation time.