Posts by no1home

Press the center blue button marked "OK" while a video is playing. That should bring up the video menu, from there you can select the stop button.

fbc Try LibreELEC Settings->Network and check "Wait for network before starting Kodi". Make sure you have at least one ntp server configured.

Quote from Soapy Smith

Does this have to be done after every update?

No, your autostart.sh script won't be overwritten by an update.

Try the workaround posted here, it's been working for me: Idling on Wetek Core leads to weird lag

First, modify the <remote> tag in your Lircmap.xml to read <remote device="devinput">

Also, some of the command names you're using such as <processinfo>, <fullscreen> probably won't work. Those names have to be known to kodi internally. Otherwise, you'll get an error like "ERROR: Remote Translator: Can't find button processinfo". Pick from among the ones listed in /usr/share/kodi/system/Lircmap.xml. You can then make them do whatever you want in your remote.xml file.

Hope that helps.

I had this problem on Arch also. I downgraded gperf to 3.0 as a workaround.

I have this problem as well. A workaround that was been working for me is to use the hotplug frequency governor. Log in the the Core via ssh and issue these commands and reboot:

echo "echo hotplug > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" >> /storage/.config/autostart.sh
chmod +x /storage/.config/autostart.sh

Have you tried LibreELEC Settings->Network->"Wait for network before starting Kodi"?

try it with: PROJECT=S802 ARCH=arm DEVICE=M8

There is an option in Settings->TV->General->"Use channel numbers from backend".

Same issue on Wetek Core. Twitch video doesn't display unless hw accel is disabled for h264. Started happening with Krypton beta 5 LE builds.

I have encountered this problem as well on the Core with Krypton builds using various skins including the default Estuary skin. The Kodi UI becomes very unresponsive after sitting idle for random periods of time. Interestingly, a restart of Kodi doesn't correct the problem, a reboot of the Core is required.