Posts by chewitt

The trace doesn't show much; other than it doesn't include the usual references seen when the SD card is bad. It's not a general issue with 1B hardware as we had several staff (one of whom works for pi foundation) successfully test boards with the 006 image; so there's no eureka moment.

The install process is already documented in the forum posts you've been linked to and the learning experience that follows is all part of the added value in your decision to purchase a cheap no-name Chinese S905 clone (caveat emptor). There is no single definition of "Mini MX" to code around. There are probably 20+ definitions and some will just work while others will need fiddling. On the +ve it's hard to truly "brick" a box, only to put it into a software state that's beyond your confidence.

Solution is in post #3 .. create the LE card and let it install/configure itself normally then resize the ext4 /storage partition to create a third partition on the card that you format as exFAT/NTFS/etc. to be used as media partition that's visible to both OS.

If there's a difference in scraping behaviour it's down to changes between Kodi Helix and Kodi Jarvis (or Kryton) not OE vs LE; and from memory there are a few differences. In all cases a debug log showing the scraping is the first step in understanding why something is/is-not happening.

The correction that you flagged in the OE commit from 2014 is already present/committed in the kernel we use in current Alpha builds (and Milhouse builds) so I'm not sure what you're asking us to do?

Nope, but it's Python and ~90% of all Kodi add-ons are Python, so it can't be too hard, right?

Correct time is a good thing but is also cosmetic to the Kodi GUI so there is no reason to make Kodi start depend upon it. From a support perspective this would make things worse given that some routers act as bad/misconfigured NTP servers, users have a habit of adding typos to their input, and some ISP's blocking port 123 (lord knows why, but it happens).

As 99% of NTP issues are seen on Raspberry Pi .. the cure is adding an RTC card not adding workarounds to the OS.

You can't downgrade the drivers but you can try upgrading to a current Milhouse build as these are running a 4.8 kernel which resolves some Intel GPU issues; although no guarantee this is one of them.

It should work as the Heroku cloud service talks directly to the Kodi webserver so there's nothing to install on LE, but doing this requires you to expose the webserver on your Kodi box directly to the Internet which is not a great idea. It's not really designed/intended to be exposed that way and it's only password secured

v7.90.007 will appear a few days after Kodi release v17b3 .. which is maybe due in the next week (but no guarantees; moving targets etc.)

It's probably possible, but you cannot use pip to install things in LE so the required files/config need to be packaged up into an add-on.

btw, anything involving Amlogic hardware should be labelled with "Here be dragons" due to the higher level of boot/run complexity vs. normal x86 kit which is comparatively straightforward.

It shows a TLS handshake time-out, so maybe NordVPN have a network issue or you're using a config that talks to incorrect servers - but ultimately that's a guess as I have no clue about that add-on. I suggest you contact the add-on creator for help; it's not one of ours.

No debug logs. No problem

Yes in theory you can take the patches and various kernel bits but there is no nicely written wiki article to explain the entire process so in reality it's one of those "If you have to ask how it's done, you're not going to succeed at the task" cases. I don't mean to be arrogant in saying that, it's just that I have a load of experience with people trying to fiddle with the logical and well structured LE build-system, and that's how it plays out.

In some devices the region coding is embedded in device firmware so selection is handled automatically by the kernel. In other devices the default is a world region code. This is in theory what RPi3 has, only the wireless driver has some caveats on auto-detection and only sees channels 1-11 unless you force the region code (which has nothing to do with Kodi). We don't ask for the region code because a) we have no way of asking it currently, b) no other driver needs this, c) out of tens of thousands of installed systems only about 10 people have complained.

No it would not. Setting the region in Kodi has nothing to do with wireless region in the OS layer.

There are no PDFs but

shows how to download and connect to the box over SSH from Windows using PuTTY. From there you run "dmesg | paste" and reply here with the something URL it generates. Regular contributors to the project include a paramedic and an airline pilot so being a plumber is no excuse