Garmin Oregon Beta 2.97 — Quick Fix for 2.96 Issues
Apr.29, 2009 in
Garmin Oregon
Just a few days after releasing beta 2.96 Garmin has quickly released 2.97 to address two significant issues reported by users here on GPSFix:
- Fixed lockup when a search returns no results
- Fixed map stopped drawing while autorouting
I’ve already loaded the beta and it does resolve the autorouting issues I was seeing. The POI search hang seems cured as well, although I’m seeing a five second delay when I enter the second character of a text search. Annoying but better than a hang.
Let us know how 2.97 works on your Oregon.
Related posts:
April 30th, 2009 at 12:50 pm
I have an Oregon300, with software 2.80
now i installed this version 2.97, no problems there. Now my oregon does not want to startup anymore.
it says “SYSTEM SOFTWARE MISSING“, and my laptop does not see it anymore. no garmin, and no sd card.
anyone know what i can do?
April 30th, 2009 at 1:15 pm
That is usually a bad sign. You might want to see if either of these recovery methods work:
http://garminoregon.wikispaces.com/Miscellaneous#toc3
April 30th, 2009 at 2:14 pm
The download worked fine for me. I did not need to remove my memory card and my Geotags where maintained. Appears to work OK but have not had chance to use in anger
April 30th, 2009 at 3:07 pm
My 2.97 download worked, but for some reason I never got the new “Waypoint Averaging” function. Not sure if I need to download each update separately. I would think that the newest version would contain all the previous fixes right? Thanks.
April 30th, 2009 at 3:28 pm
Jeff, take a look at the 2.96 post. There are instructions there on how to make the button visible. -Scott
April 30th, 2009 at 3:48 pm
Uploaded V2.97 this morning after having lot’s of problems with the V2.96 (I even switched back to V2.95). Now with V2.97 there is no lock up in the Automotive mode (drove over 160 km), changed the profile several times, did several GeoCaches including a Wherigo, without having to restart! So it seems fine to me.
I do not have the experience with the search option yet.
May 1st, 2009 at 12:08 pm
With both version 2.96 and 2.97 I have the problem that the position drifts and jumps very much when in motion. It’s nearly unusable, especially for recording tracks.
May 1st, 2009 at 3:06 pm
hello, Pierre from France.
The name of the 2.96 and 2.97 version I download are “Oregon400t_297Beta.exe” can I use this beta version with my Oregon 300?
May 1st, 2009 at 3:10 pm
Yes, the images are all the same.
Or you can use this link: http://www.garmin.com/software/Oregon300_297Beta.exe
-Scott
May 2nd, 2009 at 5:37 pm
Had problems with 2.97. When I was geocaching my position jumped all over the place. Made it impossible to find the geocache. I plan on switching back to 2.95.
May 2nd, 2009 at 5:45 pm
Jason — I’d be surprised if there was any difference between 2.97 and 2.95. The GPS software is the same.
May 2nd, 2009 at 8:34 pm
This beta has been running great!! I’ve put over 300 miles on this beta and had no trouble until today. This afternoon on the drive home my map screen lost half of it’s display and went white and froze in place. I had to hit the zoom in or out buttons to get it to redraw. I was able to recover though just by using the zoom in and out. Otherwise I’m loving this release!
May 3rd, 2009 at 2:42 pm
This Beta version is much better than 2.96 but I find out that I was jumping from left to right for about 20 mtr or more while I was standing still.
Even when driving on CityNavigator I was driving sometimes more then 20 mtr near the road.
The EME at those moments gave 2 till 3 mtr so I’m thinking to go back for 2.95.
Ger@ld
May 3rd, 2009 at 5:35 pm
Must have been a fluke thing. 2.97 seems to be working ok for me now…. going to continue using it.
May 4th, 2009 at 3:13 am
I have updated my Oregon 300 to 2.97 and I have now noticed that every time I download new geocaches to it the first time I try and start up the device after removing the usb cable it hangs at the point it is loading the geocaches and waypoints.
I have to remove and replace the batteries and restart the device again then it starts normally. I did not have this . problem with earlier releases.
May 4th, 2009 at 7:21 am
Have been using 2.95 since it came out with no problems at all.
Have not experienced any position jumping ever with the Oregon except when there is a weak link to satellites as you get indoors etc. I run it every day on the way to work and back again with virtually no variation in track recorded. Great release and I love the new features
May 4th, 2009 at 11:35 am
I have the same problem of the unit hanging to the point of removing the batteries on both my 300 and 400t.
May 6th, 2009 at 10:56 am
i installed first 2.96 and now 2.97. the track-recording is set to by time to one second. if i walk with nearly clear sky (in germany), the gps-accurancy says 2 m – but the track jumps around (the distance from point to point some untill 8 m). a had waas enabled and got the “D” in the satellites-page – 9 satellites (7 with full stregth).
i hope very much, that this will soon be much better – otherwise a had to look for another gpsr.
May 6th, 2009 at 12:30 pm
A minor bug I have found with 2.97 on my 400t: when a push pin in dropped between contour lines on the map page, the resulting elevation readout, obtained after pressing the splash window, is inaccurate. Not sure if this started with 2.97 or before, but I know it worked properly with earlier non-beta versions of the software.
May 6th, 2009 at 3:59 pm
You are right John, this did work and I can reproduce the problem on my unit. I’ve submitted it to Oregonbeta (but it would be good if you did as well).
-Scott
May 6th, 2009 at 9:20 pm
Is there a special place to report problems with beta software? I did report this issue to tech support via the online web form. Nothing seemed to happen after hitting the “send” button (twice), so I am not sure if it went through.
May 7th, 2009 at 5:33 am
Send all issues to OregonBeta@garmin.com .
May 9th, 2009 at 2:39 pm
2.97 looks good, particularly the averaging feature which worked a treat today.
The downside is a wandering position as posted previously here. It has actually made finding caches quite difficult and is a noticably backward step from previous versions
May 10th, 2009 at 4:14 pm
Buongiorno
da quando ho scaricato la nuova versione del software 2.97 la mia unità oregon 300 non traccia piu bene sulla mappa,benchè il segnale dei satelliti mi da una precisione di 2mt.sapete darmi una risposta?
Grazie
Fabrizio
May 12th, 2009 at 3:48 pm
One old problem reappeared: Did one sight and go, after that no more communication with Mapsource possible.
I had to delete ALL waypoints, then everything was running again.
May 12th, 2009 at 4:53 pm
Alex, my guess is that the “Sight N Go” waypoint has some corrupt data in it. I’ll check later today, but in the meantime delete the Sight N Go waypoint and then try the transfer to Mapsource.
May 16th, 2009 at 7:09 am
Scott, thank you for your quick answer.
I did that at first, bit it didnt´d help.
I had to delete all other waypoints first, after that the transfer of the track was possible.
May 16th, 2009 at 7:20 am
Alex, I tried a Sight N Go and was able to transfer the waypoints to my Mapsource fine, so that doesn’t appear to be the issue. I’ve seen this before and it is caused when the GPS or the software you use to load waypoints on the GPS inserts characters into the name or description of a waypoint that aren’t supported by the GPX file format. The easiest way to figure this out is to open \Garmin\GPX\Current\current.gpx in a text editor (like notepad/wordpad) and see if you can see any “garbage” characters. That would help identify which waypoint has the problem (you can also clean it up) so we could figure out how the bad data is getting in there in the first place.
How do you load your waypoints? Are they all created by hand or do you import from some other program? I’ve seen problems like this importing waypoints from ExpertGPS.
-Scott