Changes made from version 6.30 to 6.40:
Improved map and content transfer speeds.
Improved software stability.
Nuvi 34xx v.6.40 Released
Mon, 05/14/2012 - 2:02pm
 |
  3 years
|
new & interesting places for your GPS
|
|
NavigationActive forum topicsUser login
Popular contentWho's onlineThere are currently 5 users and 50 guests online.
Online users
|
Custom POI's still bad?
I'm assuming the custom POI situation remains the same as I haven't found any favorable results being reported yet with v.6.40?!?!
Garmin: GPSIII / StreetPilot / StreetPilot Color Map / StreetPilot III / StreetPilot 2610 / GPSMAP60CSx / Nuvi 770 / Nuvi 765T / Nuvi 3490LMT * Pioneer: AVIC-80 / N3 / X950BH
just in case ...
... I think I'll stay away from this one ...
--
it's the dog's fault
Garmin nuvi 2455 - nuvi 2555 for my other car - nuvi 350, 260 (spares) - my other toys: iMac G5, MacBook, Mac OS-X 10.6.8 and my best friend, Mayhem - a 2009 Harley-Davidson Superglide - and his Garmin nuvi 2455. The dog's name is Punky.
Still Broken
Hindsight is 20/20 but I wish I still had v6.20 stashed somewhere so I could revert back.
"Primum Non Nocere" 2595LMT Clear Channel and Navteq Traffic
Great update. The speed of
Great update. The speed of the route calculations and recalculations is vastly improved.
As stated before we need to stop talking about the brokens and let Garmin know that we want a fix for the POI issue immediately.
Garmin is going to deny that firmware version 6.30 broke Custom POI by sub-category on the following units 34xx, 35xx, 24xx and 25xx series until enough Garmin users call them or email them to tell them to fix it soon.
Monday–Thursday: 8 AM–6 PM, Friday 8 AM–5 PM Central Time (closed holidays)
Phone numbers:
U.S.: 913-397-8200
U.S. toll-free: 1-800-800-1020
Email:
https://support.garmin.com/support/searchSupport/escalateFor...
Lets get all the Garmin users to start contacting tech support to see if we get results quickly.
finally Garmin has
finally Garmin has acknowledge that the POI sub-category is broken;
Here is an email I got from Garmin:
Thank you for contacting Garmin International. I would be happy to help you.
We are aware of this issue and are working towards a resolution. I do not have an expected date at this time for a fix.
Please check WebUpdater for software updates as this is how the fix will be released.
Great, hope they release a
Great, hope they release a fix for my 2555
Garmin 2555lmt
yea new map
alright new maps
Finally maybe a fix
finally Garmin has acknowledge that the POI sub-category is broken;
Here is an email I got from Garmin:
Thank you for contacting Garmin International. I would be happy to help you.
We are aware of this issue and are working towards a resolution. I do not have an expected date at this time for a fix.
Please check WebUpdater for software updates as this is how the fix will be released.
That's good news! Finally maybe a fix soon!
Staying @ v.6.20 for now.
Let's hope it's in the next f/w update and not three down the road! I want to update for the other reasons listed but hate to leave v.6.20 until the fix comes through.
Garmin: GPSIII / StreetPilot / StreetPilot Color Map / StreetPilot III / StreetPilot 2610 / GPSMAP60CSx / Nuvi 770 / Nuvi 765T / Nuvi 3490LMT * Pioneer: AVIC-80 / N3 / X950BH
Also received similar email from Garmin Tech Support
finally Garmin has acknowledge that the POI sub-category is broken;
Here is an email I got from Garmin:
Thank you for contacting Garmin International. I would be happy to help you.
We are aware of this issue and are working towards a resolution. I do not have an expected date at this time for a fix.
Please check WebUpdater for software updates as this is how the fix will be released.
I received the same email in response to reporting this issue. Have to believe that they are now working on it and we'll eventually see an update to correct it.
"Primum Non Nocere" 2595LMT Clear Channel and Navteq Traffic
we seem to have Garmins attention
I emailed about the custom poi issue and they asked for specifics about my poi file setup. I do think we've got their attention.
.
It does work but only if you use the proper file & folder structure when building the files. It worked just fine in the past but they broke it by fixing it? Crazy
nuvi 760, nuvi 765T, nuvi 855, nuvi 3790LMT, nuvi 3490LMT - SoCal area
Workaround
It does work but only if you use the proper file & folder structure when building the files. It worked just fine in the past but they broke it by fixing it? Crazy
So what's the workaround? Is it making individual folders for each category?
v.6.40 no longer available?
This firmware update seems to have been pulled by Garmin.
http://www8.garmin.com/support/download_details.jsp?id=5303
Garmin: GPSIII / StreetPilot / StreetPilot Color Map / StreetPilot III / StreetPilot 2610 / GPSMAP60CSx / Nuvi 770 / Nuvi 765T / Nuvi 3490LMT * Pioneer: AVIC-80 / N3 / X950BH
Only problem is, v6.40
Only problem is, v6.40 didn't break the POI sub-categories, v6.30 did. Makes you wonder what the issue was with v6.40 that made them pull it. Wish they would tell us! I will say I have had a nagging feeling that the auto-dimming feature has seemed flakey since I updated to v6.40 but can't really prove it yet.
"Primum Non Nocere" 2595LMT Clear Channel and Navteq Traffic
Mine still work fine with POI
knock on wood...
That's right
This firmware update seems to have been pulled by Garmin.
http://www8.garmin.com/support/download_details.jsp?id=5303
That's right Garmin pulled the following:
Version 2.50 for the Nuvi 30/40/ and 50 (now back to 2.30)
Version 6.40 for the Nuvi 34xx and 35xx (now back to 6.30)
Version 6.40 for the Nuvi 24x5 and 25x5 (now back to 6.30)
We should all get a Beta Tester T-shirt from Garmin for the number of times we install firmware that they haven't tested properly.
Nuvi 350, 760, 1695LM, 3790LMT, 2460LMT, 3597LMTHD and TomTom XXL540s
Nuvi 34xx v.6.50 Released
Nuvi 34xx v.6.50 Released
I installed 6.50 and The sub-category issue was NOT resolved on my 3490
Beta Tester T-Shirts? how about a wet t-shirt contest :)
We should all get a Beta Tester T-shirt from Garmin for the number of times we install firmware that they haven't tested properly.
isn't that what the end users are for??? Developers are way to busy to actually test something before they send it out to the abuser community.
Just be thankful they aren't developing automation equipment for a medical procedure your about to have performed!