Posts by chewitt

Our packaging for Samba (where files live) is a little different to conventional distributions but we provide /usr/bin/smbpasswd so you can create and maintain a Samba credential file somewhere on /storage that's referenced from samba.conf. There shouldn't be any functional need to run Samba in a container at all if you use the right configuration. NB: You're straying firmly off the trodden path from an LE use-case perspective and should not expect detailed support for things like TimeMachine backups, but our Samba is just Samba and such things should be possible.

You're asking a relatively niche question so answers might take awhile. You need to be patient.

Docker (Community Edition) is the application that supports 'containers' from the linuxserver.io "docker repository"

Nope. Use the backup and restore feature in the settings add-on.

Quote from icefox

I've enjoyed LE but maybe key devs have moved on to this branch, like how they moved from openelev to LE.

Incorrect. It's not at all like the OE move where the entire team (literally everyone minus one) moved on to leave the single problem developer to work by themselves. Only the two developers that proved themselves unable to work to the standards set by the rest of the team moved on. The rest of the team are intact and the Amlogic mainline kernel change is our focus. The key developers and active contributors towards the future of Amlogic working on that are all here and things in the mainline camp are moving along quite nicely. There are event test images available in these forums.

GitHub - LibreELEC/service.libreelec.settings: the LibreELEC settings addon for KODI is the source code. It's possible to clone the add-on and run it under a different ID to the one embedded in the image (same as other Kodi add-ons) but remember that python code is compiled before it runs so you need to develop/learn a workflow of making changes, cleaning the compiled files out, restarting the service, test, etc.

"ThePlayersKlub" is a pirate IPTV service so you're asking for advice in the wrong forum.

I can't speak for Ubuntu (someone else's problem) but under LE we implement various "high quality shaders" to handle those functions. Some of them are configurable, others are not.

We validate the md5sum of the KERNEL/SYSTEM files in the .tar file, not the actual .tar file.

Images for G12 devices (X96/N2, etc.) are still rather "work in progress" in places. You only need to do "touch /storage/.update/.nocompat" but that will need another Linux device to mount the SD card from. It's probably easier to create a clean SD card.

A.S._id read the error message on the screen and do what it tells you (create .nocompat)

pan.rozowy mainline kernel images will not support SSV wireless chips due to the driver code being utter rubbish and SSV going bust in 2016 which all but guarantees nobody will update the driver code. We did have a go at updating the SSV6051 driver but ran out of enthusiasm due to it being such awful code. Use a wireless Ethernet bridge .. better performance and more future-proof than USB wireless dongles (beware that we are unlikely to add support for cheap Realtek WiFi chip devices due to Realtek code also being low-quality).

<profiles>
    <lastloaded>0</lastloaded>
    <useloginscreen>false</useloginscreen>
    <autologin>-1</autologin>
    <nextIdProfile>1</nextIdProfile>
    <profile>
        <id>0</id>
        <name>Master user</name>
        <directory pathversion="1">special://masterprofile/</directory>
        <thumbnail pathversion="1"></thumbnail>
        <hasdatabases>true</hasdatabases>
        <canwritedatabases>true</canwritedatabases>
        <hassources>true</hassources>
        <canwritesources>true</canwritesources>
        <lockaddonmanager>false</lockaddonmanager>
        <locksettings>0</locksettings>
        <lockfiles>false</lockfiles>
        <lockmusic>false</lockmusic>
        <lockvideo>false</lockvideo>
        <lockpictures>false</lockpictures>
        <lockprograms>false</lockprograms>
        <lockgames>false</lockgames>
        <lockmode>0</lockmode>
        <lockcode></lockcode>
        <lastdate></lastdate>
    </profile>
</profiles>

^ that's the default content of /storage/.kodi/userdata/profiles.xml if you want to recreate it

No idea. Android has a large SEP field around it.

Quote from sinisab89

Hi!

I have a WiFi problem with LibreElec. I get low speed and high ping and I dont know why. My device is Tanix TX3 Mini - H, 2GB RAM 16GB mem with SSV6051 WiFi chip inside. Dtb is glx_p281_2g and it boots nice and fast. Signal strength is 75%, it connects to WiFi with no problem but I cant get more than 9Mb/s. I have 20Mb/s ADSL. Android on this same device goes up to 18Mb/s, this version of LibreElec goes to 9Mb/s, LibreElec 8.2 goes up to 12Mb/s and CoreElec 9.0.1 goes only to 4Mb/s. With higher speed ping gets smaller. Can't figure out the problem, it's strange how different versions behave differently with wifi. Is there something I can do to fix this behavior cause I would really like to use LibreElec on my box, Kodi works so much better than on Android...

Get an Ethernet bridge and you'll get proper wifi speeds .. and you'll avoid the future issue that SSV6051 will not be supported on mainline kernel images due to the driver being dreadful crap that we couldn't port (we tried, but, eww.. it's sucky code). It's no surprise that SSV went bust in 2016

Lollipop is Android and we have no "launcher" app, so you're not running LibreELEC and you're in the wrong forum.

RPi3B+ with DTS is more than enough for normal use .. IMHO worry about the upgrade when it happens, not now

I've been using Lima on the family daily-driver (Amlogic) box since last November and it's about 90% complete from a Kodi perspective. There are some minor corner cases with specific screensavers/visualisations not working fully (e.g. shadertoy) and there's the occasional glitch, but Kodi is a fairly simple app to support and it's very usable. However most RK devices we support need panfrost which is a trickier proposition. Amlogic test images are now using this out of necessity (the T820 GPU in the S912 box has no Linux blob) and we're now using the recently merged DRM driver and performance from an OpenGLES perspective is starting to look rather nice. On the kernel side there are still memory management issues and crashes/hangs to resolve, and we're still working to upstream support for 32-bit userspace. There's a lot of activity around panfrost and it improves daily. I'd estimate it's 75% complete for midgard right now. Since RK hardware has mali blobs available there's no rush to switch so we'll let panfrost mature before making that decision. Bifrost support is also completely missing; the developers are deliberately ignoring it for now to keep the focus on midgard hardware.

Still work in progress, but as the API's are fairly stable now we've started to experiment with the Kodi side of things. It will take time as there's far too much stuff to get our heads around and we need to coordinate changes over multiple GPU types. In the future Kodi will have A1+ support for all this but you'll have to wait for a blog post to find out why