Posts by chewitt

    DVB is one of the more challenging bits of our codebase. Support for USB and PCI type devices improves significantly in modern kernels as several of the major vendors "got their stuff together" and upstreamed their drivers; and the upstreaming processes ironed out lots of quirky crap code. However boxes with embedded cards like Amlogic devices are still a long way from being supported in mainline so the BSP kernels are still functionally best, but also aren't perfect (and the code is horrible) and the people who championed work on them appear to have stopped work and drifed away, so they aren't improving over time.

    You need(ed) to shrink /dev/sda2, then move it to the end of the disk to create space at the front, then grow /dev/sda1 to fill the gap between them that was created. Gparted can do everything in a single operation but clean installing is usually quicker :)

    "AlexELEC" is a Ukranian rip-off release. He originally cloned OE, then LE, and now I think CE, re-attributing all the commits/changes to himself and never contributing anything back to any of the codebases - although since his images are rammed full of piracy crapware like Acestream we're kind of okay not having anything to do with him/them.

    You have two choices:


    a) Grow the boot partition by booting from another OS (e.g. Ubuntu LiveUSB) and using "gparted" to shrink and relocate the storage partition by 256MB so the boot partition can be made larger. This is not hard to do, but normally a very slow operation even with an SSD in the box.


    b) Make a backup of the current storage partition, move it off-box, then clean install the same LE version to get the larger (512MB) boot partition and then restore the backup you took.


    I'd personally take a third option:


    c) Make a backup oof the current storage partition, move it off-box, then clean install the latest LE version and then unpack the backup and selectively restore DB files and config .. then reinstall add-ons at latest versions. In short, do a spring clean of the install, but keep the essentials from the old.

    Current HDR support starts at 9th Gen (Gemini) and based on Q&A with Intel devs a couple of days ago Intel has no current plans to implement HDR for older Generations. We might try to influence that once Kodi support has matured, but I wouldn't get hopes up.

    If you have a secondary GPU which can be exclusively passed-thru to the VM, then yes, but otherwise no. The VM image is created for functional testing and development work not playback.

    I haven't had any contact with afl1 for 18+ months and I have never knowingly been in contact with any MeCool developers.


    I do have direct contact with Availink who create the demod chips, but their repo is quiet since the summer (no idea why) and I haven't spoken to them for a while either. I got their new demod driver to compile, but quite a bit of work is needed to disentangle all the other drivers (tuners, demux) from their code so that each driver follows kernel APIs and can be independently compiled. Someone also needs to write a V4L2 deinterlace driver because we cannot use the Amlogic vendor drivers; it's written against a bunch of proprietary APIs that don't exist in the mainline kernel.


    TL/DR; I wouldn't expect to have "integrated" DVB stuff working anytime soon.

    Changing the wireless properties is not supported and the authors of ConnMan have historically resisted the idea of adding that capability because the current-coded feature is intentionally a mobile phone "hotspot" and not a "wireless accesss point" manager. You'll notice that your phone doesn't allow anything more than SSID, passphrase and on/off either. If you need a router .. you need to get a router.

    You can set folder permissions to make media (content) read-only. The only devices I know of with a switch are full-size SD cards, but you would not be able to use these for the boot device as the OS still needs some writeable /storage for itself.

    Seeking is not-working in the DRMPRIME stateful decode path (H264 on all Pi boards) and the same issue also affects Amlogic, iMX6, etc. which are also stateful decoders (HEVC on RPi4 is statelesss and works fine). If you disable DRMPRIME you are software (CPU) decoding which works fine but you may struggle to decode higher bitrate content. It's a long-running issue that hasn't had a eureka moment yet, and it's the primary reason we may not initially release RPi images for LE10.