I had opened up bug 2751 on this issue a few days ago (https://bugs.maemo.org/show_bug.cgi?id=2751). From doing a bit of research and testing, it appears to be load related -- if a key press results in a spike in cpu utilization, the key release code doesn't go through so the app thinks that the key is still pressed down. So I previously didn't notice this until I configured microb to do a page down with the d-pad.

I did a bit of additional research, and I've seen this same issue reported in various Linux distro forums (google keywords: "linux key repeats stuck"), and a common theme seems to relate to cpu load, and power management. Apparently on some portable devices the power management circuit is shared with the keyboard interrupt, so back-to-back key interrupts get lost (one interrupt for a key press, a second one for the key release). I don't know if that relates to the same probelem that we see on the Nokia devices, but it sounds plausible. Here's a thread talking about this on Ubuntu: https://bugs.launchpad.net/ubuntu/+s....15/+bug/39315