If the USB drives have EXT4 partitions you can use "e2label" to change disk labels. If they are NTFS rename on Windows.
Posts by chewitt
-
-
Kodi has a simple "shutdown timer" which you can set via the power icon in the top-left corner of the home screen. Once the timer has been set the system shuts down (without prompting to remain awake) when the timer value is reached. So if you are confident of falling asleep in ~20 mins, set the value to 30 or 40 mins and the system will be off shortly after you are.
If you are playing local video media or some form of PVR or internet stream, the system remains in an active state for the duration of the media or stream and the screensaver will not show until x minutes after the system is seen to be inactive.
Detecting when you fall asleep and sending a remote shutdown command X mins later would be a fun RPi + sensors project
NB: Most TV's have a built-in sleep timer function. I have elderly relatives that have their TV configured for 60 mins. It prompts to reset/continue by hitting OK on the remote and if not pressed (because they dozed off) it shuts down.
-
I've been using LE13 images for 12+ months without any real-world issues, albeit on an RPi5 and not something that uses Generic with an AMD card. It would be more useful to triage on the current development release since that will receive updates. LE12 is less likely to see another release.
-
The first thing I'd do is update to an LE13 nightly to see if the newer kernel resolves the origina (radeon) issue?
-
Latest is Nexus not Omega
-
If the main repo hasn't reveived new commits but we've been chasing a CI build error/issue resulting in multiple CI runs it can happen.
-
How does LibreELEC solve, that there is actually no 64-Bit Widewine for arm chips
ChromeOS started shipping a 64-bit update image that we could extract 64-bit widevine libs from about two years ago, hence we switched all 64-bit ARM SoC hardware to "aarch64" for LE12 as there was no longer a need to force "arm" userspace.
So we do exactly nothing and inputstream.helper picks the correct version to use; except in your case where some upstream bug has resulted in it installing a 32-bit lib instead of 64-bit, which is not arch compatible and results in errors.
NB: I'm not entirely sure how to reword your too-long and incorrect thread title, but I'll have a go.
-
It's an IPTV stream (not antenna) hence all the talk of being "on wifi" on the website, but currently it's all wrapped up in a custom app which is only available on the latest-generation TV's. I've seen things written about it being 'open' but then cannot find any technical details and if it's truly open I'd expect it's requirements/methods to become public fact fairly quickly. The one thing I noted from reading around was that it's not possible to record live TV using the app; which would be achievable with Tvheadend providing some kind of intermediate role. No idea though.
To be continued..
-
Code
nano /path/to/the/fileUse the "nano" editor to open the file ^ and make changes, then "ctrl + o" to save and "ctrl + x" to exit.
-
I'll put something in the wiki about adapters .. nice to hear it's resolved
-
Best to ask the add-on author via his GitHub repo, it's not something the core project created.
-
Code
find /storage/.kodi/addons/tvheadend43 -name lovcombo-all.jsNo idea, but that ^ should find it [sic].
-
The box is running a downstream version of Linux 3.10 from 2013 full of hacky vendor code. There are many improvements to CEC support in Linux since then, but you are stuck with an ancient kernel because the vendor made zero effort to upstream support for their products. The codebase is basically untouched since release.
The same old kernel and surrounding userspace are probably the reason for poor WireGuard support too. -
-
Any steer on a resolution would be much appreciated.
It's a bug and the fix is merged upstream: https://github.com/tvheadend/tvheadend/pull/1786/files
The fix is included with the Tvheadend add-on in our LE13 repo, but the LE12 add-on is still an older version. You can manually edit the lovcombo-all.js file to effect the fix until the add-on is bumped.
CvH Is there a reason why we've not bumped LE12?
-
-
The ultimate fix would be Kodi evolving proper 'hotplug' support so that audio/video properties are dynamic rather instead of being fixed at startup, but it's one of those problems which ends up touching more bits of the codebase than you'd initially think, which is probably why nobody has willingly volunteered to tackle it yet. Until then the EDID workaround is good.
-
Any suggestions?
Post in balbes150 support thread as he creates those images, not us.
