Posts by chewitt

Krypton disables installation from zip unless you explicitly enable support in Kodi settings. This is a new function designed to make people think twice before installing pirate add-ons. There are no known issues installing other skins. If you believe there to be an issue please enable debug and component http logging then clean boot. Once rebooted demonstrate the problem and run "cat /storage/.kodi/temp/kodi.log | paste" or use the log file submit option in the settings add-on to create a sprunge.us URL to share the log file. No log = No problem.

Nice. Welcome to the 21st century

Fix is merged and will appear in next release. I'll mention the wakeup issue to others .. it's not part of the OS that I understand.

Please test LibreELEC-Generic.x86_64-7.90.010.tar which contains an updated version of atvclient and report back here with results. I no longer test this package with AppleTVs so it got missed in the move to Krypton.

Nope. I got back from from vacation this afternoon and will look at the build issue sometime tomorrow .. and by the time that's done we'll be releasing something with Kodi 17.0-RC1 so I'll probably skip creating a 7.90.010 build and just run with that.

Update to LibreELEC-Generic.x86_64-7.90.010.tar and then run "dmesg | paste" and share the URL again. The build has the ath10k driver enabled; it is unlikely to give working wireless as-is but I can see the firmware load failure messages. Thanks.

Repositories are add-ons that are installed from a zip file like any other Kodi add-on. Most people who publish a repo for public consumption will also provide a zip to install the repo. NB: @vpeter's add-on was cleaned-up a little and is now in our main add-on repo as "Touchscreen" .. so no need to install a repo.

Install Hyperion from our add-on repo. Use our version of HyperCon (look in our wiki) to configure it.

LE 7.0.2 was released in June before support for Skylake and newer GPUs was available so you will need to run the Alpha build (which is very solid on x86 kit - ignore the label). To collect the logs I asked for you can connect the board via Ethernet. I need to see the output from them.

Debug log from clean boot exhibiting the problem please.

Debug log shows that you have the "default" audio device selected and this has no passthrough capabilities. You need to select either the S/PDIF (ALC283 Digital S/PDIF) or HDMI (PIO SC-2022 on HDMI) outputs as the passthrough audio device.

No support for this at the current time. Sorry.

Be adventurous and go try it..

lspci | paste
lsusb | paste
dmesg | paste

run those commands over SSH and paste the sprunge.us URL's generated. Then we can see what wireless chipset is on the motherboard and figure out what needs to be done to support it.

People need to go back and read post #8 again. No facts or technical data = No developer cares about the incomplete issue report.

autostart.sh is run at the very start of userland boot so you will need to background the task and use a "sleep 15" or similar value to ensure a) the network is up, b) Kodi has been started and reached home screen.

Current behaviour is the sum of changes by Kodi team and various add-on contributors. I'm not sure waiting will achieve anything as those upstream exist in a state of ignorance (and Music is the bastard child to all-important video). You're much better off poking around to see if you can get a better result.