Garmin Oregon Issues List




Much of this list came from the group of Garmin Oregon users who frequent the Groundspeak GPS Units and Technology forums . Thanks to the many people who have made contributions to this page!

Just because an issue is mentioned on this list does not mean it will be fixed by Garmin. The authors have no affiliation with Garmin and although I believe they have seen the list and may monitor it you should contact Garmin (1-800-800-1020) with the issues which matter to you most.

Feel free to reference the Issues List in your discussions with Garmin about the Oregon.

How to Read the Issues List



  • Issues are grouped by areas which roughly correspond to the various "Tools" available from the Oregon main menu.
  • Issues are categorized as follows:
    • Bugs: Issues that result in a failure of the system or adversely affect the way a Tool is supposed to work. High priority bugs which result in freezes, resets or power-offs are prefixed with (Crash).
    • Missing features: Feature is available in another Garmin outdoor handheld unit such as the GPSMAP 60csx or Colorado.
    • New feature requests: Request for functionality not available on the Oregon or any other Garmin handheld.
    • Need Investigation: Potential issues that have been observed but are not characterized yet
    • Resolved: Fixed issues or added features. The fixed-in version is listed first followed by the Garmin release note (if any) in italics.
  • Issues specific to the Oregon 200, 300, 400t, 400i and 400c are prefixed with [x00] and issues specific to the Oregon 550 and 550 are prefixed with [x50]. If an issue has no platform label it is assumed to be common for both the x00 and x50.
  • Issues are labeled to mark the most recent version of Software where the issue was observed. If two versions are given (e.g. 2.98/2.10) the first is the x00 software version and the second is the x50 version. The software versions which this list is based on are referenced on the x00 Versions page and the x50 Versions page.



Intermittent or Difficult to Reproduce



A place to capture issues that have been observed but cannot easily be reproduced or characterized.

  1. Occasionally the Oregon will freeze during the boot after loading a new gpx file. Batteries have to be pulled to recover. (2.98)
  2. Heading on the unit freezes for long periods of time. Under cover the heading data field (or compass heading or map cursor orientation) unit can sometimes freeze for up to 45 seconds. Observed with electronic compass off for over 10 minutes. Walking back into a clear view of the sky seemed to restore updates of the heading to about one every second. (2.98)

Hardware


Hardware Issues


Issues listed in this section are assumed to be hardware related based on feedback from the user community. If you experience any of these problems it is recommended that you should contact Garmin technical support.

  1. Battery connector failure: The bent metal contacts on the battery connector can fatigue over time, and snap. There are two types - the connecting bar at the bottom, and the individual feed tabs at the top. The bar could be replaced by Garmin sending out a new piece, however the individual contacts at the top appear to be glued into the case. One of the individual connectors on mine failed after 7 months, and had to be replaced by Garmin under warranty. Tip - be careful when inserting and removing batteries - insert the positive end of the battery first to avoid the hard snap and related stress due to the dimple on the contacts.


Basic Operations


Bugs


  1. Set North Reference to Magnetic, and then search for Geocaches or Waypoints. In the list view, the bearing displayed will still be in Degrees True. Once you select a Waypoint or Cache, and go to the map, it will be correctly shown with its bearing in Degrees Magnetic. (3.4)
  2. [x50] The project waypoint tool reports incorrect bearing when Setup>Heading>Display is set to Directional Letters. Projecting a waypoint with these setting will work correctly (the waypoint is placed properly) but the project waypoint screen will incorrectly display the heading of the projection on the final page. For example a waypoint projected at 90 degrees will report a bearing of 2 degrees and a projection of 180 degrees will report 4 degrees. It appears that instead of displaying numerical degrees the unit is printing the location of the character(s) associated with the directional letter(s) in an enumerated list. (2.3)
  3. (Crash) [x50] Exiting from the recent finds list sometimes causes the unit to crash. Select WhereTo?>Recent Finds and then tap the button in the lower left corner to exit. Sometimes the unit will crash. It may be related to the timing hitting the return key (hitting just after the photo thumbnails appear seems to increase the frequency of the failure) and if the Recent Finds list has photos on the first page the unit will sometimes fail more frequently (2.2)
  4. (Crash) Adding startup.txt file with more than 5 lines of 30 characters each can cause the GPS to repeatedly hang during startup (3.01)
  5. User cannot search for special language specific characters without being set to that language. All characters should be available for spell searches regardless of the language setting to allow users to search for names in a different language even though the language is set to their native language. (2.98)
  6. With the language set to Nederlands the Oregon displays two overlapping messages upon disconnect from power, one in Dutch the other in English making it difficult to read either. The English message should be suppressed. This doesn't happen in all languages (German seems fine) but it does happen in Dutch, Italian and Swedish. (2.98)
  7. Battery saver mode sometimes results in a blank white screen. When following a route with battery saver mode the screen can end up as a blank all white screen under the following circumstances: 1) the screen has turned off as a result of the battery saver mode, 2) a turn alert is received for the active route and 3) the user touches the screen at nearly the same time the alert is received. The white screen can be cleared by tapping the power button twice. (2.94)
  8. Wrong German translation in some menus. Example: for "on" the german word "ein" should be used, not "auf" (= open) - Fixed by OpenGTT (2.5).

Missing features

  1. [x50] During boot backlight on the Oregon x50 comes on much later than on the x00 Oregon. This makes it difficult to read the custom startup text when the unit is booting. (ORx00) (2.10)
  2. Oregon doesn't support night/day color modes. (60csx) (2.98)
  3. The order of all distance-based lists (ie. waypoints, recent finds, geocaches) should update dynamically as the unit is moving. (60csx) (2.98)
  4. [x50] No support for transferring saved objects using "Receive from GPS" (Waypoints, Routes and Tracks) from the Oregon x50 series into Mapsource. BaseCamp still has problems with some TOPO products (Topo France, Topo Swiss) so it is not a solution. Note: Workaround is to open gpx files in [OR drive]:\Garmin\GPX directly into Mapsource. (60csx, x00) .
  5. User should be able to change display orientation so that the Oregon could be used vertically or horizontally. (Garmin V) On 550 with camera image display rotates according to orientation, and so should the unit's other functions.

New feature requests

  1. Add ability to set the time period over which the average speed data field is calculated.
  2. Provide a golf profile or some ability to use the Approach G5 golf application on the Oregon (even as paid upgrade).
  3. [x50] Provide small icon/large icon configuration setting which uses same high color icons but in a smaller format so there is less map clutter
  4. Right scroll buttons (right arrow) should "wrap" to the first page if you've reached end of a page sequence. Similarly for the left scroll button.
  5. Paging down should "wrap" to the top of the page if you reached the bottom of a page or list. Similarly for paging up.
  6. Add a configuration option to allow the user to auto screen lock if the screen or power button has not been used in a certain period of time.
  7. Add a configuration option to disable tones and turn off the backlight when the screen is locked. If you are carrying a locked unit in your pocket the backlight frequently comes on and tones can be heard if the screen is hitting another object.
  8. Once locked the power button screen should auto-exit after few seconds if the power button is pressed. If the power button is hit accidentally this may prevent the unit from being inadvertently unlocked.
  9. Add different color modes to improve readability under bright sunlight. Schemes should include dark letters/numbers on light backgrounds for pages like the odometer page.
  10. Tapping the lightbulb on the power button screen should cycle the backlight setting between full backlight, user defined backlight and no backlight (similar to GPSMAP 60CSx). "+" and "-" should be used to control the persistent user defined backlight level.
  11. The space between rectangle buttons (e.g. in Settings) could be made smaller -- this would allow to have direct access to 6 (instead of 5) buttons. That means less scrolling and faster access to all functions.

