+allory Posted March 16, 2011 Share Posted March 16, 2011 Oregon x50 software version 4.45 Beta http://www8.garmin.com/support/download_details.jsp?id=4743 Changes made from version 4.32 to 4.45: * Improved GPS performance * Improved JNX file handling * Improved the usability of the main menu setup page * Increased maximum number of supported JNX files to 250 from 200 * Fixed shutdown when more than the maximum number of JNX files were present * Fixed 'Search Near' functionality on Hunt & Fish and Sun & Moon pages * Fixed shutdown related to topographical maps and land cover text size * Fixed shutdown associated with certain custom POI files * Fixed Glide Ratio to Destination field * Fixed problem with profiles and the fields on the map page * Problems with the software may be reported to OregonBeta@garmin.com Quote Link to comment
+myotis Posted March 16, 2011 Share Posted March 16, 2011 Well I am going to wait until I hear some good reports-like how does WAAS work? They don't list fixing the bug with the alarm when Daylight Savings time changes. The alarm went off an hour late. Quote Link to comment
yogazoo Posted March 16, 2011 Share Posted March 16, 2011 When you select the "About" button in setup to check the software version it stays blank white for about 10 seconds before the display shows anything. Quote Link to comment
+dfx Posted March 17, 2011 Share Posted March 17, 2011 Upgrade went fine here, field test tomorrow. Quote Link to comment
+larryc43230 Posted March 17, 2011 Share Posted March 17, 2011 Upgrade went fine here, field test tomorrow. Same here. So far so good. One minor glitch I've noticed: After the update, all the maps I have on the unit were suddenly enabled, including a City Nav Night Mode map and a "My Trails" map, both of which had been disabled just before the update. Actually, I just noticed an exception: The one custom map I have on the unit was still disabled. Curious. Anyway, the fix was easy: Just change the maps back the way you want them, and the change sticks from that point on. --Larry Quote Link to comment
eaparks Posted March 17, 2011 Share Posted March 17, 2011 I had seen the same thing on some of the software updates in the past for the Oregon 400t; but it was usually limited to just the profile I was in at the time of the update. The ones not active were not changed. Quote Link to comment
+arcs Posted March 17, 2011 Share Posted March 17, 2011 (edited) Quick, easy install on a 550. Seems to be running fine. Locked on inside my hotel room. Don't think it used to do that. One thing seems to have changed - I was getting strange battery life indications. Full batteries would show to be depleted way early. I reinstalled semi-used batts and they are showing more reasonable capacity. Edited March 17, 2011 by arcs Quote Link to comment
savant9 Posted March 17, 2011 Share Posted March 17, 2011 Changes made from version 4.32 to 4.45:* Improved JNX file handling * Increased maximum number of supported JNX files to 250 from 200 This should read as.... modified the way .jnx files are handled to make the current firmware patcher inoperable. Quote Link to comment
+ecanderson Posted March 17, 2011 Share Posted March 17, 2011 Changes made from version 4.32 to 4.45:* Improved JNX file handling * Increased maximum number of supported JNX files to 250 from 200 This should read as.... modified the way .jnx files are handled to make the current firmware patcher inoperable. ? What "firmware patcher" would that be? Quote Link to comment
+Spatial Distortion Posted March 17, 2011 Share Posted March 17, 2011 Install went fine. Will field test ASAP. Quote Link to comment
+Unobtainium Posted March 17, 2011 Share Posted March 17, 2011 This should read as.... modified the way .jnx files are handled to make the current firmware patcher inoperable. At the risk of sounding incredibly ill-informed, what are .JNX files and what have I been missing? Quote Link to comment
MtnHermit Posted March 17, 2011 Share Posted March 17, 2011 At the risk of sounding incredibly ill-informed, what are .JNX files and what have I been missing? +1 Quote Link to comment
+Triple Crown Posted March 17, 2011 Share Posted March 17, 2011 This should read as.... modified the way .jnx files are handled to make the current firmware patcher inoperable. At the risk of sounding incredibly ill-informed, what are .JNX files and what have I been missing? BirdsEye aerial images are stored as .JNX files Quote Link to comment
+Unobtainium Posted March 17, 2011 Share Posted March 17, 2011 Update went OK, but I did create a dummy profile before hand and delete it afterwards. Field testing tomorrow. Quote Link to comment
+myotis Posted March 17, 2011 Share Posted March 17, 2011 How is WAAS working? Everyone should ALWAYS back up your profiles before a firmware change! Quote Link to comment
+dfx Posted March 17, 2011 Share Posted March 17, 2011 Everyone should ALWAYS back up your profiles before a firmware change! Nobody cares about backups. All they care about is restores - when they need them Quote Link to comment
+arcs Posted March 17, 2011 Share Posted March 17, 2011 (edited) One thing I did discover today - my Canada Topo maps showed the caches, road names, railways and all just fine but - no roads. Had to do a hard reset and all seems well now. Had me worried for a minute there. Edited March 17, 2011 by arcs Quote Link to comment
+Edsfind Posted March 17, 2011 Share Posted March 17, 2011 all went well with my oregon 550, test it this weekend Quote Link to comment
+larryc43230 Posted March 18, 2011 Share Posted March 18, 2011 I took my updated 550t out caching today, and overall I'm pleased with the update. I still can't reliably get a WAAS fix; then again, that's been true since the previous beta release, and the "GPS software" version didn't change with the latest release (it was and still is 5.00). I did notice two minor glitches which I'm fairly sure were introduced with the new release: When I display a cache description, it seems to take a bit longer (a few seconds) to display. I see a blank white screen for a couple of seconds between the time I ask for the description and when it finally displays. Also, a couple of times when I was watching the map display while driving, the map refresh seemed a bit flaky. The area I was driving into wasn't displayed, and all I saw was blank background in that area. In both cases, zooming out and back in again seemed to "wake up" the display. --Larry Quote Link to comment
+dfx Posted March 18, 2011 Share Posted March 18, 2011 Field test went fine here as well. I did manage to get a WAAS lock, and I think faster than with the previous firmware (which most of the time didn't give me WAAS at all). Might've been coincidence though, I'll keep an eye on it. I didn't notice any problems. Quote Link to comment
+ecanderson Posted March 18, 2011 Share Posted March 18, 2011 The only glitch I've seen with 4.45 so far was that initially, the Birdseye collection on my 450 showed up as a blank space at the bottom of the map list in "Map Information / Select Map". After pressing the blank white space, I could enable/disable/brightness and it did exactly what you'd expect for Birdseye - but it was just blank for the descriptor - didn't say what was actually there. Of course, I knew, but ... It finally started to produce a partial list of my *.jnx files in what had been the blank space, but the word "Birdseye" still never appears as part of the description for the 'map' there. Quote Link to comment
+ecanderson Posted March 18, 2011 Share Posted March 18, 2011 When you select the "About" button in setup to check the software version it stays blank white for about 10 seconds before the display shows anything. I've found that in that version screen, the Digital Globe data description is badly mangled. Just a bunch of random characters down the left side of the screen. Do you see that same thing? Could be the unit trying to parse that information and struggling with it. Quote Link to comment
+dfx Posted March 18, 2011 Share Posted March 18, 2011 The only glitch I've seen with 4.45 so far was that initially, the Birdseye collection on my 450 showed up as a blank space at the bottom of the map list in "Map Information / Select Map". After pressing the blank white space, I could enable/disable/brightness and it did exactly what you'd expect for Birdseye - but it was just blank for the descriptor - didn't say what was actually there. Of course, I knew, but ... It finally started to produce a partial list of my *.jnx files in what had been the blank space, but the word "Birdseye" still never appears as part of the description for the 'map' there. I don't see that on mine. The button is labeled with "Enabled - Digital Globe" (and a list of all JNX files), and pushing on it gets me to the brightness adjustment menu, with "Digital Globe - Enabled" as the title. Pushing on the information button there causes a long delay to finally bring up two almost identical lines (MDA Federal ...). No mention of Birdseye anywhere though. When you select the "About" button in setup to check the software version it stays blank white for about 10 seconds before the display shows anything. I've found that in that version screen, the Digital Globe data description is badly mangled. Just a bunch of random characters down the left side of the screen. Do you see that same thing? Could be the unit trying to parse that information and struggling with it. I do get the same delay, but don't see any garbled characters. Digital Globe is only mentioned in the second section with four lines (seems to be the same as from the information screen mentioned above). Quote Link to comment
rsaxvc Posted March 19, 2011 Share Posted March 19, 2011 When you select the "About" button in setup to check the software version it stays blank white for about 10 seconds before the display shows anything. I've found that in that version screen, the Digital Globe data description is badly mangled. Just a bunch of random characters down the left side of the screen. Do you see that same thing? Could be the unit trying to parse that information and struggling with it. Post a screenshot? Quote Link to comment
+Bullygoat29 Posted March 19, 2011 Share Posted March 19, 2011 Post a screenshot? Quote Link to comment
+rovers3 Posted March 19, 2011 Share Posted March 19, 2011 I was out caching and hiking today and noticed a couple of things with my Oregon 450 1) I had to reboot a couple of times as the distance was stuck in the compass screen and seemed OK after the reboot. 2) I was with another cacher who also has an Oregon 450 with older version. Purchased at same time as mine. In the past we have been able to easily send caches wirelessly back and forth but today we couldn't. On a couple of tries the units showed 12% and 25% transfer and then reverted back to searching but most often just showed a searching message. Tried sending both ways to no avail and at different distances and different locations. Quote Link to comment
+rovers3 Posted March 20, 2011 Share Posted March 20, 2011 As an update. My friend was able to send and receive from and to his wife's 62. I was not able to send or receive from my 400t. So this is only after I updated to 4.45 Beta Quote Link to comment
+ecanderson Posted March 20, 2011 Share Posted March 20, 2011 Post a screenshot? Yes, something along those lines exactly. I'm not near a cable for my unit, but you'd see pretty much the same thing on mine. Quote Link to comment
+dfx Posted March 20, 2011 Share Posted March 20, 2011 WAAS performance still isn't up to par. My wife's 550 (with stable firmware) consistently gets a WAAS lock while I don't. However, at the same time it shows a much higher "accuracy" number than mine, sometimes double of it. It could just be a cosmetic problem... who knows? Quote Link to comment
+rovers3 Posted March 20, 2011 Share Posted March 20, 2011 Has anyone else seen the problem that I described above re share wirelessly since the update? I was going to call Garmin support but wanted to be sure whether it is only me. Quote Link to comment
savant9 Posted March 21, 2011 Share Posted March 21, 2011 Has anyone else seen the problem that I described above re share wirelessly since the update? I was going to call Garmin support but wanted to be sure whether it is only me. I am seeing the same behaviour. Cannot send or receive between my Colorado, although one time they actually connected, got to about 16% then failed. Additionally, and this is likely related to the same issue, my Oregon 450 will also never detect a chirp with this firmware. Quote Link to comment
+myotis Posted March 21, 2011 Share Posted March 21, 2011 I'm glad I did not install this. Sounds like the bugs greatly outweight the benifits. Quote Link to comment
+arcs Posted March 21, 2011 Share Posted March 21, 2011 Just checked to see if my 550 had a problem with chirp detect and communication. I have a chirp and turned on the detect - no problem that I can see. Quote Link to comment
savant9 Posted March 21, 2011 Share Posted March 21, 2011 Just checked to see if my 550 had a problem with chirp detect and communication. I have a chirp and turned on the detect - no problem that I can see. I see now that if I turn on my 450 with chirp searching already enabled, it will pick up the chirp right away. If I have chirp searching off, attempt to send/receive waypoints from another gps, which fails, then it will never pick up the chirp after enabling chirp searching unless I power cycle the unit. So to sum it up, chirp searching works unless you have a failed attempt at wireless transfer, you will need to power cycle, it seems to crash the wireless radio. Quote Link to comment
+1bertoc Posted March 21, 2011 Share Posted March 21, 2011 In my Oregon 550 Birdseye is no longer profile independent. Now is enable or disable in all profiles. Can anyone confirm this please. I also noticed something strange when I pass through a tunnel. Now seems that when GPS loose satellite contact it resets Ephemeris data (?) and takes considerably longer than before to regain position (before was almost instantaneously after exiting the tunnel). Quote Link to comment
yogazoo Posted March 21, 2011 Share Posted March 21, 2011 Confirmed: Birdseye imagery is no longer profile dependant. If you enable it in one profile it is enabled in ALL profiles. Based on stability and map issues I'm reverting back to the previous release. Quote Link to comment
+rovers3 Posted March 21, 2011 Share Posted March 21, 2011 Confirmed: Based on stability and map issues I'm reverting back to the previous release. That's what support at Garmin recommended when I reported the send wirelessly problem Quote Link to comment
yogazoo Posted March 21, 2011 Share Posted March 21, 2011 That's what support at Garmin recommended when I reported the send wirelessly problem Well, there you have it. Quote Link to comment
+ecanderson Posted March 21, 2011 Share Posted March 21, 2011 Ditto. No known benefit, a few more problems. Back to 4.32 we go. BTW, I did note that a couple of users had 4.40 shipped on new units. Has anyone seen a copy of this around for download/test? For that matter, I don't see any 4.30 links... Quote Link to comment
jholly Posted March 21, 2011 Share Posted March 21, 2011 Ditto. No known benefit, a few more problems. Back to 4.32 we go. BTW, I did note that a couple of users had 4.40 shipped on new units. Has anyone seen a copy of this around for download/test? For that matter, I don't see any 4.30 links... Garmin seems to like to do that sort of thing. The 60/76CSx latest firmware on the web is 4.00, but units shipped from the factory had 4.20. Makes one wonder what is in the firmware. Quote Link to comment
Henrylw Posted March 21, 2011 Share Posted March 21, 2011 (edited) Confirmed: Birdseye imagery is no longer profile dependant. If you enable it in one profile it is enabled in ALL profiles. Based on stability and map issues I'm reverting back to the previous release. That's not the case with mine. I can still see map only on my Automotive profile and then change to my "BirdsEye" profile to see Birdseye imagery. Edited March 21, 2011 by Henrylw Quote Link to comment
savant9 Posted March 21, 2011 Share Posted March 21, 2011 That's not the case with mine. I can still see map only on my Automotive profile and then change to my "BirdsEye" profile to see Birdseye imagery. BirdsEye images are not displayed if you have the orientation view set to "Automotive Mode", as this skews the image and would be too difficult for the gps to display with acceptable performance. If you check the map setting you will see that birdseye is enabled, even though it doesn't show. The problem is there, its just not apparent in the automotive profile. Quote Link to comment
yogazoo Posted March 21, 2011 Share Posted March 21, 2011 Confirmed: Birdseye imagery is no longer profile dependant. If you enable it in one profile it is enabled in ALL profiles. Based on stability and map issues I'm reverting back to the previous release. That's not the case with mine. I can still see map only on my Automotive profile and then change to my "BirdsEye" profile to see Birdseye imagery. Test for Henrylw: 1) Enable a vector map along with your Birdseye imagery on your "Birdseye" profile. 2) Try disabling the Birdseye in both profiles and then enable it for one of them to see if it now "sticks" to the other. Quote Link to comment
+Parabel Posted March 22, 2011 Share Posted March 22, 2011 Just checked to see if my 550 had a problem with chirp detect and communication. I have a chirp and turned on the detect - no problem that I can see. I see now that if I turn on my 450 with chirp searching already enabled, it will pick up the chirp right away. If I have chirp searching off, attempt to send/receive waypoints from another gps, which fails, then it will never pick up the chirp after enabling chirp searching unless I power cycle the unit. So to sum it up, chirp searching works unless you have a failed attempt at wireless transfer, you will need to power cycle, it seems to crash the wireless radio. Well, I hade the same problems, downgrade my Oregon 450 back to 4.20 Quote Link to comment
+ecanderson Posted March 22, 2011 Share Posted March 22, 2011 Well, I hade the same problems, downgrade my Oregon 450 back to 4.20 You might want to consider 4.32. It was an improvement over 4.20, and without any major bugs that anyone ever reported. Supposed to have improved WAAS. Seemed to do so on my unit. It's the second from the bottom entry, found here -> http://www.gawisp.com/perry/oregon Quote Link to comment
+Parabel Posted March 22, 2011 Share Posted March 22, 2011 Well, I hade the same problems, downgrade my Oregon 450 back to 4.20 You might want to consider 4.32. It was an improvement over 4.20, and without any major bugs that anyone ever reported. Supposed to have improved WAAS. Seemed to do so on my unit. It's the second from the bottom entry, found here -> http://www.gawisp.com/perry/oregon Thank you Quote Link to comment
+Jonovich Posted March 23, 2011 Share Posted March 23, 2011 Yup, I'm also backed out. I had the Wireless connectivity issues, plus if I used Setup/Reset/Delete all waypoints, the unit would freeze up. Jon. Quote Link to comment
+dfx Posted March 24, 2011 Share Posted March 24, 2011 Yeah wireless sharing is definitely hosed. Not good! Quote Link to comment
yogazoo Posted March 24, 2011 Share Posted March 24, 2011 Does anyone have a link to Version beta 4.32? The link on the Oregon Wiki is hosed. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.