Posts by chewitt

Several pirate add-on repo's are installed. Support stops here.

Connect the NUC to the TV and dump the EDID using the embedded "getedid" script that configures Xorg so it believes the TV is always connected. If you're lucky that overrides whatever the Pioneer AVR is screwing up.

Enable BT under services or system, then go back to the BT devices screen. It's something that needs to be relocated for 9.0

nickr I'm not aware of any and the community efforts are still quite focussed on Krypton, which is probably a good idea considering the amount of plumbing that will radically change before Leia release; new modern kernel and graphics architecture, all the vpupdate stuff etc. in Kodi.

That kind of feature request belongs in the Kodi forum, it's not something we (an OS that runs Kodi) can or would implement.

I'm sure it can be made to work; in the past I created an experimental MT7601U package for OpenELEC that worked and the drivers are similar, but "working" and "supportable" are different things. The driver requires configuration via a user-editable file, which is not how things are done in any modern Linux and certainly not in an embedded distro. Mediatek drivers make Realtek ones look polished so I will reject any attempt to add their current drivers to our images. You're welcome to make your own custom image though.

If you end up with a working/reliable add-on, please consider submitting it to our repo.

"journalctl -b 0 --no-pager | paste" and share the URL generated after a clean boot where the wireless is not on

There are no plans to include this driver in release builds because it is not cfg80211 compliant and looks like it was written by first year CS student, although that's insulting most first year CS students. Mediatek need to get their sh1t together and provide a proper driver.

cat /storage/.kodi/temp/kodi_crashlog_20170512125355.log | paste

send some crashlog's to sprunge and share the URLs

Commits · kodi-pvr/pvr.argustv · GitHub

still shows some development.

If you can provide a URL to a pastebin'd debug log that shows the error(s) that would be best.

The only links that will not work are old alpha/beta links that are no longer relevant.

LibreELEC.tv/linux.arm.conf at libreelec-8.0-sX05 · kszaq/LibreELEC.tv · GitHub

if you are using @kszaq's S805 image and the chipset is the same one the other user identified, the driver is enabled in the kernel. This means it should work, although how well it works appears to be in question.

Google doesn't reveal much for that chipset so it's hard to comment.

It needs to be added to kernel boot params in syslinux.conf or extlinux.conf (whichever is used)

mount -o remount,rw /flash
nano /flash/extlinux.conf
add the changes to kernel boot params in extlinux.conf, save and exit
mount -o remount,ro /flash
reboot

I already told you on Facebook that you need to provide information on the chipset inside the device. Then (and only then) can we investigate what is required to support the device. e.g. run "lsusb | paste" over SSH and share the URL generated so we can see the device IDs.

12:38:34.560 NOTICE: Running on DroidBOX iMXQPro_v2 with Android 6.0.1 API level 23, kernel: Linux ARM 32-bit version 3.14.29

this means you are running Android, not LibreELEC. I suggest you post in the Droidbox forums.