Resolved

  1. (x50: 2.3) Fixed user heading setting for mils so that all applicable headings are displayed with the correct heading format. Projection tool doesn't properly handle headings set to Mils. User is directed to enter bearing in degrees although unit is expecting Mils and projection is displayed in degrees when completed. Same issue as on OR400t which was fix in 2.99 (2.10)
  2. (3.2) Fixed potential issues during power on. Not sure what this issue addressed. Still seeing power on hangs after loading new gpx files, leaving that issue open.
  3. (3.15) (x50: 2.3) Added LKS92 map datum
  4. (3.10) Improved Spanish keyboard
  5. (2.99) Improved display of numeric degrees and mills. Improvement is related to font used for degrees in list views. Previously the display of mils would be truncated to 3 digits. In addition there were several bugs in the Waypoint Projection tool which incorrectly asked the user for input in degrees when what was expected was mils. Similarly the projection was presented in degrees not mils.
  6. (2.96) Added customizable text to unit power-on screen (see \Garmin\startup.txt)
  7. (2.95) Added new trip computer dashboards. TOD in seconds is now available on the Trip Computer screen. There is no place on the Oregon to see the time of day seconds. All of the time of day data fields are hours and minutes only. (2.94)
  8. (2.94) Improved Main Menu setup and added option to add and remove items.
  9. (2.94) Improved readability of configurable data fields
  10. (2.94) Fixed increased battery consumption and shutdowns in some units. (Crash) Oregon randomly powers off for some users (2.93)
  11. (2.94) Fixed increased battery consumption and shutdowns in some units. (Crash) Oregon sometimes hangs on the first boot after loading a new gpx file. Batteries must be removed to proceed. (2.93)
  12. (2.94) Fixed increased battery consumption and shutdowns in some units. Oregon drains batteries much faster in 2.93 than in previous releases (2.93)
  13. (2.85) Improved battery gauge for NiMH batteries. This does work much better with the new release. The battery meter is inaccurate when using NiMH batteries. The battery meter will quickly drop from 4 down to 2 bars (usually within minutes of inserting fresh batteries) and hold at 2 bars until there is about 1 hour of battery left. There is a brief drop to 1 bar 10-15 minutes before the unit powers off entirely. The progression of the meter should be more linear. (2.8)
  14. (2.85) Improved stability when changing profiles. Sometimes after switching profiles the unit displays the "Default" pebbles background image instead of the selected background image. Power cycling the unit clears the problem. (2.8)
  15. (2.7) Added a display option in the setup menu to save battery power. Under Setup>Display>Battery Saver is a new option that allows the user to configure battery saver mode. If this feature is enabled and the backlight timeout feature is enabled when the backlight times out the enter screen will be turned off.
  16. (2.7) Fixed shutdown that can occur when you enter coordinates in demo mode. (Crash) Put the Oregon in Demo mode using Setup>System>GPS>Demo Mode. Go to WhereTo?>Coordinates, enter new coordinates and press the check mark. The Oregon will shut off (2.6)
  17. (?) No specific Garmin release note. Verified that loading gpx files outside of \Garmin\GPX caused the file to be ignored. There are cases with both Mac and PC USB hosts where deleted gpx files are not actually removed from the Oregon storage device causing geocaches, waypoints, tracks, routes, etc to remain on the device even though the user believes they have removed them. This is a very common issue with Macs which move deleted files to /Volume/.Trashes instead of actually deleting the files. If the user doesn't empty trash the Oregon continues to read the data from these gpx files even though it appears to the user that they have been removed. Similarly there are cases under Windows (i.e. 3rd party tools and bugs in Windows) where the Oregon drive can end up with a Recycle Bin which causes deleted files to be moved to [drive]:\Recycled. The Oregon should ignore files in both directories. Note the same issue exists for Wherigo cartridges and files. (2.5)
  18. (2.6) No specific Garmin release note. (Crash) When the Oregon is plugged into a computer and in mass storage mode without batteries installed some units power off right after the archive of current.gpx data. In this case the unit had a nearly full track log and it happened several times. Batteries were placed in the unit and it successfully archived the data and transitioned into mass storage mode. Other users tested this but have not seen the same failure. Can no longer reproduce this problem, probably related to memory full and long connect times. (2.2)
  19. (2.6) No specific Garmin release note. The Oregon takes a very long time to archive current data when connecting to a computer, sometimes as much as 4 minutes, when the tracklog is full. The Colorado is somewhat faster but this operation should be optimized since most people do not actively delete the tracklog (2.5)
  20. (2.6) (Crash) Fixed issue that caused a shutdown during power on. After upgrading to 2.5 the unit will no longer boot. Unit freezes during boot. Resolved by using recovery procedure and redoing the upgrade. Some users report hard reset may also recover the unit. Could be the same issue as 4) below if the user upgrades with a large gpx file loaded. (2.5) Observed: 3-5 times, several users. (Crash) Unit hangs during reboot after loading a large GPX file. Some users report that the unit eventually can start after multi power cycles, other have to use the recovery procedure. If the unit restarts data in geocaching database is corrupted (reading descriptions on caches causes the unit to freeze). Unloading the gpx file, rebooting, and reloading the gpx file fixed the corruption issue (probably because the internal database was purged). Seems to happen with about the same frequency and at the same time as the "memory full" issue resolved in 2.4/2.5. May happen more frequently with more waypoints loaded and/or a nearly full track log. (2.5) Observed: Many times and many users.
  21. (2.4) (Crash) Fixed issues causing a 'Memory Full' warning message. Sometimes after loading large gpx files the unit will generate Memory Full messages, Database Errors and Route Calculation error messages. Power cycling does not clear the problem. In the one case a gpx file with 1440 waypoints was loaded with about 1000 geocaches and 440 waypoints. After rebooting with the new file the unit indicated Waypoints were 14% full and the tracklog was 85% full according to Setup>Reset. However, the number of waypoints on the unit should have been closer to 45-50%. Removing all of the gpx files and rebooting with no gpx files resolved the issue. The same file was reloaded and worked without errors. (2.3)
  22. (2.3) (Crash) No specific Garmin release note. Occasionally the Oregon will freeze when connecting the unit to a computer in mass storage mode. The freeze happens during the saving of current data or just after as the screen displays the graphic of the computer connected to a GPS. (2.2)


Profiles


Bugs


Missing features


New feature requests

  1. Add the ability to have measured data fields (e.g. odometer, average speed) be profile specific so that switching the profile would restore the previously saved values for the restored profile.
  2. All configuration should be per profile but certain configuration options like Language, Units, Battery Type, Time Zone should query the user and give them the option to change the option across all profiles.


GPS Receiver & Satellite


Bugs


  1. WAAS performance is very poor. Setup>System>GPS Mode>WAAS causes the Oregon to add WAAS satellites to the locate list and cycle through WAAS satellites but the Oregon takes a very long time to lock onto WAAS satellites. In the northeast when the Oregon is powered on (cold-start) it will initially try to locate and acquire satellite 51. The Oregon will display a white bar for a minute or two and then start cycling through satellites in this order 51, 33, 48, 35, 33, 34, 35, 36, 47, 48, 51. Eventually the Oregon may achieve WAAS lock but it can take 30 minutes or longer even if there is a clear view of the WAAS satellite. If the Oregon is power cycled (warm-start) the white bar for satellite 51 will display, drop and then come back again and finally lock as a green -- this takes about 4 minutes, whereas the 60csx lock within seconds under the same conditions. May have been some minor improvement in acquiring lock with open view of sky in 2.93, but Oregon still quickly loses WAAS under cover. (2.98)
  2. The Oregon reports and detects too much stopped time when being used at walking speeds. As compared to other Garmin high sensitivity receivers the Oregon periodically reports a Speed of 0 mph even though the unit is moving 2-3mph. Speed fluctuates significantly at low speeds and Stopped Time increments as a result. (2.98)

Missing features


New feature requests

  1. On the GPS satellite page add an additional button for quick access to the GPS mode configuration (e.g. normal / WAAS / simulated GPS)
    GPS.jpg

