Posts by chewitt

Two choices:

a) Wait patiently for add-on creators to udpate their add-ons to be Py3 compatible for K19.

b) Run LE 9.2 instead of Milhouse pre-Alpha K19 code - the bleeding edge is bloody.

I'd guess that ConnMan wants to have a deafult route and will add one back if it detects it's missing. If you put connman in debug mode stop the service and restart manually with -d in the command and tail the journal you'll probably observe that behaviour.

I'm no expert on routing things, but can you change the route instead of delete it? .. and what's the purpose of deleting it?

The best option in the $50 range is an RPi4 (2GB or 4GB) with a Kodi flirc case. Software is still evolving (no HDR or high bitrate audio yet) but those will come and it's more reliable then the Amlogic and equivalent Rockchip hardware that's kicking around. Most of the 'good' new box devices are some way above your price point.

I've no idea what the issue is, but it's best to run the GUI at 1080p with 4K modes (23.976/24/50/59.94/60) in the whitelist for playback. RPi4 may be a leap forwards in terms of Pi hardware and processing but it's still a low-power ARM board.

Which Xaomi device was it shipped with?

I've pinged the maintainer. The workaround will be to create another $PROJECT entry in packages/linux/package.mk so that NXP project is compiled using an eariler kernel that the patches were generated agaisnt. Until a proper kernel bump is done.

S905 does not support HDR, the -H means the chip is widevine/playready licensed.

Scraping issues are frequently caused by people not following "the Kodi way" of structuring files/folders. Put each movie in it's own "moveiname (YYYY)" folder under the (source) root and things should be fine. Stuff everything into a single folder and .. expect some scraper issues.

The clues on which sources to use are in post #68.

Yes, if you know how to self-compile Kodi .. but if you knew how to self-compile Kodi you wouldn't be asking the question

Once HDR support is fully baked (right now it is far from) nightlies for Ubuntu will be available from the official Ubuntu PPA.

How ancient is the laptop? .. and what GPU is inside?

Me? No. I've already given hints, and that's as far as I personally go towards helping anyone install torrent apps.

User posts about low-quality Realtek device delivering low-quality performance. LE staff feign surprise and advise user that the $2 USB wireless thing they purchased is garbage. User asks for officially supported and recomended alternative cheap USB wireless devices. LE staff refuse to recommend anything because all the cheap USB wireless stuff you can find is similar garbage. LE staff recommend a wireless bridge that presents Ethernet to the RPi2. User protests that $20 (for a used Apple A1rport express on eBay) is an outrageous idea and makes pithy comments about our decision to not add more low-quality realtek drivers to our distro (so they can purchase the latest expensive USB Realtek wireless garbage instead of older cheap garbage). Eventually user gives up and gets a wireless bridge that just works and the pithy comments stop.

^ is usually how these threads play out..

It's unrealistic to expect add-ons built for our current distro to work on OE. It's ~4 years since we abandoned OE to its problem creator and in that time we have maintained and evolved our codebase. Things look familiar but under the hood they are programatically different. The sole solution is updating the OS/distro. Use docker or look at the Thoradia thread for torrent apps if you really need them. If you really want it to work in OE, please ask for help in the OE forum .. although good luck in finding a real user (it's mostly spam-bots).

Tvheadend web interface on port 9981

It just means the wifi chip will not work. The chip copies (is ripped off from) a Realtek design but with enough differences that you can't simply add the chip IDs to the existing Realtek driver, and the existing driver source for Linux 3.14 "works" but is garbage code. We had a stab at forward porting to Linux 4.20? (it was some time ago) but with no documentation and badly written code to start from it wasn't a fruitful expedition and we gave up. I also had one of the Rockchip staff (native Mandarin speaker) do some phoning around and he confirmed SSV went bust in 2016 so there's never going to be newer official sources. The latest kernel the current driver will run on is Linux 4.4. After 4.4 you run into significant crypto API changes (needs a major rewrite) and this stops the driver from working.

Mainline kernel doesn't have same hard-coded 1GB/2GB device-tree silliness as older kernels. Wireless chip is the SSV6051P .. the same crap cihp that's in the Tanix box. There's no support for that chip under mainline kernel (and unlikely to change).

You can have a look for a Docker container .. or if you have any dev skills, add a package to our network-tools add-on.