Yes. Hit the power button briefly to bring up the brightness/lock screen. The time is visible in the lower right corner, tap the time to see the date and day of week.

B3.) How do I search from a location which is not my current position?

Go to Main Menu>WhereTo? and hit the target button at the bottom. This will allow you to select a Recent Find or a Waypoint as the origin of your search. This function can be used recursively to narrow a search.

B4.) How do I perform a screen capture on the Garmin Oregon?

First navigate to Main Menu>Setup>Display>Screen Capture and configure this setting to On. Tapping the Power Key will now capture the screen. Note: This setting is not remembered across power cycles, if you turn the unit off you'll need to set it again.

The screen images are stored in [OR drive]:\Garmin\scrn as bitmap files with the format NNNN.bmp where NNNN is a 3 or 4 digit number.

B5.) Can I lock the screen to avoid button presses when I put the device in my pocket?

Yes. Tap the power button and you will see a "Lock Screen" button. Once you press this button the touch screen is disabled until you tap the power button a second time and press "Unlock Screen.

B6.) I have found issues with the Oregon's language translation in my language. Can I fix this?

Yes. The language files for the Oregon are stored in [OR drive]:\Garmin\text as XML text files. You can modify these files to correct the translations. If you are making corrections please contribute to the OpenGTT project which has corrections for some languages.

B7.) Can I add a custom startup message on my Garmin Oregon?

Yes. Connect your Oregon to a computer in USB mass storage mode and edit file [OR drive]:\Garmin\startup.txt in a text editor like notepad. You can add several lines of text at the end of this file which will be displayed at startup. This feature is useful for adding contact information in case the unit is lost.

Modifying the line <display=0> in the same file will change the the number of seconds that custom startup message is displayed (i.e. <display=5> will display the message for 5 seconds). Note your boot time will increase by the same number of seconds, so a value between 5-10 seconds is a reasonable setting.

B8.) Some foreign characters are not showing up in my Garmin Oregon custom startup message. How do I fix this?

The \Garmin\startup.txt file needs to be saved as UTF-8 encoding format to display all character sets properly. If you are using notepad to edit this file, select File>Save As and under "Encoding" select UTF-8 before saving the file.

B9.) How much information can I put in the startup.txt file?

The Oregon supports up to 5 lines of text. Each line can be a maximum of about 30 characters (proportional font is used).

B10.) How come my startup message didn't not appear or why did my startup message change when the Oregon was starting up?

After you make any change to the startup.txt file you need to restart the unit once to load the new file and sometimes you will see the text change during the startup process. On the second power cycle you should see your changes.

B11.) What happens if I delete/corrupt/overwrite the a file on my Oregon? Can I backup my Oregon?

It is gone forever and, unfortunately, it is a relatively easy thing to do. It is very easy to backup your Oregon and I would strongly recommend backing up the entire contents as soon as you purchase it. Plug the Oregon into your computer and copy the contents of the entire Garmin drive to some location on your computer. You can then burn this to DVD so that if you lose your map file (or any other file) you can recover it. Note the files on your Oregon are not protected, it is very easy to delete or overwrite if you are not careful. An Oregon 400t/550t has about 3GB of file system data so a backup operation takes several hours, a 200/300 should backup significantly faster.

B12.) What time zones are available on the Oregon?

The Oregon firmware offers a list of time zones under Time in the Setup menu by region name and not by UTC offset. For a complete list of available time zones with UTC offset and DST information, visit the Time Zone page.

Issues

Bugs

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)
[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)
(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)
(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)
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)
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)
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)
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

[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)
Oregon doesn't support night/day color modes. (60csx) (2.98)
The order of all distance-based lists (ie. waypoints, recent finds, geocaches) should update dynamically as the unit is moving. (60csx) (2.98)
[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) .
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

Add ability to set the time period over which the average speed data field is calculated.
Provide a golf profile or some ability to use the Approach G5 golf application on the Oregon (even as paid upgrade).
[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
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.
Paging down should "wrap" to the top of the page if you reached the bottom of a page or list. Similarly for paging up.
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.
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.
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.
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.
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.
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

(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)
(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.15) (x50: 2.3) Added LKS92 map datum
(3.10) Improved Spanish keyboard
(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.
(2.96) Added customizable text to unit power-on screen (see \Garmin\startup.txt)
(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)
(2.94) Improved Main Menu setup and added option to add and remove items.
(2.94) Improved readability of configurable data fields
(2.94) Fixed increased battery consumption and shutdowns in some units. (Crash) Oregon randomly powers off for some users (2.93)
(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)
(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)
(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)
(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)
(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.
(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)
(?) 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)
(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)
(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)
(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.
(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)
(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)