In a way it is the app's fault. By pegging the CPU to run the processor-hungry emulator, threads that handle input often find themselves sleeping longer than usual, which limits the number of events that can be registered in a given amount of time. As the emulator is better optimized, it won't be as CPU-intensive, and this problem should improve over time. Additionally, I am adding a "turbo" feature to buttons at some point in the near future, which could be used in cases where rapid button-pressing is necessary.
