Could you please give this test build a try? LibreELEC-RPi4.arm-9.80-devel-20210124165749-4b10646.tar
It includes a couple of patches to trying to fix issues we've seen (audio FIFO overfilling, audio buffer underrun in kodi) and also includes a patch to periodically check for HDMI FIFO issues.
If you run into audio dropouts please upload a pastekodi log. BTW: no need to enable audio or video component logging in kodi, that won't reveal anything interesting and just bloats the log.
so long,
Hias
Remove 4096x2160 from your whitelist - this doesn't work in kodi Kodi switches to incorrect whitelisted resolution · Issue #19037 · xbmc/xbmc · GitHub
so long,
Hias
Check your TV and whitelist settings. Make sure overscan is disabled on TV and kodi actually used 3840x2160 (not 4096x2160).
As usual, debug logs help.
so long,
Hias
Current plan is to release official Alphas for RPi4 along with the other Alpha builds.
RPi2/3 releases will probably follow later as there's a major issue in the video driver (screen going blank). Once that's fixed RPi2 alpha builds will follow.
so long,
Hias
The 4k 24 FPS files I tested with (8 and 10bit HEVC) played fine. Can't say anything about 50/60 FPS as video driver doesn't support 50/60 Hz yet.
so long,
Hias
Quick heads up: the next nightly build adds support for 4k up to 30Hz (60Hz needs more work and will follow later).
It's best to configure display to 1920x1080 60Hz and whitelist 4k 23.98/24/25/30 and 1920x1080 23.98/24/50/59.97/60 modes (plus any other lower res modes you want).
so long,
Hias
in LE 9.2 you can change repeat settings via a udev rule, eg /storage/.config/udev.rules.d/99-my-repeat.rules with this content:
ACTION=="add", SUBSYSTEM=="input", SUBSYSTEMS=="rc", KERNEL=="event[0-9]*", \
RUN+="/usr/bin/ir-keytable --delay=750 --period=150 --device=$devnode"See also /usr/lib/udev/rules.d/70-input-repeat.rules (which applies to non-rc-core devices).
so long,
Hias
Screen tearing is a known issue with the FKMS driver used in 9.2, it's fixed in LE10 nightly builds which uses the KMS driver that doesn't have that issue.
so long,
Hias
Try with "guide" instead of "epg" in the keymap.xml file. The "KEY_EPG" code is mapped to the "guide" button in Lircmap.xml (see the devinput section).
so long,
Hias
I've just sent the fix upstream and created a PR for LE linux (default): add patch to fix ite-cir issues by HiassofT · Pull Request #4908 · LibreELEC/LibreELEC.tv · GitHub
It should be included in nightly builds soon.
so long,
Hias
truespidy I could reproduce the issue here on a PC with ite-cir, it's another kernel bug 
Could you please test with this build: LibreELEC-Generic.x86_64-9.80-devel-20210109151324-492ba03.tar
so long,
Hias
Thanks for the log, the output looks like the remote buttons were pressed for about 2 seconds.
Stop kodi and eventlircd, then run "ir-keytable", then "ir-keytable -t" and push a button for a short time and post the output.
so long,
Hias
Thanks a lot for reporting!
We identified the issue and reverted the breaking change. The next nightly build should be fine again.
so long,
Hias
We temporarily had to revert the HD audio changes as they seem to trash filesystems on RPi2 - we'll add them back once that issue is fixed.
So stay on 20210108 for testing ATM.
so long,
Hias
I tested the devel version from post #33. Unfortunately, this did not solve the problem for me. The current nightly version behaves identically. Each keystroke on the remote is now repeated several times. What commands should I execute to provide a log?
Start with describing your setup (what kind of remote, IR receiver, hardware you are using) and a standard debug log (note: either use the log update function in LE settings or "pastekodi" on the command line).
so long,
Hias
FYI: all changes have been merged into LibreELEC master and are included in today's nightly build.
Please use nightly builds for further testing.
so long,
Hias
Not really sure about the Readrate message - I've never seen that here. Might be worth to check journal/dmesg if there's some actual problem with the USB drive.
BTW: When posting logs from the console please use the "pastekodi" script. This will also include journal/dmesg which can contain very important info. And also please don't use a mouse, that spams the kodi log with lots of useless pointer move messages and it's very hard to find the actually relevant information.
so long,
Hias
RPi4 with 1GB is quite short on memory, if you experience Kodi crashes when navigating through pictures or movie library you may need to tweak GPU and CMA memory - search the forum, this has been asked (and answered) a couple times before.
so long,
Hias
