Oregon 2.8 Firwmare Issues – Read This Before You Upgrade!
As luck would have it, within hours of posting a recommendation to upgrade to version 2.8 the issues with this new Oregon firmware have started coming in from left and right. Bottom line, if you haven’t upgraded to 2.7 or 2.8 I would recommend holding off for now until these issues are resolved.
Here’s a summary of the issues I’ve experience or have seen posted on the Oregon wiki or Groundspeak boards:
- The Automotive profile Map>Orientation setting sometimes gets set to track up/north up instead of automotive.
- A background image is sometimes displayed which does not match the configured background image. It always seems to be the default “pebbles” background that displays; power cycling fixes the issue.
- Some users have reported corrupted map enable/disable settings in their profiles. Replacing the gpf profile file with a new one was the only way to resolve the issue.
- Tracklog settings are sometimes incorrectly set to Do not Record when they were previously set to one of the Record options.
- A reproducible crash happens when you switch from Automotive to Geocaching profiles with an active route destination. I’m working with Garmin tech support on this issue, but they have not been able to reproduce it.
It feels like something was broken in 2.7 or 2.8 related to profile management and configuration settings.
If you have already upgraded to 2.8 I would suggest checking the settings in all of your profiles to make sure that they are set as you would expect.
Watch this post for updates as they become available — I’m off to eat my crow…
Related posts:
December 29th, 2008 at 5:55 pm
“Tracklog settings are sometimes incorrectly set to Do not Record when they were previously set to one of the Record options.”
I can confirm this issue after upgrading to version 2.8. But worse than the settings being changed to Do not Record, is that they can not be changed from this new condition. This means that this feature stopped functioning. Finnaly I hope Garmin can repair this quickly…..
Regards,
António Ramos
January 2nd, 2009 at 11:37 pm
After the uppdate to version 2.8, the onlu problem i see is: when i choose automotive profile, i cant see any map. All i have is the base map but not City navigator 2009. Is anybody experiencing this problem?
January 3rd, 2009 at 7:40 am
Do you have the City Navigator maps enabled in your automotive profile under Settings>Maps ?
January 10th, 2009 at 11:56 am
Yes i have City map navigator enable.
January 10th, 2009 at 12:06 pm
Do you have only City Navigator maps enabled or do you have other maps installed and enabled?
When the GPS starts look at the banner at the bottom of the screen. After it says “loading maps” do you see a Navteq copyright flash by (it happens quickly). If you don’t see this you don’t have the City Nav maps loaded properly.
-Scot
January 20th, 2009 at 4:59 am
I have five Oregon 300’s and teach adults and kids how to use them. I have upgraded to version 2.8 and am having all types of freezes and crashes. Unfortunately, I’m not using them myself at the time so it is difficult to reproduce the problems. In the future I will label them and try and record which unit crashed and how. For example, I rearrange the buttons on the main menu (so the kids don’t mess up the “Setup” button easily) and find the order changes again next time I reboot the unit. I think Garmin has a long road to go if they think these units are anywhere as good as the 60CSX which I use daily in my work. It’s almost getting to the stage where I’m really not going to trust the units at all.
These units reliable….No way…
January 21st, 2009 at 12:02 pm
Yes u have city map navigator enable. It happend only with the automotive profile. I can choose another profile like recreational for example and put only vity map navigator with the Automotive view mode and it work perfectly. I just dont understand this problem and it look like im the only one with this problem.
January 21st, 2009 at 1:53 pm
The only thing I can suggest is deleting your Automotive profile and recreating it from scratch. It sounds like something might be corrupted in your Automotive profile.
To start with I would create a brand new profile, modify the settings to make it work like your Automotive profile and see if that fixes the issue. If it does, the profile was probably corrupted. If it doesn’t, it might be a particular combination of settings that is causing the issue.
January 22nd, 2009 at 12:10 pm
How can i create a new profile?
January 22nd, 2009 at 12:47 pm
Jowel80,
To create a profile goto Setup>Profiles and scroll to the bottom and select
You might also consider upgrading to the new 2.85 beta software to see if this addresses your issue, it has fixed the profile related issues I was seeing.
-Scott
January 22nd, 2009 at 1:08 pm
ok i’ll try it and keep you informed.
Thanks!
January 23rd, 2009 at 7:40 am
It worked ferfectly and i deleted automotive profile.
Is there any application with the Oregon like Iphone have?
Thanks!
January 28th, 2009 at 1:55 pm
[...] The beta software is not available through the Webupdater so you’ll need to download it directly from Garmin. I’ll be testing it out over the next few days to see how it works but I’m really happy to see the custom POI database support and improvements to the battery meter. It looks like some of the other changes are aimed at fixing the issues with GB Discoverer and the profile change instability introduced in 2.7/2.8. [...]