WanWizard

Those were all Broadcom based boxes, and Broadcom doesn't make any chipsets for the OEM market anymore (they were bought off by the media industry in 2021), so don't expect any new hardware to come to market.

The current plan is (subject to change) is to create a 9.1-release from the current develop, then promote Kirkstone to develop, which will then become OpenPLi 10 in due time.

Whatever python version is running is not very relevant, not for users, and if you are a developer and you code for specific minor versions of Python, you're doing it wrong.

Kirkstone builds are being tested, but are not publicly available for download, they are only available for developers.

( if that is not the case, something is wrong and needs to be fixed )

I'll have a look, once I've managed to fix our crashing NAS...

What's this "sat dish" sign next to channel name, is this you customization, or there's a setting for that??

Yes.

Open the channel list, menu button, Configuration, and then:

1. We will never know until that has been properly debugged on your box and with your file(s) of streams.

I remain convinced that the box isn't frozen, the box is waiting for a stream to respond.

I've passed the issue on to the developers.

You have FCC on, perhaps tuxtxt isn't compatible with it, and gets confused with multiple PID's pre-tuned?

Either way, there isn't much you can do about it. you can tell the SoC what output you want at the HDMI end, and that's about it.

Using @Dimitrij's plugin, you can make a mapping from what the channel says is broadcasted (1080i25) to what you want at the HDMI end (which basically configures the SoC on a per-channel basis), and that is the end of the tuning abilities.

If the SoC does it wrong in your opinion, the only thing you can do is to use the plugin to make a mapping so that the SoC doesn't do anything (so you map 1080i25 to 1080i25, 1080p50 to 1080p50, and so on), and hope the TV deinterlacer does a better job.

Or find a box with a BCM SoC and see if that does a better job.

The problem has always been, from day one, that HbbTV libraries have paid-for licenses, they are closed source.

Manufacturers have made an implementation, at the moment the hardware was put to market, so they could put "HbbTV" on the box (a main selling point in countries like Germany). And that was the last time they looked at it, as maintaining it costs money, and they are not in the business of spending.

So obviously, as time progresses and image makers upgraded their OE, things started to break.

The only possible light and the end of the tunnel was OpenHbbTVbrowser, an open source solution, but that project seems dead, no activity in over 3 years.

Drivers are loaded at boot time, restarting the GUI just restarts the Enigma application.

... you need to install it from the commandline, or using the advanced options menu of the software management plugin.

Then your submoduiles (or at least meta-vuplus) aren't up to date.

the old hbbtv plugin was removed from the BSP two years ago: https://github.com/O...044b3fcbdb23fdc

Have you changed things in your local OE? We don't have a enigma2-plugin-extensions-hbbtv plugin in the feed for the vuduo.

You haven't included the error message itself.