Historically we have used a common kernel for all pi and x86 things but the team is currently split between the desire to use an LTS kernel which benefits pi hardware (a huge portion of our userbase) and to track mainline which would benefit new x86 hardware. There are benefits (and cons) to both. I personally hope we end up using LTS (4.14) for pi hardware and track mainline kernels with x86 stuff - the current 8.2 release has pi on 4.9 while x86 is on 4.11 so there is a precedent, although it's not been without issue.
Posts by chewitt
-
-
Discussion on VPN use is tolerated in this forum as long as it remains focused on privacy use cases. If you drag the discussion onto the use of VPN services to bypass geoblocking (which some view as a soft form of piracy) this thread will be locked and then binned. Take that discussion to some other forum please.
-
There will be an 8.2.4 release in the future but there is no way we will contemplate a major kernel bump to support new Intel hardware (esp. with Intel drivers being oh-so-reliable) in a long-released branch. LE9 dev builds are the only option.
-
It's unlikely that LE and OE are different when it comes to RPi things .. aside from OE being outdated on software point versions.
Please provide a Kodi debug log from LE 8.2.3
-
Not that we heard of..
-
IMHO this will be a "Holy Grail" quest for two simple reasons:
a) There are probably 20+ Shenzen based manufacturers of "MXQ" boxes and they're all a teeny bit different
b) Manufacturers who stole the base design of someone else's box never publish schematics of "their" box
Good luck
-
-
Debug log .. or your problem is not our problem
-
Enable media "flags" in skin options and Estuary shows icons with resolution and audio/video codecs in the Library views. Most other skins do similar things. I also keep 4k and 4k UHD in different source folders so that I can exclude those sources on devices like RPi3 that cannot handle 4k media and include them on more capable boxes that do.
-
Although it's basically true I'm not a fan of the typical "when it's ready" Kodi answer. First alpha milestone for v18 is scheduled for April but (caveat) has already moved once and could shift again. So current guesstimate on a stable release is a few months after first alpha.
-
Code
systemctl stop kodi nano /storage/.kodi/userdata/addon_data/plugin.video.youtube/settings.xml (edit, save etc.) systemctl start kodi^ try stopping Kodi before editing in case the settings are being overwritten on exit.
NB: It wasn't the best idea to post your API keys in public. I've edited the post to add some garbage to the values so they don't work.
-
RPi2 will not cope with 1080p HEVC content but an RPi3 (especially with a little overclock) is normally okay. Any S905 (or newer) device like the C2 has native hardware decode for HEVC so it's not an issue.
-
I had a similar Q the other day so I guess Tvheadend has some kind of SMB mount capabilities that are impacted by the overall SMB changes that we made in LE 8.2 and the plain smb://path/to/nas no longer works. IMHO the easiest option is to use a systemd mount in /storage/.config/system.d to locally mount the remote (NAS) filesystem at startup to somewhere like /storage/recordings and then configure Tvheadend to use that local folder.
-
There was a V4L maintainer/contributor BOF session at ELC Europe (in Prague) last October to discuss the scheduler API changes needed to move things forwards. Consensus was achieved and changes are expected to be complete around end of Q1 and merged early Q2. Changes are then required in ffmpeg and various drivers .. but should be evolution and not revolution.
-
LibreELEC.tv/linux.x86_64.conf at libreelec-8.2 · LibreELEC/LibreELEC.tv · GitHub
^ the kernel module is enabled in config so we'd need to see "dmesg | paste" output to see if there are firmware loading or other issues.
btw, whining at the people you'd like to help you doesn't usually inspire them much. If you want to run OE, go nuts and enjoy yourself.
-
And on my Kodi partition i don't have librelec and the Librelec config fot connect Kodi to the Wifi.
^ If you do not have LibreELEC, our settings add-on will be irrelevant.
-
Official:Forum rules/Banned add-ons - Official Kodi Wiki
No further support in this forum.
-
Until Kodi actually functionally supports HDR and the complex mess of different colour space conversions that can be required (which is current work in progress) you might as well turn the TV off and go look in the garden for unicorns. It will be a more productive use of your time than trying to make broken Amlogic kernels and code that only partially exists work. I don't mean to sound rude, but that's reality. Come back in a few months when things have advanced.
