PS: Use Etcher to install LE on MicroSD. It's possible that your current installation has been set wrong read/write permissions, and ".kodi" can't be created when LE runs.
Posts by Da Flex
-
-
What should I change to fit my screen size (1920x1080) ?
That looks like the untouched version, because "videoscreen.whitelist" is empty. If it's not stored in the ".kodi" folder, than it's just the template, not the version that LE actually uses. That's why I think changing the file doesn't makes sense. Where does it come from, what's the path in LE? If you don't have the ".kodi" folder, updating "guisettings.xml" can't work.
-
PS: Because Kodi was working with your former setup, it's possible that LE uses more wattage than Win and reduces the output signal of the laptop. Just a theory...
-
Could be a weak electrical connection between laptop and TV. Maybe a weak output signal of the laptop, bad / too long cable... something like that. On such a weak connection LE can't receive all possible screen resolutions / vertical frequencies.
-
I'm using the terminal, and "ls -la" doesn't list any hidden files.
That's weird. You can use this on your PC or at SSH login:
Codefind / -name "guisettings.xml" -print -
I'm not familiar with Mac, but maybe there is an option to see hidden files at the file manager.
-
@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.
-
And again the output of this, please:
Code/storage/.kodi/addons/service.hyperion/bin/hyperiond.start -
OK. So, we still need to find out, how to start the service. What's the output of this?
Code/storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json
