[RPi5] Weird TV Remote Behavior

    Hi everyone,

    I installed libreelec on my whole new Raspberry Pi 5. I used to have a Pi 3 and wanted to upgrade in order to display 4k and h265 easily.
    Anyway, I have a weird behavior with the tv remote. Here's what I did already :

    I firstly installed my pi on the HDMI port 3. Always used to be on that port (even previous pi 3)
    The thing is, the TV told me that for HDR, I should use port 1 or 2 so I decided to connect the pi on HDMI 2.

    Sadly, the remote does not work when it's connected to port2 while it worked on port3. The funny thing is that when I navigate on a black screen on port 3 and come back on port 2, the navigation took effect. I really don't know what I can do to make it work logically at this point.

    I've read that TV can "save" those kind of device and it might be, because of that. The TV was off for 5 days and the issue is still there, sadly.

    Is anybody have an explanation and a way to fix this ?

    Thank you

    See if there is a solution here:

    Thread

    CEC or Edid problem?

    Hi.



    I recently switched to a pi5 (pi in use before) and have a small problem.

    Everything runs fine, but for some reason when i power the pi on often it wont display a picture when the corresponding hdmi port gets automatically switched by the connected devices. (sometimes even if everything is already set to the correct ones)

    The pi is connected to an AVR and that to the TV....TV & AVR are already turned on



    I also already know why it happens.

    For some reason the physical hdmi port (which can be set…
    Wolfpig
    January 5, 2024 at 1:39 PM

    The general advice for HDMI issues is to physically disconnect everything and leave powered off for 10-mins, then reconnect cables and see if anything fixed itself (as it often does).

    The getedid script solves a single and specific problem; the TV not being powered on before the RPi starts. That's the only issue it solves. It does not solve CEC problems. It does not solve any other HDMI problems. Do not use it, unless you have that issue.

    Thank you all for your help !

    Thanks to the first response, I learned that the getedid delete needed a reboot.

    I then redo a getedid create, rebooted

    After that, it worked again !