Posts by LeeDerbyshire

I don't think I have the kind of remote that you mention. I don't see any option to enable a mouse mode.

I don't have a edid.bin file. I don't even seem to have a /firmware directory under /.config .

I did try another HDMI port quite early on.

Anyway, I got a reply from their customer support: "We are seeing if we can create some software to change this ramp issue on the navigation keys." However, I don't know what a 'ramp issue' is. Maybe a technical term, or just a spelling mistake? At least they replied.

The cec-client output is pretty much the same. I have emailed Cello in the hope that there is a firmware update.

For the right button, I get repeats like this (here is prs:10):

DEBUG: [ 33933] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=44
TRAFFIC: [ 33933] >> 01:44:04
DEBUG: [ 33933] SetCurrentButton right (4) D:0ms cur:17f
DEBUG: [ 33933] key pressed: right (4) current(4) duration(0)
DEBUG: [ 33933] key pressed: right (4, 0)
DEBUG: [ 33933] CheckKeypressTimeout T:51142.040
DEBUG: [ 33933] Key right: idle (duration:0) (4) timeout:500ms (rel:500,rep:0,prs:10,rel:0)
DEBUG: [ 33933] >> TV (0) -> Recorder 1 (1): user control pressed (44)

DEBUG: [ 34264] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=45
TRAFFIC: [ 34264] >> 01:45
DEBUG: [ 34264] key released: right (4) D:3294ms
DEBUG: [ 34264] >> TV (0) -> Recorder 1 (1): user control release (45)

For the down button, I get just one:

DEBUG: [ 36984] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=44
TRAFFIC: [ 36984] >> 01:44:02
DEBUG: [ 36984] SetCurrentButton down (2) D:0ms cur:17f
DEBUG: [ 36984] key pressed: down (2) current(ff) duration(0)
DEBUG: [ 36984] Changed key down (2) D:0ms cur:ff
DEBUG: [ 36984] key pressed: down (2, 0)
DEBUG: [ 36984] CheckKeypressTimeout T:51145.091
DEBUG: [ 36984] Key down: idle (duration:0) (2) timeout:500ms (rel:500,rep:0,prs:1,rel:0)
DEBUG: [ 36984] >> TV (0) -> Recorder 1 (1): user control pressed (44)

DEBUG: [ 37225] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=45
TRAFFIC: [ 37225] >> 01:45
DEBUG: [ 37226] key released: down (2) D:242ms
DEBUG: [ 37226] >> TV (0) -> Recorder 1 (1): user control release (45)

I'll run the cec-client tomorrow.

I've thought about updating the TV firmware. There is nothing on the web site that I can see, so I'll probably need to get in touch via email. My expectations aren't high.

Well, the update went smoothly enough, although I've lost Confluence (but that's okay - I'd rather be up-to-date, and I've learned that I can't entirely leave the thing to do it by itself).

Less happily, it hasn't solved the button problem.

I see. It won't automatically do major version updates.

Is 12.0.2 the current version? I have automatic updates enabled, so I assumed I'd always be on the latest one.

I see that 12.0.2 is indeed the current one. Can I safely go from 10 to 12 in one go?

The Pi is a 4B, LE is 10.0.4.

Okay, I have some output. Apologies for the length.

This is for the short Right press:

DEBUG: [ 146950] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=44
TRAFFIC: [ 146950] >> 01:44:04
DEBUG: [ 146950] SetCurrentButton right (4) D:0ms cur:4
DEBUG: [ 146950] key pressed: right (4) current(ff) duration(0)
DEBUG: [ 146950] Changed key right (4) D:0ms cur:ff
DEBUG: [ 146950] key pressed: right (4, 0)
DEBUG: [ 146950] CheckKeypressTimeout T:83899.165
DEBUG: [ 146950] Key right: idle (duration:0) (4) timeout:30222488ms (rel:500,rep:0,prs:500,rel:0)
DEBUG: [ 146950] >> TV (0) -> Recorder 1 (1): user control pressed (44)

DEBUG: [ 147281] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=45
TRAFFIC: [ 147281] >> 01:45
DEBUG: [ 147281] key released: right (4) D:331ms
DEBUG: [ 147281] >> TV (0) -> Recorder 1 (1): user control release (45)

This is for the long (a few seconds) Right press (which repeats as expected):

