Posts by chewitt

Quote from lefty420

I'll keep researching and playing (Im a carpenter by trade) so coding is very new to me. But I am a hobbyist

Frequent contributors to the project include a paramedic and an airline pilot, so being a carpenter is no handicap!

There are no plans to officially use or encourage the use of BTRFS so no plans to add the management tools to our repo. Have you tried installing @lrusak's repo and installing it from there?

To actually check you'd need to provide us with the USB controller name/version so we can compare against the Linux kernel, but a) I doubt you can find any devices advertised with those details, b) It would a very dull exercise to do the check (not many volunteers) and c) any cheap add-on board you find is going to use the cheapest commodity chips, which practically guarantees they will be widely used and supported.

So, get a board and be amazed that it just works. Probably

I'm not disputing that this is your experience. I'm simply stating this is not the normal experience. Let's see the logs

The feature is still in active development and the code for it has not been merged yet. It looks like milhouse test builds are building with the proposed code added, so you can run those and it should be available.

That doesn't explain why it cannot access our add-ons site. I think you still have an underlying network issue (in your network).

Please test the current v7.90.004 alpha build. If this works, great. If it doesn't, at least you're using something that is still being actively developed. At this stage in the Jarvis lifecycle (all Kodi development stopped 5-6 months ago) we are unlikely to go back and fix anything, even if the issue is related to drivers in the OS (probably) and not actually about Kodi.

15:58:47  29.458195 T:1790964640   ERROR: CCurlFile::FillBuffer - Failed: Couldn't resolve host name(6)
15:58:47  29.458345 T:1790964640   ERROR: CCurlFile::Open failed with code 0 for http://addons.libreelec.tv/7.0/RPi2/arm/addons.xml.gz.md5
15:58:47  29.458445 T:1790964640   ERROR: Open - failed to open source <http://addons.libreelec.tv/7.0/RPi2/arm/addons.xml.gz.md5>
15:58:47  29.458509 T:1790964640   ERROR: CRepositoryUpdateJob[repository.libreelec.tv] failed read checksum for directory 'http://addons.libreelec.tv/7.0/RPi2/arm/addons.xml.gz'

The Kodi log upload website is not always up/reliable to use, but this also shows the box failing to retrieve information from our addons server, which is very reliable and indicates there is a general networking problem, which probably explains why the log uploader is not working.

Are you using Ethernet (great idea) or internal RPi3 wireless (terrible idea)?

Enable debug logging and additional CEC logging, clean reboot, demonstrate the problem, and then "cat /storage/.kodi/temp/kodi.log | paste" the log and share the URL so we can see it.

You should probably track down Chemstar and either ask him to provide sources (else nobody has something to work from) or ask about his plans to update the add-on?

The differences between OE 6.x and LE 7.x are minor so there is no major reason why one should be faster/slower than the other, and as 80% of our installed base runs some form of Pi hardware we'd see a ton of posts if it was a major issue; it's not.

You need to provide a debug logs via "cat /storage/.kodi/temp/kodi.log | paste" and share the URL after a clean boot and some exhibition of the problem, or from our perspective there's no problem.

Remove all traces of docker from /storage/.kodi/addons (if there is any) then enable additional HTTP logging in Kodi, reboot and try again. If still having issues run "cat /storage/.kodi/temp/kodi.log | paste" and share the URL to the full debug log.

There are no mount errors from the 2x SATA drives. Which one is the NTFS drive? .. run "blkid | paste" to see where it mounted.

Try force refreshing the Kodi repo via the context menu. Once it refreshes you will see additional skins available. If it doesn't refresh, provide a Kodi debug log with additional HTTP logging so we can see the error between your box and the webserver it's trying to connect with.

#!/bin/bash
(python /path/to/A.py)&
(python /path/to/B.py)&
exit

this executes each python script independently so they run in the background, allowing autostart.sh to complete. The bash shebang and exit aren't strictly necessary; I included them so you understand start/finish of the script.

You should be able to software decode HEVC/1080p but 4k will need hardware decoding support, which your NUC does not have.

Quote from sharkman

thanx i know u busy and stuff but any idea when it will be ready so can test it

The traditional reply from developer to impatient user is "when it's ready"

update pushed..

I misread the original post (on a mobile phone with tiny screen) and thought you were connecting to an AP, not creating/hosting one.

service.libreelec.settings/connman.py at master · LibreELEC/service.libreelec.settings · GitHub

I'm incompetent at python so I'm not sure whether it's been excluded for a reason. I'll ask. If it's something harmless to tweak, we can tweak the script to allow @ in the name. If not we can better document allowed characters in the settings help text.

NB: As an information security professional I'd advocate you don't use an email address for an SSID as you're divulging something normally considered to be private that associates your identity to the network.