No traffic delay with 3.30 - 755T

 

Garmin support is working on this for me, but wondering if anyone else has noticed the same problem.

After updating to 3.30, I am not getting any traffic delays when on an active route. The icon will change from green...to yellow...to red and 'traffic on route' will show multiple incidents, but there will not be a delay. After downgrading back to 3.10, all is well. I tried this a couple of times with the same result.

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T

Same problem here too...

I had traffic delay times displayed I believe only once since I installed v3.30 but that's it. Other than that one time, I have not seen the delay time displayed next to the traffic severity (red, yellow, green) icon.

--
nuvi 760, nuvi 765T, nuvi 855, nuvi 3790LMT, nuvi 3490LMT - SoCal area

yup

I think I have had it once as well. I'll post if they find anything. They have bumped it up a tech level, but of course have not been able to repeat it, whereas I have. 3.10 I will stay for now since everything seems to work fine with that update.

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T

.

I have not personally tried this yet but you may want to try and disable/turn off ecoRoute and delete your vehicle profile and see if you have the same problem with the traffic delay times not being displayed. As I said in my reply above, I remember the times were displayed once after installing v3.30 but I am not sure that ecoRoute was setup at that time.

I will test this out later on myself and report back.

OK, I tested by resetting user data, thereby disabling ecoRoute, but I'm still seeing the same results. Traffic delay times are still not being displayed next to the traffic button when on a route with traffic on it. Looks like yet another firmware bug-fix is in order. rolleyes

--
nuvi 760, nuvi 765T, nuvi 855, nuvi 3790LMT, nuvi 3490LMT - SoCal area

attempt

I was just about to say that I had not re-entered my vehicle profile after downgrading and upgrading, but you beat me to it with your results. wink

I saw something about traffic in the update profile...maybe that is what caused the new problem.

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T

question for you

Do you only have the free Navteq traffic on your 765T's GTM20?

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T

.

I have two GTM 20's. One with both Navteq and Clear Channel Lifetime subscriptions on it and the other with Clear Channel Lifetime only. Both are exhibiting the same problem with traffic. I also have the MSN Direct GDB 50 but it does NOT have these buggy traffic issues.

Firmware v3.00 prevented displaying of traffic incidents nearer than 6 miles to my current location. v3.30 corrected that issue for me but has now botched up the displaying of the traffic delay times. I have reverted back to v2.50 as it's the only version where traffic works 100% correctly for me using the GTM 20.

I don't know what Garmin is doing with these "updates"...they fix one thing and break two more things. You'd think they'd have enough experience by now with coding firmware but who knows. rolleyes
The 760 had it's own share of issues...now it's the 765T's turn since the 760 has been discontinued.

Changes made from version 3.10 to 3.30:

* Correct error that caused some unique traffic events to have an improper delay associated.

--
nuvi 760, nuvi 765T, nuvi 855, nuvi 3790LMT, nuvi 3490LMT - SoCal area

3.10

Thanks, I have let them know that I am not alone and now can advise that it is NOT because I have Clear Channel and Navteq on the same GTM20. They didn't say it was, but at least I can tell them it isn't. Who knows...maybe it's a Clear Channel problem, they are all powerful.

One would think that they would look at the traffic change they made from 3.10 to 3.30 as the culprit...but who are we to decide that? wink

Did 3.10 cause any problems for you? I have reverted back and stayed with that one as at least the reboot issue was solved for me and it so far seems to be the most stable.

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T

.

craig470 wrote:

Who knows...maybe it's a Clear Channel problem, they are all powerful.

I really doubt that because traffic works just fine on both my GTM 20's using my nuvi 760. Traffic also works just fine using both GTM 20's on my 765 running firmware v2.50. It's only when I go to v3.00 or above that I have traffic problems.

craig470 wrote:

Did 3.10 cause any problems for you?

Yes, I had problems with v3.00 along with v3.10. Traffic incidents closer than ~6 miles were clearly shown on the traffic map but those same incidents were not being displayed under traffic search...they simply did not exist to the unit except on the traffic map. The incidents were verified as being valid by connecting my nuvi 760 to either GTM 20 at the same point in time and also verified using traffic.com (Navteq's online traffic page). This issue was fixed with v3.30 but now the delay times are not being reported.

I am testing v3.30 using my MSN Direct GDB 50 for the next week or so. At least traffic works as advertised (hopefully) using that combination.

Garmin is really having problems keeping things working correctly...2009.11 map issues, traffic issues...it seemingly never ends. I hope they can fix these issues before the 765 is discontinued. rolleyes

--
nuvi 760, nuvi 765T, nuvi 855, nuvi 3790LMT, nuvi 3490LMT - SoCal area

ya

craig470 wrote:

Who knows...maybe it's a Clear Channel problem, they are all powerful.

That was a little CC dig. I am not a big fan of their omnipotence in the media world.

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T

back to 2.50 I go

Well DN,

I thought all was working OK with 3.10 and 3.00 with regards to the traffic issue, but realized something that I had forgotten. I noticed it before but the updates were coming fast and furious that the no delay at all problem took over. Although the delay would show next to the icon, the trip ETA would not adjust as the delay increased or decreased. Thank you, by the way, for providing the links to past updates on the other site. 2.50 works fine in the traffic area and solved most reboot problems that I had so I will stay with that one until MAYBE they will fix the problems they are creating without creating new ones.

--
Garmin Quest/Quest2/Nuvi660/Nuvi755T