DEBUG: [ 149353] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=44
TRAFFIC: [ 149353] >> 01:44:04
DEBUG: [ 149353] SetCurrentButton right (4) D:0ms cur:4
DEBUG: [ 149353] key pressed: right (4) current(ff) duration(0)
DEBUG: [ 149353] Changed key right (4) D:0ms cur:ff
DEBUG: [ 149353] key pressed: right (4, 0)
DEBUG: [ 149353] >> TV (0) -> Recorder 1 (1): user control pressed (44)
DEBUG: [ 149353] CheckKeypressTimeout T:83901.568
DEBUG: [ 149353] Key right: idle (duration:0) (4) timeout:30222488ms (rel:500,rep:0,prs:500,rel:0)

DEBUG: [ 149685] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=45
TRAFFIC: [ 149685] >> 01:45
DEBUG: [ 149685] key released: right (4) D:332ms
DEBUG: [ 149685] >> TV (0) -> Recorder 1 (1): user control release (45)

This is for the short Down press:

DEBUG: [ 153315] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=44
TRAFFIC: [ 153315] >> 01:44:02
DEBUG: [ 153315] SetCurrentButton down (2) D:0ms cur:2
DEBUG: [ 153315] key pressed: down (2) current(ff) duration(0)
DEBUG: [ 153315] Changed key down (2) D:0ms cur:ff
DEBUG: [ 153315] key pressed: down (2, 0)
DEBUG: [ 153315] CheckKeypressTimeout T:83905.530
DEBUG: [ 153315] Key down: idle (duration:0) (2) timeout:30222488ms (rel:500,rep:0,prs:500,rel:0)
DEBUG: [ 153315] >> TV (0) -> Recorder 1 (1): user control pressed (44)

DEBUG: [ 153556] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=45
TRAFFIC: [ 153556] >> 01:45
DEBUG: [ 153556] key released: down (2) D:241ms
DEBUG: [ 153556] >> TV (0) -> Recorder 1 (1): user control release (45)

This is for the long (a few seconds) Down press (which does not repeat as expected):

DEBUG: [ 156065] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=3 addr=01 opcode=44
TRAFFIC: [ 156065] >> 01:44:02
DEBUG: [ 156065] SetCurrentButton down (2) D:0ms cur:2
DEBUG: [ 156065] key pressed: down (2) current(ff) duration(0)
DEBUG: [ 156065] Changed key down (2) D:0ms cur:ff
DEBUG: [ 156065] key pressed: down (2, 0)
DEBUG: [ 156065] CheckKeypressTimeout T:83908.280
DEBUG: [ 156065] Key down: idle (duration:0) (2) timeout:30222488ms (rel:500,rep:0,prs:500,rel:0)
DEBUG: [ 156065] >> TV (0) -> Recorder 1 (1): user control pressed (44)

DEBUG: [ 156305] CLinuxCECAdapterCommunication::Process - ioctl CEC_RECEIVE - rx_status=01 len=2 addr=01 opcode=45
TRAFFIC: [ 156306] >> 01:45
DEBUG: [ 156306] key released: down (2) D:241ms
DEBUG: [ 156306] >> TV (0) -> Recorder 1 (1): user control release (45)

I'm guessing that the 200ms between each press is coming from the setting currently configured for the CEC adapter. I'm also guessing that although the remote is sending long Down presses (or at least sending something), the TV is not forwarding them like it does for Left and Right.

I've noticed a difference between the longpress Down (above) and the longpress Right. The Right longpress shows multiple entries with increasing durations. With the Down, there are no repeats.

2025-05-13 15:06:06.820 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 0
2025-05-13 15:06:06.825 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right
2025-05-13 15:06:07.478 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 658
2025-05-13 15:06:07.494 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right
2025-05-13 15:06:07.679 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 859
2025-05-13 15:06:07.680 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right
2025-05-13 15:06:07.879 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 1059
2025-05-13 15:06:07.893 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right
2025-05-13 15:06:08.079 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 1259
2025-05-13 15:06:08.089 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right
2025-05-13 15:06:08.279 T:1020 DEBUG <general>: PushCecKeypress - received key a8 duration 1459
2025-05-13 15:06:08.293 T:982 DEBUG <general>: HandleKey: 168 (0xa8, obc87) pressed, action is Right

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

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.

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?

Hi All. Can I enable HDMI audio and ALSA USB audio simultaneously in Kodi on a Pi Zero W? In the GUI, it only allows me to select one or the other. My previous model B+ had analogue audio, and there was an option to enable both at the same time, but I don't see similar for USB audio. I want to be able to leave the HDMI active continuously, but, when required, be able to switch on an audio amp close by without having to change the output setting in the Kodi GUI.

Thanks.