Quote:
Originally Posted by ekaser
I'm quite sure (from much experience with low-power devices that go into 'sleep' modes) that what's happening is that:
1) The unit is asleep (VERY minimal power).
2) You quickly press and release a button.
3) The pressed button starts to wake the unit up, but before it completes its wakeup and scans the buttons to see which one was pressed, you've already released the button, so it doesn't see any button down, and doesn't do anything, and goes back to sleep.
|
That would also explain why the older firmware was more responsive to button presses, since it never went to sleep and ran the battery down in a few days.
