After spending some time turning pages, I have been paying attention to the times when the Gen3 seems to miss the button press. I have noticed that when it "misses", the green activity LED does turn on. If I press again while the light is on, I seem to get a quicker page turn.
My guess as a real-time Linux programmer is that the button press is doing two things: 1) it is waking up the Gen3 from a low-power state. This seems to take a little time. Then it looks at the button states to determine what action to take. If I have let go of the button after "waking" the unit, but before it scans for the button press, it will miss the page turn. If I hold the button down just a little longer, the page turn works.
If my hypothesis is correct, there are a couple of ways the problem might be fixed. If the I/O chipset that is connected to the buttons can be programmed to "latch" or hold the press state until cleared, the button press would be available after the unit gets around to reading the buttons. Another way to reduce the likelihood of a quick press not registering would be to move the button-read logic earlier in the wake-up cycle. This might require some kernel programming or driver modifications.
Or I could be entirely wrong.
