IIRC, LE RetroArch isn't GL accelerated yet, all the cores are software mode.
Good point. frankvw was talking about Tombraider, which is an OpenGL game. Maybe only the non-GL PS1 games run smooth on LE.
I would try dual boot with a gaming OS as workaround.
True statement. Support means updates and answering questions. Very important, and it means long-term costs for companies.
Since the release of RPi 4B we have a low-cost 4K streaming box, which runs LibreELEC, and has free support. 
It's hard for streaming box companies! Even China can't concurrent with it. That's why this forum is currently under attack from there.
That said, Mario77 has it running fine on his RPi2 so there must be something wrong with my install or settings.
Do you use RetroArch as suggested by Mario77? Or maybe the ROM's are wrong (not optimized for the emu).
PS1 games are known to be very demanding on an RPi. Not sure if they run smooth on any RPi OS.
Multi-Threading is the best way to get max. performance, but the PS1 emu has to be made for this (can be a serious task).
See what pure gaming OS'es can do, and then compare with the LE performance.
If you see room for improvement after this, make it a feature request.
Because Serviio supports:
- Movie thumbnails (Kodi - not supported or not working; I've seen complaints in forums but no solution)
- Video playback resume (not supported in Kodi; scrolling with TV remote to a middle of the 2hrs movie - nightmare; and you have to remember where you stopped)
- Sorting automatically my TV series into series, seasons, last watched episode etc. (not so good in Kodi)
Good ideas for feature requests. Go for it! 
To install Java for this would be kind of an overkill.
So is it possible to install Java, FFmpeg, libRTMP, libASS, libx264 and libmp3lame to LibreELEC?
No.
Tell us what you want to do, and maybe a solution beyond Serviio already exists.
Sorry if I didn't explain it very well. Somehow I pressed a button on my Verizon FIOS remote that enabled the Kodi mute function. I had not mapped any keys on the remote to be a mute button. I tried several buttons, but it didn't un-mute. Had to attach a keyboard to get it to un-mute.
You can do two things with my method:
a) find the already defined and undesired mute button, and disable it by overwriting it with a "noop" action
b) keep the undesired mute function alive, and use a color button to un-mute (copy my example, and press yellow)
I'm using an RPi 3B+, too. Yesterday I went back to LE version 9.0.2, because the system went into safe mode a couple of times with LE 9.1.002.
I suggest to use the stable version 9.0.2. If you still get issues, post the log as mentioned by Iridium. Your current link doesn't works.
Sir, you could define a mute / un-mute button on your remote control (full keymap list).
Here is an /storage/.kodi/userdata/keymaps/remote.xml example:
<keymap>
<global>
<remote>
<red>VolumeDown</red>
<green>VolumeUp</green>
<yellow>Mute</yellow>
<blue>ContextMenu</blue>
</remote>
</global>
</keymap>I don't think it's an LE problem, because screen calibration has no effect. Modern TV's often have picture optimization modes, and some modes slightly change the filling of the screen. Play around with your TV settings.
This is almost 100% incorrect... (sorry...)
CEC data is never part of the AV stream. In fact, CEC is a separate LOW speed interface (actually a bit like a slow I2C bus). It uses a separate line in the cable from the AV data. Most cables will include CEC support, but there are some that do not.
Info here... https://en.wikipedia.org/wiki/consumer_electronics_control
Thanks for the info, I was just guessing to find the problem.
Am I correct when I'm saying, the CEC part has a different implementation for RPi4B, compared to RPi3x?
Because that's the point to find a solution.
I've been installed a power button and a status LED on my RPi3B+. This works for RPi4B, too. After SSH login, you can use the nano editor to create or edit all necessary files.
Power Button Hardware Part
Use GPIO03 (Pin #05) and the opposite Ground (Pin #06) to connect a push button for power on / off.
Power Button Scripting Part
Add dtoverlay=gpio-shutdown to config.txt.
Switching off will let the shutdown menu appear.
To shutdown instantly instead, create this /storage/.kodi/userdata/keymaps/keyboard.xml:
<keymap>
<global>
<keyboard>
<power>shutdown</power>
</keyboard>
</global>
</keymap>Status LED Hardware Part
Use GPIO13 (Pin #33) and the opposite Ground (Pin #34) to connect an LED. Also use a resistor with 330 Ohms or more.
Status LED Add-On Part
Install the Raspberry Pi Tools add-on to use the GPIO programming library in Python.
Status LED Scripting Part
The status LED will be triggered from autostart.sh, which calls the Python script status_led.py . It will switch off automatically at shutdown, no script action required for this part.
Create this /storage/.config/autostart.sh :
#!/bin/sh
(
python /storage/scripts/status_led.py
) &Create this /storage/scripts/status_led.py :
#!/usr/bin/python
import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
import RPi.GPIO as GPIO
# Replace YOUR_CHOSEN_GPIO_NUMBER_HERE with the GPIO pin number you wish to use.
# Make sure you know which rapsberry pi revision you are using first.
# The line should look something like this e.g. "gpio_number = 7".
led_gpio_number = 13
# Use BCM pin numbering (i.e. the GPIO number, not pin number).
# WARNING: this will change between Pi versions.
# Check yours first and adjust accordingly.
GPIO.setmode(GPIO.BCM)
# Switch LED on.
# LED will switch off automatically at shutdown by using normal GPIO state.
GPIO.setup(led_gpio_number, GPIO.OUT)
GPIO.output(led_gpio_number, True)Reboot.
Thank you but I am not sure if that can be the case either as libreelec is perfectly working fine on the same tv with rpi2 andd 3's.
I think it's possible, because CEC data is merged into A/V data. RPi4B uses a different graphics driver to deal with higher resolutions and two HDMI outs. CEC signals have to be filtered out of the HDMI stream, before CEC adapter can handle it.
Thank you - I've tried that already but it doesnt work - changed 5 different cables but no luck
OK, then it's probably not the HDMI cable.
My final idea is that your TV uses special CEC codes, which are not yet implemented for RPi4B.
You could write a bug report, and become a part of the solution.
Write the full TV model name, and give a link to this thread, so devs can know about what you already did.
HDMI is a standard, and the only parameter that could really change between devices is data transmission speed.
My advice is to take the HDMI cable from the working TV, and plug it into the not working one. Just to be sure it's not the cable. As you know, some HDMI cables are ready for high speed, and others are not, so CEC data could get lost.
I had the safe mode bug today at LE 9.1.002 (RPi3B+).
It happened after I've been added the Kodi Nerds repo, and installed / uninstalled "Amazon Prime Music" from there.
After shutdown and power on I went into safe mode.
I did a reboot from SSH, and normal mode worked again. Maybe it helps to find the bug.
...such a shame i have to return this pi now and wait for a proper build to come out first.
Not so fast! RPi4B is a brand new device, which takes time at the software part. Don't forget it's made by hobby programmers.
Thanks for the info. The RPi4B is a brand new device. Just wait until all the little things will be fixed.
Also you can do a formal bug report, or just mention it at News and Announcements, where some developers are reading, too.
