TV's often retain info on connected devices and the only way to truly clear this is disconnecting cables and properly powering everything down before turning the TV back on and reconnecting and powering everything on again. Once it works it generally stays working 
Posts by chewitt
-
-
The OS boots from the 512MB sized /flash partition, but there is also a persistent /storage partition that resizes to 100% of the remaining space on the card during first boot. So you should have ~240GB available for media storage.
-
The /etc/fstab file exists because there are binaries in the OS that behave badly without it, but we don't otherwise require or use it, hence it's not populated with anything. The OS checks /flash and /storage (only) before mounting during boot and will automatically fsck them if any issues are detected. So just reboot once in a while. Since LE12 any issues detected are logged to /flash.
-
Add-ons aren't always built immediately. It might take a couple of days before the next run populates the nightly repo.
-
Assuming you've read this? https://wiki.libreelec.tv/configuration/wireguard .. what LE release are you running?
-
I installed the update on Dreambox 2 and it worked efficiently all audio and video formats 1080p encoding works but 4k does not work
Known. There is a long-term effort to rework the drivers being funded by Libre.Computer, but this already had one false start and the next step needs some information from Amlogic (discussions are taking place). Until something comes to fruition G12A/B and SM1 boxes are effectively 1080p max since they software decode everything except H264 and software encode everything; hence the official release focus on older GXBB/GXL/GXM hardware which has more code support (albeit rather unfinished code).
-
-
The root of the SMB share is the /storage folder in the OS. So from there, visit to Configfiles > hosts.conf - but note that you must use a text editor that supports Unix line endings to edit the file, i.e. Notepad++ as most versions of the default Notepad.exe app don't and Windows line endings cause problems.
-
https://www.silicondust.com/product/hdhomerun-connect-duo/ and https://www.silicondust.com/product/hdhomerun-connect-quatro/ both support DVB-T/T2 ..the Hauppage tuners are generally well supported upstream though (they invested in upstreaming drivers).
-
Official:Forum rules/Banned add-ons - Official Kodi Wiki
You will receive no support for your install in this forum. Good luck.
-
Nothing LE related I think. Best to report via the Skin add-on support thread in the Kodi forums so the authors investigate.
-
How are you running moonlight? - we deprecated our add-on so presumably something in a Docker container?
-
One down, more to go. The main one is Kodi moving to RC releases. There are still some important changes pending upstream. In the past we'd be trying to release-match Kodi with beta's and such but these days (older, wiser, etc.) we're not in a rush.
-
I'm not aware of anything within the Kodi ecosystem; there is a very deliberate focus on playing media from YouTube, not downloading it.
-
The OS contains cron already so all you need to do is "crontab -e" to start editing in nano, then paste the cron content, and ctrl+o (save) and ctrl +x (exit) .. and all should be good. NB: In LE /profile doesn't exist so you need to be using somewhere on /storage
-
It's best to ask questions about specific add-ons in their support thread in the Kodi forums - it's unlikely to be an LE specific issue.
-
If you have one on LE11 and one on LE12 it will "work" but they're accessing different versions of the DB so you loose watched/unwatched status and you'll need to scrape new content into both DB's. The LE12 nightlies are stable to use. There will be a kernel bump to Linux 6.6 at some point soon; that's one of our critera before moving to LE12 beta > release.
-
Have a look at HDHomeRun boxes for a 'Network' tuner device. Then use something else as the client/player device. In the long term you can update the client as needed for latest features while the tuner remains the same. It avoids lots of kernel/driver matching complexity which is often a challenge due to the state of DVB drivers in the kernel.
