I noticed that too on the C code: If keypress comes from the remote control, driver does both "push down" and "release" immediately. Some years ago I made a version that did something like this: I measured that a remote control sends "key pressed" in about 20ms cycles. Thus I decided that the driver can do following: Whe key '1' is pressed initially, send "key 1 pressed to input layer". If within 30ms a '1 pressed' comes from the remote control, driver keeps '1' as pressed (do nothing for input layer). If there won't come a '1 pressed' from remote within 30ms, then driver sends "key 1 unpressed to input layer". I don't know if there is any reusable algorithm (easilly usable code) for remote control drivers for this. Regards, Marko Ristola 21.05.2011 10:23, Adrian C. kirjoitti: > Haven't noticed earlier that every button press is executed twice, until > I did some testing with Oxine. Not sure how much Lirc is to blame for > this, and for button 0 not working. I will move to the Lirc list. > > Thanks again for the patch. > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html