Remote control longpress question.

    Hello. I have an issue where the long down arrow press on my TV remote is not scrolling down title lists of my RPi/libreelec/Kodi. It used to work fine with the remote of my LG television, but I recently changed to a Cello TV, and now although everything else still works, the repeated up/downscrolling does not, meaning that I have to keep pressing the up/down arrows to move up/down more than once. I'm pretty certain that this is going to reduce the working life of the affected button :) Long pressing the left and right arrows still works, but that is of much less use to me.

    I know that the remote is continuing to send a signal, since a flashing indicator on the front if the TV tells me so. Is there any possibility of getting this working as before?

    Try and play a little bit with these settings for the CEC adapter:

    • Remote button press repeat rate (ms): 100
    • Remote button press delay before repeating (ms): 200
    • Remote button press release time (ms): 0

    Settings -> System -> Input -> Peripherals -> CEC Adapter

    Many thanks for the reply, but I'm afraid it didn't help. In fact, I already had those values set, since I'd seen it mentioned in another post while I was searching for suggestions. I've tried all kinds of other values, too, but without success.

    Appears like a firmware issue of your Cello TV. To diagnostic what happens in detail, you could enable the KODI debug logging and watch with tail -F /storage/.kodi/temp/kodi.log which key events will be received from your TV via CEC during you held the up/down arrow keys and if there is a different to left/right arrow keys.
    Some TVs interprets a long press signal from the remote control as a different function or the remote control sends a different key instead of repeating. If there is send a different key via CEC, then you could map this to Channel Up / Down to have page wise scrolling to mitigate the issue.

    Only the last entry here is a longpress (the others are just presses). It looks like it can't see any difference between short down and long down.

    2025-05-13 11:20:40.137 T:1020 DEBUG <general>: PushCecKeypress - received key a9 duration 0
    2025-05-13 11:20:40.145 T:982 DEBUG <general>: HandleKey: 169 (0xa9, obc86) pressed, action is Left
    2025-05-13 11:20:41.541 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 0
    2025-05-13 11:20:41.558 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right
    2025-05-13 11:20:43.117 T:1020 DEBUG <general>: PushCecKeypress - received key a6 duration 0
    2025-05-13 11:20:43.128 T:982 DEBUG <general>: HandleKey: 166 (0xa6, obc89) pressed, action is Up
    2025-05-13 11:20:44.302 T:1020 DEBUG <general>: PushCecKeypress - received key a7 duration 0
    2025-05-13 11:20:44.313 T:982 DEBUG <general>: HandleKey: 167 (0xa7, obc88) pressed, action is Down
    2025-05-13 11:20:47.825 T:1020 DEBUG <general>: PushCecKeypress - received key a7 duration 0
    2025-05-13 11:20:47.828 T:982 DEBUG <general>: HandleKey: 167 (0xa7, obc88) pressed, action is Down