Posts by Da Flex
-
-
@maxagaz:
It's in STORAGE -> .kodi -> userdata.
-
After the LE installation you'll start with an untouched "guisettings.xml", which seems to work fine. After the first boot the "guisettings.xml" will be updated with a "videoscreen.whitelist" (see XML tag inside the file) fitting to your screen. I think that process fails.
To test my theory, do this:
- make a fresh LE installation on MicroSD
- copy the untouched "guisettings.xml" from MicroSD to your PC
- boot the RPi with LE
- power off RPi by shutdown menu
- remove the MicroSD card and plug it into your PC
- copy the potentially corrupted "guisettings.xml" to your PC (verify it, and maybe post it here)
- replace it by the untouched original
- try to boot the RPi again
It could end up having a DE-15 <---> HDMI issue.
-
Does the touchscreen work with the other two OS's?
-
Pooling gpio pin every second is probably very bad idea.
Yes, I think the Python version is more efficient.
-
You maybe had some bad experiences, but I would stay with a MicroSD when it's just about storing the OS itself. Store all important personal data on an external SSD, and your system will be very save (SSD's are nearly unbreakable). Most MicroSD cards are killed by too much write processes. If they are just read (as the OS do), they will last very long.
-
Yes, the current stable LE still needs scripting to use an on/off button. I did it by calling a Python script. Using the above Shell script works basically the same way. It would be cool to get this function just by setting a "dtoverlay" option. I'll switch to it, when it's part of a stable LE version.
"dtoverlay=gpio-shutdown" on LE 8.95.002 will let the shutdown menu appear, when pressing the power button. Instant off only works by the described scripting.
-
Activate log level 1. When it crashes, power off, remove the MicroSD card, read the log file and post it (use a link to PasteBin). If you use a Windows PC, there are tools to read the card anyway.
-
I have been helped another HiFi enthusiast to make DTS work for him. It can end up buying a lot of new equipment.

Read the thread:
-
Just to be curious, do you know what that line we deleted in python code was for? (The one which contained port 80?)
Yes, this are notifications to make the on/off calls visible at the LibreELEC GUI. Definitely not needed, you'll see it anyway.
-
That's great, man! Thanx for the symbolic beer.

Please mark this thread as solved.
-
-
-
I guess I found the port 80 error. It's inside "ledon.py". One line must be deleted, and it should look like this:
Codeimport subprocess import time subprocess.call('/storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json </dev/null >/dev/null 2>&1 &', shell=True) time.sleep(2) subprocess.call('/storage/hyperion/bin/hyperion-remote.sh --priority 100 --duration 400 --effect "Rainbow Swirl"', shell=True,)Please edit the file, and try to run it again:
After that edit the "ledoff.py" to avoid the same port 80 error. It should look like this:
-
-
-
terminate called after throwing an instance of 'std::runtime_error'
what(): JSONSERVER ERROR: could not bind to port
LibreELEC:~ #
Maybe because of this?
Quote
Tried editing script and changing port 22 instead of 80..Please set the port number back to the original value and comment the Python script out by adding # at that line:
Then reboot, and try the command from my last post again. Don't be too quick.
-