Posts by milhouse

    Not a problem as such, but we may experience users asking for or expecting features in non-imx6 platforms - as we have seen this week - because a feature already exists in imx6 but not elsewhere. Normally all our platforms strive for parity in terms of features, but having one platform with kitchen sink features can be confusing for users who then demand the same elsewhere. It's just a question of how we handle this.

    The clue is in the im6/xbian name .. the origins of that Kernel are not OE/LE so there will be a few differences.

    Yeah, it's not the first "difference" this week. I can see this being a potential long-term issue (or at least, topic of discussion) unless the imx6/xbian options are harmonized with all other platforms.

    It's trivial to add the module, but does the device also require firmware?

    I've no idea about firmware, it's one of those DVB do-hickies. :)

    MN88743 seems to be enabled as a module only for imx6/4.4-xbian. All platforms have module support for MN88742. Not sure why 88743 is only enabled for the imx6 platform, it's possibly something that could be added to all other platforms if there is a requirement for it (is the 88743 a replacement for the 88742?)

    You can install your own Kodi splash by copying a png file into /storage/.kodi/media/Splash.png. This would allow you to use the same artwork for both LE and Kodi splash files.

    However with an upcoming change (kodi: database migration splash text by MilhouseVH · Pull Request #537 · LibreELEC/ · GitHub) your current custom splash may not be ideal, as the space below the central logo would be best kept clear (you have the LE logo). You'll only have an issue during a database migration, which will be a one-time issue (per major release), and may be something you can easily live with.

    You can just delete those directories as the fs_resize process will delete and recreate the storage partition, so you will lose every item of data currently stored.

    If the fs_resize process is failing, there are four possibilities (in no particular order):
    1) Insufficient power supply
    2) SD card has failed (they have a limited number of writes, and will fail eventually)
    3) Fake SD card and it's not really 32GB capacity (test with various software tools designed to detect fake SD card)
    4) SD card is not compatible with default sdhost driver, try adding "dtoverlay=mmc" in config.txt before first boot

    Yes, we identified the 4.6.x kernel commit that causes the auto-repeat failure. Reverting this commit fixes the auto-repeat issue but causes other more serious lirc issues so not really sure what the solution is right now. Assuming the kernel commit is in fact correct, perhaps the lirc system requires a tweak to accommodate the kernel change - reverting the kernel commit probably isn't a long term solution, and it already requires a rework for the 4.7 kernel.

    Nope, no new driver nor any other change in #0629 that would explain the new behaviour you describe.

    Upload "dmesg | paste", "journal -a | paste" and "/var/log/Xorg.0.log | paste" from #0629 in the Kodi forum thread along with a full description of the issue, as this is where the Milhouse builds are supported (and also fully documented so that you can see what is new and changed in each build).

    The Milhouse builds are not supported on the LE forum, so if you want help with a Milhouse build post on the Kodi forum.

    OpenELEC currently has (or had, as of 2 months ago, not sure of the exact current figure) half a million active users.

    You have absolutely no idea of the size of each distributions userbase. Presuming that the userbase size for a distribution is "small" based on your personal skin usage figures is pretty misguided, not to mention woefully inaccurate - it's more likely to indicate that your skin simply isn't very popular with those distributions.

    HW limitations: RPi will never play HEVC/H.265

    Just to say this isn't true, as the RPi2/3 does support H.265.

    The RPi2 can play H.265 720p content without any issue, and with moderate overclocking can also playback H.265 1080p content (up to a bitrate of about 10Mbps). This actually makes a lot of H.265 1080 content quite playable on the RPi2. With the RPi3, it's usually not necessary to apply any type of overclock to achieve good H.265 1080p playback.

    Obviously 4K playback isn't possible.

    No, to be honest I don't see any errors/issues in either dmesg so I can't explain why the fsresize is failing when using the sdhost driver. I wonder if a dmesg from a freshly imaged SD card would reveal the issue, but this would require you to re-image your SD card, allow fsresize to fail, then grab the dmesg - I'd expect there to be some mmc-related errors logged.

    If you're using one of my test builds you should be posting in the Kodi forum thread which documents these builds, as that's where they're supported. If you want help from the LibreELEC forum then use an official build.

    Thanks for the information. So i'll keep the patches.

    I don't know if it's a useful information, but your build 0617x with the lirc bump did not affect the kernel 4.6.2 broken remote repeats. Just tested without knowing, if it's really technically related... So. As said, just fyi - if even valid

    Thanks for the confirmation, but #0617x wasn't expected to fix that.