Resolved

  1. (3.2) (x50: 2.3) Added GPS firmware 3.70. GPS firmware is much more stable than previous release, fixes most drift and jitter issues in tracklogs. GPS receiver sometimes has significant drift (>100') for lengthy period of time (>10 minutes). (2.98, 3.10, 3.13)
  2. (2.98) Fixed not acquiring signal from all satellites in view.
  3. (2.98) Changed EPE to be more dynamic in changing conditions
  4. (2.98) No Garmin specific release note. Receiver accuracy is good but produces very noisy tracks. Trip odometer reports data that is higher than previous releases and other Garmin GPS devices (60csx). Related to GPS improvements in 2.93. (2.93)
  5. (2.93) Improved GPS reception. The Oregon trip odometer reports data that is consistently 6%-15% lower than the tracklogs it records. Similarly the trip computer records low as compared to other Garmin high sensitivity handheld receivers (60csx and Colorado). (2.6)
  6. (2.93) Improved GPS reception. GPS performance is very erratic with 2.86 software with sometimes large (100'-200') errors observed. Reported accuracy numbers have improved but actually accuracy is much more variable. Unit is more sensitive to movement although the "too much stopped time issue" seems to still be a problem. (2.86)
  7. (2.86) Improved GPS performance at slow speeds in tree cover. Changes have been made in this area but the general consensus among most users is that the unit has more error than before (prior to and including 2.86). The unit is more sensitive at slower speeds but maybe too sensitive with these changes.
  8. (2.6) Improved position accuracy calculation. GPS accuracy (aka EPE) is now much closer to the 60csx and Colorado.
  9. (2.6) Improved static position accuracy.
  10. (2.3) Added ability to set position after pressing the go button when GPS is in Demo Mode. Oregon does not support the "Set Location on Map" feature that most Garmin receivers support for simulation of routes from a location other than the current location of the GPS (CO, 60csx) (2.2)
    • Put GPS in demo mode Setup>System>GPS>Demo Mode and then WhereTo?>[search for a new location] or select location on a map and hit Go. There is a new option "Move to Location" which will move the GPS to the new location.
  11. (2.3) Improved GPS performance. Not clear what this improvement was (2.2)


Navigation & Routes


Bugs


  1. [x50] Route recalculation when off-route sometimes takes a very long time to happen (when compared side-by-side with an OR400). (2.10)
  2. [x50] Reproducible route recalculation that takes an 8 mile detour rather than a simple readjustment of the route. Driving north on an interstate, exit one exit earlier than the suggested route. If I have lock on road set I get a very quick route recalculation on the exit ramp that tells me to get back on the interstate going south for 3-4 miles, perform a U-turn, drive north 3-4 miles and rejoin back to the original route. (2.10)
  3. [x50] Frequently during auto-routing the unit displays an extra "off-road" leg at the end of a route which shows up on the map page but not in the active route tool. The issue is not always reproducible on the same route although I've seen it many times. (2.30)
  4. [x50] Adding photos as a route point from the map page does not work. In Route Planner select Create Route>Select First Point>Use Map and select a photo from the map and Use. Note that the photo added has a blank entry in the route point list. If you exit route creation and reenter the point will disappear as if it hasn't been added to the route. (2.10)
  5. [x50] (Crash) Create a route using waypoints or photos as route points. Navigate to the route and select a route point (blue pin) on the map page. The multi-object selector should activate showing two objects with the same name (the route point and the waypoint/photo). Select the route point and you will see an a blank information page. At this point the unit will freeze requiring a battery pull to restart (2.10)
  6. [x50] The elevation plot of a route does not display the symbols of associated route points (or it only displays some of them). If some are displayed reversing the route seems to wipe them out. Route Planner>[select route]>Elevation Plot (2.10)
  7. [x50] When selecting or reviewing points for a route in the Route Planner the name of the point does not show up in the map page button. Route Planner>[select route]>Edit Route>[select route point]>Review and note that the button at the top of the map page does not have a name in it. Similarly: Route Planner>[select route]>select next point>Recent Finds>[select point} and note that (in some cases) the button at the top of the map page does not have a name in it (2.10)
  8. [x50] The "distance to waypoint" displayed in the list view, in the button at the top of the map page and in the waypoint detail view are based on different calculations and precision. The distance in the waypoint detail view should provide more precision (like the x00). All three calculations should be done using the same formula so that they give the same results. (2.10)
  9. The output of Where To>Cities>ABC should be sorted in distance from the current location. It is not. (3.01)
  10. The data field "Waypoint at Next" only works if you are navigating along a route, it does not display the name of the waypoint if you are navigating directly to a Waypoint. Like other "Next" fields (e.g. Time to Next, Dist to Next) this field should display the waypoint name even if the waypoint is the final destination. (2.99)
  11. Centered search tool doesn't work in Route Planner when selecting route points. Edit a route in the route planner, "Select Next Point" and use the "target" button to select a destination. Selecting items from the Search Near menu brings you back to options in the route editor and does not display recent finds, waypoints, etc as expected. (2.99)
  12. When displaying the elevation plot of a long route the unit can hang for a very long time causing the user to think the unit has frozen. The Oregon should display the "spinning hourglass" during all lengthy operations (2.94)
  13. Switching between routing on-road for distance and on-road for time does not cause the Oregon to reroute. Switching between on-road and off-road will force a reroute, switching between the on-road settings should have the same behavior. (2.93)
  14. Start an autoroute and enter the Active Route Tool. The turn-by-turn summary list includes a distance to each turn but no turn direction arrows. (2.97)
  15. When using older versions of City Navigator (City Navigator Europe 5) the Oregon fails to find a State/Province when autorouting to an address or crossroad. With CN Europe 5 loaded, select WhereTo>Address. Begin text entry for a State/Province, the Oregon does not find any matches. City Navigator 2008 and 2008 NT work without issue. (2.2)
  16. Recalculate on On Road without satellite fix results in routes that cannot be stopped and stopped routes which do route. (2.6) To reproduce both bugs follow these steps:
    • Power on Oregon where where it does not have GPS signal
    • Setup>Routing>Guidance Method>Off Road
    • Setup>Map>Map Information>[autorouting map Enabled]
    • WhereTo>[select some destination]>Go
    • WhereTo>Recalculate On Road
    • (Bug #1) WhereTo does not provide the option to Stop Navigation
    • WhereTo>[select another destination]>Go
    • WhereTo>Stop Navigation
    • (Bug #2) Move to a place where there is signal, navigation on roads begins even though it was canceled previously
  17. Selecting Setup>Routing>Off Road Transitions>Manual gives the user an alert with incorrect information. The warning indicates that to step through route points the user must press LEFT and RIGHT. On the Oregon the user simply needs to tap the route point to select it, this warning is left over from the Colorado (2.85)
  18. In some cases routing on the Oregon 300 is different and less efficient than Mapsource. In the example below the Oregon chooses a much longer track using "On Road for Time" routing as Mapsource (6.14.1) using City Navigator Middle East 2008. (2.6)

Middle_East_Routing.JPGpcmap.JPG


Missing features

  1. Oregon is missing the "add as Via Point" option when selecting a destination under WhereTo? when there is an active route (Nuvi) (2.97)
  2. Oregon is missing the route detour feature (CO) (2.97)
  3. There is no option to have the navigation text always appear, including when not navigating. This is useful for seeing upcoming cross streets when the unit is not navigating. The navigation text should be separate from the data fields. (60csx) (2.97)
  4. The Active Route tool does not provide the ability to display custom data files like Leg Distance, Leg Time, Distance to Point, ETA to Point, etc. (CO) (2.97)

New feature requests

  1. Provide the ability to hide the pins and labels of route point makers so they do not obstruct map detail on the map page.
  2. Provide the ability to change route color, width and transparency so routes can be configured to not obstruct map detail on the map page.
  3. [x50] Add the ability to search for photos by name in Where to?>Photos
  4. The desc tag on a route should be visible when viewing the details of a route. In Mapsource you can add a Note to the properties of a route which ends up on the <desc> tag of the gpx file. When you view the details for a route by selecting it in the Route Manager or from WhereTo? you can only see the name of the route, it would be nice to see the desc field as well.
  5. When navigating an off road route the first leg of the route should be a dynamic magenta navigation line from the current position to the point in the route the unit is navigating to. Currently the navigation line is static point-to-point line and it is not possible to easily see where the unit is navigating and the progress which has been made.

Resolved


  1. (x50: 2.3) Fixed issue with the address wizard not searching in the correct city
  2. (3.20) (x50: 2.3) Added support for GPI routes. This feature allows for support of new "Trail Routes" packages Garmin is offering (discussion).
  3. (3.15) Fixed issues with routing avoidances
  4. (3.10) Improved automatic route recalculation. Autoroute automatic route recalculation takes too long. In many cases when the Oregon has been off route for more than .3 miles (moving directly away from current route) the unit still has not recalcuated a new route automatically. (2.98)
  5. (2.97) Fixed map stopped drawing while autorouting (2.96)
  6. (2.86) Fixed possible shutdown when searching for an address and selecting Search All cities
  7. (2.8) No Garmin specific release note. Ferries are now used although there is still no configuration option. The Oregon has no routing option to support to routing using ferries. Ferries seemed to be avoided by default. (Nuvi) (2.6)
  8. (2.85) Improved stability when changing profiles (Crash) Unit sometimes shuts off when switching profiles with an active navigation destination. To reproduce the problem follow the following steps with City Navigator NA NT 2009 and the built in 400t Topo maps (2.8)
    • WhereTo?>Stop Navigation (to cancel any active navigation)
    • Profile Change>Automotive (or a profile with autorouting enabled)
    • Power Down
    • Power Up
    • Let unit acquire satellite lock
    • WhereTo?>Waypoints>[select a waypoint]
    • Allow the autoroute to complete
    • Exit the map page
    • Profile Change>Geocaching (or a profile with direct routing enabled)
  9. (2.4) (Crash) No specific Garmin release note. Create a route in the Route Planner and view the Elevation Plot of the created route. Zoom in on the X and Y axis and then quit. Scroll the plot back and forth (left and right) and notice that the elevation plot flattens and eventually freezes the Oregon (2.3)
  10. (2.3) Fixed being unable to pan or zoom when reviewing a route. Select a route in the Route Planner and select View Map. The map page available can be zoomed but not panned like every other map page on the Oregon. (2.2)
  11. (2.3) Added option to add a point from the map in Route Planner. Cannot add a point from the map to a route in the Route Planner (2.2)
  12. (2.3) Added option to search near a point on the map in Where To?. Need ability to search near a point on the map (2.2)
  13. (2.3) Added preview of on-road routes in Route Planner. A route is always shown on a map as off-road route, user is not given a choice to use road data. Added preview of on-road routes in Route Planner. When routing is set to On Road, View on Map will show the autorouted route on the map. (2.2)
  14. (2.3) Added preview of on-road routes in Route Planner. The elevation plot of a route is always based on off-road routing, there is no option to show the profile using road data. (60csx) (2.2)
  15. (2.3) (Crash) Fixed issues with Cyrillic characters. When you approach a roundabout in automotive/routing mode with Czech set as the language the Oregon shuts off. You can hear beep and the unit turns off leaving garbage on display. Believe this is the Cyrillic language issue referenced in Garmin's release notes. (2.2)


Waypoints & POIs


Bugs


  1. [x50] The dates in waypoint file names are derived using Zulu time not the local time zone. For example, in EDT (GMT-4) if I create a waypoint on 7/8 at 8:01pm the unit creates a file called Waypoints_09-JUL-09.gpx for this waypoint. Note the timestamps in route file names appear to be correct. (2.10)
  2. [x50] Malformed GPX file is created after deleting a photo included in a waypoint. Take a photo, create a waypoint, edit the waypoint and "Change Photo" to add the photo to the waypoint. Goto the Photo Viewer and delete the waypoint. In USB Mass storage mode open the Waypoints gpx file associated with the new waypoint. The waypoint entry has a bogus "/" before the wpt tag. There is also still a link to the deleted photo which should probably be cleaned up. (2.10) For example:
    • </<wpt lat="42.592734" lon="-71.328666"><ele>80.654160</ele><time>2009-06-12T22:05:38Z</time><name>003</name><link href="DCIM/1000GRMN/DSC00125.JPG"/><sym>Trail Head</sym></wpt>
  3. [x50] GPX files are not loaded (waypoints or geocaches) from the SD drive. If you copy a file into [SD drive]:\Garmin\GPX the contents of these files do not show up on the Oregon 550t. (2.10)
  4. From the WhereTo?>Extras list the unit displays heading arrows for each custom POI category. This doesn't make sense and is not consistent with how lists are displayed under map POI's which have sub-categories. (2.99)
  5. Selecting a waypoint and POI at the same location on the map page does not activate the multi-object selector, you can only select the waypoint. Select a POI and tap the save as waypoint button, exit and goto the map page. Select the location of the POI/waypoint and note that only the waypoint is selectable from the map page (2.98)
  6. During symbol entry for a waypoint it is not possible to determine the currently selected symbol by looking at the screen. Selecting Change Symbol should highlight the symbol currently used until the user makes a selection. (2.98)

Missing features

  1. There is no way to clear the Recent Finds list without performing a master reset. (60csx, CO) (2.98)
  2. Newly created waypoints should immediately show up on the Recent Finds list to make them easy to locate for subsequent navigation (a very common operation) (60csx) (2.98)
  3. WhereTo?>Search Near should list All POIs as an option or alternately from any POI you should have the ability to "Search Near Here" (60csx) (2.98)
  4. No support for custom waypoint symbols (60csx) (2.98)
  5. Search and delete by waypoint symbol is not supported (60csx) (2.98)
  6. Waypoint symbols are not visible in list views (e.g. recent finds) (60csx) (2.98)
  7. After selection a navigation destination (i.e. Waypoint, POI, Geocache) the type of point and the symbol should be displayed in the summary box at the top of the screen with the green Go button (not just on the map). (60csx) (2.98)
  8. On the Waypoint/Geocache/POI list views when you select the ABC button to start a spell search you should not have to enter any characters to get an alphabetical listing of all Waypoints/Geocaches/POIs. Currently you have to enter at least one character which means getting a filtered list of points and they are not in alphabetical order. You shouldn't have to enter any characters and should be able see the entire list sorted alphabetically. In some cases when a point is over 20 miles from your current location this is the easiest way to search when you don't remember the name. (60csx) (2.98)

New feature requests

  1. Add the ability to see the "cmt" field of waypoints imported from gpx files. Particularly with geocaching child waypoints this field is used to describe the waypoint and it would be nice to be able to see this information on the detailed waypoint screen.
  2. [x50] When selecting "Change Photo" from a waypoint edit it is not obvious which photo is selected (if there is one)
  3. Add the ability to disable the proximity alerts that display when arriving at a destination. Alternately, make the alerts smaller (like the 60csx) so that the entire screen is not covered.
  4. The UI design for the edit waypoint screen is very poor. In order to edit a waypoint you should immediately see all of the waypoint parameters (not just the name) and fields rather than having to select each to view it and determine if it needs to be changed. In 2.6 coordinate entry improved.
  5. Add support for a special Home waypoint and shortcut to goto Home.
  6. Add support for a set of high priority "core waypoints" (on Nuvis this is "My Favorites") that can be loaded and managed separately from all other waypoints. Frequently I want to have a "core" set of waypoints always loaded on my GPS: Home, Work, Friend's House, etc. I'd like to be able to delete all other waypoints on the unit (ie. those more temporary waypoints related to Geocaching for example) without deleting the core set.
  7. When you mark a new waypoint you should be given the option to navigate to the waypoint without having to go back to WhereTo?>Waypoints.
  8. The special cursor movement mode visible when editing waypoint fields should be eliminated and incorporated into the other data entry screens to reduce keystrokes and jumping between modes, similar to how coordinate entry works now.
  9. Waypoint symbol pages should be alphabetized, it is difficult to remember whether you need to scroll right/left to find a particular symbol.
  10. Change Symbol should land you immediately on a page that contains the most recently used set of symbols.
  11. Editing the coordinates of a waypoint could be optimized, the touch pad should be look like this:
    1 2 3 Up
    4 5 6 Down
    7 8 9 ^/v
    < 0 > >>
    The number scheme is well known and easier to use, the two empty button fields may be used for ">>" jump to next number field (from degree to minutes from minutes to second etc.) and "^/v" jump to first/second line.

Editing Names

There are some points which could be improved concerning editing waypoint (or track) names
• the used character for a space looks like a hyphen, this should be changed
• there is no possibility to insert characters (insert/overwrite mode or just inserting spaces)
• multiple tipping necessary to get the cursor to the end/start of a text line
• no possibility to enter special chars with accents etc.

These things could be done without compressing the actual user interface, here are some screen shots demonstration this (personally I find, that a "single" window containing the cursor/edit buttons would look better than the seperated buttons):
Edit_Main.jpgEdit_SelectPage.jpgEdit_EditChars.jpg



Needs Verification


Resolved

  1. [x00] (3.20) Fixed potential shutdown related to drawing 32-bit map points. Believed to be same as item below.
  2. [x00] (3.13) Fixed potential shutdown with custom POIs with custom symbols. Sometimes in automotive mode the unit will shutdown on the map page when navigating to a custom POI or with custom POI's visible on the map screen. (3.12)
  3. [x00] (3.12) Fixed issues with back button not appearing when editing a waypoint. Edit a waypoint and modify a parameter like "Location". After completing the edit of the parameter there is no red "X" in the lower left corner to return to the main menu. Selecting View Map allows you to return to main menu. (3.12)
  4. (2.97) Fixed lockup when a search returns no results. Introduced in 2.96.
  5. (2.96) Added Waypoint Averaging application. No support for waypoint averaging (60csx) (2.94)
  6. (2.96) Increased the number of waypoints viewable from the Waypoint Manager and Where To?>Waypoints
  7. (2.95) Added POI subcategories. Map POIs should support the ability to filter by category, currently the Oregon only supports filter by database. Note 2.85 added support for databases and categories on custom POIs but not map POIs (Colorado, 60csx) (2.94)
  8. (2.94) Added ability to edit a waypoint from the waypoint review. Should be able to edit a waypoint without having to enter the Waypoint Manager. For example you should be able to edit a waypoint selected from the WhereTo?>Recent Finds, WhereTo?>Waypoints lists or by selecting the waypoint from the Map Tool. (CO) (2.93)
  9. (2.93) No Garmin specific release notes. The Spell feature under WhereTo?>Custom POIs is confusing. If you enter a letter which is contained in one of the database names you will get a list of database names to select from. If enter a letter/sequence which is not contained in one of the database names you can search all Custom POIs. Search should probably do one or the other not both. (2.93)
  10. (2.93) No Garmin specific release notes. Under WhereTo?>Custom POIs>All Databases no POIs are displayed ("No Results Found") even if there are multiple databases containing POIs (2.86)
  11. (2.86) Improved Custom POI spell search.
  12. (2.86) Improved Custom POI database organization. Loading a single custom POI database does not work properly. Using POI loader (2.5.3) to load a single gpx file as a custom POI database results in a single entry under WhereTo?>Custom POIs which when selected appears like a waypoint in the middle of the Atlantic (link). POIs in the database are only visible during a "Spell Search" of the database. (2.85)
  13. (2.86) Added distance and bearing to point when reviewing a Custom POI.
  14. (2.85) Fixed some scan points not working properly with Garmin GB Discoverer maps
  15. (2.85) Added support for Custom POI database and category selection. This resolved the issue for Custom POIs, however Map POIs are still do not display categories. The Oregon should have the ability to narrow POI searches by selecting POI categories. POI categories are not visible on the Oregon. (CO, 60csx) (2.6)
  16. (2.6) Fixed issue when marking waypoints in the W Malayan RSO position format.
  17. (2.6) Added GDA 94 datum.
  18. (2.6) Added NAD 83 datum.
  19. (2.6) Added 'Coordinates' option to the 'Where To?' menu. Support direct entry of coordinates as a destination under WhereTo?>Coordinates (Zumo/Nuvis) (2.5)
  20. (2.6) Improved user interface for waypoint location editing. When entering UTM coordinates (Waypoint Manager>[Waypoint]>Change Location) there is no space between the easting and northing (2.5) The notation in the coordinates is confusing because a 2-digit degree number has a "-" in the leading position which looks like a negative sign. When there is no character the position should be blank. Entire set of coordinates should be visible when editing the coordinate field of a waypoint. At a minimum there should be a confirmation page where the entire set is displayed before accepting the changes. (60csx) (2.5)
  21. (2.4) Fixed issue with duplicate waypoint names. User now gets a warning if they try to create waypoints with the same name. Create two waypoints with the same name "Test". The second waypoint will not be renamed and there is no warning that the waypoint was not renamed. (2.3)
  22. (2.3) Improved handling of naming a waypoint the same as an existing waypoint. This does not fix the issue above. (2.2)
  23. (2.3) Fixed creating invalid gpx files after projecting a waypoint. Projected waypoints have corrupted <desc> fields that cause current.gpx to be unreadable by Mapsource. From the Main Menu select the Waypoint Manager Tool and select an existing waypoint. Project a waypoint and save the newly created waypoint. Connect the Oregon to a computer and open current.gpx in Mapsource. You will receive an error "There was a problem communicating with the device" because the projected waypoint has garbage characters in the <desc> field. Opening the gpx file in a text editor reveals that the waypoint <desc> tag has bad characters. Deleting the waypoint fixes the problem. (2.2)
  24. (2.3) Improved feedback when typing an invalid character into the keyboard. The keypad available for various characters in the coordinate string should be optimized to only show the characters valid for that location. For example the keypad needs only N, S, E, W when entering the lead character for latitude or longitude. Invalid character entry results in a beep and the character is highlighted red. Note: This fix actually prevents invalid characters from getting entered as well. (2.2)
  25. (2.3) No specific Garmin release note. Sometimes during coordinate entry the display gets confused when entering numeric data. The result is the numeric entry pad is displayed on the symbol selection grid. Use the Mark Waypoint tool to create a waypoint and select Save and Edit. Select Change Symbol and select a different symbol for the waypoint, then select Change Location and hit the check mark to exit cursor move mode. The number grid will be displayed on top of the grid used for symbol entry. (2.2)
  26. (2.3) Improved feedback when typing an invalid character into the keyboard. It is possible to modify the coordinates of a waypoint such that Mapsource will fail to import current.gpx from the GPS. Using the Mark Waypoint function create a new waypoint and then select Save and Edit>Change Location. Edit the longitude of the location to be E-180 00.002 and save these changes. When connected to a computer Mapsource will fail to import waypoints from the Oregon indicating a "There was a problem communicating with the Garmin device". Deleting the waypoint in the Waypoint Manager fixes the issue. The code below shows the illegal longitude value in the current.gpx file. The edit waypoint user interface should prevent the user from entering invalid characters or coordinates. (2.2)
    <wpt lat="42.592850" lon="180.000002">...</wpt>
  27. (2.3) Fixed Custom POIs not being removed from Recent Finds after the Custom POI database was deleted (2.2)
  28. (2.3) Fixed issue where the Oregon would temporally stop responding after a spell search. Similar to issue seen on Colorado where Geographic POI searches would hang the display for several minutes. (2.2)


Maps


Bugs

  1. Disable all vector maps from Setup>Map>Map Information. Return to the map page and notice that all waypoints, POIs and tracklogs are no longer visible (3.41) (2.71)
  2. [x50] Photo thumbnails don't show up in the map page multi-object selector list. Select a point on the map page that includes multiple objects where at least one is a photo. Use the multi-object selection tool on the top right of the map page and note that the photo does not have a thumbnail like other list views. (2.10)
  3. If the user temporarily changes the map orientation on the map page and powers the unit off when the unit is powered back on the Map Orientation setting is now set to the temporary setting. Temporary map orientation changes should never be saved unless the user explicitly changes the setting. (2.97)
    To reproduce:
    - Goto Setup>Map>Orientation and set to Automotive Mode (or just enter the Automotive Profile)
    - Goto the Map page
    - Tap on the map so that the map exits Automotive orientation and goes to Track Up orientation (this is supposed to be temporary change)
    - Turn off the Oregon
    - Turn on the Oregon
    - Goto the Map page and observe that the map is now in Track Up orientation
    - Goto Setup>Map>Orientation and observe that this setting is now Track Up
    Similarly:
    - Goto Setup>Map>Orientation and set to Automotive Mode (or just enter the Automotive Profile)
    - Goto the Map page
    - Tap on the map so that the map exits Automotive orientation and goes to Track up (this is supposed to be temporary change)
    - Top on the Compass Rose symbol in the upper left corner to enter North Up mode (this is supposed to be temporary change)
    - Turn off the Oregon
    - Turn on the Oregon
    - Goto the Map page and observe that the map is now in North Up orientation
    - Goto Setup>Map>Orientation and observe that this setting is now North Up
  4. Panning the map sometimes results in the screen being only partially drawn. If during a map pan the user's finger touches the information bar at the top of the map screen the map is panned but part of the map page is not redrawn (areas which are not redrawn are white) (3.2) (x50: 2.3)
  5. (Crash) Using Mapsource load the same maps from City Navigator NT NA 2009 onto the internal memory and on the SD card. The Oregon will fail to boot and resets during the initialization process (2.5)
  6. Any waypoint, geocache, POI, map point, etc selected as a navigation destination from the Map Tool does not get added the Recent Finds list. (3.2) (x50: 2.3)
  7. Land cover zoom settings do not work with City Navigator NA NT 2009. Land cover is always visible at the 8mi zoom level and below. Setting the land cover zoom settings to anything other than Auto (Off, 20ft, etc.) does not have any impact on the visibility of the land cover. Land cover zoom setting does seem to work with Topo 2008 maps. (2.94)

Missing features

  1. Auto zoom does not work in off-road modes (60csx) (2.97)
  2. When using products like Topo v3 which have a lot of map segments the map screen gets very cluttered when zoomed way out (>120m) because of all the map boarders. Oregon should have a declutter option to get rid of these boards (60csx) (2.97)
  3. Accuracy rings are not supported on the map page (60csx) (2.97)
  4. User to should be able to select the map page zoom level where track up orientation switches between north up and track up. Currently this is fixed at 50mi (north up) / 20mi (track up) (60csx) (2.97)
  5. Map options and setup (e.g. select maps to display) should be available directly from the map page without having to exit and go to Setup>Maps (CO/60csx) (2.97)

New feature requests

  1. Allow the user to change the triangular cursor indicating current location. Provide a crosshair cursor so the map detail of the current location is not obstructed when using Discoverer GB maps. The triangle can easily obstruct a map area of 180m x 120m on a 1:50k map which makes navigation in the immediate area of the cursor impossible.
  2. Topo maps on the 400t must be available on DVD to allow trip planning on a computer and to allow the user to customize the size of the map image load.
  3. Users should have the option of having the map always orient "North Up" when panning in map mode. Panning on the map currently does not change the map orientation when in "Track up" or "North up" mode. Some users like the map to jump to "North up" mode once they start to pan (regardless of the map setting) others like it to say as is. "Panning Orientation" should be added as a configuration option with two options 1) North up or 2) Use Map Orientation.
  4. Map should have the option of setting the data fields and navigation bar to transparent (completely, not just partially transparent like they are now).
  5. Landscape view for automotive mode.
  6. Custom raster image map support.

Needs Investigation


Resolved

  1. (x50: 2.3) Fixed issue where multiple GB Discoverer maps would not draw
  2. (x50: 2.3) Fixed possible shutdown due to deleting a waypoint while panning on the map page
  3. (2.99) Fixed elevation errors when reviewing a point other than a waypoint. Elevation readings based on the DEM in the 400t topo maps are not working properly. Go to the map page and select a location in between two contour lines where there is no other waypoint, POI, etc. You should see a set of coordinates in the "status bar" at the top. Select the status bar and note the elevation at the top of the next page. This reading should be close to the contour lines on the map, but it is not. Example: N 42 29.401, W 071 53.312, contour lines indicate 1960' elevation, DEM shows 358'. (2.97)
  4. (2.99) Added ability to load maps from any img file in the Garmin directory
  5. (2.96) Added option to display four configurable data fields on the map. Add the option of having more than 2 data fields to the map (4 would be sufficient) (60csx) (2.94)
  6. (2.95) Fixed shutdown on the map. (Crash) While driving set the unit to automotive profile and enter the map screen. Tap the map screen to exit Automotive orientation and hit the return arrow in the lower left corner to return. The unit will shutoff. There are other variations of this crash introduced in 2.94 which cause the unit to shutoff. (2.94)
  7. (2.94) Improved render quality of GB Discoverer maps and maps with satellite imagery
  8. (2.94) Added ability to see a list of points from the map when several points are at the same location. If there are two or more features, POIs, waypoints, etc at the same location on the map page it is only possible to select one with the cursor, if the user selects the set they should be given a pick list of available objects to select. (60csx) (2.93)
  9. (2.93) Fixed GB Discoverer map not displaying while zooming (introduced in 2.86 beta)
  10. (2.93) Fixed roads not showing on maps with satellite imagery (introduced in 2.86 beta)
  11. (2.93) Fixed map with no DEM data drawing with a gray background (introduced in 2.86 beta)
  12. (2.93) No Garmin specific release note. Panning the map sometimes results in the screen being only partially drawn. If during a map pan the user's finger touches the zoom controls the map is panned but part of the map page is not redrawn (areas which are not redrawn are white). (2.86)
  13. (2.86) Improved map panning and zooming when shaded relief is turned on
  14. (2.85) Fixed airport points not displaying on the map
  15. (2.85) Fixed roads being shown on top of Garmin GB Discoverer maps
  16. (2.85) Improved map zooming. Map zooming is a little more visually appealing, when a zoom change is made the current level is interpolated and then the new level is drawn once it is rendered.
  17. (2.85) Improved raster map appearance. Improvements seen on GB Discoverer, images are more clear than with previous releases.
  18. (2.85) Improved map draw speed. May be slight faster but not a big improvement.
  19. (2.85) No Garmin specific release note. Probably fixed with the changes in zoom display and zooming When the Map Tool is in Automotive mode and zoomed into the 300-500' level quickly panning map will leave you with a blank or partially drawn map screen. To reproduce this load City Navigator 2009 NA NT and zoom in on the Map Tool while in automotive mode to get the perspective view. Quickly pan the map (do not tap to drop the red pin, just perform a very short drag). The map view transitions to track up but sometimes the map (ie. roads, waypoints, etc) do not get drawn leaving the screen blank except for the location cursor. Sometimes the features get partially drawn (ie. back roads but not interstate highways). (2.6)
  20. (2.8) Added setting to change land cover text size
  21. (2.8) Fixed shaded relief being set to 'Do Not Show'. Setting Relief Shading to "Show if Available" works but the setting is not retained across power cycles. After power cycling the GPS all profiles will have this setting set to "Do not Show" (2.7)
  22. (2.7) No Garmin specific release note. Zoom level settings are global and not stored per profile. In Profile A and Profile B got Setup>Map>Advanced Map Set>Zoom Levels and set all zoom level settings to Auto. In Profile A switch one of the settings, like Map Points, to 20'. Switch to Profile B and back to Profile A. Note that Profile A is set back to Auto. (2.6)
  23. (2.7) Added support for Garmin GB Discoverer maps
  24. (2.7) Fixed a potential shutdown that can occur when panning the map that is showing satellite imagery
  25. (2.?) No Garmin specific release note, closing since I have not seen this issue for several weeks. Panning the map screen sometimes results in the map page not being completely redrawn. Many times there are white spaces left around the boarders of the screen after panning, the only work around is to zoom in/out to refresh the display (2.2)
  26. (2.3) Added option to search near a point on the map in Where To?. When a waypoint is selected the map screen the Oregon does not allow you to search from that selected waypoint. Workaround: You can search from a selected waypoint, just not from the map page, WhereTo?>Search From (target button)>A Waypoint>[find waypoint] (2.2)
    • WhereTo?>[O]>Use Map Point will provide the user with a way to select a waypoint from the map to use as a search center.
  27. (2.3) Improved map drawing performance in some situations. Not clear what the improvements were. (2.2)
  28. (2.3) Improved display of intermittent water areas. Ephemeral bodies of water don't display as blue crosshatch in Topo2008 on the Colorado (like they do on other Garmin handhelds). They display as a light yellow area which is hard to see and it is not obviously a body of water because of the color. Thread with example for Colorado, displays the same on the Oregon. (2.2)
  29. (2.3) No specific Garmin release note. When you pan the map and drop the red pin the Oregon gives a distance and bearing to the selected location. The distance provided should be more precise, currently it only supports distances to tenths of a mile/km, it should support hundredths of a mile/km (60csx) (2.2)
  30. (2.3) Fixed waypoint and geocache symbols not updating on the map after being changed. Pan to a waypoint/geocache on the map screen, select it, change the symbol of the waypoint, return to the map page. The new symbol does not appear on the map page (old symbol is still visible). Workaround: Scroll the waypoint off the map page and back on again, the waypoint is displayed with the new symbol or power cycle (2.2)
  31. (2.3) Fixed issue where left map data field could get stuck on depth (2.2)
  32. (2.3) Fixed city coloring with CityNav 2009 (2.2)
    • This seems to have changed more than just city coloring. The background color of the City Nav maps seems to be white (easier to read).
  33. (2.3) Fixed map getting stuck in north up mode after panning. Sometimes while panning the map in Automotive view the Map Tool can get stuck in north up mode. It is not easy to reproduce. The only way to get back to Automotive view is toggle the Map settings from automotive to track up and back to automotive. City Navigator NA NT 2009 maps being used. (2.2)


Tracks


Bugs

  1. [x00] Tracks imported from Mapsource (and other 3rd party tools) sometimes can't be deleted from the unit. Deleting the file that was used to import them (temp.gpx) and deleting them on the unit will not remove them. The only workaround is to delete the /Garmin/GPX directory and restart the unit, but remove an eventual SD card first. It isn't clear what causes this to happen in the first place but it could be the order of deletion on the unit and removal of the file. (3.22)
  2. Current tracklog segments created before and after power cycling the unit are sometimes joined on the Map page. This causes clutter on the Map page and requires additional editing to clean up the track off-line. The current tracklog should always start a new segment when the unit is powered on and these segments should not be visibly joined on the map page. (3.01)
  3. ETA to Dest and ETA to Next data fields do not work when navigating along a track. Select WhereTo?>Track>[select track] and add ETA fields to map page. Both fields display the current time, not an estimated time to navigate along the track (2.98)
  4. If a track doesn't contain elevation data (e.g. tracks from Mapsource or 3rd party software) the user should be warned when selecting the Elevation Plot or the option should be grayed out. (2.2)
  5. Saved track segments should show "on top" of the the current tracklog. Currently if you save a track segment and change its color it is immediately invisible because the current tracklog is on top (assuming the current track is set to display on map) (2.93)

Missing features

  1. No option to have a daily archive the tracklog on the Oregon. Currently the archive is based on file size. (60csx) (2.93)
  2. Cannot rename a track in the Track Manager (60csx) (2.93)

New feature requests

  1. Mapsource/BaseCamp should display the color of the track as selected by the Oregon and similarly the Oregon should be able to display the color of the track imported from these tools.
  2. Allow some functions to be applied to all tracks (not just a single track). For example "Show on Map",
    "Hide on Map", "Set Color" could be applied to all tracks.
  3. Add the ability to sort the WhereTo?>Track list by distance from location (like waypoints). By default the list is sorted chronologically.
  4. Add the ability to search and filter the Track list by name. (ABC-button like waypoints and POIs)
  5. Add the ability to split a track segment so that it can be saved as a partial tracklog. Currently you can only save an entire track segment.
  6. When saving a partial track the track segment list provided should list the track segments from most recent to least recent. Normally a user will be trying to save a partial track from the most recent track segment (i.e. tracback). In the current implementation the user has to scroll through several pages of tracklogs to find the most recent one.
  7. Cannot view, delete or rename auto archived tracks from the GPS. User should have access to these tracks without having to use a computer.
    • A file manager would solve this problem.
  8. Add the ability to see all track details from the track manager. An additional "Track Information" button under each track could show statistics about the track: start/stop time, track length, area, speed stats, elevation stats, etc.
  9. Navigate from current location (can be outside a track) to the nearest point of the track and then following the track to the point selected in the track (now can only navigate to the end of the track). Show the magenta line from the current location. This will be the track navigability that had garmin in old etrex cx products.

Needs verification


Resolved

  1. (3.70) Cannot change the color of the current tracklog, it is always black. (60csx)
  2. (2.93) No Garmin specific release note. Garmin enhanced NMEA support to include A301 for direct tracklog transfer.
  3. (2.85) Fixed track logging setting being changed when changing profiles while simulating GPS
  4. (2.7) Added a display option in the setup menu to save battery power. Add support for a low-power tracklog only mode. In order to preserve battery life unit should support a mode where the display is disabled and only records tracklogs to preserve battery life.
  5. (2.7) No specific Garmin release note. Tracklog recording setting is not preserved with profile. Change Setup>Tracks>Tracklog to Record, Show on Map in Profile A. Switch to Profile B and set Setup>Tracks>Tracklog to Record, Do Not Show. Switck back to Profile A, verify the setting is still Record, Show on Map and then back to Profile B. Profile B will be set to Record, Show on Map (2.6)
  6. (2.3) Added option to clear the current track from Track Manager. (2.2)
    • Track Manager>Current Track>Clear Current Track


Compass


Bugs

  1. [x00] (Crash) Unit shuts off randomly under the following conditions: 1) unit is on the map page, 2) compass is set on auto and 3) unit is starting and stopping or moving slowly. Shutoff does not happen if the compass is off. Issue happens with and without the compass calibrated. It is not reproducible at will but it happens fairly frequently the Oregon 400t. (3.12, maybe 3.10)
  2. [x50] Seen two instances where the compass was constantly spinning. Both instances either started while I was in the car or just as I got out of a car but did not correct themselves after leaving the car. In both cases the compass had been working and correctly calibrated. Heading field was erratic in both cases and moving above 1-2mph "fixed" the problem because the compass was auto-disabled. In both cases recalibration of the compass failed unless I power cycled the unit because it would repeatedly fail on the calibration of the first axis. (2.10)
  3. [x00] The "Hold Level" warning for the electronic compass should be visible on the map and odometer page if the compass is on and the unit is not being held level. The user can see spinning maps or erratic data fields under these conditions without being able to associate it with the compass. (2.93)

