Posts by chewitt

"Generic" Milhouse builds are available from the Kodi forum, the thread is normally adjacent to the Pi thread.

[script.module.inputstreamhelper] 0.2.1 by emilsvennesson · Pull Request #607 · xbmc/repo-scripts · GitHub ..was merged to Krypton so should also appear in master/Leia? - It provides a Kodi approved method for grabbing the lib. Everyone you ask will agree that downloading a 1GB ChromeOS image to extract the file sucks compared to simply embedding it, but this approach ensures the file is obtained from an official Google published location (not some random other place we happen to know exists) and ultimately it's the end-user who is initiating the install of the lib (should it break rules, licenses, or TOS etc. somewhere) and not you or us. Hopefully common sense (or better legal advice) will prevail at some future point.

Things change (at Google's end if nowhere else) and with our OS and the YT add-on, so I asked for a debug log from your box today, not someone else's box several months ago.

Please run "dmesg | paste" and "lspci | paste" and share the URLs so we can see what video hardware is being used. There are a number of video card options for those boxes in addition to the onboard (VGA) device and it's not clear what is being used.

Quote from bester69

ok, Its working in libreelec, (were not working with openelec)

Good to know .. enjoy

Feedback on milhouse releases is best done via the Kodi forums; it's where he (and Kodi developers) watch for things.

Honestly no idea what your issue(s) are. I have kids that watch YouTube stuff all the time and we live in a sleepy backwater of the internet with high ping times and low(er) bandwidth .. and IMHO things play fine. Provide a current debug log from a clean boot where you demonstrate the problem.

Droidbox "LibreELEC" releases have nothing to do with us, and we have no knowledge of what hacks and such have been added. The best place to ask for advice is their forum.

Yes, 2.0.19 is the latest for Krypton

Select the "RPi2" image for RPi2/3 devices. If you download the RPi (0/1) image it will not boot and show the screen you describe.

The inputstream.adaptive add-on is in our add-on repo, so as long as you didn't manually disable automatic add-on updates, it has probably already updated, or a reboot will make sure that it does.

There is no 64-bit libwidevine library, only 32-bit, which is why future LE 9.0 releases have switched to the same split 64-bit kernel, 32-bit userspace arrangement as Android. Please also note that Google's license for libwidevine means it is not redistributable without signing formal agreements that result large liabilities for the signing entity. Community or personal LE releases that ignore the license and embed libwidevine for convenience will be suspended from this forum if we become aware they are doing so, because we do not want the legal attention that may result from their release here. There is a Kodi helper add-on for inputstream.adaptive that provides the libwidevine library via a user-initiated process. If it hasn't appeared in the Kodi repo yet, it will do soon - it's inclusion was agreed by Kodi developers at the recent Prague DevCon.

update was published earlier today

If you hear the clicks and whoshes from keyboard navigation Kodi is running but the default output (60Hz, 1080p) doesn't agree with the TV for some reason. You might need to experiment with changes in config.txt, see Raspberry Pi Documentation .. it has nothing to do with the SD card.

The pi-tools add-on contains several packages useful for GPIO things. There are also threads in the forum from users wiring up on/off controls. The GPIO pins might be different for you, but there's probably some prior-art to crib something from.

Things should improve once development builds reach the 4.14 kernel

No idea what's needed, but in LE the custom xorg.conf is located in /storage/.config/xorg.conf .. then reboot to effect the change.

It contains a Realtek RTL8814AU chipset which we have no drivers for, and no plan to add support for. We are basically fed-up with Realtek breeding chipsets on a monthly basis and with absolutely none of them receiving mainline kernel support; which means we would have to maintain the driver ourselves, and we have better things to do with our lives.