Posts by Da Flex

At which point you had the bug after vanilla LE installation?

Whats the add-on you try to display on the screen shot?

Quote from gabigabi

if that still doesn't work, the cable man should come again.

p.s. : he was there maybe 20 minutes, put his measuring device into the antenna socket and that's it ... a long-term test would be better.

Yep.

The technician probably just measured constant date rate and check sums. The data rate of TV might suffer when EPG data (or other service) is updated. Then it would be a provider error. You should close out that case first, especially if the error happens at non-Kodi devices, too.

Quote from Animejin

are you referring to the Settings -> System -> Peripherals?

Exactly, but because it's for CEC events, it can't help you for IR events.

Nicolas Maybe you're right, I'm not familiar with current DVB-C receiver cards. If the error happens at the same time on different devices, then it could be a provider error, too (worst case).

Not sure whether you got my point.

First, I don't think your cables (or even the fridge ) are the problem. I know DVB-C cable problems, and they usually show up in missing or massively disturbed TV channels. That's not what you have.

My theory is that your DVB-C provider updates EPG data periodically, but (at least) your PC's DVB-C receiver is unable to process EPG data AND showing TV at the same time. Doing those two tasks at the same time probably needs more processing power than you currently have.

So my suggestion is to try a new DVB-C receiver card. It should have better processing power than your current one.

Nicolas I'm thinking of an EPG service, triggered at the same time:

Quote from gabigabi

I still want to get rid of one thing, today I ran my TV and the ASRock J5005-ITX with Digital Devices TV card at the same time, what can I say, the TV also had 4 BER errors at the same time.

If you could use CEC instead of IR, then CEC adapter settings will solve the multi-trigger problem.

Your technician says, DVB-C signal is OK, and top says, kodi.bin process isn't at max. So my theory is that your DVB-C receiver gets a processing overload when dealing with EPG, which leads to continuity errors.

gabigabi / Gabi / Sandra or however you call yourself:

We prefer links to complete logs to get the picture. Read here how to do it.

Which keys do you want to assign for volume control?

Another approach: Start your own script whenever the power button has been pressed. Like the above XML, but with tag content:

<power>RunScript(script[,args]*)</power>

Read here for details. Use a shell environment variable and a Python script to note the suspend state.

If you have to handle that button event under a dependency, like suspend mode, you have to write a script. That script should have a variable, that represents suspend mode. You can use autostart.sh to start such script.

Read here how to edit config.txt.

Read here how to enforce an HDMI mode at config.txt.

Overwrite the power menu call by an empty XML tag at /storage/.kodi/userdata/keymaps/keyboard.xml:

<keymap>
    <global>
        <keyboard>
            <power></power>
        </keyboard>
    </global>
</keymap>

Did you installed the "Raspberry Pi Tools" add-on? It's needed to do GPIO programming.

The user-editable place for add-ons is /storage/.kodi/addons . I'm not familiar with manual add-on installation, but you can try to copy to that location.

1) Usually the TV manual says, which HDMI modes are supported. (please check it)

2) If 1) is OK, the next part of the chain is the HDMI cable. That cable should comply HDMI 2.0 or 2.1 standard to be able to transfer high 4K data rate. (please check it)

3) If 1) and 2) is OK, you can enforce 4K / 60Hz by adding this lines to config.txt:

hdmi_group=1
hdmi_mode=102