Missing features

  1. Can't set the "auto-compass-on" trip point speed (i.e. compass turns on below XX mph) (60csx) (2.93)

New feature requests


  1. Compass arrow should be wider so it is easier to see. (fixed on x50)

Needs Verification


Resolved


  1. (3.20) (x50: 2.3) Improved compass responsiveness. Compass rotates more smoothly and little slower on the x50.
  2. (3.12) Fixed issues with thresholds used for auto compass switching.
  3. (3.10) Improved compass responsiveness in challenging GPS environment . The heading on the Oregon sometimes freezes for about 90 seconds. It happens under the following conditions: 1) compass is set to auto and 2) unit is turned on and locks while stationary but starts moving almost immediately at car speeds. In these situations it appears that the compass does not disable itself and the heading (and compass/map pointers) get stuck. The heading is not completely stuck but tends to move a few degrees even though heading changes can be much larger. The "hold level" indicator in the compass page is visible even though the unit is moving at 20-40mph. Eventually after about 90 seconds the e-compass turns off and the heading returns to normal. Switching the satellite mode between Normal and WAAS will reactivate the problem. (3.10)
  4. (2.96) Added Sight 'N Go application for the Oregon 300/400i/400c/400t. The Oregon does not support Sight'n Go (projection of a waypoint based on sight with using a bearing). (60csx, CO) (2.93)


