Posts by HarryH

    You can also use cec-client to get more CEC details than with the KODI debug logging.

    • Stop KODI process: systemctl stop kodi
    • Start CEC client: cec-client

    This CLI client will announced as "CECTester" on the TV. Depending on the behaviour of the TV it could be necessary to switch to the selected HDMI port again, to get CEC to work.

    In general it's sometimes a good idea to disconnect the HDMI devices and TV physical and make all the components powerless simultaneous for some minutes. Afterwards the HDMI handshake will be initiated again and sometimes the CEC issues are like "magical" blown away.

    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.

    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

    My experiences: some VC1 Bluray releases for example "The Bucket List" or "The Red Baron" are not playable fluent anymore, since the VC1 hardware decoder has been dropped with RPi4. Overclocking the RPi4 above 2.1 GHz also seems to make it fast enough to decode these titles via software, but it's like riding the razor's edge as to whether these settings are stable enough to enjoy the movie.

    If you want support from experienced users or from experts like chewitt , you shouldn't skim with information. Snippets of logs are in 99.99 percent are pointless and and results into same as if you post "something is going wrong" - nothing more, no helpful content. Please provide a full debug log like described above.

    Perhaps I should take another look at this. The shutdown script expects the setting value (false/true) to be present. There may be an edge case that I didn't stumble across in my tests.

    EDIT:

    I assume you had a previous version already installed and updated to 1.1.9. Can you remember your workflow? Did you have opened the add-on settings afterwards and left the menu with OK at least once, before you observed the failing shutdown?

    Has anyone else observed the same misbehavior?

    The add-on is now also available for LE12 via the LibreELEC add-ons repo. It was automatically updated in the background, although it was previously a manually installed version 1.1.9. This happened shortly after the start without a confirmation dialogue appearing.
    It was showing in the log that it was 1.1.9 during KODI startup but I couldn't reproduce that situation afterwards, maybe depends on the refresh of the repo inventory. This behaviour was unexpected, but it seems a good working mechanism.

    chewitt , heitbaum ,
    Many thanks for merging the 2 PRs.

    Version 1.1.9 released:

    • compatibility: some early MCU firmware versions could hang off after register support check
    • added menu option to explicitly disable register support detection for ONE V1/Fan HAT

    It would be nice if someone could test with a V1 case whether the effort for this switch was worthwhile and now helps to achieve a functioning fan control or whether it is useless.

    Version 1.1.8 released:

    • Contains a workaround against the long standing installation bug with LE 10 / 11 that after a installation from scratch a error message was thrown and second reboot was required to activate the I2C bus. Happened only if system-tools wasn't already installed before, like if you installed LE from scratch.

      It is therefore more of a kind of clean-up/maintenance of the code to make it reliable for users of the old LE versions 10 and 11. If I look at the download counter at #25 there seems some to stay with LE 10 / 11.

    Have you thought about working around the problem with the missing context menu (long press on OK) if you use a separate button on your TV remote control? I'm not talking about customisation via the Keymap Editor add-on.

    It depends on the manufacturer and model of your TV. Some manufacturers (e.g. SONY) also support passing through the menu buttons via CEC. Sometimes this function has to be specially configured in the depths of the TV settings, but usually there is also a separate button for the context menu by default.

    Maybe this could be an option for you...