Posts by chewitt

The most common reason for shutdown problems are background services installed via add-ons that take a long time to shutdown after receiving an instruction to stop, so Kodi reaches a timeout value and has its process killed before guisettings.xml has been fully written. The incomplete xml file is then detected at startup so Kodi substitutes a clean (default) file without the settings you've made. The most common problem things that I've seen delaying shutdown are large docker containers, torrent client add-ons, and some of the torrent based pirate streaming crapware. There is no general LibreELEC shutdown issue on NUC devices else the post count in forums would be notable (they are popular hardware) so it is likely to be something local to your install.

Solve the reason for guisettings.xml and things aren't an issue. I'd also look at hardcoding an edid.bin file (run getedid from the console) as this will negate handshaking issues if they also contribute to weirdness.

In the past I'd say "whatever works for you works for us" when it comes to LE/OE choices, but the longer OE continues to fester without security updates and bad design choices, that statement becomes ever-harder to make.

Please have a look at current submissions for Linux 4.12 kernel at kernel.org .. if it's not listed it's not been upstreamed.

Please have another go at submitting the packages to our github repo. It's hard to see exactly what the mistake was in the previous attempt but i'd guess you did changes in a local copy of the 8.0 branch and then submitted the PR to our master branch. This will include all the changes between 8.0 and master (350+ commits) in addition to your changes, which get lost in the noise.

First clone our repo to your personal GH account using the GH web interface. Now clone (download) your repo to wherever you're going to make the changes. Checkout a new "topic" branch from master for the changes. Make changes. Push the local topic branch to your GH repo. Then PR from the topic branch in your GH repo to the master branch in our GH repo using the web interface.

The rookie mistake (and we've all done it, everyone is a git noob at first) is cloning from our repo and making changes in the master branch. It works for something you build locally but it becomes almost impossible to upstream/contribute a clean PR.

DaVu connman allows WLAN and Ethernet to be active at the same time, but if Ethernet is active it always has priority, e.g. becomes the default gateway to the internet.

pettwaya251 please do "dmesg | paste" after a clean boot (on WLAN) and share the URL generated so we can see the log.

I'd use TVHeadend and a DVB tuner stick, then you get all the finnish channels and no add-on is required (apart from the TVHeadend client).

No Kodi debug log = No problem.

In screenshot003.png the "Services" tab is one line above the BT option highlighted. It is in LE settings not Kodi settings.

wget http://chewitt.libreelec.tv/xorg.dri3 -O /storage/.config/xorg.conf && reboot

Run ^ that command against an 8.0.2 install and see what happens. It installs a custom xorg.conf that forces DRI3. It does remind me of some older Intel GPUs that don't play nice with DRI2 vs. DRI3.

Navigate left on the items that are clipped and once you get to the left-most icon everything lines up again.

It's your fault for not leaving your home screen tidy

I believe those devices have the Amlogic 8726MX SoC which means it's old and few people target them for development.

If anything is available it will be here: [INDEX] LibreELEC community builds for Amlogic

Quote from sone13

solution to problem?

find some black tape and cover the LED(s)

It sounds like you enabled "disable password auth" in the SSH section of LE settings. This won't disable the login prompt but will prevent the default root/libreelec password combo from being used (only SSH key-auth works).

What's the resolution of the display?

TVHeadend etc. can only save recordings to the local machine, so you need to mount a remove share from the NAS to a local folder. LibreELEC can auto-mount the share at startup using a systemd .mount file. SSH into the box and copy the example file in /storage/.config/systemd and edit (and then rename) to suit your share names etc. ~ it's not so hard.

Look in /storage/.config/systemd and there's an example .mount file to crib things from. Compared to setting-up TVHeaded it's not hard

You cannot install it, it would need to be compiled from source and packaged as an add-on. I'm sure that's possible as Oolite already runs on a broad range of Linux distros but it's a task that would need to be done by the community. It won't be on the roadmap for official development.

That trick no longer works (out of the box) for LibreELEC because we added a compatibility check to the update process that detects you are trying to update with an incompatible image and aborts the update. The check was added because we (used to) get a percentage of Generic (x86) users who cannot see the large Raspberry Pi logo on the default download page trying to update with the Pi (arm) image.

The trick can still be done, but you need to disable the compatibility check with "touch /storage/.update/.nocompat" first.

Using "make image" will result in .img.gz and .tar files in the target folder. All versions of LibreELEC support updating from either file.

You might see crashes building Python with only 4GB. I'd allocate 8GB of RAM for compiling.