Posts by chewitt

    If it was as easy as installing an RPi board I'd show interest. However while it can technically be done, it's not simple, so precisely because "it could be a big thing" is why I'd run for the hills before supporting it .. because endlessly walking people through some fiddly install process on a piece of cheap hardware is not fun. Kodi runs well under Android on Firesticks "as designed" so we'll stick to that.

    The original has 6x Channel AC3 audio while the rerip has 2x Channel AAC. Not all AVRs/TVs support AC3 audio tracks, so my hunch is that you have that enabled in Kodi pass-through settings and a receiving device that doesn't support it - hence when you swap audio tracks (that are not AC3) they play, and when you play other content (which is not AC3) it plays, and the rerips (which are not AC3) play. If you disable Kodi AC3 support those tracks will be remixed to multi-channel PCM for output.

    Then connman tethering is not the solution you are seeking, because it shares the Ethernet connection behind NAT and has deiberately has zero config options beyond SSID/Passphrase. If you want a proper bridge either learn how to create that at kernel level or buy a WiFi bridge device. I use some older Apple Airport Express devices for testing when I want to avoid the need for WiFi drivers; they are obsolete and thus rather cheap to find on eBay (the last one I grabbed was $12).

    I want to try to create an external swap because randomly the system freezes and reboots by itself, the probable symptom is that the RAM memory is full. Trying the free command I see that about 100MB is left available and I think this is causing the random reboots

    If the system randomly freezes something like power or disk corruption or an actual code bug are more likely causes. The kernel will actively manage RAM use and if there is ever an Out Of Memory (OOM) scenario the kernel oom-killer function will proactively kill idl/active processes to free space. If that happens it's fairly obvious from logs.

    Users are forever seeking some magic cure for "my cheap board doesn't have enough RAM" and the ONLY solution to that problem is buying a less cheap board with more actual RAM. Swap and Zram and such can fake more; but at the cost of reduced I/O performance and high wear on the SD cards that most LE systems run from and/or reduced CPU performance (due to compression) on an already low-end device.

    NB: RPi Zero was on the edge of acceptable performance with the older RPi codebase (LE 9.x) which uses highly optimised media drivers. The newer standards-based codebase (LE10/LE11) is in our opinion too heavy for acceptable performance on 512MB devices which is why we have formally dropped support for all boards/devices with 512MB.

    If you're able to play other media with audio? .. it's something specific to that file and I'd suggest using "mediainfo" to find out what codecs are needed to play the audio back (maybe some exotic thing or Kodi binary-addon is needed). If you're unable to get audio with other files, then it's something to do with audio configuration (wrong output device or such).

    Code
    wget https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.arm-10.85.0.tar /storage/.update/
    reboot

    ^ That will update the box to current test code. I wouldn't expect any real-world improvements, but also no harm. There's no need to make new SD cards or back things up.

    Capture the projector's EDID data to a static edid.bin file and configure the RPi3 to use this. It's normally used to address issues where the HTPC device is powered on before the TV (and thus HTPC doesn't detect audio and resolutions correctly) but it means the RPi always sees the TV (or Projector) as present and all you do is turn the projector off/on as needed. Instructions should be in the wiki.

    I've not seen issues with stuttering and jumping in HEVC videos but the HEVC codec is unfinished so it's not impossible. I'd normally associate that kind of description with bad encodings or TV's without correct modelines (e.g. 24Hz not 23.976Hz, or perhaps 3:2 pulldown; 23.976Hz at 60Hz) where occasional corrections are required.

    I have a VIM4 and currently see no sensible route to an LE image that runs on it due to zero upstream kernel support and a long (and not guaranteed to ever happen) time-gap until that happens. It's not simply a new iteration of the A311D (VIM3) chip, it's an all new SoC with some non-trivial IP changes (new USB, new HDMI driver, etc.) that need all-new drivers. CE can probably handle this device better since they work with vendor kernels that bundle those drivers, but even for them it's not so straightforward as Amlogic has dropped amcodec and most traces of older hardware from their latest iteration of codebase.