There are three: YouTube, YouTube Channels, Tubed (Matrix only). You're probably referring to the first one.
Posts by chewitt
-
-
Kodi overscan settings only change the output of Kodi itself so when you run this add-on Kodi is stopped and the add-on runs from the framebuffer which has no knowledge of them (or mechanism to recreate them) then when you exit Kodi restarts and the overscan settings are reapplied. The solution to overscan is to set the TV to "just scan" or similar so you don't need overscan, it's a hack. You might need to change HDMI outputs as some TVs don't support it on all.
-
OK. Bad news for le but thanks for your reply!
The number of active nVidia users continues to dwindle with time and stats show the vast majority have older cards (using the older of the two drivers we ship) so even if we implemented support for NVDEC and EGL streams in Kodi (could be done, but nobody in Team Kodi is interested in implementing another proprietary nVidia method) this will only benefit the tiny number of installs with the latest cards. In the end, GBM/V4L2 is a big move forwards for Kodi and not having to maintain the 40+ packages needed for X11 support is good news for LE.
-
Just test stuff .. and report things that don't work or cause problems. If things work, we don't need to know. Debug kodi.log and sometimes dmesg if it shows errors are useful .. you can "cat /path/to/log | paste" to send to a paste site and get a URL to share. Most staff auto-ignore text file attachments (as too much effort to download/open) and logs pasted into posts (as usually ends up incomprehensible to read).
-
Hello all! I have a nvidia and as I underdtand, after libreelec 10, it won’t be supported anymore or did I get it wrong ?
At some point, after LE10, probably LE11 (K20) we will transition LE to GBM/V4L2 and you will either need to transition to another distro that runs X11 with the nVidia vendor drivers, or change GPU to Intel/AMD. No dates, but it will happen.
-
LE is not derived from any other distro, it's assembled from sources using Welcome to Linux From Scratch! principles.
-
The connection manager is ConnMan doc - connman/connman.git - Connection Manager
OSMC uses the same AFAIK.
-
The cummulative number of struggling users and/or feature requests we've seen over the yers suggests it's not a top-of-mind issue. There are no plans among our entirely volunteer stafff to pursue this that i'm aware of, but we have no objections to someone else (perhaps someone with two CS degrees?) making the effort and sending us a pull-request.
-
User numbers are small because an RPi3B+ is not a huge amount more $$ and is a considerably better Kodi device. RPi0 has never been positioned as an HTPC board and the only reason we "support" installs on it with LE 9.2 and older images is it happens to use the same image as RPi1 devices and thus needs no effort. Using MMAL in LE 9.2 is sub-optimal so most users are forced to use OMX anyway (same for RPi1) so Kodi is pushing the limits of what's sensible on the low-spec Pi boards for a while already. LE10 formalises that reality by discontinuing support completely.
If OSMC works better for you that's great and we encourage you do us it. OSMC currently runs the same underlying kernel, drivers and Kodi version that we use in LE 9.2 so there won't be any major difference, but the packaging might be easier for you. NB: In the near future they will make the same decision to end support for RPi0/1 as LE because they will migrate to the same K19 code stack that we're developing for Kodi. K19 does not support OMX or MMAL, only GBM/V4L2, so the decision is technical and nothing to do with user numbers.
-
HBR audio changes are in all images/branches now.
-
Use Index of / for older releases.
-
Could anyone share ideas about a good (stable with acceptable speed) USB Wi-Fi adapter for LE use.
I'm adding a LE player in a location where Ethernet is not an option.
My $0.02 is to invest in an Ethernet/Wireless bridge device. I use them with whatever test device I happen to be looking at .. to avoid the hassles of configuring WiFi connections. As "router" devices they have a larger antenna built-in which contributes to more stable connections (although stable is not a word I ever associate with WiFi) and since they present Ethernet to the test device there are zero driver issues. I used to collect/use old Apple a1rport devices as they are simple and cheap, but these days they're getting a bit old.
-
In post #2 i've given you the correctly spelled filename (only "unique" to 25m+ Pi devices) and in post # 4 I've given you the path to the file in LE.
-
MrChromebox.tech <= has all the boot things for Chromebox devices but that would be mostly useful for a clean install. If you've already got LE installed and there is a space problem the solution is probably to do some spring cleaning to make space.
-
The main (only?) hardware where this request comes from is RPi0 where the default board lacks physical ports. LE10 drops support for 512MB RPi hardware as in our opinion the performance under the new GBM/V4L2 pipeline (using more RAM and not-using OMX) is no longer suficcient for a good Kodi experience. It might improve over time with optimisation but under LE9.2 that optimisation requires 100k lines of not-upstream code and one of our long-term goals with Kodi is no (or minimal) not-upstream code, so it will be hard to replicate. Active-install numbers for RPi0/1 are tiny so from our side it's a low-impact change. So thanks for the creative thoughts, and I'm sure it's not the answer you wanted to hear, but we will indirectly solve the RPi0 problem by no longer supporting the hardware that has the problem.
-
Talking about UUIDs and labels demonstrates you've been looking in the right locations, e.g. /flash, so I replied to your high-level question with a similarly high-level answer. I even gave you the name of the file to change. I'm not someone who spends time providing step-by-step spoon feed instructions so you'll need to use a little initiative.
-
manual update (SSH console): Updating - LibreELEC.wiki
-
Netfix probably detects the IP/ASN you connect from belongs to a commercial hosting provider (where you created the VPS that runs WireGuard) and like many streaming media providers, they agressively block access from non-domestic hosting ASNs.
NB: Discussion on bypassing geo restrictions will put you on the wrong side of our forum rules.
