And sorry to bother you guys again, but two more issues. They have both been mentioned before.
I attached the debug log where I experienced this loss of HDMI signal when playing a Dolby Vision file.
kodi.log (3.7 MB)
But the funny thing is, when I enable debug logging, the frame skipping issue disappears.
Boot CE, start your DV sample for 2-5 seconds. Stop it by keyboard x or by remote stop. Run dmesg | paste right afterwards.
When this is done navigate to your media file ready to start and run first:
echo 3 > /sys/module/aml_media/parameters/debug_dolby
dmesg -c
Then start media file again for 2-5s and stop and run dmesg | paste again.
You need to use the special mode of debug logging which doesnāt show any extra info on the screen, thatās how I was able to catch it in -ne. I think also the component specific logging should be enabled. Iām not 100% sure but video/audio timing is probably needed here.
After the kernel update to version 5.15.137, I have problems with black screen/no signal displays on my Samsung QLED. It happens every time the HDMI connection is interrupted, for example when the TV is switched off briefly or the AV receiver is switched off. However, Kodi continues to run in the background, because if I blindly start a video in which the frame rate is switched (important), the signal comes back. Without switching the frame rate, only restarting the box helps (restarting Kodi via ssh does not help).
In the system.log there is an error at hdmitx_common_validate_mode_locked..
02_System.log (109.4 KB)
This problem did not occur until kernel version 5.15.119. I leave my Homatics R 4K Plus running 24/7 and normally only switch off the TV and AV receiver. Now I have no picture every time the TV is switched on again.
Unfortunately still wonāt work for me. The same with the couple of my DoVi test clips of my own encodes. They work fine on the latest -ne build using TV-led.
https://paste.coreelec.org/RetinalWelcome (TV-led, black screen)
https://paste.coreelec.org/JumperMissile (Player-led, works)
Maybe because of:
Dec 23 22:56:50.594212 CoreELEC kernel: [drm] meson_vout_update_mode_name: hdmitx update vout 1 name 1080p24hz.
Dec 23 22:56:50.607959 CoreELEC kernel: [hdmitx:] hdr: [hdmitx_set_vsif_pkt]: type = 1, tunnel_mode = 1, signal_sdr = 0
Dec 23 22:56:50.608078 CoreELEC kernel: [hdmitx:] hdr: [hdmitx_set_vsif_pkt]: SDR->MESON_DOLBYVISION Sink-led
Dec 23 22:56:50.649677 CoreELEC kernel: [hdmitx:] hdr: [hdmitx_set_drm_pkt]: tf = 16, cf = 9, colormetry = 0
Dec 23 22:56:50.650000 CoreELEC kernel: [hdmitx:] hdr: [hdmitx_set_drm_pkt]: SDR->HDR10
On Player-Led:
Dec 23 22:58:49.270584 CoreELEC kernel: [drm] meson_vout_update_mode_name: hdmitx update vout 1 name 1080p24hz.
Dec 23 22:58:49.283791 CoreELEC kernel: [hdmitx:] hdr: [hdmitx_set_vsif_pkt]: type = 4, tunnel_mode = 0, signal_sdr = 0
Dec 23 22:58:49.283907 CoreELEC kernel: [hdmitx:] hdr: [hdmitx_set_vsif_pkt]: SDR->MESON_DOLBYVISION Source-led
Please make same logs again with this image:
I have same exact issue. S905X4.
https://paste.coreelec.org/AnubisGrowl - TV-led
https://paste.coreelec.org/GenderChuckles - Player-led
Iām trying out NO on Odroid N2+ and have the nightly for 24/12 installed. Thereās an odd problem with my remote.conf (which is the same file I use on NG). The key for move left doesnāt work. Iāve tried correcting this using keymap editor but the addon doesnāt see the keypress. The key is working in my NG setup using both of the remotes I own.
Iāve attached the file Iām using. I have it in the root directory of the SD card Iām using for the try out.
remote.conf (665 Bytes)
I hope you can help with this. Back to the immaculate NG 21.1.1 for now. Happy xmas and respect guys.
I have the same problem on a minix mini X3 box
The āleftā key on the IR remote dont work whith the last nightly
I test another IR remote whith another remote.conf
In this configuration the āmouseā key dont work
Downgrade to 20241220 and check if still not working. If not you will need to record the IR code for this button and also like for left, right, down and up. Search for ir-keytable -u is forum.
20241220 work 20241222 , 20241224 dont work
I use with 20241224 the ir-keytable -u command
The IR codes are normal eg:
1b - right
5a - left
But right work, and left dont work
remote.conf (2.8 KB)
I have same exact issue.
TOX3 S905X4.
CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20241222.tar - no picture
CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20241224.tar - no picture
CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20241220.tar - everything is ok
Same on Khadas VIM4 - after upgrade to kernel 5.15.137 HDMI output stops working and doesnāt come back even after reboot. Receiver tells me there is no signal being transmitted for either audio or video.
Downgrading to last 5.15.119 (20241220) release, display is back to functional.
Same thing happens on beelink gt king 2 (a311d2) and I also noticed that if I play videos on YouTube addon audio is fine but image freezes on first frame. If I disable acceleration it works fine.
On nightly of 17/12 all is back to normal .
On 20/12 it also gives the same hdmi problem . Strangely it didnāt gave on 20/12 before going to 24/12.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice