Posts by chewitt
-
-
No current plans for official nightly builds. Alpha builds are every few weeks. Milhouse builds are every few days.
-
It's never been enabled in official builds, so maybe you've updated/upgraded from a custom build. What hardware are you using?
-
It can be done by fiddling with routing tables and not-routing traffic to the IP ranges used by Auntie's CDN infrastructure. However, as those IP's are not publicly listed anywhere and some are dynamicly allocated (much more than the website needs to be handled) it's not a simple task. You'd be better off using the LE box for TV and a NAS for whatever dubious function requires a permanent VPN to mask your traffic.
-
Much depends on the GPU drivers. Windows drivers are generally better written (over a wide range of hardware) and can be fiddled with extensively due to the potentially wider range of use cases on a general purpose OS ~ drivers are shipped with a very safe configuration so a major tweaks are needed to get decent performance for Kodi. Hence such packs/add-ons exist. Linux GPU drivers expose dramatically fewer things to fiddle with but tend to run optimised out of the box. However, that's all moot because there is a choice of Kodi VideoPlayer or Kodi VideoPlayer. If you find a better player you need to suggest it to Kodi developers as their app needs to include support before we can bundle anything. Good luck in making the suggestion
.. do you have a crash helmet and earplugs? -
User donations fund some VPS for web/forums. The project is happy to receive "no strings" donations and support, but we prefer to be independent of "sponsor" obligations (another lesson learned). It might change in the future, but seems to be working for now

-
We've been sort of hoping/wishing that GitHub improves the Issues function; they've hinted changes are coming. At the moment it's deliberately turned off as OE experience shows an open tracker attracts a lot of "my wireless doesn't work" noise, and users get confused on where to report issues (we'd prefer the forums, and GitHub requires another registration). If we could restrict GitHub issues to prior contributors or a list of known people it would be ideal. We'd pass on the offer of using your server; the gesture is appreciated but as a result of our OE experience the team mandates that infrastructure and apps must not being dependent on any single person .. once bitten, twice as shy!
-
Boot from the debian USB, create an MBR partition scheme on the HDD with two partitions labelled BOOT (512MB) and STORAGE (the remainder of the space). Format both as ext4 and install syslinux bootloader to BOOT. Copy the SYSTEM, KERNEL and extlinux.conf files to BOOT; edit extlinux.conf to use BOOT=LABEL=BOOT and DISK=LABEL=STORAGE .. and then reboot. Installing LE manually takes ~10 mins.
-
WP/WC alpha builds should start with v7.90.004
-
The lack of fix is not due to a lack of effort. I'm told that it's not been forgotten, and continues to be invesigated..
-
AML changes for 23.976 on S805/S905 are not relevant to the AML8726MX SoC in the WP box. It's a different device. It needs a different solution.
-
LE has a strong "community" focus and is structured as a collective of people with a common interest. Although a number of us regard ourselves as "on the team" none of the people working/collaborating with the project have ever been asked to declare a formal affiliation to the project. Contributors are not asked to pick sides and are free to contribute to either project as they like. Establishing a legal entity for the project in the future may require us to formally distinguish between voting and non-voting members, thus creating a team, but that's in the future. Today there is no formal team, so it's not appropriate to publish lists of names. Our GitHub commit history provides the best guide to our regular contributors.
-
Post back when you've got a working dev build.
-
We have no plan to go into more detail as any attempt at explaining ends up reading like an attack on OE's founder, which would be inappropriate and broadly misunderstood. The fork was no betrayal or coup, and although the main reasons are "about a person and their actions" (or mostly their lack of actions) they were never personal.
LE's git codebase fully respects our origins in OE, and there is nothing to stop OE continuing as a successful distro. In all communications with Stephan before, during, and since the fork we have always clearly stated our desire for both projects to coexist respectfully. So there is no "LE vs. OE" situation and we would ask that nobody attempts to frame one. In the long-term the differences between projects can speak for themselves.
-
releases.json .. the spec is not final yet, and may change again before we reach beta
-
Not supported.
-
no debug log, no problem

-
Compile - LibreELEC <= Get a working development build first, then support for the RAID card is a case of making a one line change to the kernel config to enable Linux Kernel Driver DataBase: CONFIG_BLK_DEV_SIIMAGE: Silicon Image chipset support and then rebuild.