Looks like you can mark the thread as solved. ![]()
Posts by Da Flex
-
-
Thanks, I had a look. Follow my advice, and make 4K / 60Hz the last line. Otherwise it can be overwritten by later settings of config.txt.
-
Is LE really updating itself without recreating a LibreElec SD?
Yes. Please post your config.txt.
-
You can also try the Xorg way. The user at my above link has Coffee Lake, but maybe his solution works for you, too. Give it a shot.
-
Bassman Simply add the line at the end of config.txt. By the way, you can safely update to LE 9.2.3.
-
If you're low on money, buy a used RPi 3B(+). Many people upgrade to an RPi 4B at the moment.
-
Probably a driver problem on LE, read here.
-
-
What's the relation to LE?
-
Also, Settings/System/Display won't let me select a refresh rate above 30.00Hz at 3840x2160 resolution. The hardware is capable of 4K@60Hz. Is this expected behavior?
Yes. You can enforce 60Hz at config.txt (hdmi_enable_4kp60), but it's not suggested, because most provided 4K content is lower than 60Hz.
-
Is there's any tutorial on how to make or edit an xorg.conf files. pls im newbie to linux stuff
That's a reason to try my approach first.

Follow my link, and you'll find instructions.
-
You probably need a custom EDID file.
-
-
On a touch-screen-only system without RC, you should try to find the dev of the skin first. Those devs are usually at the main Kodi forum.
If that's not possible, you can attach a physical button at the GPIO, and define it as "back navigation". Easy to do, but ugly.
-
We're not the developers of that skin. As a workaround you can define "back navigation" on your remote control.
Here is an example to define the yellow button as "back navigation" at /storage/.kodi/userdata/keymaps/remote.xml :
-
Papalapa Login by SSH, go into the folder by cd /storage/.update and download the file by wget <URL> .
-
Edit: using powering down of the kodi menu did create a failure. powering down ignoring, reboot, system halted. it stagnated in LibreELEC icon.(this is the nightly build.)
I'm sure this will be fixed at the stable version. You can help to fix this bug, if you provide a link to a log file. Then we can see what goes wrong when you try to shutdown. I suggest to open a new thread at our bug report sub-forum for this issue.
You can mark this thread as solved by editing your first post.
-