Posts by Da Flex
-
-
If your fan has an on / off mode (only two contacts in use), then you can apply the same wiring and software, like for the status LED. Switch it on by the auto-start script, and after shutdown the pin goes (hopefully, in your case) back to default state, which means off for the fan.
-
Good to hear. In my link at post #2 I gave instructions, how to power on / off a status LED. That's usable for your fan problem, too.
-
Use the default skin. It might be a wrong function mapping on a custom skin.
-
Disable the CEC adapter on the input settings (click on it, and deactivate it). I think RPi gets a CEC wake-up call after shutdown.
If you need CEC, only deactivate CEC wake-up functions on those settings.
If that doesn't help, provide a proper kodi.old.log, like I said above.
-
Thanks for the verification. Do you have a spare microSD? If yes, install LE 10.0.4 from scratch on it, and try again.
If no success with those factory defaults:
- create an advancedsettings.xml file, and activate log level 1
- after your next unwanted reboot, upload kodi.old.log to PasteBin (make sure that it's complete after uploading)
- post the resulting PasteBin URL
-
To be precise, you have two options:
a) SSH login from another PC
- find the IP of your LE device by using your router menu
- open a terminal on another PC, and type ssh root@<IP_OF_YOUR_LE_DEVICE> to connect to your LE device
- use the default password "libreelec" to finish the login
- to end your SSH session, just use the "exit" command
b) Use an LE terminal add-on
- download the "System Tools" add-on
- start the "Terminal" app
-
I tested a 64-bit build of LibreELEC and it does improve VC-1 playback.
Hopefully LibreELEC (Orion) 12 will be 64-bit by default.
That's a big thing!

-
How do I get to a command line to run parted?
Login by SSH.
-
I don't know. Menu shutdown works for me, so I eventually just have different settings.
Please login by SSH, and open /storage/.kodi/userdata/guisettings.xml with the nano editor.
My power management section looks like this. Try the same settings:
Code<setting id="powermanagement.displaysoff" default="true">0</setting> <setting id="powermanagement.shutdowntime" default="true">0</setting> <setting id="powermanagement.shutdownstate" default="true">1</setting> <setting id="powermanagement.waitfornetwork" default="true">0</setting> <setting id="powermanagement.wakeonaccess" default="true">false</setting> -
Thanks for clarifying! How can I tell that this has happened? I'm quite not familiar with Github
Keep an eye on our News and Announcements.
We always mention the used Kodi version. If it's newer than Kodi 20.0, go and get it.
We also have an RSS feed, just in case you want automatic notifications.
-
Install raspberry pi tools from repo. Pi3B+ shutdowns, if Kodi power off is used in libreelec 10.
This seems to be right. I'm using Raspberry Pi Tools for a long time, because I need it for the power button GPIO's. I usually shutdown by Kodi menu, and it still works since LE 10.
-
There is a subtitle bug in LE 10. Please update to LE 11 Nightly. Put that image into .update folder, and reboot to install.
-
-
Then I would activate log level 1 at advancedsettings.xml, and look at kodi.old.log after reboot due to Kodi hanging.
You can upload that file to PasteBin, and post the URL. If the log is long, you eventually have to split it, and share multiple URLs.
If you prefer to write a Python script, please share your code.
-
You could auto-start a Python script with a "try" loop to check a key event. I'm no Python expert, so I can't tell you more.
When Kodi hangs next time, login by SSH, and give us a log file...
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Dev says, it's a bug in Kodi "Matrix", which is used by LE 10. LE 11 (still nightly / test) uses Kodi "Nexus". So stay with "Nexus".
-
Very helpful, thanks!
