Posts by KyleS

    Does anyone have the latest on h.265 support for this? CoreElec still cannot play simple 4k60hz video and has completely corrupt output (dusted off my "new" box from February and these basic same issues are present) so I'm totally looking to flip again.

    I also had eMMC corruption the last time I tried the LE image (from Bables) - has this been resolved?

    This forum is not a platform for spreading unsubstantiated misinformation on other operating systems.

    I am privy to all CE matters being part of the team and say you are BOTH wrong in the quotes you have made.

    Please edit to correct your errors.:dodgy:

    Quote from 20 minutes ago

    You have been suspended from the forum until 24 September 3019 07:00.

    lol. Talk about retaliation...

    The reason I made the thread was to bring awareness to the issue and to help resolve as I'm aware team members don't necessarily have 4K panels to truly test. The information being purposely hidden (see how adam unlisted the thread) is incredibly problematic and I know would have certainly stopped me and many others from buying a box.

    LibreELEC (OSS Linux really) currently can't do 4K content as the decoder isn't upstream and/or written yet. This is why I made the thread here to ask if it's actually fundamentally a hardware problem - or if it's a simple amlogic SDK problem.

    New look with KODI-19. Please note, this is the first trial version and many things may not work.

    X96 MAX 64/4G eMMC and SD Card work.

    Does anyone have usable wireless? The box seems to get very upset with very little traffic.

    You came to the resource to the developers, agitate for competitors. Are you a provocateur or want to look like the smartest?

    CE has linux 4.9, here going development of 5.0. What are you want to say?...

    CoreELEC is moderating any threads not related to the Odroid-N2 or legacy boxes, there's no free speech over there... LibreELEC is at least trying to keep universal support mainline for the SoCs themselves, CoreELEC is focusing their efforts on the old SDK instead...

    That's the difference.

    Some comments:

    WiFi on S905X2: may not be supported for a while yet, or at all. S905X2 has a design flaw in how the SDIO module is internally connected and while an egregious hack/workaround exists in Amlogic's 4.9 kernel it's looking unlikely that a cleaner solution acceptable to upstream kernel maintainers can be found. We might attempt a mainline kernel version of the egregious hack through a local patch, or since the majority of users stream media over Ethernet anyway, we might just leave it unsupported and avoid the support/maintenance work. The issue is allegedly resolved with the S905X3 chip which is already being sampled to manufacturers.

    Device trees: The mainline kernel avoids the silliness of 1G/2G/3G variants needed on the legacy kernel which makes life easier, but we will still need to figure out (and then upstream) the device trees for popular devices. I'm keen that device trees are sent upstream so that devices can be uniquely identified by "compatible" strings in the device-tree, as this allows simple things like the remote control keymap (also sent upstream) to be described in the device-tree for a better out of box user experience. Submitting changes to the kernel is not the most straightforward process but if non-coding folk like myself can figure it out (my personal collection of one-line kernel changes is slowly increasing) the bar is not set impossibly high.

    arm vs. aarch64: performance is marginally higher on aarch64 but arm allows us to support widevine drm (which is not available in 64-bit format) so arm is our preferred option and official nightlies and the Kodi binary add-ons to match them, once they start, will be arm only. Maintaining a single image for all Amlogic hardware (two images until panfrost evolves bifrost support) is a bigger win than the minor performance gain. On G12 hardware the future gain from running the CPUs at full speed (at the moment they are under-clocked) will dwarf the architecture difference.

    Please re-consider the WiFi stance. I'm in a condo and use WiFi exclusively from my current s905 Kodi box. I've had a x96 Max (4GB) for a while and I'm excited to see LibreELEC leading the charge once again for these boxes. I can't wait to watch 4k HDR over my point to point wireless :-).

    I've seen this issue on and off since starting to use Libreelec. I thought it was a couple bad servers in the pool, and just bad luck... However, even tonight I added 1.ca.pool.ntp.org and 2.ca.pool.ntp.org, rebooted... still no clock set.

    Obviously adding `ntpd -p 0.ca.pool.ntp.org 1.ca.pool.ntp.org 2.ca.pool.ntp.org` to my autostart.sh resolves the issue instantly, but this is crap for less knowledgeable people. Please consider using ntpd or similar instead of the current mechanism.