Posts by chewitt

I think the best option is a simple finned heatsink that can be attached with a small dab of [heat] conductive paste and a small elastic band around the SO-DIMM board to hold it in place. This would be simple for users to apply and doesn't result in direct contact with the casing. Solutions that achieve case contact will be thermally more efficient but there's a higher risk of mechanical damage; not from thermal flexing, but when a fat-fingered user puts a huge gob of paste on the CPU which uses all the tollerance up and places stress on the SO-DIMM connector. The CM3/Slice has been designed to run quite happily at high temperatures so the goal of adding heatsink is not to achieve the best possible thermal transfer; only to reduce the temperatures enough to keep the thermometer off-screen. I'm only seeing it during large library scans or when trying to software decode HEVC content that it can't handle (with any level of overclock) so it's not really a big deal.

SD cards and USB sticks are equally crap and unreliable IMHO. I would keep things simple and run from SD card, but spend time organising a nightly (or weekly minimum) backup so that when (not if, when) things go wrong it's not a major inconvenience. If you want something faster to boot and scroll around in menu's with (and more reliable) spend $$ and get the eMMC card.

Appendix B. X Config Options lists all nvidia config options available for the current driver that we use. The only item I can see there that might be related is AddARGBGLXVisuals but nothing really stands out.

mkpkg_kodi only packages the Kodi source files; next you need to copy them to sources/kodi and fake the matching .url and .md5 files and then configure the kodi package.mk so that PKG_VERSION contains the correct githash, or you host them on a local server and change PKG_URL (and PKG_VERSION) in the kodi package.mk. The first option is probably easier.

pvr.zattoo is an addon so "PROJECT=RPi2 ARCH=arm scripts/create_addon pvr.zattoo" will build it, then you can install the zip via Kodi GUI. The add-ons we embed in the image are built as packages (similar but different package.mk) not add-ons.

setenv bootrootfs "boot=/dev/mmcblk0p1 disk=/dev/sda1"

Change the boot/disk configuration in boot.ini to look like and it should work? You must partition/format the USB to use EXT4 first.

Quote from darren3976

will this work on libreelec 64 bit

It will work on x86_64 (Generic). It will not work on aarch64 for the reasons already explained above.

Once you add a case, wireless, bluetooth, cables, PSU, and a decent USB tuner, etc. the price difference between C2 and WP2 won't be so large. If you like the DIY approach you'll favour the HK product. If you like everything shrinkwrapped the WeTek box will look good. They're different devices created to suit different consumer tastes.

No random PM please. I've nothing more to say in private than I'll post here.

Hub has the newer S905-H chipset which is considerably better than the older MX chip in the WeTek Play v1. WeTek Play v2 uses exactly the same S905-H chip as the Hub but has more RAM and a Tuner card.

If you want something rock solid with LE the Raspberry Pi v3 is probably the best supported and most stable device, but it sadly doesn't have 4k/HEVC capabilities.

Sorry but I cannot understand the question. Please post links to the OE procedure. Please repeat in your native language.

Not possible (without an immense amount of pre-testing) and there are no official images for S812 devices. You might find something suitable in the Amlogic community section of the forum though. If it's a crappy device, it might be time to swap it out for something better.

Quote from ute

In Krypton Beta builds there are none ..have to wait till it is a full release

That statement is incorrect. Krypton builds have all the same PVR add-ons compiled and maintained in the repo. I'm the authoritative source on that information .. because I'm the current repo maintainer.

NB: You won't see add-ons for Amlogic builds on 7.0.x because those builds are not official and providing add-ons for them is up to the people who provided the builds.

The main Kodi developer working on ADSP continues to work on it so it works/breaks/works/breaks/etc. depending on whether the point we created the latest alpha build was a good or bad day. As popcornmix said, current Kodi plans are to disable it before final v17 release.

I'm not 100% sure, but ISTR there are two problems:

a) Kodi has dependencies on samba 3.x and they need to bump to 4.x before we can use it
b) Samba changed its compile process between 3.x and 4.x and it became a challenge to cross-compile

I believe someone gave up on B as there was no point until A happened, but that was some time ago. I'm not sure anything changed though.

You might be able to connect if you unhide the network temporarily, connect to create/cache the connman service file, then rehide the network?

connmanctl
agent on
scan wifi
services
connect <string for your wifi>

NB: The security benefits of hidden WiFi are zero because periodic re-authentications made by connected devices in normal use leak the SSID to anyone with a network sniffer/cracking app and WEP security will inconvenience the same cracking app for no more than 300 seconds. Hacking your network is kindergarten stuff for any security researcher or script kiddie with a copy of Kali Linux. WPA2 is considered secure; so use it.

LibreELEC.tv/options at master · chewitt/LibreELEC.tv · GitHub

It can be set there, but the level of additional CPU optimisation you get during cross-compilation will be minimal and you probably break binary compatibility with Kodi add-ons in our repo that have not been compiled with the same configuration.

Correct, "git checkout 7.90.008" sets the repo to that specific commit.

Theory: I think you disabled "parent folder items" in Kodi GUI navigation and somehow you're being dropped into the "Services" folder in our repo (which doesn't have the PVR stuff in it) when you need to go back up a level to the root of our repo and then and into the PVR clients folder where pvr.hts can be found.

The way our build system works it's quite trivial to change one tiny part of the OS, but you cannot apply an incremental patch to existing KERNEL or SYSTEM files so you must replace both.