Posts by chewitt

You need to cross-compile the image (we don't call them ROM's) from sources with the driver module included. You might be able to copy things from another image if the source is using *exactly* the same kernel as you. Usually that's not the case.

If you want to run lots of extra services via containers you'll see delays in shutdown. If you want to avoid that, it's best to get a NAS and run them somewhere else. Make sense?

No difference.

script.moonlight was waiting on an upstream fix since the recent major repo and libCEC changes. It's in the repo now.

You're looking at a virtual read-only filesystem that is uncompressed from /flash/SYSTEM on boot. It cannot be changed. If you need to add something either self-compile an LE image with changes or Google and learn how to bind-mount things.

There are now two repo's; one for v7.90.001-008 and v7.90.009 onwards. If you refresh the add-on repo Kodi will pull down a newer version of the add-on that's compiled against the newer SSL version.

In the last 24h I found an old 80GB PATA drive in the cupboard which enabled me to literally blow the dust off a mk1 ATV box and test/boot the 7.0.2 image that I created back in ~July when the HDD died (and then vacations, etc. forced me to down tools).

It works, meaning it boots and CHD is active, but it's not a great result. I'm using the same collection of hacks and tricks used on the OE 6.0.1 build but the result is not as nice. Gut feel (from general experience on many devices) is that Jarvis is a little heavier in RAM footprint than Isengaard and on a box already RAM starved Jarvis looks to be a step too far. I'm able to play lower-bitrate and smaller sized media reasonably well, but higher bitrate and larger filesize things cause "reboot required" lock-ups. Aside from RAM use being higher Jarvis has some VideoPlayer changes (core plumbing) that move the codebase further along from the last CHD-supported point and it's clear things are not aligned; which is something I am not skilled to fix.

I'll sleep on it for a few days but as things stand this means I won't be releasing a 7.0.2 build, at least not with CHD support. You can get a cheap Amlogic box for $40 that makes the mk1 AppleTV look and feel like the 10-year old design that it is. As much as I'm fond of them, I couldn't use this build as a daily or even occasional use box.

I'm able to install any add-on I like from the 7.0 and 8.1 repos on an RPi3, Slice_CM3, x86_64 box, and WeTek Play2/Hub boxes, which means I'm fairly sure the repo is working fine. I'm going to ask again (last time) for a Kodi debug log with additional component logging on http so we can see what's being queried and the response given. Otherwise, no log = no problem.

If the add-on is in the stock Kodi repo it will be visible in the LE Kodi repo .. because it's the same repo.

This should be resolved in the 7.0.3 update which should be out in the next 48 hours subject to testing. In case anyone gets too excited, 7.0.3 is basically 7.0.2 with a couple of minor changes (Pi firmware update being one of them).

Should be fixed now. There will be further updates to inputstream.adaptive in the next day.

*.*.158.199 - - [05/Dec/2016:23:58:56 +0000] "GET /7.0/RPi/arm/addons.xml.gz.md5 HTTP/1.1" 206 295 "-" "Kodi/16.1 (X11; Linux armv6l) LibreELEC/7.0 HW_RaspberryPi/1.0 App_Bitness/32 Version/16.1-Git:c327c53"
*.*.158.199 - - [06/Dec/2016:09:56:14 +0000] "GET /7.0/RPi/arm/addons.xml.gz.md5 HTTP/1.1" 206 295 "-" "Kodi/16.1 (X11; Linux armv6l) LibreELEC/7.0 HW_RaspberryPi/1.0 App_Bitness/32 Version/16.1-Git:c327c53"
*.*.158.199 - - [07/Dec/2016:09:56:16 +0000] "GET /7.0/RPi/arm/addons.xml.gz.md5 HTTP/1.1" 206 295 "-" "Kodi/16.1 (X11; Linux armv6l) LibreELEC/7.0 HW_RaspberryPi/1.0 App_Bitness/32 Version/16.1-Git:c327c53"
*.*.158.199 - - [08/Dec/2016:09:58:00 +0000] "GET /7.0/RPi/arm/addons.xml.gz.md5 HTTP/1.1" 206 295 "-" "Kodi/16.1 (X11; Linux armv6l) LibreELEC/7.0 HW_RaspberryPi/1.0 App_Bitness/32 Version/16.1-Git:c327c53"

Your box is querying the current 7.0 repo without issues (MD5 is checked, if the hash changed the full XML is downloaded). Your IP doesn't show up in error logs for the same period so I have to assume the issue is client side and the box is not querying for the updated add-on. Perhaps remove the Addons*.db file(s) and let it recreate the DB on next boot? .. and/or enable http component logging in Kodi and look there.

PM me your public IP address so I can look in our webserver logs. I'd also like a copy of the Addons26.db file so it can be looked into.

I'm not sure why you're trying to build the add-on when it's already built and present in our repo. Solve the network (or whatever it is) problem that prevents you from downloading the add-on, then it will self-update. Put Kodi in debug mode and activate http logging and look at the logs for more information. If that doesn't show anything you can PM me your public IP address so I can see what's in our webserver logs.

This is expected and documented in the v7.90.009 release notes:

"WETEK HUB REMOTE
The popular WeTek Hub box ships with a small and simple remote and many users would like a larger remote with more feature buttons. To accommodate this we are testing a switch from amremote to lirc which allows the on-board IR sensor to be configured for other remotes. These changes remove the Airmouse function which has little use under Linux, and the ability to power-on the device from the remote. We consider power-on important and are investigating changes to restore that capability."

Are you using the internal wireless of the RPi3 or an external USB dongle? ..and what wireless regulatory domain (country) is your router set to?

Jester Skinning is not our forté so we would welcome suggestions (and ideally code) that make the LE settings add-on work better or behave neutrally with other skins. The add-on was originally created for Confluence and has been lightly hacked for Estuary (1) so I'm sure improvements are needed for Estuary (2) let alone other established skins like Amber/Nox/etc.

It should be possible to export any $PATH you like from autostart.sh or ~/.profile ?