Makes sense if the firmware sucks
Tom Martin said:
This used to happend with my 295. It is caused by an improper internal vent. It used to happen to me after being at altitude for a while and then descending. It would lock up for 15 to twenty minutes until the pressure stabilized and then the buttons would work again. Send it back to garmin.
Tom Martin
Try this on for size..
Rubbery buttons are made in a sheet with the buttons drawn into them with a conductive button that makes contact with the printed circuit when pressed.
Sounds to me like while descending the increasing pressure finds a seal and presses the button(s) down. The firmware expects a press-and-release and waits and waits and waits for release. Meanwhile, nothing else gets done. Eventually, the pressure equalizes and the button 'releases' and processing resumes.
**********
I actually hope I get shot down on this and someone finds another reason because:
1) I don't like posting when I haven't tried it myself .. but..I couldn't resist and...
2) Boy, I make my living fixing things just like this and don't like the implications.
3) And I'm buying lots of Garmin and..
4) Its late.. and..
5) If 'venting' is the solution to 'processing' ... hmmmm..Experimental
Someone.. go flying and press and just hold some button and see what happens.. Holding a button indefinitely should not hang the firmware. That said, buttons in an airplane should not be sensitive to pressure changes.
Lets find the problem before I spend money
Thanx
John