What you all mention, this .MVI file, is already the Enigma2 recording screen, not the splash logo of the device manufacturer, which is displayed immediately when the set-top box is turned on for a short time.
You have the flashing logo of the device from the Vu+ manufacturer in the attachment... unzip it normally to a USB key and flash the Vu+ Duo2 set-top box. This is the original device logo from the manufacturer of the Vu+ device.
Hi.
You can also change 1.) the "splash.bin" boot-logo of the device and also 2.) the Enigma2 boot-logo.
The first is done by flashing. Unfortunately, the OpenATV image contains their own splash logo for the device, which it overwrites with its OpenATV logo... unfortunately. If you want to change it, you have to flash the device again, but without all the files. You only leave this splash-logo there. The file name of this splash-logo can be different in each set-top box (it differs according to the manufacturer and sometimes also according to the specific type of device from this manufacturer). Find the splash boot logo for the manufacturer of your device online. Then create a USB key for flashing again. Upload everything as before, but delete the redundant files - and... leave the USB keys in the appropriate folder, just splash.....bin file. Perform flashing and you will have back the flood boot logo from the device manufacturer.
The second type of boot logo is already in Enigma2, in its directory structure, as a short "video". It is a special .MVI file format. This can also be changed / modified, but the procedure is more complicated. You can find the procedure on the internet.
//// EDIT :
Some original enigma2 firmware supplied by device manufacturers also contain this file. For example, Vu+ firmware contains its own attached file, for each device, called as "splash_auto.bin" or "splash_cfe_auto.bin" or something else - whose name also depends on the specific type of manufacturer's device !
H.
If Softcam is not visible in Enigma2-GUI, it does not mean that it is not installed. It can be installed. But you used an older IPK-package or one that does not support a specific Enigma2 distribution. The new OpenATV and OpenPLi have the softcam support built-in... so that it contains the file name, as well as the file extension. According to the type of extension, the Enigma2-GUI then identifies, shows, and enables the Softcam to be managed (via the Enigma2 GUI - in MENU). They should be file names such as:
/etc/init.d/softcam.osccam
/etc/init.d/softcam.cccam
/etc/init.d/softcam.ncam
There is a sym-link also created:
/etc/init.d/softcam
...and it points to the currently set and used by the user, one single softcam, out of these several.
Softcam can be updated easily if you get its binary file - according to the type of chipset in your set-top box. Then stop Softcam in Enigma2. Then copy the binary file manually via FTP. And finally, start Softcam again. But even this requires minor IT knowledge.
If you want to keep the updates on feed sources, you have to add another feed source. If you use OpenATV, there is an unofficial feed for it, which you have to install in OpenATV (you can also find it here on the discussion forum).
If you use OpenPLi, they already have a built-in feed with softcams. Hardly, it updates every time you let Enigma2 update. Alternatively, you can update the OpenPLi softcam manually, using the opkg manager, via a Telnet/SSH connection.
/////////// EDIT : (according to your post update)
The symbolic link will not work in this case, because if it refers to a removable USB key, then at the moment of booting Linux, when the USB key is not yet mounted in the system, the non-existent sym-link will be deleted. If I'm not mistaken.
Of course, you can have Oscam configuration files anywhere. But at the moment of starting Oscam, during the boot of the set-top box, the USB must already be mounted in Linux... and I don't know for sure if that will happen. I suppose so. So in theory it should work.
The safest thing is to edit the start link in the shell script in the /etc/init.d folder. Find the appropriate shell script and edit it. Find the executable binary oscam file. Add there an argument for entering a specific configuration path.
-c, --config-dir <dir> | Read configuration files from <dir>
More info: https://wiki.streamboard.tv/wiki/OSCam/en/ShellCommands
For example:
/usr/bin/oscam -c /media/usb/config
Searching of configuration folders after starting Oscam is also built-in. But your choice is not among these folders: Does the location of Oscam's config files depend on the image/hardware being used? -being-use/?postID=618671#post618671
Hi julius52 .
There is no "put" way :-).
First of all, it is unfortunately only intended for IT professionals.
EDIT: OK, you don't have to be a professional, but you have to have really good IT knowledge.
Secondly, everything is inside the shell script ;-).
Minor update...
pola188 Especially for you too: Please read a few posts above (toward the back) 
- post number #445. Wait approx. 1-2 days until the minor problem is resolved.
/// EDIT :
So it's working again (4/9/2024, 18:30). Thanks to chocholousek for the painstaking work of rewriting new paths to folders on the server :).
5.0.240904
BUG fix:
----
File "/usr/lib/enigma2/python/Components/ScrollLabel.py", line 58, in setText
TypeError: in method 'eLabel_setText', argument 2 of type 'std::string const &'
----
- this was a string conversion issue between C++ and Python, in Enigma2 - Gemini Project 4.2
- thx to Warder for the BUG report and for testing the BUG fix in Gemini
Azzurra look at the posts towards the back.
5.0.240903
Minor improvement:
- in case of a problem receiving an HTML file instead of a 7zip file, the found HTML title from the file will be displayed
- fixed wrong resolution, in case of alternate image "image_not_found.png"
Note: download + online installation procedure can be found on the first page of this discussion thread.
You didn't do it right. I see that you have an folder "picon_50x30" and also a symbolic link with the same name "picon_50x30", under the path "/usr/share/enigma2".
As I wrote before. Start by deleting all the folders you have created so far for picons + and their contents (or back them up on your PC first). Also delete the symlinks, but they should delete themselves if you remove the physical folders.
And then continue to do what I wrote - in post #439 - RE: Chocholousek Picons updater (Enigma2 plugin) .
First, create the directory "/picon" and copy there all picons with a resolution of 220x132 there.
Then create symbolic links, also as I wrote.
And restart the set-top box.
Then check again what the contents of the "/usr/share/enigma2" folder looks like. BTW, there is also a shell command for this, which also displays symbolic links:
ls -al /usr/share/enigma2
----------------
If it doesn't work, the second way is to delete the symbolic links you created (in folder "/usr/share/enigma2"). Probably SKIN requires two separate folders, each with a different picon resolution. So... you create two new separated folders (not symbolic links):
/usr/share/enigma2/picon_50x30
/usr/share/enigma2/picon_220x132
In the configuration of the Chocholousek-Picons plugin, you will use two configuration profiles. In one, set the picon resolution to 50x30 and the update path to the "/usr/share/enigma2/picon_50x30" folder. In the second profile, set the picon resolution to 220x132 and the update path to the "/usr/share/enigma2/picon_220x132" folder. I hope at least this second way will work :).
Whichever path you choose maho33, I would also like to mention that up to 3 configuration profiles can be used in the Chocholousek Picons plugin. This means that it is necessary to use 50x30 picons and 220x132 at the same time, so you can set it up.
For example, in configuration profile 1, picons with one resolution are downloaded to the first folder, and then, another picons will downloaded to another folder - through configuration profile 2.
But I think it's better to create symbolic links, as PakTo mentioned. If SKIN can automatically transform the resolution of picons, it is better if you have only one common directory for picons.
I personally would delete the other picons. And I would use one "/picon" folder right in the root. And then I would direct symbolic links into it:
mkdir -p /picon
ln -s /picon /usr/share/enigma2/picon
ln -s /picon /usr/share/enigma2/picon_220x132
ln -s /picon /usr/share/enigma2/picon_50x30OK, then you have to write to the creators of this SKIN to fix the error.
Or... turn on debug mode in your Enigma2 distribution (Merlin 2.5) if possible... and then send the generated debug log file... where it should be displayed error when trying to open a picon via the InfoBar algorithm.
What exactly SKIN are you using ? Is there any Github or open code on the internet for this SKIN? I would look to see if I can find something there.
However, it would be best if you provided a debug log file from your Enigma2 distribution, after triggering the bug (opening the InfoBar - without the icon displayed).
This needs to be addressed with the team that developed the SKIN... or with the creators of Merlin 2.5 of the Enigma2 distribution. They have a bad algorithm there, for using or searching for picons.
I think one directory is enough for SKIN. All modern SKINs these days should be able to automatically adjust the size of the icons. That is that they must appear correctly in the channel list and also in the InfoBar.
Or the alternative solution is, as I wrote, to create a symbolic link (make a virtual directory), where SKIN will then find the necessary picons.
If it is the case that SKIN already uses one directory for InfoBar picons + channel list, then it is enough to use only this single directory and direct the picons there (in the configuration of the ChocholousekPicons plugin, browse the path to this SKIN-directory).
Try reboot of the set-top tox OR try quick restart of the Enigma2 / GUI.
If it doesn't help, you're probably using an alternative (non-original) SKIN that can't find picons in the appropriate folder or uses a bad algorithm for finding picons on the disk in the set-top box. This is usually solved by creating a symbolic link to directory with picons for SKIN as well or by setting a directory path to picons in the SKIN configuration.
So in that case it depends on the type of encoding system of the card.
Some decoding cards in the card reader require receiving some EMM packets for their functionality. Usually this needs to be done on the softcam servers so that they are ready for ECM decoding after the Oscam restart.
I did this for the IRDETO coding system. This is a softcam shell-script for "init.d", which is modified so that after every Oscam-restart, the tuner is activated for a while with some preset satellite channel and then, after a few seconds, the tuner deactivates / turns off again. For this purpose that I describe, you need an "init.d" shell-script named as:
"softcam (+ zap channel each time when softcam was started)"
... and then rename it as you need, according to your current "softcam" script in the folder " init.d".
Of course... don't forget to edit this script of mine so that the name of the binary file fits... or any other details in the script.
If you just want to restart Oscam, just add a simple line to the CRON scheduler and you don't need any modified softcam script (for example):
# restart the Oscam , every night, at 04:30
30 04 * * * /bin/bash /etc/init.d/softcam restartHowever, keep in mind, as I mentioned the exemplary IRDETO coding, which I know a little, that there is a need to always accept EMM packets after the Oscam restart - so that the IRDETO card starts working.
------------------------------------
If you're looking for what was said in the original question, you're probably looking for this:
# refresh entitlements via Oscam Webif, every 9 days, at 06:00
00 06 */9 * * /usr/bin/wget -q -O - "http://USER_LOGIN:USER_PASSWORD@127.0.0.1:8888/readers.html?action=reread&label=OSCAM_READER_NAME" > /dev/null 2> &1(a note: by this method, entitlements are only refreshed inside the Oscam... not written to the card... the EMM packets must take care of writing entitlementmenets to card)
Why wouldn't it work ? Try it and you'll see :-).
But that's a bit more complicated. A "shell script" is not enough, so to speak. You have to be able to run it, apply it, leave it running in the resident background of a Linux system... or something similar. It is not enough to have a shell-script alone.
Or write what you want to achieve exactly.
Hi.
Which one exactly do you mean ?
I have stopped using and therefore updating many shell-scripts, so it is not verified whether they work.
If you want, I can verify the functionality of any shell script. Alternatively, write to me on Skype or private message.
OK... thanks.
In any case, the plugin itself will take care of the installation. I would need to see a debug (in the dreambox enigmas "journal") why this 7z cannot be installed or downloaded from the internet.
Oh... I see now, this is the name of Enigma2. However, I don't know this "GP4.2 Nobody Image" at all. So I probably won't advise you. I couldn't find anywhere how to start debugging on it, or what Enigma2 core it's based on... or where it actually comes from. I also found some German discussion forum and download these Enigma2 images. But I didn't find anything else. No support forum for reporting bugs. On most Enigma2's that are used on Dreambox devices, installing 7z works. Moreover, I am not familiar with those "Dreambox" firmwares. I only know old Enigma2 cores. But it's a mystery why it doesn't work. On other "Dreambox" firmwares, installing 7z works OK.
The debug file could show where the error occurs :-/.
For example, try to connect via terminal / linux shell to the set-top box. Then try to examine the journal:
journalctl -f -u enigma2 >> /tmp/journal.log - the entire system log will be displayed, with a filter for "enigma2" processes, and this will be redirected or it will be added to our file "/tmp/journal.log"
journalctl --since "1 hour ago" - display syst. log from the current time, 1 hour backwards (probably doesn't work under Enigma, but only in full-fledged Linux)
But I can't say whether a journal is used there. I am not at all familiar with this offshoot of the Enigma2 firmware and I don't even know what it came from.
Hi. You still haven't written which Enigma2 you use exactly, it's done a little differently everywhere. :)
