Why do you want to use lvm? Overlayfs is really the best solution for use on LibreELEC.
Otherwise you have to have lvm create loop images and whatever and it's just not ideal.
Why do you want to use lvm? Overlayfs is really the best solution for use on LibreELEC.
Otherwise you have to have lvm create loop images and whatever and it's just not ideal.
Just get me the output of those commands and I'll fix it. Thanks.
If you can ssh and run chromium from the command line that would probably show what the issue is.
Not sure, but proper support was just merged, however, I don't think that it should blank the hdmi...
see,
LibreELEC
linux: fix JustBoom device name and add alsa IEC958 conf by chewitt · Pull Request #1163 · LibreELEC/LibreELEC.tv · GitHub
Please keep talk of Plexus and acestreams out of here.
the bump has already been merged, it just has to be built
The LE 8.0 builds that include Kodi 17 Krypton are very stable, some minor changes will be incorporated before final but nothing big.
Your add-ons should automatically update after you update your installation.
Docker sounds like a good tool to use here
The "Bluetooth" label for the pulseaudio device in kodi is just a label. It is just using the "default" pulse device. So you can set the default device in pulseaudio then use that "Bluetooth" device in kodi
That's it as for the ladspa module I have no idea if we even support it. I'll have to check it out later.
I really wouldn't bother.
Just add the packages at compile time.
You cannot use pulseaudio with chromium. Like I have already said......
chromium is not linked with pulseaudio therefor pulseaudio cannot be used in chromium.
I have tested linking pulseaudio in but it will not let you choose an alsa device so we can't have that.
The backup function is in our own LibreELEC settings add-on
probably not to the base system, but it can be included in the system-tools add-on