blzr

if you'd like to preserve some package (like softcam including its startup script) against updates, you can flag it with hold, like:

opkg flag hold enigma2-plugin-softcams-oscam

please note:

if you use (install) the e2iplayer version from @zadmario then after start from e2iplayer it comes a error as you can see in the following picture

(but this error is only a cosmetic problem because this e2iplayer still works good in openpli-8.0. 

 

openssl_error.jpg

 

 

regards

Pike

 

on current 8.1 release, to get rid of this error:

opkg install libcrypto-compat

see this:

https://forums.openp...dpost&p=1298642

If you're on develop image - for openssl version detection "issue" - install libcrypto-compat package, should help after latest changes to it

(and I suggest to use ffmpeg and other iptvplayer dependencies from feed and not any third party precompiled bianries - installing enigma2-plugin-extensions-e2iplayer-deps)

done

https://github.com/O...e-core/pull/946

//however, I am quite worried about your described health situation, I really hope it is only temporary...
take your time, rest easy, get well soon

for me modifying just one line was enough to get rid of this bogus error message at plugin startup:

diff --git a/IPTVPlayer/setup/iptvsetupimpl.py b/IPTVPlayer/setup/iptvsetupimpl.py
index 1221226..a4b479e 100644
--- a/IPTVPlayer/setup/iptvsetupimpl.py
+++ b/IPTVPlayer/setup/iptvsetupimpl.py
@@ -291,7 +291,7 @@ class IPTVSetupImpl:
     def getOpensslVersionFinished(self, stsTab, dataTab):
         printDBG("IPTVSetupImpl.getOpensslVersionFinished")
         if len(stsTab) > 0 and True == stsTab[-1]:
-            for ver in ['0.9.8', '1.0.0', '1.0.2']:
+            for ver in ['0.9.8', '1.0.0', '1.0.2', '1.1.1']:
                 if ver in dataTab[-1]:
                     self.openSSLVersion = '.' + ver
                     break

as i know after inspection Openpli 8.0 were build without openssl support: !!!!!!

I have no idea what was the subject of your inspection, but above statement, while very emphatic, is definitely not true...

Go to /usr/share/enigma2/display/skin_default and open skin_display.xml.
Edit it by putting 'Clock' instead od 'Number' in the first part of the file like this:

<screen name="InfoBarSummary" position="0,0" size="1,1">
        <widget source="session.CurrentService" render="Label" position="0,0" size="1,1">
            <convert type="VfdDisplay">Clock</convert>
        </widget>

Restart enigma2.
The problem is, sometimes after update it reverts back to the previous state.

 

to protect your changes from overwriting when skin is updated, you need to put them into /etc/enigma2/skin_user.xml (general, it will apply to each skin you use) or /etc/enigma2/skin_user_name-of-the-skin.xml (for specific skin only);
these user files have priority over those in /usr/share/enigma2/... and are preserved during updates
entire altered screen has to be put there there

<skin>
	<screen>
	...
	</screen>
</skin>

(you can customize multiple different screens of the skin this way, and also e.g fonts used)

 

STEP 5

For exteplayer3 to work properly, it is required in the file settings located at / etc / enigma2 / settings,
insert the following line:
config.plugins.iptvplayer.exteplayer3path = / usr / bin / exteplayer3

You must do this with a command via telnet:
init 4 && sleep 1 && echo "config.plugins.iptvplayer.exteplayer3path=/usr/bin/exteplayer3" >> /etc/enigma2/settings && init 3

 

I still get   - It seems that the video player "external eplayer3" does not work properly. STS: nice cant execute'-u': No such file or directory. Error Code 127

 

check if you have for sure the config for exteplayer path in /etc/enigma2/settings,

 

if you enter it manually, note that path must not include spaces, as it does in this quotation above

config entry should be:

config.plugins.iptvplayer.exteplayer3path=/usr/bin/exteplayer3

Who doesn't work exteplayer3 add this line: config.plugins.iptvplayer.exteplayer3path=/usr/bin/exteplayer3
to file settings:/etc/enigma2/settings.

good hint!

I can only add, that you must stop enigma before changing 'settings' file otherwise the changes won't be applied

init 4

... now edit /etc/enigma2/settings - add line to it and save

init 3

or directly from commandline (be careful, in case typing this by hand, pay special attention to double '>>')

init 4 && sleep 1 && echo "config.plugins.iptvplayer.exteplayer3path=/usr/bin/exteplayer3" >> /etc/enigma2/settings && init 3

but of course first you have to have enigma2-plugin-extensions-e2iplayer-deps installed

and what exactly problem you have with exteplayer? with installing it, or running?

root@vs1500:~# opkg list-installed *player3*
exteplayer3 - 68+gitr125+52666ca-r0.9

you can install dependencies for e2iplayer in bulk by running the console command:

opkg install enigma2-plugin-extensions-e2iplayer-deps

this will install the following:

Recommends: duktape, exteplayer3, f4mdump, ffmpeg, gst-ifdsrc, gstplayer, hlsdl, iptvsubparser, lsdir, rtmpdump, uchardet, wget

yup, this plugins's dependencies check / install method is quite 'unstandard' to say the least
of course you do have openssl installed in openpli 8 it's the latest release 1.1.1 version, and plugin's script is outdated in this regardd

install plugin dependencies:

opkg install enigma2-plugin-extensions-e2iplayer-deps

and don't bother with this fake error message (just close it with 'ok'...)
 
if you'd like to get rid of it for good (it'll keep appear at first plugin start after every e2 restart) you'd need to adjust iptvsetupimpl.py to include current ssl version 1.1.1

I did so, but nothing, always the same, maybe your skin is in the feeds mine not

no, it is not (and it is irrelevant in this case...)
please find attached archives with unpacked content of your skin and plugin, taking a look into them should possibly get you a clue which folders and files should be added to backup (?)

@serch826
you can backup any folder/file with autobackup plugin, and restore it at first boot after flash (if you accept when asked if restore settings from backup)
so, you need:
- go to autobackup plugin > menu > select files to backup > browse to your skin folder, and probably also some its own specific converters/renderers (you'd need to look into your skin package structure, to make sure what it exactly consists), and mark them all to be backed up (yellow)> save (green)
- create a backup manually (yellow), unless you have daily automatic backup option set
then, after flash, when you choose to restore settings, your skin should be restored, and box should run with it on...

If your language is not correct then please document what needs to be fixed and I will try my best to get things right.  Please check your change requests carefully as I really don't want to be correcting this data for the rest of my life.

 

It would be appreciated if people can also confirm that their language is correct if that is now the case.

 

Regards,

Ian.

 

well, 'original' Pli numerical text input layouts for given languages were created by their native users, hence one could assume that they knew exactly which national characters are used in their language,
to not add / remove any 'national' characters to these old layouts might have been not the worst idea in the first place (?)
just saying...