Posts by chewitt

Either you used the RPi image (which is for RPi 0/1 devices) not the RPi2 image (for RPi 2/3 devices) or you have the RPi2 image but your RPi2+ is actually an RPi (1) device. The rainbow screen shows when you have the wrong image.

The WeTek device wrxtasy linked above is designed for markets where wireless 4G (LTE) networks are more prevalent than fixed-line broadband and it's targeted at ISP/telco customers (along with IPTV middleware which is WeTek's main business). The second one I saw first-hand in January is an S905X evolution of the Hub (slightly smaller and like all S905X, it uses 100BaseT Ethernet). I was told that device may be available to consumers later in the year but there were no specific dates.

The laptop dates from 2005/6 and the GPU inside dates from 2004. LE has never intentionally supported laptops or ancient hardware (we target recent HTPC devices) so if it works that's nice, but if it doesn't; sorry but we're not going to investigate to fix support. FWIW, I never heard of any LE supported devices using S-Video output. Raspberry Pi 3B+ would be a major upgrade in performance over your old laptop.

The website supports RSS, and official releases will pop a toaster message saying "new release available" as long as you're on the same base release, e.g. you'll see a notification for 8.2.5 (once released) if using 8.2.x and the notification hasn't been disabled.

WIFI will depend on whether the router is forwarding UDP broadcast packets to the Ethernet segment of the network. Some routers do, some routers do not.

TVH cannot mount network volumes, but you can locally mount a remote NAS share at startup using systemd. Go look at the example CIFS and NFS sample .mount files in /storage/.config/system.d

Either change PKG_URL to point to your repo and set PKG_VERSION to the short githash of the commit that you want to include (typically git HEAD of the branch), or create a git patch of the commit that includes the changes you want, and add that to packages/devel/libcec/patches/libcec-xx-description.patch, then re-run the build command and changes to the package will be detected, old code cleared, and new code with changes built.

You may need to test a current Milhouse release to have working ath10k drivers as support is not enabled in LE 8.2.x, and even then you might be missing firmware for that QCA device, but that would be easy to see in dmesg output as it will show errors.

Sorry.. I stopped recommending hardware to users about 5-years ago

No debug log = No problem.

Get a milhouse release from Kodi forums.

At first glance it looks like an older box with a GPU that supports H264 but not H265 hardware decode, so HEVC is software decoded and this normally requires a decent (newer) CPU to work.

If you write the "RPi" (0/1) LE 8.2.4 image and use on RPi3B+ you get rainbow screen. If you write the "RPi2" (2/3) LE 8.2.3 image (or older) and use on RPi3B+ you get rainbow screen. If you write the "RPi2" 8.2.4 image all should be good.

I never used them, but ISTR Kodi repo has some add-ons for adding bonus feature support into screens/menus.

Netflix requires crypto support that is only available in Kodi v18, so you need to use an LE 9.0 development build not LE 8.2.4 (Kodi v17).

Unless you have disabled auto-update, all official LE release will (by default) auto-update from 8.2.3 to 8.24 (to 8.2.5, etc.). You can manually update using the LE settings add-on.

Quote from pepeq

is the following criteria met by OSMC on RPi3: - play 4k HDR material

Raspberry Pi is amazing for a $35 device, but 4k is way beyond it's capabilities.

Thread closed because this topic is not open for debate.

There is consensus among team and community developers to stop supporting the installtointernal script. Installation on eMMC/NAND provides a marginal performance gain on most boxes, but adds significant complexity to the installation process and the number of installs that go wrong and need significant hand-holding to correct is proportionally high (much too high).

Creating releases is fun. Finding bugs and resolving them can be rewarding. Supporting users with the same installtointernal issues over and over and over makes you hate life, Android boxes, and users. The script is gone. The script is not going to return (the risk is our sanity, not your box).