[mythtv-users] Remote keys repeating way too fast

[Doug Scoular (dscoular)]

Hi All,
    Apologies for the earlier incomplete post, I hit the send key
    by accident.

    I just did an apt-upgrade of my ubuntu 20.10 mythtv 0.31 server and
    suddenly my hard won lircd setup has started repeating keys when I
    use my generic Microsoft Media Center remote.

    The update updated mythtv to 31.0+fixes.202103051941.6c7c8b0351 and
    the kernel version to 5.8.0-45-generic #51 so I'm not sure if the
    problem was due to mythtv, the kernel or some other package update.
    Lirc was not updated and remains at 0.10.1[1087].

    I wanted to take lircd out of the equation and see if the problem
    lies with the kernel's dev-input layer, so I shutdown lircd and
    ran evtest to see if the remote's keys generated the repeats.

        root at lisa:~# systemctl stop lircd
        root at lisa:~# evtest
        No device specified, trying to scan all of /dev/input/event*
        Available devices:
        /dev/input/event0:      Power Button
        ... lines omitted for brevity
        /dev/input/event16:     Media Center Ed. eHome Infrared Remote Transceiver (0471:060c)
        Select the device event number [0-16]: 16
        Input driver version is 1.0.1
        Input device ID: bus 0x3 vendor 0x471 product 0x60c version 0x101
        Input device name: "Media Center Ed. eHome Infrared Remote Transceiver (0471:060c)"
        Supported events:
          Event type 0 (EV_SYN)
          Event type 1 (EV_KEY)
            Event code 2 (KEY_1)
            Event code 3 (KEY_2)
            Event code 4 (KEY_3)
            ... lines omitted for brevity
        Key repeat handling:
          Repeat type 20 (EV_REP)
            Repeat code 0 (REP_DELAY)
              Value    500
            Repeat code 1 (REP_PERIOD)
              Value    125
        Properties:
          Property type 5 (INPUT_PROP_POINTING_STICK)
        Testing ... (interrupt to exit)
            Event: time 1618540114.824036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f0421
            Event: time 1618540114.824036, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 1
            Event: time 1618540114.824036, -------------- SYN_REPORT ------------
            Event: time 1618540114.931034, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f0421
            Event: time 1618540114.931034, -------------- SYN_REPORT ------------
            Event: time 1618540115.037033, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f0421
            Event: time 1618540115.037033, -------------- SYN_REPORT ------------
            Event: time 1618540115.143035, type 4 (EV_MSC), code 4 (MSC_SCAN), value 800f0421
            Event: time 1618540115.143035, -------------- SYN_REPORT ------------
            Event: time 1618540115.338814, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 2
            Event: time 1618540115.338814, -------------- SYN_REPORT ------------
            Event: time 1618540115.474815, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 2
            Event: time 1618540115.474815, -------------- SYN_REPORT ------------
            Event: time 1618540115.606815, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 2
            Event: time 1618540115.606815, -------------- SYN_REPORT ------------
            Event: time 1618540115.738815, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 2
            ... repeating lines omitted for brevity ...
            Event: time 1618540127.938815, -------------- SYN_REPORT ------------
            Event: time 1618540127.938815, type 1 (EV_KEY), code 106 (KEY_RIGHT), value 0
            Event: time 1618540127.938815, -------------- SYN_REPORT ------------

    One key press of the right arrow key on the remote generated
    around 96 KEY_DOWN events.

    I tried playing with ir-keytable's -D and -P options but this just slowed down the
    repeats and I still got around ~96 repeats. It doesn't matter which key I hit either.

    If I start up lircd, irw reports the same issue as I understand it simply reading 
    from the kernel input layer.

    I even upgraded the kernel from 5.8.0-45-generic #51 to 5.8.0-50 #56 in the hope
    that the problem in the input layer might already have been fixed... but no joy.

    Any thoughts hugely appreciated.

Cheers,

Doug
--
"The big print giveth and the small print taketh away."