OpenPLi Wiki - User contributions [en]

Information for Developers

2023-05-11T09:59:14Z

WTE: Minor update

==''''I'm a developer, is there any technical info available from the PLi® team?'''==
Welcome and tell your developer friends about us

Yes and welcome aboard! If you have specific question, you can use our PLi® Third Party Development forum to ask it. You will find we are most accommodating.

This page is about software development using OpenEmbedded-core. If you're looking for the text that used to be on the this page, it's now called developer-information-old.

=='''Create your own build'''==
See also this forum post on setting up a development environment: [http://openpli.org/forums/topic/18806-openpli-quick-setup-ubuntudebian/http://openpli.org/forums/topic/18806-openpli-quick-setup-ubuntudebian/]

Basically, it boils down to this:

Run Linux. Most of us use the latest Ubuntu desktop release, I suggest you do the same, if you don't know what to pick.

Make sure the disk you use for the OE tree supports symbolic links, and you use at least git v1.8.0.

Install prerequisite packages, as described here: [http://www.openembedded.org/wiki/OEandYourDistrohttp://www.openembedded.org/wiki/OEandYourDistro]

For Ubuntu 22.04 LTS, that's:

sudo apt-get install sed wget cvs subversion git-core \
coreutils unzip texi2html texinfo docbook-utils \
gawk python3-distutils diffstat help2man make gcc build-essential g++ \
desktop-file-utils chrpath default-jre gettext zip libssl-dev

You may need to create a symlink makeinfo->texi2any (in the bin folder) and a symlink makeinfo->/bin/texi2any in the hosttools folder.

For CentOS, that's:

sudo yum install gawk make wget tar bzip2 gzip python unzip perl patch \
diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath socat \
openssl-devel zip python3 perl-Thread-Queue libstdc++-static \
glibc-devel.i686 libgcc.i686 libstdc++-devel.i686

Setup the build environment:
sudo chmod ugo+rw /opt
mkdir -p /opt/openpli
cd /opt/openpli

Clone the openpli repository:
git clone https://github.com/OpenPLi/openpli-oe-core.git
or
git clone git@github.com:OpenPLi/openpli-oe-core.git

Setup the OpenPli environment
cd openpli-oe-core
make -f Makefile

Build your first image
MACHINE=xxXXXX make image
or
cd build
MACHINE=xxXXXX
source env.source
bitbake -k openpli-enigma2-image

To find the valid MACHINE=xxXXXX you can have a look at the .conf file in the meta-folder of the manufacturer MMMMM:
cd meta-MMMMM/conf/machine
ls

If the build is successfull the resulting file will be into:

./openpli-oe-core/build/tmp/deploy/images/xxXXXX/
openpli-homebuild-xxXXXX_usb.zip

===Updating===
Before every build, update your cloned git repositories with
cd openpli-oe-core
make update

Note that by default, the develop branch of Enigma is used when you build an image, assuming that most "homebuild" users will want to build the latest development image.

If you want to build a homebuild release image, you need to specify the correct branch when building:
cd openpli-oe-core
git checkout release-7.2
git submodule update --init --recursive
ENIGMA2_BRANCH=release-7.2 MACHINE=xxXXXX make image

The resulting file will be into:

./openpli-oe-core/build/tmp/deploy/images/xxXXXX/
openpli-homebuild-xxXXXX_usb.zip

=== CentOS incompatibilities ===

Note that CentOS, even CentOS 7, comes with gcc 4, which is pretty old. It is advised to use DevToolsets to switch to 7 or 8:

sudo yum install centos-release-scl devtoolset-7 devtoolset-8

which gives you the option to use versions 6, 7 and 8 as well. You can enable a version using "scl enable devtoolset-8".

When you want to compile OpenPLi-8+ (i.e. an image based on Yocto Zeus or higher), you need at least tar v1.28, but CentOS comes with 1.26, and bitbake refuses to run.

You can address this issue by (as root):
cd /tmp
wget https://rpmfind.net/linux/mageia/distrib/6/x86_64/media/core/release/tar-1.28-3.1.mga5.x86_64.rpm
rpm2cpio tar-1.28-3.1.mga5.x86_64.rpm | cpio -idcmv
cp /tmp/usr/bin/tar /usr/bin

=== Ubuntu incompatibilities ===

When running a build on ubuntu, you can run into the issue that the build is aborted by the sanity checker, complaining that "makeinfo" does not exist. Even though the package texinfo is installed. This is caused by the fact makeinfo is now a symlink, which doesn't make it into hosttools.

To fix this, execute
cd <your-build-dir>/build/tmp/hosttools
ln -s /usr/bin/texi2any makeinfo

=== Cleaning up the sstate cache ===

You will notice that after each build, the storage used by the sstate-cache will increase. This is because this cache holds all data required to be able to skip building packages that haven't changed, and previous release data is not purged by bitbake.

To address this, make your git directory the current directory, and run
./openembedded-core/scripts/sstate-cache-management.sh --cache-dir=./build/sstate-cache --stamps-dir=./build/tmp/stamps --yes

Note that if your cache is old, this may take a long time, as on our buildserver (which does build all images!) the result after a second build run is "1385449 out of 1682374 files will be removed!"

=='''Your own feed server'''==
Once you've built your own image, you'd want to keep it up to date. You can just let the box update itself from your build PC using the GUI as if running a full distro.
To do that, you first need to build the optional packages that go into the feed:
cd openpli-oe-core
MACHINE=xxXXXX make feed

Next, you need to install a webserver of some sort on the build PC, for example Apache2.

As an example, if you've installed apache on Ubuntu, it will share /var/www/html/ with the world. Create a feed subdirectory, and then add a symlink to the "ipk" folder of your build, for example:

sudo mkdir /var/www/html/feeds
sudo ln -s ${HOME}/work/openpli-oe-core/build/tmp/deploy/ipk/ /var/www/html/feeds/openpli-homebuild

To tell your box about this feed location, edit your local.conf or site.conf to contain the following lines:

FEED_NAME = "openpli-homebuild"
DISTRO_HOST = "mybuildpc.local"

After this, if you run a new image build, it will make the /etc/opkg/ files on the box point to your feed. After installing the built image on your box, you should be able to upgrade with opkg commands or the enigma2 GUI.

==='''No real webserver handy?'''===

If you don't have a real webserver, like Apache or Nginx, handy, there are some other options available to serve files via http.

Using PHP 5.4+:
cd /var/www/html/feeds
php -S 0.0.0.0:80

Using Python 2.x:
cd /var/www/html/feeds
python -m SimpleHTTPServer 80

Using Python 3.x:
cd /var/www/html/feeds
python3 -m http.server 80

Using Ruby:
cd /var/www/html/feeds
ruby -rwebrick -e'WEBrick::HTTPServer.new(:Port => 80, :DocumentRoot => Dir.pwd).start'

Using Ruby 1.9.2+:
cd /var/www/html/feeds
ruby -run -ehttpd . -p80

Using Perl:
cpan HTTP::Server::Brick # one-time install of perl dependency
cd /var/www/html/feeds
perl -MHTTP::Server::Brick -e '$s=HTTP::Server::Brick->new(port=>80); $s->mount("/"=>{path=>"."}); $s->start'

Using Busybox HTTPd:
cd /var/www/html/feeds
busybox httpd -f -p 80

NB: For ports below 1024, like the standard HTTP port 80 in the example above, you need root or administrator privileges.

=='''OpenPLi - Git commands'''==
Here is the link to some basic [[git-commands | '''git commands''']].

Backup/RecoveryMenuBackup

2019-06-02T08:16:59Z

WTE: Created page with "'''Recovery Menu Backup''' ---- [todo: picture screenshot] Some boxes have an external tool "Recovery Menu" which is used for install, restore and backup a complete image...."

'''Recovery Menu Backup'''
----
[todo: picture screenshot]

Some boxes have an external tool "Recovery Menu" which is used for install, restore and backup a complete image.

'''How to create a backup'''
----
The backup will been stored on an USB flashdrive like an USB harddisk or USB stick, this should been connect before you start.
Goto the recovery menu if your box support it and navigate to the image which you want to backup.
Press on your remote-controller the menu button and select "Backup image". Follow the produce on the TV screen and wait untill the image is ready. You The pogress of backup image size will been shown and this can take up several minutes. Just be patience.

'''How to restore a backup'''
----
In the same recovery menu you can easily restore the made backup image.
#Connect the USB stick with the backup image in one of USB slots of the receiver. Select in the recovery menu "Flash local image" and choose the storage device which contains the backup image.
#Select the backup image zip file and choose to install the image into one of the 4 image slots. The progress will been showing on your TV screen.

Backup

2019-06-02T07:53:34Z

WTE:

[[File:Backup-001.png|200dpi|frameless|right|]]
'''Intro'''
----
When you choose to update or flash OpenPLi, you willingly take the risk that it can be for better or worse.
So, when things don’t turn out for the better, having a backup is essential. If you don’t like the changes that the update has made and want to revert to before these changes were made.

When changes have been made it is always meant to make things better, but there are no guarantees. Keep in mind that the developers have day time jobs and all this is done in their spare time.

Updating isn’t necessary, when things work there is no good reason why you should update. Remember, If it ain’t broke than don’t try to fix it! It is always sane to check the commit logs or read the forum if there is good cause to update or not.

As always, make a '''backup before upgrading or any change you want to make''' and have install media of the version you are coming FROM handy. Then you are never more than a few minutes from being right back were you started when you have those two things in-hand.

Here I will deal with two types of backup that are a must have. These two can make you always go back to the state of OpenPLi when they were created, in say less than 5-10 minutes or so. There are much more details about the two types of backup I mention here, but I want to keep it simple.

First things first, AutoBackup which is native to OpenPLi and second BackupSuite maintained by Pedro_Newbie. There are differences between these two that (can) make them complementary.

'''Difference'''
----
So the main difference between these two is that with AutoBackup you will restore OpenPLi to the exact state you configured it, when you made the AutoBackup. So all settings and some plugins (that are in the OpenPLi feed) will be restored, but none of system files of OpenPLi. The system files will stay the same as to the day you flashed or when you last updatet.

The BackupSuite or RecoveryMenu Backup makes a complete copy of OpenPLi, so all files, including the system files, like drivers (which are closed source). When you restore it, '''all''' files will be in the same state and version as when you made the Backup, that's why this backup will be a lot bigger that the one made by AutoBackup.

'''Complementary'''
----

So using these two backups, AutoBackup and BackupSuite, you are fairly safe, well as safe and stable as at the time you created them. These two methods are complementary. AutoBackup when you’ll need to flash and don’t want to set all the settings manually and BackupSuite when you want to restore to the "exact" state of OpenPLi, (including the system files).

'''Advice'''
----
Set AutoBackup to run every day at a certain time and use it when you want to flash. Use the BackupSuite to make a backup when your OpenPLi is in a stable configuration, so when you try things, you can always return to this state.

* [[Backup/AutoBackup | AutoBackup]]
* [[Backup/BackupSuite | BackupSuite]]
* [[Backup/RecoveryMenuBackup | RecoveryMenu Backup (only available on some models)]]

Main Page

2019-06-02T07:49:57Z

WTE: /* • Backup */

<div style='text-align: right;color:steelblue;font-size:125%'>'''{{CURRENTDAYNAME}}, {{CURRENTMONTHNAME}} {{CURRENTDAY}} {{CURRENTYEAR}}''' </div>
----
{{CURRENTUSER}}, Welcome to the Open'''PLi''' Wiki 


[[File:MAIN-OpenPli-004.jpg|frameless|Centre|750px]]

{| class="wikitable"
!colspan="6";| Current version: 7.0
|}

[[Releasenotes | '''• Releasenotes''']]
----

=='''OpenPLi - Installation and configuration:'''==

===[[Supported_Receivers | '''• Supported receivers''']]===
Overview of all supported receivers and how to flash a your receiver. Also there is a comparison table were many receivers are listed and are compared right down to component level, so you can make an easier choice if you want to buy one. Also there is a special table that gives the power consumption of many receivers.

===[[Installation | ''' • OpenPLi installation''']]===
Here will be explained how to install OpenPLi on your receiver, various methods are explained and below are the various links that you might need. The link to the what, how and why to backup is recommended.

===[[Installation | ''' • OpenPLi configuration''']]===
Below is explained how you can configure OpenPLi

====[[Backup | '''• Backup''']]====
Before you update, upgrade or change anything it is good to have a backup. Here the plugins "Autobackup" (by default installed), the "BackupSuite" (has to be installed) and some models which have an internal backup function are explained.

====[[Cable | '''• Cable settings information''']]====
Looking for network ID's, symbolrates and frequency's to scan your cable channels..? Here you can find the information of our cable provider.

====[[Channel_Settings | '''• Channel settings for satellite receivers''']]====
Channel settings file for various satellites.

====[[Data_sharing | '''• Data sharing''']]====
If you want to share your data like a NAS, OpenPLi receiver, PC (desktop, notebook) or any other medium using NFS, CIFS (SMB/Samba), this is were to look.

====[[External_Device_support | '''• External device support''']]====
Here you will find a list of known external devices that are known to work with OpenPLi.

====[[Softcam | '''• Softcam Wiki''']]====
When you want to look at encrypted channels and not only Free to Air (FTA) you can use a softcam. In this section is explained how to install and use a few.

===[[Tips_and_Tweaks | '''• Tips and Tweaks''']]===
Many useful tips on various stuff on working with OpenPLi, Putty, SSD useful or not, debugging, how to crashlog, etc. etc.

===[[Problems and Solutions | '''• Problems and Solutions''']]===
This section deals with all kind of problems and possible solutions. If you run into a problem using OpenPLi you can take a peak here to find a solution.

=='''OpenPLi - Functions and default plugins'''==

===[[Hidden_functions | '''• Hidden functions''']]===
Some functions are not easy to find, but can be very helpful, here there are a few.

===[[HDMI-CEC | '''• HDMI-CEC''']]===
This feature can make your devices work better together, so like using one remote to control TV and receiver. Note it is turned off by default

===[[Hotkey | '''• Hotkey''']]===
With this function Hotkeys can be (un)selected to make things easier.

===[[MountManager | '''• MountManager''']]===
Here the mountmanager is explained. It is used to mount (make) accessible external drives, like with a NAS or (the harddisk of) other receivers. Mounting means associating a storage device to a particular location in the directory tree.

===[[Plugin_Wiki | '''• Plugin browser''']]===
If want to extend the functions of OpenPLi you can install plugins from the feed (=the ''technical'' name where the plugins are stored) . Remember these plugins are not maintained by OpenPLi, so always backup before installing.
====[[Plugins | '''• Plugins''']]====
In the OpenPLi feed are many plugins. Here is explained, like what these plugins can do and how some of these plugins work, Refresh Bouqet, Autotimer, etc.

===[[Fallback_remote_receiver | '''• Fallback remote receiver''']]===
This function gives you the option to use the tuners from another OpenPLi receiver, when they are wired or wireless (WiFi) connected. This way you can watch TV when there is no access to satellite or cable or expand your tuners.

===[[Webif | '''• Webif''']]===
Information about the Webif (webinterface) and how to access and configure it.

=='''OpenPLi - Information for advanced users'''==
===[[Knowledge_base | '''• Knowledge base''']]===
Many useful information on various subjects, to name but a few; GStreamer, HbbTV, Overscan, Satfinders, TV-headend, Unicable and VPN

=='''OpenPLi - Information for developers'''==
===[[Information_for_Developers | '''• Information for developers''']]===
Info for developers and some basic Git commands.

===[[Create_Bootlogo | '''• How to create a bootlogo''' ]]===

=='''OpenPLi - Information for translators'''==
===[[Information_for_translators | '''• Information for translators''']]===
OpenPLi is always looking for help to have it translated properly in many languages. Here there is information, FAQ etc. to help you along the way.

=='''OpenPLi - Faits divers'''==
===[[History | '''• History''']]===
===[[Up-Download_magazine | '''• UP-Download magazine '''(Dutch language)]]===

[[Moderator_Page | π ]]

Cable:TriNed

2019-06-01T23:35:15Z

WTE:

Frequentie: 304.000 
Symbolrate: 6875 
Modulatie: QAM256 
Network ID: 01000 Without smartcard 
Network ID: 02000 With smartcard 
 
bron: https://www.trined.nl/klantenservice/instellingen/

Cable

2019-06-01T23:32:44Z

WTE:

Looking for network ID's, Symbolrates and frequency's to scan your cable channels..? Here you can find the information of our cable provider. 
 
'''The Netherlands'''
----
{|
|-
| * [[Cable:Caiway | Caiway]] || Dutch information
|-
| * [[Cable:Detla | Delta]] || Dutch information
|-
| * [[Cable:Glashartmedia | Glashartmedia]] || Dutch information
|-
| * [[Cable:SKV_Veendam | SKV Veendam]] || Dutch information
|-
| * [[Cable:TriNed | TriNed]] || Dutch information
|-
| * [[Cable:Ziggo | Ziggo]]
|}

'''Belgium'''
----
{|
|-
| * [[Cable:Telenet | Telenet]]
|-
| * [[Cable:Numéricable | Numéricable]]
|-
| * [[Cable:Voo | Voo]]
|}

'''United Kingdom'''
----
{|
|-
| * [[Cable:Virgin_Cable | Virgin Cable]]
|-
|}

'''Germany'''
----
{|
|-
| * [[Cable:Unitymedia | Unitymedia ]]
|-
|}

Cable:TriNed

2019-06-01T23:30:45Z

WTE: Created page with "Frequentie: 304.000 Symbolrate: 6875 Modulatie: QAM256 Network ID: 01000 Without smartcard Network ID: 02000 With smartcard"

Frequentie: 304.000
Symbolrate: 6875
Modulatie: QAM256
Network ID: 01000 Without smartcard
Network ID: 02000 With smartcard

Releasenotes-7.1

2019-05-18T16:34:16Z

WTE: /* Multiboot procedure (HD60, H9combo and Multibox): */

==New: ==
* NFS server is now part of the image by default, with /media/hdd exported to any client.
* Multiboot for Mutant HD60, Maxytec Multibox and Zgemma H9combo. Below the procedure you have to follow to make use of it.
* Main menu -> Information -> About: here the skin and resolution used and the debug level is now mentioned.

==Improvement since previous version: ==
* Added UHD testscreen.
* Add a SystemInfo entry for Enigma Debugmode.
* Fallback tuner: added the option ''Customize OpenWebIF settings for fallbacktuner''. This is required for the fallback timer feature when retrieving the settings, EPG and streams are 'secured' from an import that has a password.
* HotKey: Put GMEPG by default on yellow long.
* Hotkey: Help text added, "Press or select button and then press 'OK' for attach function" when no function is attached to the key selected.
* Hotkey: Help text added, "Press or select button and then press 'OK' for attach function or edit attached", when a function is already attached.
* Virtualkeyboard update.

==Support for: ==
* ET7000/75000 use generic et7x00 images
* Edision Os mio 4K: support multiboot and online flashing
* Maxytec Multibox
* Qviart Lunix 4K
* Realtek - add kernel 5.0 support for:
**rt8723bs
**8812au
**8814au
**8822bu
* Zgemma H9 Combo
* Zgemma H9 Twin

== Other improvements: ==
* Many driver (bsp) updates, like for the * Vu+ Duo 4K Multistream support
* Many translation improvements

==Items moved:==
* Moved lcd4linux from image to feed, lcd's are supported natively by Enigma

==Multiboot procedure (HD60, H9combo and Multibox withBootmenu r245 or higher):==
#Basically you just have to flash a recovery image (recovery_emmc.zip file) once.
#This will be done in the regular way so unpack the image, unpack it on an USBstick and flash it in an USB2.0 slot (white usb slot is USB2.0 and blue usb slot is USB3.0) like you were used to do as before. This works for all similar models that support this new Multiboot procedure.
#After the recovery image is flashed it will start one-time direct to the Multibootmenu. Which you can install the actually image online or manual by USB.
#Now that you have entered the Recovery/Multibootmenu, if available, you can choose an image that you wish to boot.
#If no images are available or you want to install a new image, select the bootmenu and choose if you want to install/flash an image online or manual by an USB stick.

How to flash an image from the recovery/bootmenu?
#To flash an image online: Select in the Bootmenu "Flash online image" (the box should been connect to the internet).
#Select one of the online image and choose to install the image into one of the 4 image slots. The progress will been showing on your TV screen.
#To flash an image by USB: Download an *emmc.zip and put it on a USB stick/disk. Beware that you should not unpack this zip!
#Connect the USB stick in one of USB slots of the receiver. Select in the Bootmenu "Flash local image" and choose the storage device which contains the image.
#Select an image zip file and choose to install the image into one of the 4 image slots. The progress will been showing on your TV screen.

How to make a backup image from the recovery/bootmenu?
#Navigate in the head-menu to the image which you want to backup.
#Press on your remote controller the menu button and select "Backup image".
#Select the storage area and wait till the backup is ready. (The backup image can been restored with "Flash local image" in the bootmenu)

How to delete an image from the recovery/bootmenu?
#Navigate in the head-menu to the image which you want to delete.
#Press on your remote controller the menu button and select "Delete image"
#Confirm with yes to delete the image

==='''Howto go back to the Recovery/Multibootmenu''' ===
Every box has some extra options to enter back to recovery/ multibootmenu.
#Solution1: Press and hold the ’Ok’ button on your remote before or direct after the box is power up from powerswitch, deepsleep, or restart Enigma2, If the box has a display wait until '''rcvy''' appears in the display or else hold it untill Multibootmenu or logo appears on your TV screen.
#Solution2: "Not yet available in Enigma2 select in Multiboot Recovery" (Advanced users can copy the STARTUP_RECOVERY to STARTUP in the partition Bootoptions)
#Solution3 only for Mut@nt HD60: Hold down the power button on the frontpanel of the receiver when power up the receiver, untill Multibootmenu or a logo appears on your TV screen.
#Solution3 only for Maxytec Multibox: Hold down the "reset" on the left side of the reciever when you power up the receiver, untill Multibootmenu or a logo appears on your TV screen.

Note 1: It's possible to add multiply images using online flash in your multiboot environment. This does not affect any other image. 
Note 2: Advance users: It's possible to add beside the 4 preprogrammed slots extra images by manually install images in the userdata partition and make a STARTUP_* line in the bootoptions partition.’ ;)

[[File:Multiboot-001.jpeg|left|480px]][[File:Multiboot-002.jpeg|centre|480px]]

Releasenotes-7.1

2019-05-16T12:12:44Z

WTE: /* Mutliboot procedure (HD60, H9combo and Multibox): */

==New: ==
* NFS server is now part of the image by default, with /media/hdd exported to any client.
* Multiboot for Mutant HD60, Maxytec Multibox and Zgemma H9combo. Below the procedure you have to follow to make use of it.
* Main menu -> Information -> About: here the skin and resolution used and the debug level is now mentioned.

==Improvement since previous version: ==
* Added UHD testscreen.
* Add a SystemInfo entry for Enigma Debugmode.
* Fallback tuner: added the option ''Customize OpenWebIF settings for fallbacktuner''. This is required for the fallback timer feature when retrieving the settings, EPG and streams are 'secured' from an import that has a password.
* HotKey: Put GMEPG by default on yellow long.
* Hotkey: Help text added, "Press or select button and then press 'OK' for attach function" when no function is attached to the key selected.
* Hotkey: Help text added, "Press or select button and then press 'OK' for attach function or edit attached", when a function is already attached.
* Virtualkeyboard update.

==Support for: ==
* ET7000/75000 use generic et7x00 images
* Edision Os mio 4K: support multiboot and online flashing
* Maxytec Multibox
* Qviart Lunix 4K
* Realtek - add kernel 5.0 support for:
**rt8723bs
**8812au
**8814au
**8822bu
* Zgemma H9 Combo
* Zgemma H9 Twin

== Other improvements: ==
* Many driver (bsp) updates, like for the * Vu+ Duo 4K Multistream support
* Many translation improvements

==Items moved:==
* Moved lcd4linux from image to feed, lcd's are supported natively by Enigma

==Multiboot procedure (HD60, H9combo and Multibox):==
#Basically you just have to flash a recovery image (recovery_emmc.zip file) once.
#This will be done in the regular way so unpack the image, unpack it on an USBstick and flash it in an USB2.0 slot (white usb slot is USB2.0 and blue usb slot is USB3.0) like you were used to do as before. This works for all similar models that support this new Multiboot procedure.
#After the recovery image is flashed it will start one-time direct to the Multibootmenu. Which you can install the actually image online or manual by USB.
#Now that you have entered the Recovery/Multibootmenu, if available, you can choose an image that you wish to boot.
#If no images are available or you want to install a new image, select the bootmenu and choose if you want to install/flash an image online or manual by an USB stick.

How to flash an image from the bootmenu?
#To flash an image online it speaks for itself.
#To flash an image with an USBstick download an *emmc.zip and put it on a stick. Beware that you should not unpack this zip!
#After placed the stick in the box you can choose the zip file and the image will been installed. The progress will been showing on your TV screen.

==='''Howto go back to the Recovery/Multibootmenu''' ===
Every box has some extra options to enter back to recovery/ multibootmenu.
#Solution1: Press and hold the ’Ok’ button on your remote before or direct after the box is power up from powerswitch, deepsleep, or restart Enigma2, If the box has a display wait until '''rcvy''' appears in the display or else hold it untill Multibootmenu or logo appears on your TV screen.
#Solution2: "Not yet available in Enigma2 select in Multiboot Recovery" (Advanced users can copy the STARTUP_RECOVERY to STARTUP in the partition Bootoptions)
#Solution3 only for Mut@nt HD60: Hold down power button on the frontpanel of the receiver when power up the receiver, untill Multibootmenu or logo appears on your TV screen.
#Solution3 only for Maxytec Multibox: Hold down "reset" on the left side of the reciever when you power up the receiver, untill Multibootmenu or logo appears on your TV screen.

Note 1: It's possible to add multiply images using online flash in your multiboot environment. This does not affect any other image. 
Note 2: Advance users: It's possible to add beside the 4 preprogrammed slots extra images by manually install images in the userdata partition and make a STARTUP_* line in the bootoptions partition.’ ;)

[[File:Multiboot-001.jpeg|left|480px]][[File:Multiboot-002.jpeg|centre|480px]]

Offline decoding

2017-07-02T13:03:33Z

WTE:

We are looking for people owning a CI module, and people using a softcam with a local smartcard (should be everyone!) to test the offline decoding capability of all OpenPLi supported hardware. 

To test, do the following:
# Stop the softcam, and remove all CI modules from the box
# Make a short test recording from an encoded channel that uses a smartcard, using a timer, with Recording type "don't descramble, record ECM"
# When done, do the same, but then from an encoded channel that uses the CI module
# In case you have a smartcard that works in both a CI and with a softcam, one recording is enough.

Now play back the recording(s), to make sure your screen stays black. 

# Start your softcam again, make sure the smartcard is operational, and play the first recording back again.
# If you now have an image, your box supports offline decoding via the softcam.
# Stop the softcam again, insert the CI module with the smartcard, and play back the second recording.
# If you now have an image, your box supports offline decoding via de CI.

Source: https://forums.openpli.org/topic/51311-help-needed-offline-decoding/#entry720296

{| class="wikitable"
|-
! Receiver !! !! Softcam !! CI !! Extended CW API
|-
| Dreambox || 500 HD || unknown || unknown || yes
|-
| || 7020 HD || unknown || unknown || yes
|-
| || 800 SE || yes || unknown || yes
|-
| || 8000 || yes || no || yes
|-
| Edision || Os Mega|| yes || unknown || yes
|-
| || OS Mini || no || unknown || yes
|-
| || OS Mini + || || || yes
|-
| Formuler || F1 || yes || no
|-
| || F3 || yes|| no
|-
| || F4 || yes|| no
|-
| || F4 Turbo || yes|| no
|-
| GI || ET 7000-Mini || no|| no
|-
| || ET-11000 || no|| no
|-
| Golden Interstar || Speed LX class S2/C || unknown || unknown
|-
| Maxdigital || XP 1000 || yes || unknown
|-
| Miraclebox || Premium micro || no || unknown
|-
| || Premium twin+ || no || no
|-
| || Premium Micro v2 || no || no
|-
|Mutant || hd11 || yes|| N/A
|-
| || hd51|| yes|| yes || yes
|-
| || hd500c || yes|| N/A
|-
| || hd530c || yes|| N/A
|-
| || hd1100 || yes|| N/A
|-
| || hd1200 || yes|| N/A
|-
| || hd1265 || yes|| N/A
|-
| || hd1500 || yes|| unknown
|-
| || hd2400 || yes|| yes
|-
| SAB || Alpha Triple HD || yes|| no
|-
| Spycat || Spycat
|-
| || Spycat Mini || unknown || unknown
|-
| || Spycat Mini Plus || unknown || unknown
|-
| Vimastec || VS 1000 || yes|| N/A
|-
| || VS 1500|| yes || yes || yes
|-
|VU+ || Duo || no || no
|-
| || Duo 2 || no || no
|-
| || Solo || no || no
|-
| || Solo 2 || no || no
|-
| || Solo SE || no || no
|-
| || Solo 4K || no || no
|-
| || Ultimo || no || no
|-
| || Ultimo 4K || no || no
|-
| || Uno || no || no
|-
| || Uno 4K || no || no
|-
| || Zero || no || no
|-
| || Zero 4K || no || no
|-
| Xsarius || Fusion HD SE || yes || unknown
|-
| || Fusionhd || yes|| unknown
|-
| || Pure HD || yes|| unknown
|-
| || Revo 4K || yes|| unknown
|-
| || Galaxy 4K || yes|| unknown
|-
| Wetek || Play || no || N/A
|-
| Xtrend || et4x00 || yes|| N/A
|-
| || et5x00 || yes|| N/A
|-
| || et6x00 || yes|| unknown
|-
| || et7x00 || no || unknown
|-
| || et8000 || yes|| no
|-
| || et8500 || no || unknown
|-
| || et9x00 || yes|| no
|-
| || et9500 || yes || no
|-
| || et10000 || yes|| no
|-
| Zgemma || Star H1 || yes || unknown
|-
| || Star H2 || yes|| N/A
|-
| || Star H.2S || yes|| N/A
|-
| || Star H3 || yes|| N/A
|-
| || Star H3.AC || yes|| N/A
|-
| || Star H4 || yes|| N/A
|-
| || Star H5 || yes|| N/A
|-
| || Star H5 2S || yes|| N/A
|-
| || Star H5.AC || yes|| N/A
|-
| || Star H5 2TC || yes|| N/A
|-
| || Star H7 || yes|| yes
|-
| || Star H.S || yes|| N/A
|-
| || i55 || yes|| N/A
|-
| || LC || yes|| N/A
|-
| || Star S || yes|| N/A
|-
| || Star 2S || yes|| N/A
|-
|}