Trip Computer


Bugs

  1. Trip computer have badly centered columns titles. Note this is not just a cosmetic issue, poor centering limits the number of characters which can be displayed for the data field titles for internationalization (2.97)
    trip-computer-center.png
    Trip computer center bug
  2. Trip odometer has significant errors (sometimes greater than 50%), worst when hiking slowly under tree cover. The actual distance is under reported (3.80).

Missing features


  1. There should be a way to reset the Elevation fields (total ascent, total descent, max elevation) independent of the Trip Computer data (3.2)
  2. There should be a way to reset the Odometer (not Trip Odometer) data field. There is no way to accomplish this aside from a reset. The user should have the ability to reset this field independent of other fields in the Trip Odometer or Altimeter. (CO, 60csx) (2.97)
  3. There is no way to independently reset the Max Speed field from the Trip Odometer (CO, 60csx) (2.97)
  4. Trip Computer, Compass and Elevation Plot pages should support a "% Grade" data field (Garmin Fitness devices) (2.98)
  5. Realtime display of Altidude Above Ground "AGL" - (is missing altogether).

New feature requests


  1. Include option to add "GPS Altitude" information (as in satellite page) as Trip Computer data field.
  2. Add ability to create additional custom dashboards
  3. Add a function button at the bottom of the Trip Computer page to allow quick access to a submenu containing the following functions:
    • Start/Stop Track Recording
    • Clear Current Track (greyed out if no Track Data is available)
    • Activate/Stop Trip Computer
    • Reset Trip Data (greyed out if no Trip Data is available)
    When clearing or resetting data provide an additional confirmation screen which asks "Are you sure you want to reset?". Additional hints about the stored data, like "Delete track started on 16.5.2009 (123 waypoints collected in 12:30 hours)" would be helpful.
    Trip1.jpg Trip2.jpg
  4. Data fields should be grouped together in categories (like POIs) when selecting a new data field from the list. Eg. all data fields related to time in one category, all related to distance in another etc. This requires a lot less scrolling up and down and will make the data fields faster and easier to find.
  5. There should be a "Pace" data field for speed in minutes per kilometer. Both "Current Pace" for the last kilometer and "Average Pace" since the trip computer was reset.

