Garmin Colorado Beta 2.95 Available
After recommending that Garmin Colorado owners avoid beta 2.94 because of a problem with importing GPX files, Garmin has released Colorado beta 2.95 which addresses this issue. Garmin’s release notes for 2.95 spells out fixes for two issues:
- Fixed issue importing GPX files introduced in 2.94 beta.
- Fixed issue navigating to points.
Garmin also makes the following recommendation before you upgrade:
If updating from 2.94 beta, please remove any GPX files from the device before installing software.
I’ve upgraded my Colorado to 2.95 and didn’t experience any issues during the upgrade. After the upgrade I imported a GPX file containing 1500 geocaches and it loaded without any issues and the geocache details all seem to be intact. I’ve tried to reproduce the waypoint averaging crash in beta 2.94 and that appears to be fixed — that may be what Garmin is referencing in the second release note above.
The 2.95 discussion thread on the Colorado wiki is located here.
Related posts:
July 21st, 2009 at 9:47 pm
I removed all GPX files from my Colorado, which was running 2.90. The upgrade to 2.95 went smoothly, I loaded 1900 caches on there and several POI files.
Running City Navigator NT 2010, Topo Canada v4 and the Ontario Trails Project maps – went for a cache and tried some street routing on the way home. Using the .IMG format for the maps on the base unit.
So far, it’s running smoothly from what I can tell. Seems a bit quicker as well to me, but that might just be me.
July 22nd, 2009 at 5:56 am
Has anyone experienced how averaging feature works with 2.95 beta?
July 22nd, 2009 at 5:59 am
The best place to look for information on how to use the new averaging feature is on this post related to the feature on the Oregon.
July 22nd, 2009 at 6:31 am
OK. But with Colorado 2.94 beta there was powerdown problem when using this averaging feature. Is it the same problem still?
July 22nd, 2009 at 8:29 am
I tried the waypoint averaging sequence that cause the crash this morning and couldn’t reproduce it. Maybe that it what Garmin meant by: “Fixed issue navigating to points”.
I haven’t had any issues loading gpx files yet, geocaches all seem to show up with full descriptions. So far so good.
-Scott
July 27th, 2009 at 2:28 am
I had no issues with averaging, and also the battery indicator works very well.
Yesterday I experienced big drifts (100 and more meters), and the unit was’nt able to recovery it after power off (I’ve tried three times with a clear view of the sky). For about half hour was completely unusable (and pretty crazy), but before to reach my home I got again a stable fix.
Looks like the unit got something wrong in the almanac (but this is only my guess).
The oddity is that the unit worked very well in the wood under high trees, and I got the drift when I reached the main road out of the wood.
July 28th, 2009 at 9:26 am
Oooooooh I found a glitch!
If you rename GMAPSUPP.IMG to something else, like CITYNAV.IMG be advised that you will no longer be able to search for Addresses, Cities, or other map features – even though the map itself will load, display and route properly.
To reproduce this, rename your map file and then perform the following:
If I go to WhereTo? > Addresses > Ontario (pick your state/province from list) > Spell City
You will always get “No Matches Found”, even if City Navigator loads and displays at startup.
July 28th, 2009 at 9:22 pm
@Gregory, nice find. I heard about some one else with a similar problem a few days ago — I bet this is what it was. Have you posted it to the ColoradoBeta email? I’m guessing that this might affect more than just the Colorado.
-Scott
July 29th, 2009 at 3:29 pm
Yup, sent that on to the ColoradoBeta email moments after I posted it here (priorities you know
)
- Greg