I disagree. I just want to remind everyone that the basis function of these kind of hardware actually is to watch television via satellite, cable or terrestrial. This hardware isn’t a mediaplayer although many people would like it to be. Be happy with the functions that are available and usually are stable. That is our main goal.
Hi,
no, please, don't start this rant again.
We know there are modern smart-tv and android-boxes but I don't want/need one more device: already my old vuduo2 has more than enough juice for multimedia apps.
There are many other priorities, we know, like the old OE checkouts OpenPLi is based on, the painful enigma2 spaghetti-code, the unmaintained vendor's bsp, etc. etc.
Neverthless we can't just ignore that most of the people who bought (consciously) an enigma2 receiver do NOT just use it for TV but also as a NAS, or a media-player. I do.
The problem is that the extensions/plugins do not work or do not compare at all with the dedicated (xbmc) add-ons.
I imagine the reason behind this (vuplus fault) still we cannot force all the vendors to provide a working browser.
So while I agree many people are tempted by the gray-zone/pirates add-ons I give here my perfectly legal case: the Hbbtv extension does not work here in Italy for italian service providers (RAI on Demand).
The Kodi/KodiLite add-on does instead work.
For my machine I have been told a special kernel is needed for Kodi (different commandline I think btw) but this appears not to be mandatory because KodiLite 5 does indeed work on OpenPLi 7.1 (installed by hand its installer)
Now, what to do?
As OE developer I must have missed the tragedies behind the OE2/OE3 OE-Alliance, OpenPLi splits back in the years.
What I see is there are around the recipes for Kodi in almost any other 'distro' (big word).
Are there any more conceptual taboos?
Is it adviseable/permitted/suggested/accepted to just import the Kodi stuff from oe-alliance to the PLi layers?
Cheers
A.A.