jup

I keep running into both of these issues all the time while geocaching on hikes. I think the crash has been introduced by latest firmware (2.90) - there is other thread about it. It does not happen just with geocaches, but often with other POIs as well. Add to it that any such crash will mess up track statistics (total elevation climbed will usually start counting from 0 after crash) and I have multiple crashes per hour and unit is basically unusable for simultaneous geocaching and track recording. The geocaching screen issue on the other hand I believe has been around for a while, as well as quirks with responsiveness (basically, the screen "thinks" part of it is pressed and reacts to that). I've seen it on different then geocaching screens as well though it's most easily replicated with geocaching screen. The only solution is power cycle.

I take this one back. It can be gotten to a state when it dies before you have a chance at master reset. I did the mistake of putting geocache files into unit directly, and it just died up. Since one can't effectivelly remove internal storage, there's no way to get it to some normal state. Recovery procedure worked for me, although I had to alter the step 6 (when you just realease power button after LOADER is displayed, it reboots and dies again, while holding the power button a bit longer seems to work). This is starting to become RPITA, though. Had this happened somewhere without computer access, I'd just end up with little worthless brick. Since this unit is supposed to be one of the best on the market for geocaching, and since simple pocket queries can so easilly break it, I would recommend everybody to just not buy this piece of trash right now. Bugs that break barometer are just a nuissance, but bugs such as this one make this unit very unreliable, IMO.

I've seen my Oregon freeze during start-up countless times. I was travelling with two micro-SD cards containing 2000 geocaches each, and switching them according to region. When I switch the cards, Oregon obviously goes through process of reading all those geocaches, which takes some time, and with 2000 caches in my experience freezes at least 50% of time. Some times, after freeze, when it's turned on, it freezes again. Other times, it will just boot quicky, but geocache database ends up incomplete/empty (and nothing short of removing micro SD card and inserting different one/master reset can force it to read the card again). Once it gets throuph process of reading whole geocache database without freeze, it usually works flawlessly until card change, although there's one hurdle. For weird reasons, sometimes Oregon reads geocache database even when the card isn't changed (you can tell, because start up takes much longer then usuall), and again freezes at least 50% of the time when attempting this. It seems to be realed to former Memory full issue. With firmware prior to 2.4, unit offten generated Memory Full message after changing card, and ended up with incomplete geocache database, but freezes were less common. With 2.4 or 2.5 firmware, Memory Full message is gone, but freezes happen instead. Master reset always worked for me, and it hardly ever freezes right after master reset. But, having to master reset unit about 5 times a week kinda sucks. I hope to see some fix for this soon.