Resolved

  1. (2.95) Added new trip computer dashboards. No long data fields are available in the trip computer (CO, 60csx) (2.93)
  2. (2.95) Added big numbers option to the trip computer. Big number mode is not supported (CO, 60csx) (2.93)
  3. (2.95) Added new trip computer dashboards. The trip computer should support a "no-dashboard" option to allow the user to configure the maximum number of data fields. (CO, 60csx) (2.93)
  4. (Not an issue) If the trip computer odometer field goes over 1000 miles it starts to report incorrect data (2.2)


Camera (x50 only)


Bugs


  1. (Crash) [x50] Oregon will freeze sometimes when adding photos to waypoint. To reproduce do the following:
    1) Main Menu>Camera
    2) Take a picture
    3) Tap x to exit
    4) Mark Waypoint
    5) Save and Edit
    6) Change Photo
    7) Select most recent Photo in the upper right corner
    8) Use
    9) Tap x to exit
    Repeat steps 1-9 without doing anything else in between. After 10-20 repetitions the unit will crash someplace along the way (2.3)
  2. [x50] The Oregon x50 does not properly decode the coordinates for some images which are geotagged by external applications. The issue might be related to the byte ordering used in the EXIF region. In the example file below both pictures should be located at latitude West 6 and "good" version does show up at that location when copied to the Oregon. However the same picture which was edited and saved in MS Vista Photo Viewer shows up at latitude East 6. Third party applications like Picasa and Opanda EXIF display the photo properly at West 6. The only difference I can see is the "bad" photo uses Motorola (big endian) byte ordering in the EXIF region whereas the good picture use Intel (little endian) byte ordering which seems to be the byte order used by the Oregon. exif_byte_order.zip (2.3)

Missing features


New feature requests

  1. [x50] Add ability to change photo resolution from the camera tool
  2. [x50] Add the ability to copy an image from SD card to internal memory. Useful for importing images in the field from a camera which supports an SD card (especially if this camera also supports geotagging).
  3. [x50] EXIF GPS 2.2 information supports altitude/elevation and it appears that the 550t fills in this field but it is not visible through the user interface. When displaying photo details make elevation visible and when creating a waypoint from the photo, auto fill the elevation field of the waypoint using the photo elevation.
  4. [x50] Add the ability to geotag an image which has already been taken (or was loaded onto the GPS) w/o a geotag
  5. [x50] Provide ability to rotate orientation of photos on GPS
  6. [x50] Add ability to change the name of an image or photo
  7. [x50] No way to search for images by name in Photo Viewer. This isn't really needed for photos taken using the camera since they have similar names but it is nice for images uploaded to the GPS.
  8. [x50] Add the ability to read (2D) QR Barcodes, as you can do on most camera mobile phones. The feature should also parse out GPS coordinate(s) (if any) from the barcodes text and optionally allow the user to add them as waypoints.

