I also disabled DV once and then all the DV modes became unavailable until I rebooted. I did the same later and I did not have that problem.
I'm guessing it's because I am using a centralised MariaDB database. Maybe it killed the network connection. Dunno. Just glad I didnt have to reinstall from scratch
Display MoreI have been trying to diagnose my issue with the test files playing as 2.35:1 using Grok (yeah, I know). In doing so, I found a nasty bug.
I tried disabling DV processing in the Player menu. When disabled, the files played as 16:9. All good. However; when I went to change it back to Dolby Vision, all of the available options showed as "unavailable" and could not be selected. Okay, try a reboot... It gets to the Piers screen and comes up with "failed to initialise databases. exiting". Now just bootlooping. Not good.
Grok narrowed the initial aspect ratio problem down to....
That isolates it cleanly.
When DV processing (CB1) is enabled → image becomes 2.35:1
When DV processing is disabled (native Kodi) → image is correct 16:9The problem is inside the CB1 Dolby Vision pipeline of the CroqueMr build, not in Kodi’s normal video path, the whitelist, the TV, or the file container flags.
Most likely causes in this build
- Mis-handling of L5 / active-area / letterbox metadata in the Dolby Vision stream
- The “skip processing on black-bar / inactive areas” optimisation incorrectly treating part of the 16:9 frame as inactive
- An interaction with Fast rendering, FEL upscaling method, or the specific rendering mode you are using
Disaster averted! I unplugged the Kodi box and powered it on again. Booted and was able to select DV again. Phew. Still hopefully it's useful feedback.
I think my issue is something to do with this
https://forum.kodi.tv/showthread.php?tid=366528&page=3
Probably outside the scope of this project. Might try the CRU thing
Okay, I installed the debug version and played the three test videos. Hope this is useful...
I did a clean install of Beta4 but there still seems to be some issues. When I play the three "test" files, they still all seem to have the wrong aspect ratio. I am assuming they are 16:9? The FEL Test is weird: when it starts, all i get is a black screen. However, if I activate the OSD, the picure appears (red screen). Turn off the OSD and it goes back to a blank screen. It does come on by itself about halfway through.
Also, I am using the Estuary Mod V2 skin and it blocks all access to the Enhanced player information. I just get the basic one. Thats probably a "me" problem!
This is my hardware...
LG C9 TV
Clean install, no add-ons or mods
I installed R1.0.0-Beta3 on my backup Libreelec box (GK3V Pro + LG C9). Still a bit flaky for everyday use but its getting there!
For some reason, the "All Layers Test" was showing in the wrong aspect ratio. Looked like cinemascope. Also, as has been previously mentioned, the on-screen menu and Player Process/Player Debug displays were cut off.
I did install over the top of standard Libreelec v13, not sure if that was a good idea?
I've reverted back to LE 21.2. I'll stick with that until Kodi v13 appears. If it was affecting other users, it would be worth following up but not just for one device.
Okay, here's what I have discovered:
Clean install of 21.3 Generic freezes within a minute of booting
Clean install of 21.3 Generic-Legacy freezes within a minute of booting
Clean install of 21.3 Generic (latest nightly) freezes within a minute of booting
Clean install of v13 Generic (latest nightly) seems to be happy (so far)
The problem I have is that I am using a remote MariaDB. I updated kodi-headless to 21.3 (with the intent of then updating the mini-pc's). It has created a new database. I need to have all Kodi devices running the same version for them to use the same database. I don't seem to be able to upgrade the mini-pc's to 21.3 and I don't seem to be able to downgrade kodi-headless to 21.2 (not available). As v13 has not been released yet, there is no kodi-headless version for it.
I don't know if the problem is an incompatibility with the Gemini Lake chipset? There doesn't appear to be anyone else having problems with the update, so I guess I'm just unlucky.
Generally yes, but the old X11 can sometimes fix issues like this.
If the clean install doesn't work, I'll try it. Thanks
Enable SSH and see if you can access the device to run “pastekodi” and share the URL or perhaps just “dmesg > dmesg.log” or “journalctl > system.log” to dump info to disk so that post-downgrade you can do “cat *.log | paste” and share URLs. In short, we need to see some logs to have any idea what the issue might be.
I don't think it gets as far as connecting to the network. I tried to connect with ssh but not available.
I will try a clean install rather than upgrade, see what happens
Same with Generic-Legacy?
Haven't tried. Been using Generic up until now. I thought Legacy was for NVidia cards?
I have two GK3 Pro mini PC's. They have been running every version of Libreelec from Matrix to Omega 21.2.
I did an update to 21.3 on one PC and it doesn't like it. It hangs at the splash screen and after a while shows Hard and Soft Lockups. Just in case it had become corrupted, I undated the second PC too. The behaviour was the same. I have downgraded them back to 21.2.
Does anyone know what might be causing this?
CPU: Intel Celeron J4125
GPU: Intel UHD Graphics GPU
Memory: 8GB
Storage: 256GB SSD
Where/how did you disable it?
Doesn't seem to be an option for it on my router (TP-Link AX1800). Is there a way to disable it in the adapter settings in Libreelec?
My little Celeron-based box running a recent Nexus nightly has a RTL8821CE and runs reasonably reliably. Sometimes I have to restart as it fails to connect and the list of available wifi networks is empty. Always connects after restart (although if I refresh the network list they will disappear again.)
The RTL8821 driver has been in the nightlies for quite a while.
Thanks for solving this problem. I used your instructions to do the same for my G20BTS remote. However; "70-local-keyboard.hwdb" didn't work for me so I added the lines to the existing "99-osmcrf.hwdb". The README file in that folder states that "
your files must be named 99-xxxxx.hwdb", so I don't know if that's why it didn't like it? I am on 11 nightly (Dec1).
It's this one, if anyone else need to do the same
evdev:input:b0005v2B54p1600e0000*
KEYBOARD_KEY_c0041=enter
This looks similar.
Very helpful, thanks
I got the same problem with this remote (BPR1 model, simplest one):
https://www.aliexpress.com/item/100500420….2576f19cHxTbSj
Any luck?
Nope. I asked about it over on the Kodi forum in the thread for the Key Mapper add-on. No response (so far).
Hi guys,
I have searched and found a few similar threads but no solutions.
A couple of years back I bought an G20S RF remote for my LE box (PC/Generic) and it works perfectly. Recently, I bought a couple more. Also G20 models but "Pro" (more buttons/backlight/bluetooth). The new ones have an issue with the "OK" button not being recognised.
If I go into Keymap Editor, it does register the OK button but it is not the same five-digit format as the rest of the keys. So, Global/Navigation/Select Item is set to 016839168 but doesn't work!
Apparently, this is something to do with the remote sending a "KEY_ENTER" instead of "KEY_OK"?
If Kodi is registering the button press there must surely be a way to map it to "Select"?
As others have found, If I turn on the airmouse, the OK button functions normally (but I find it difficult to control 
).
Any advice would be much appreciated!
You could try copying the EDID file from the TV/monitor via the getedid script, here is how: Custom EDID [LibreELEC.wiki]
Thank you!! Worked perfectly.
