Posts by ghtester

The same issue with LE Nightly 20220601-0e57a30. The audio is permanently muted in HDMI output. Analog output (bcm2835 Headphones) works.

RPi 4B / 2GB

After upgrade from LE11 nightly 20220528 using LibreELEC - Updates - Available Versions menu I was not able to get the HDMI audio output anymore.

No GUI sound, no LiveTV sound. Tried all available HDMI targets - no way. The analog output worked. Tried to force defaults in Audio properties without any positive effect.

Also sometimes after some menu selection I got black screen during Live TV watching, stopping the channel helped to get the GUI menu back .

Reverting back to 20220528 fixed the issue.

Audio stream sometimes not (or wrongly) detected on LE Nightly 20220528

Quote from zomboided

If you start and stop openvpn outside of VPN Mgr then you’ll probably see some conflict as VPN Mgr tries to restart openvpn if it sees it go away. You should choose one way or another of controlling openvpn but definitely not both.

VPN Mgr has an API which can be called from scripts allowing some external control as well as from within Kodi. It’s documented on the wiki.

It's a good comment. I don't use any VPN Mgr so I did not point out a possible conflict.

The examples above should work fine when the VPN Mgr plugin is disabled.

Well, the OpenVPN connection is based on config file (usually with .ovpn extension). The destination gateway is specified there so you have to always know which server you are connecting to. You should be able to find the config file in your prefferred VPN plugin and run the connection manually.

The start / stop OpenVPN connection could be performed for instance with simple scripts which may look like:

Connect script:

#!/bin/bash
openvpn /storage/PathToYourConfigfile/NameOfYourConfigfile.ovpn &

Disconnect script:

#!/bin/bash
pkill openvpn

Learn something about ConnMan first: https://wiki.archlinux.org/title/ConnMan

You need to obtain your specific service name related to your AccessPoint, by using the connmanctl services command. Then connmanctl connect wifi_*****_psk should work.

Quote from nokia3660

is there a way to check the VPN status in command line? If yes, could anyone be kind enough to share the command? I am on LE9.2.8 on a Pi4.

There are several ways to check the VPN status. You may check the status of ping command to some machine inside the target network. But perhaps the check of tun network device (which is created when OpenVPN tunnel is established) presence is enough. For instance ifconfig or ip link would be useful.

A simple example:

 ip link | grep tun | cut -f4 -d,

should return UP when the OpenVPN tunnel is active otherwise it returns nothing.

The issue described in post #19 still happens on LE Nightly 20220508.

Of course there are text editors present by default in LE (AFAIK nano and vi ) but at first you have to enable the SSH service. Then use latest PUTTY to connect it.

Nevertheless, if you need to configure just a few transponders, the most easy & quick way is to configure them in Tvheadend GUI directly. Just ignore the predefined networks and create your own.

The same or maybe even worse issue on LE 11 Nightly 20220508.

Fixed by Author: https://github.com/herrnst/script.xbmc.lcdproc/issues/65

Quote from oneillb

kill and kill -9 are ineffective in killing the older kodi.bin processes, and issuing a reboot via ssh, does not reboot the box.. it brings down the network etc., but there is no reboot..

Try this command from SSH console to force reboot immediately (do it only if there's no other option than power cycle):

   echo b > /proc/sysrq-trigger

Try the same script in LE, in general it should work. If not, you need to compare OS release & configuration differences and make appropriate adjustments.

I am not using any script for a fan controlling as a most simple solutions works best. In my case it's a 12V CPU fan powered by 5V.

I am using both versions but I am sorry I can't really point out any improvement in 4.3 (that I could appreciate). Instead there are really strange issues with Networks / MUXes configuration (it depends on web browser used) and worse compatibility with Kodi (so for instance subtitles are not displayed on some MUXes despite recorded properly).

Both have an issue with 'random' EPG records corruptions (don't know if it's country / language related or what's the reason) and timeshift buffer issues.

But in general, both usable as soon as you went through the config nightmare of 4.3.

Yes it's always much better to use USB/SATA converter + SSD (or m.2 SATA adapter) than micro SD card. You just need to use a compatible adapters.

I would recommend to use Tvheadend 4.2 as 4.3 has more configuration & function issues in LE and (from my point of view) no advantage.

Some config issues also depends on web browser used.

I have no experience with this on x86_64 platform but the configuration in Kodi should work the same.

So it depends if your HW is supported. As soon as both of your HDMI devices are recognized properly, I believe you should be able to configure them as needed.

If you are using RPi model which supports a boot from USB, you don't need a SD card - write the LE image to USB key and boot from it.