Resolved


  1. (x50: 2.3) No Garmin specific release note. Add support for GPSImgDirection in the EXIF region using the heading at the time the picture was taken
  2. (x50: 2.3) Fixed issue with backlight timer not functioning properly. The backlight timer no longer goes off at all when the unit is in camera mode. I would have preferred the unit to support the backlight timer in camera mode but at least it is consistent now. The display timeout/battery saver does not work all the time from the camera screen. If the camera is enabled the screen will never timeout. When the screen is locked on the camera page the display will timeout. However, after the screen is unlocked the display will timeout one more time and then never again until the screen is locked. (2.10)
  3. (x50: 2.3) Fixed possible shutdown from low alkaline batteries when on camera page
  4. (x50: 2.3) Added estimation of the number of remaining photos that the unit can take
  5. (x50: 2.3) Added thumbnail to camera page for quick review/deletion of most recently created photo. Add a delete photo button in camera mode to delete the most recently taken picture (or at least a 3 second window where you have the option to delete the photo immediately after it was taken)


3D View


Bugs


Missing features


New feature requests


Resolved

  1. (2.8) Fixed 3D view not displaying. 3D View doesn't display, only blue is visible entering 3D view. (2.7)
  2. (2.3) Fixed 3D View not showing detail from supplemental maps (2.2)
  3. (2.3) Fixed 3D View occasionally not showing anything. Starting 3D View a second time results in an all "sky" blue display where the ground is not displayed. Start 3D View, quit and restart. Observe that the ground level is not displayed. (2.2)


Geocaching


