Display MoreThe recommended way of installing the OpenATV secret feed is typing this one line on a shell session on the box:
The easiest method of getting a shell session to the box is the "Terminal" in OpenWebif, but feel free to use puTTy or whatever you already use.
That one-liner makes sure you get the latest version of the feed for your actual image version and architecture.
No need to download the IPK, copy it to the box and installing it through GUI or shell when using the one-liner but you are still free to use an IPK, if you insist on it.
Use version 4.3r2 or later in that case.
The new feed supports OpenATV 5.3 through 6.3, that is "the last 5 versions of OpenATV".
In OpenATV 5.3 to 6.1 you will only have one place to configure the CAMs, that is in "Menu -> Settings -> Decryption", because it would probably cause more problems to patch it into old versions of E2, while that hook in "Menu -> Settings -> Decryption" is just a plugin.
Starting as of OpenATV 6.2 (Images 2019-06-15 and later), the softcams can be configured in three places:
- "Menu -> Info Panel", just as before with softcam panel
- "Quick Menu" (In most cases on blue key or long blue key), just as before with softcam panel
- "Menu -> Settings -> Decryption and parental protection", as it is the most logical place to search at if you aren't already used to the other places
The softcam panel was entirely removed due to user problems, e.g. one team member losing his line due to double logins (He had two oscams running in parallel, one through the new method, one through the old one), so to avoid problems, having both methods inside the image appeared a bigger problem than making a cut here.
Installing the feed through older IPKs, like versions 2.0 or 3.0, will only get you an empty secret feed, except for one package: The new secret feed :)
The new feed has multiple advantages:
- All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.
oscams on the feed for OpenATV 6.3 are built inside the OpenATV 6.3 build environment, oscams on the feed for OpenATV 6.2 are built inside the OpenATV 6.2 build environment, oscams on the feed for OpenATV 6.1 are built inside the OpenATV 6.1 build environment and so on.
Most CAMs you can download from forums are simply built in generic cross-compiler environments that do usually not really contain the matching libs ...
- All OScams and Ncam are built every night if their sources get updated.
If you install oscam-trunk, you will always get the latest one with a maximum delay of 24h.
For conservative users that do not want to live on the edge, there is oscam-stable, which will give you oscam svn11518 until there is some really important change in trunk and that change has proved being stable (By not being changed again within the next weeks).
- Starting CAMs through init.d is more robust and stable than forking them as childs of E2 (That's why there isn't a "watchdog" anymore, it's simply not needed)
- CAMs started through init.d are easier to maintain remotely
You can simply start/stop/restart them from the shell
Coderoot@quad4k ~ # /etc/init.d/softcam stop Stopping Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam start Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam restart Stopping Softcam service oscam-smod: OK Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam status Softcam service oscam-smod: Running.
e.g. after editing config files.
No need to mess around with "kill", "killall" commands or figuring out if you need to background the cam manually or if it will background automatically if you start it directly via shell.
- CAMs started through init.d are ready when you are ...
As the CAM starts early during boot, it has time enough to initialize card readers or server connections to decrypt instantly as soon as E2 can tune.
Python CAM start added a delay, because starting the CAM didn't happen any earlier than tuning the startup/previous station
Display MoreThe recommended way of installing the OpenATV secret feed is typing this one line on a shell session on the box:
The easiest method of getting a shell session to the box is the "Terminal" in OpenWebif, but feel free to use puTTy or whatever you already use.
That one-liner makes sure you get the latest version of the feed for your actual image version and architecture.
No need to download the IPK, copy it to the box and installing it through GUI or shell when using the one-liner but you are still free to use an IPK, if you insist on it.
Use version 4.3r2 or later in that case.
The new feed supports OpenATV 5.3 through 6.3, that is "the last 5 versions of OpenATV".
In OpenATV 5.3 to 6.1 you will only have one place to configure the CAMs, that is in "Menu -> Settings -> Decryption", because it would probably cause more problems to patch it into old versions of E2, while that hook in "Menu -> Settings -> Decryption" is just a plugin.
Starting as of OpenATV 6.2 (Images 2019-06-15 and later), the softcams can be configured in three places:
- "Menu -> Info Panel", just as before with softcam panel
- "Quick Menu" (In most cases on blue key or long blue key), just as before with softcam panel
- "Menu -> Settings -> Decryption and parental protection", as it is the most logical place to search at if you aren't already used to the other places
The softcam panel was entirely removed due to user problems, e.g. one team member losing his line due to double logins (He had two oscams running in parallel, one through the new method, one through the old one), so to avoid problems, having both methods inside the image appeared a bigger problem than making a cut here.
Installing the feed through older IPKs, like versions 2.0 or 3.0, will only get you an empty secret feed, except for one package: The new secret feed :)
The new feed has multiple advantages:
- All CAMs that can be built from source code (All OScams and Ncam) are built from source code using the matching OpenATV build environment, that means they perfectly fit the libraries inside the actual image.
oscams on the feed for OpenATV 6.3 are built inside the OpenATV 6.3 build environment, oscams on the feed for OpenATV 6.2 are built inside the OpenATV 6.2 build environment, oscams on the feed for OpenATV 6.1 are built inside the OpenATV 6.1 build environment and so on.
Most CAMs you can download from forums are simply built in generic cross-compiler environments that do usually not really contain the matching libs ...
- All OScams and Ncam are built every night if their sources get updated.
If you install oscam-trunk, you will always get the latest one with a maximum delay of 24h.
For conservative users that do not want to live on the edge, there is oscam-stable, which will give you oscam svn11518 until there is some really important change in trunk and that change has proved being stable (By not being changed again within the next weeks).
- Starting CAMs through init.d is more robust and stable than forking them as childs of E2 (That's why there isn't a "watchdog" anymore, it's simply not needed)
- CAMs started through init.d are easier to maintain remotely
You can simply start/stop/restart them from the shell
Coderoot@quad4k ~ # /etc/init.d/softcam stop Stopping Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam start Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam restart Stopping Softcam service oscam-smod: OK Starting Softcam service oscam-smod: OK root@quad4k ~ # /etc/init.d/softcam status Softcam service oscam-smod: Running.
e.g. after editing config files.
No need to mess around with "kill", "killall" commands or figuring out if you need to background the cam manually or if it will background automatically if you start it directly via shell.
- CAMs started through init.d are ready when you are ...
As the CAM starts early during boot, it has time enough to initialize card readers or server connections to decrypt instantly as soon as E2 can tune.
Python CAM start added a delay, because starting the CAM didn't happen any earlier than tuning the startup/previous station
I'm using openatv 6.3 image on 14.06, but if update so the softcam be unavailable, Can get the softcam back if I use your Code?
DM800 se v.2
openAtv 6.3
Oscam 11523