Bugs


  1. (Crash) Certain html tags in logs cause the unit to hang when displaying geocache logs. GC1AZXZ logs can be used to reproduce the problem if the gpx file contains the Loch Cache log from 8/7/09. This log contains an html comment and white html font tag. Viewing this logs for this cache after either downloading the gpx file or performing "SendToGPS" results in a hang of the Oregon (both x00 and x50 behave the same way). SendToGPS (GPX) Native GPX (GPX) (3.13/2.10)
  2. Oregon does not properly interpret GPX V1.1 files. Garmin's implementation is non-standard and the Oregon doesn't recognize a 1.1 GPX Geocache file as Geocaches. Instead it loads Geocaches as Waypoints. Garmin's GPX 1.1 implementation of the Groundspeak <extensions> is non-standard. The problem is the groundpeak: extension tag qualifiers - they should be there in every extension tag and are correctly recognized in V1.0 files. However Garmin units won't recognize the extensions in 1.1 files and thus see the point as a Geocache unless all the groundspeak: qualifiers are removed. (3.13/2.10)
  3. [x50] Some caches don't display properly on the map preview page (the first page you see after selecting a cache from a list view) when loading 5000 geocaches. The unit appears to load all 5000 caches however many caches seem to be located at some bogus coordinates on the map preview page (near N 00 E 00) even though the coordinates for the cache in the description look correct, the distance to the cache looks correct in list view and the cache is visible on the map page. There seem to be the roughly the 900-1000 are the last caches in the file which have the problem. A smaller number of these caches show up on the map preview page near the center of all the caches in the file (i.e. my home coordinates). GSAK export with 5000 caches and 5 logs. The caches are exported as one 26.6MB file. (2.10)
    • Attached zipped archive of the GPX file which caused the issues described above. The cache Sasquatch exhibits one problem where the cache previews on the map in a location which is not the location of the cache. Similarly the Halibut Point EarthCache previews at the bogus coordinates above. geocachesHOME.zip
    • I've seen a similar problem with a gpx file of around 1400 files. As above, the problematic geocache shows up on the list unfound geocache list normally and I can select it and read the description, but when I preview the cache on the map it appears as if it is 100's or 1000's of miles away. If I goto the cache the navigation never starts, I cannot access the logs, hints, etc that you see that you normally can after navigate to a cache.
  4. If the user loads a gpx file with a newer version of a geocache that what is currently loaded the old version of the geocache will continue to be visible. The Oregon should always load the most current version (based on gpx file timestamp) of the cache available if the cache shows up in multiple files. (2.97)
  5. Selecting the geocache on the map page which is the current off-road destination results in a blank page with just a "Go" and "return" button. The Go button doesn't appear to have any function although the return button still works. (2.97)
  6. The Oregon allows the user to enter double quotes (") as part of the field note log text. Since this is the same character used to delimit field note text the site cannot parse the field note and drops it. Not clear if this is a problem with the unit or the site. (2.5)
  7. If a cache that was marked found is then marked unattempted the last found time on the Geocaching Dashboard does not readjust (assuming that the cache was the most recent cache found). Note the find count does decrement properly. (2.85)
  8. Earthcache/APE/Maze Event/Mega Event icons show as Traditional caches. All geocache icons should be supported. (2.97)
  9. "Needs repair" log attempt on a geocache should not increment the geocache find count and should not add a geocache to the found list. "Needs repair" should have the same semantics as groundspeak's "Needs Maintenance" log. It should be a separate note which has no impact of found statistics. It should also have the same name. (2.97)
  10. Navigate to a Geocache. Stop Navigation. Navigate to a normal Waypoint. The Geocaching Dashboard will continue to show the direction and distance to the last Geocache while Compass/Map point towards the newly selected Waypoint. A possible solution would be to extend the Custom Dashboard Options in Setup, so that different Dashboards can be setup depending on wether one navigates to a geocache or waypoint. (4.20)

Missing features

  1. Add geocache log attempts to calendar (e.g. finds, DNFs) (60csx) (2.93)
  2. Filter waypoints by Symbol (60csx) (4.20)

New feature requests

  1. Display the geocache "placed on" date on the detailed geocache view. gpx files encode the placed on date in the <date> tag of the geocache waypoint.
  2. Add the ability to enable/disable the display of geocaches on the map page. Currently the user cannot disable the display of geocaches on the map page without impacting custom POIs and waypoints. Visibility of custom POIs, waypoints and geocaches are controlled by the Zoom Level for "User Waypoints". Each of these types should have their own independent Zoom Level control, particularly geocaches which could be disabled outside of the Geocaching profile.
  3. The Oregon does not display corrected coordinates which are part of geocache logs. Specifically the optional tag which is not displayed as part of the log is <groundspeak:log_wpt lat="xx.xxxx" lon="xx.xxxx" />
  4. The only time you can edit or view field notes on a geocache is when you log a find. A feature should be added to allow the user to edit and view fieldnotes made as part of any log. When selecting a Geocache from the Found or Unfound list there should be an "Edit Fieldnotes" option which displays the fieldnote, if any, and allows the user to modify them.
  5. Handling of multi-cache waypoints need to be improved in geocaching mode. A geocache should be allowed to have multiple (waypoint) destinations which can be added in the field and be marked as found. This would help with Mystery/Unknown caches as well as offset and Multi-caches.
  6. Oregon should support the ability to add a "Note" log to a geocache at any time. The entry would be time stamped and generate a field note which is a groundspeak "note" on the cache logged.
  7. When the Oregon truncates a geocache description (or any field) the user should get warned after the gpx file is downloaded (see geocache summary page feature request below).
  8. Geocaches marked Found or Did not Find should automatically be saved as waypoints in the current.gpx file so that they can be archived along with the current tracklog.
  9. Geocache type icon should be visible in the geocache list views. Difficulty, terrain and size would be helpful in the list view as well. (workaroundgerman language)
  10. Add icons for disabled/archived caches (e.g. red "X" through the standard icon) so that caches in the disabled/archived state are easy to recognize. Alternately provide some indication in the description to indicate that the cache is in a disabled (or archived) state.
  11. Add icon for "write note" geocaching logs. Currently "write note" logs have no icon in the log list.
  12. Geocaching mode should have a summary page (and extension of the geocaching dashboard) which shows the total number of geocaches loaded and from which files. Other stats would be helpful as well like total number of DNFs, size of the unfound list, truncated cache descriptions, etc.
  13. Add special symbol for "Did not Find" geocaches. Suggestion: Use same cache icons with red background or red hash through the symbol.
  14. Add handling for child waypoints of geocaches. Child waypoints should be associated with a geocache so that they can be found quickly. Removing a gpx file with child waypoints should also result in these waypoints being deleted (like geocaches). Child waypoints could be made into special non-editable waypoints or custom POIs. Current child waypoint names are available in the text it would be nice if each cache had a Show Child Waypoints button that listed the waypoints associated with the cache.
  15. Suggest improvements to geocaching mode (there are many) but being able to select next geocache (don't assume it is always the closest) or parking would be helpful for example. When you complete a geocache you should be given the option to goto the WhereTo? menu, not just Done and Find Next Closest Geocache. Many times my next step is to go (back) to parking.

Resolved

  1. (2.96) Added the ability to view geocache logs separate from the description. Logs should separate from the descriptions because it takes too long to scroll to the logs of caches with long descriptions. A "Show Logs" button should be added at the same level as "Show Description" and "Show Hints" (CO) (2.93)
  2. (2.95) Added 'search near' option to Geocaches search. Currently you cannot search for geocaches from a different location because they are not listed in the WhereTo? menu which is available after centering a new search. Geocaches should be listed on the WhereTo? menu just like the Colorado (CO) (2.93)
  3. (?.?) Not sure if cache owner changed pages to work with Oregon or if they were really fixed. Either way these caches below now work on the Oregon. (Crash) Reading certain cache descriptions causes the Oregon to freeze. Download the gpx file for GC1F974 and copy it to [OR drive]:\Garmin\GPX. Select the cache from the Geocaching list and press the information bar at the top of the screen to display the description. The Oregon will freeze. Note "Send To GPS" works, although a lot of raw html is displayed. This failure only happens if you download the gpx file or load the cache from a pocket query directly from geocaching.com. GC18DFE, GC1H3JQ and GC1E4PK cause similar problems. (2.85)
  4. (2.4) Fixed text writing on top of itself in some geocaches descriptions. Description of certain geocaches are corrupted (text is written over other text) GCTF1Y. GPX file downloaded from Groundspeak on (8/21/08) is provided here. (2.3)
  5. (2.4) (Crash) Fixed freeze when loading some geocaches descriptions. Showing the description of certain geocaches will cause the Oregon to freeze. Download the GPX file for this cache or use this GPX file, GCRBM8.gpx (which was downloaded directly from Groundspeak on 8/18/08). Copy this file onto the Oregon. Goto Main Menu>Geocaches>find and select GCRBM8>select Tigger's Quest at the top of the screen. The unit will freeze. Fails similarly on the Colorado. (2.3)
  6. (2.4) No specific Garmin release note. Geocaching find count increments incorrectly when aborting log creation. Navigate to a geocache and then select Main Menu>Geocaches>Log Attempt>Found. If at this point you tap "back", "back" and "x" to abort the found log the geocaching counter still gets incremented (incorrect) even though the found fieldnote does not get created (correct). (2.3)
  7. (2.3) No specific Garmin release note. If a cache that was previously marked found is later marked unattempted the found count on the Geocaching odometer dashboard does not adjust. (2.2)
  8. (2.3) Added option to save a geocaches as a waypoint (2.2)
  9. (2.3) Added error message when the maximum number of geocaches is exceeded (2000) (2.2)
  10. (2.3) Added error message when the maximum number of gpx files is exceeded (200) (2.2)
  11. (2.3) Added support for downloading geocaches written using Groundspeak v1.1 extensions (2.2)
    • Preparation for a new cache schema
  12. (2.3) Fixed geocaches without names not being in the geocaches list (2.2)
  13. (2.3) No specific Garmin release note. If a cache that was previously marked found is later marked unattempted the found count on the Geocaching odometer dashboard does not decrement. (2.2)


Altimeter


Bugs

  1. Immediately after power on for a period of about 15 minutes the graph displays for ambient pressure, barometric pressure and elevation over time are broken. Set the Oregon so that Pressure Trending is set to Save When Power On and turn off the Oregon for 10-12 hours. Turn on the Oregon, set Plot Type to Ambient Pressure or Barometric Pressure and go to the Elevation Plot tool. On the pressure plot, zoom in on the X-axis to 45 min (max zoom level) and observe that the pressure plot has a huge drop to zero right around the time the unit was powered on. Zooming out to the 3hr level causes this drop to disappear. After enough new data is gathered (15 minutes) this issue seems to go away at the 45 minute zoom level. A similar problem exists with the elevation over time plot, no data is visible on this plot until about 15 minutes after the unit is powered up.(2.6)

Missing features

  1. From the elevation profile there is no way to select a location and view the map at that same location (60csx) (2.97)
  2. There is no way to independently reset the Max Elevation field from the Trip Odometer (CO, 60csx) (2.97)
  3. There is no way to independently reset the Altimeter's elevation data from Trip Odometer data (CO, 60csx) (2.97)

New feature requests


Resolved

  1. (2.5) Fixed issue with elevation over time plot.
  2. (2.5) Fixed issue with barometric pressure. The barometer data field and the barometric pressure / time plot do not work. The data field doesn't provide any reading and the plot drops to zero once 2.4 is installed. Calibrating the altimeter causes the barometer to start working again, however when the unit is power cycled the barometer no longer works. Having auto-calibration turned on with a GPS elevation does not seem to fix the issue either. (2.4)
  3. (2.4) Fixed issues with power off pressure trending.
  4. (2.4) Improved accuracy of altimeter for large altitude changes.
  5. (2.3) Added the ability to control the scale of the x and y axes of elevation plot . Tap the x-axis legend to zoom the x-axis. Tap the y-axis legend to zoom the y-axis. Elevation plot does not provide control over the scale of the "Y"-axis (e.g. elevation, pressure). If there are anomalies (e.g. spikes) in the data this can cause the plot to be zoomed out too far to see the data. (2.2)
  6. (2.3) Added elevation plot type to user profiles. Setup>Altimeter>Plot Type is not saved with each profile, it is currently a global setting and should be changed when the profile is changes like all other settings (2.2)


Marine


Bugs

  1. [x50] With BlueCharts maps enabled in Marine profile, if you select the details of a "marine point" (e.g. Tide Station, Navaid, etc) you will see a bar at the bottom which includes a button called "Chart Details", the "Go" button, etc. Pressing the "Go" button turns the button from green to blue, but does not start navigation to the point. (2.10)
  2. Water temperature data field on the Oregon does not work. When sending NMEA data to the Oregon which includes $SDMTW sentences the Oregon fails to display water temperature in the data field available on the map page and trip computer page. (2.98)
  3. Depth data field on the Oregon does not work. When sending NMEA data in to the Oregon which includes $SDDPT sentences the Oregon fails to display depth in the data field available on the page and trip computer page. Note, depth alarms do appear to work correctly. (2.98)
  4. When the Time Format setting of the Oregon is set to 24 Hour, tide data is still displayed in 12 Hour format. (2.93)
  5. Red and green buoy are not drawn at the correct position in the map. (2.5)

Missing features


New feature requests

  1. Allow a waypoint (and the center of the swinging arc) to be selected as the datum for the anchor alarm rather than using the current position.

Resolved

  1. (2.96) Added Man Overboard application
  2. (2.86) Fixed possible shutdown when reviewing a Tide or Current Point using Where To?
  3. (2.85) Added NMEA 9600 baud
  4. (2.7) Added ability to view marine chart notes for marine points
  5. (2.7) Added ability to change the date for the tide and currents charts. Add the ability to see tide data on days other than the current day. Oregon only displays tide data for the current day. (60csx) (2.6)
  6. (2.6) Added support for marine fishing, nautical, and off modes
  7. (2.6) Added tide and current charts. Add the ability to see tide graphs (60csx) (2.4)
  8. (2.6) Added ability to access marine point information on the review page
  9. (2.6) Made marine POIs available when panning the map. Add the ability to see depth of obstructions. (2.4)
  10. (2.5) Fixed issue with tide station data. Tide data is not displayed when viewing a tide station. No tide times or heights are displayed on the detailed tide station page. This feature was working in 2.3 and was broken in 2.4 (2.4)


Wherigo


Bugs

1. Unit turns off during Wherigo. When you enter a zone with an "on Entry" message while a Input message is displayed the
unit will turn off.

Missing features


New feature requests


Resolved

  1. (2.99) Improved Wherigo stability. Wherigo player performance is slow on the Oregon. Playing the Whack-a-Lackey cartridge on the Oregon demonstrates the issue. Play this cartridge in the most difficult mode with the largest playing field. The performance issue is seen when arriving at a "Lackey" or a "Black Hole". The Oregon freezes for 10-15 seconds each time this happens (2.93)
  2. (2.99) Improved Wherigo stability. (Crash) Selecting an item in Inventory does not display the name, text and images associated with the item and occasionally can crash the GPS. Use the Wherigo Tutorial cartridge to see the issue. Select Play>Inventory>Spacesuit to start. Note that only the "Wear" button is visible, no name, description or image. Click "Wear" and go "back". Sometimes the Spacesuit name and image will display, sometimes the unit will crash. Behavior is similar with other cartridges when you select items from inventory. (2.98)
  3. (2.3) No specific Garmin release note. Sometimes after restoring a Wherigo cartridge clicking the first action after the game was restored brings you to a quit Wherigo with save yes/no dialog instead of continuing (2.2)


Fitness



Bugs


Missing features


  1. Ability to setup and view Heart Rate Zones instead of the Heart Rate BPM (Edge 305 & 705) (3.20)
  2. Ability to set Min/Max Heart Rate alarms based on BPM or Zone (Edge 305 & 705) (3.20)

New feature requests


Resolved



Miscellaneous


Bugs

  1. In the Image Viewer you can pan the entire image out of the screen and far away from it. You should never be able to pan/zoom so that you cannot see at least part of the picture. (2.97)

Missing features

  1. Stopwatch is missing the set lap by distance feature. (60csx, CO) (2.97)
  2. Sun and moon page is missing time of day (60csx) (2.97)
  3. Calculator doesn't support scientific mode (CO, 60csx) (2.97)
  4. Sun and Moon page does not show position of sun and moon in sky (CO, 60csx) (2.97)

New feature requests

  1. The image viewer should have the ability to display the properties of a picture (i.e. name, size, date, etc.)
  2. Image viewer should have the ability to search pictures based on name, date, etc.
  3. Add a torch/flashlight application which automatically enables full backlight with an all white background.
    Torch.jpg
  4. When navigating through the menus, there are up to five or six levels of sub-menus. Going back means tapping multiple times on the left-bottom button (with the back arrow) and one more click on the button (with the red "×") to get to the main menu.
    Pressing and holding the back arrow button for one second (or maximum two seconds) should bring you back to the main menu.
  5. Add ability to change font type (to more readable font type).

Resolved

  1. (2.96) No Garmin specific release note. Set up the Oregon to receive a wireless transfer from another Oregon or Colorado. Instruct the sending GPS to transfer a single waypoint to the receiving Oregon. After the transfer is complete note that the receiving Oregon displays the name of the gpx file transferred in the lower left part of the screen -- it cannot be removed unless the unit is restarted. (2.93)
  2. (2.95) Added change location to Sun and Moon. Sun and Moon page only allows you to get position information for your current location. It should allow you to select a new location (CO, 60csx) (2.93)
  3. (2.95) Added change location to Hunt and Fish
  4. (2.93) Improved connection reliability with Spanner.
  5. (2.85) Added ability to force the Oregon into mass storage mode by holding the power button for 30 seconds while plugged into a USB cable
  6. (2.3) Added panning and zooming to the image viewer. Image viewer doesn't support zoom and pan (CO) (2.2)
    • Add + and - zoom control near the top and dragging the picture pans the image.