Once again, the issue is nothing to do with Enigma2, it is the machine bootlogo which is loaded at startup. Some distros ( mainly ATV) change them instead of leaving them alone. Most other images add their distro logo to show after Enigma2 starts its booting process.
Solution for Vu+ splash logos is here:
Problems and Solutions - OpenPLi Wiki
Link to the vu splash screens is there
It's not the Enigma2 logo, it's the machine boot logo. Have a look at the pli wiki, there is a link to pre built boot logo that you have to flash by USB.
No need for such an aggressive and rude response. Especially to a very competent coder.
Confirmation that the issue is still present on the latest image is what was sought. There was no such confirmation.
I have just flashed Open ATV 7.6 (21 Jan 2026), it is there for me in the system plugins category.
i use ATV 7.. image
7 point what please?
Which image are you using at the moment?
Freeview uses propriety software for their version of hbbtv. So nothing available on Enigma2. Should work with the TV itself if you have an internet connection.
From the questions you asked, I would say that it is highly discouraged to use chkroot multiboot.
Me or nillsat?
What do you mean exactly? You don't have to use it if you don't want to.
Using service references for picons means that every time the transponder changes, they have to be renamed. To avoid this perpetual change, SNP was introduced in 2014 ( twelve tears ago). UTF8SNP has subsequently replaced SNP in 2024. Enigma2 code supports all formats and checks in this order
Exact SRP
Modified SRP (e.g namespace/dvb type changes)
Utf8SNP
SNP
More details here:
The satellites.xml file is used to:
1. Provide a list of satellites that can be used by Enigma2. This includes the names and orbital positions.
2. Provide a list of transponders on each satellite that are scanned/probed.
On Manual scan and signal finder, the list of pre-defined transponders is also obtained from the xml files.
There is no need to trim the xml files, Enigma2 will filter selection based on your Tuner configuration.
Plugins like Blindscan, AutoBoquetsMaker, AutoBouquets 28.2, SatScanLCN, Terrestrail scan do NOT use these files.
There are two locations for the xml files
NB:
Some channel list providers include an outdated version of the xml file or one from a source that uses different criteria.
They have been asked to stop attaching xml files,, but they refuse to co-operate.
The XML files are not using for tuning/activating the channels. That data is held in lamedb.
If you dont believe this, remove all the transponders for your satellite in the xml file, the name must exist then reboot. If you corrupt the satellite name, it will not be available to Enigma2. You will find all the existing channels will still work, thereby removing your misconception.
The same applies to Cables and Terrestrial xml files.
On OE-A images, the satellites, terrestrial and cable XML files are part of the Tuxbox plugin.
The data in satellites.xml file on OE-A and PLI images is from Lyngsat. OE-A images until recently used to update it every Saturday.
The repository is here: https://github.com/oe-alliance/oe-alliance-tuxbox-common
The Tuxbox plugin is rebuilt when the image line is built. It is dependent on an image build being run before it becomes available in a software update.
Vix does not have nightly builds like OpenATV. Even for ATV, some users do not update images for a long time. That means whe they scan (not using a plugin), the data is old and not all transponders are scanned/probed.
To deal with this, for many years, OpenViX has had an option for users to update the xml files from the receiver. The plugin is called XML update and is located within the scanning menu. It is pre-installed on Vix and maybe OBH.
Attached is plugin created by Huevos to install on images that do not have it, it is for Python 3 images. It has been adapted to install on all receivers by KiddaC.
Please note: There is an issue with un-installation of the ipk.
Source code is here: https://github.com/oe-alliance/oe-alliance-plugins/tree/master/xmlUpdate
Install by your usual method:
1.
Place the ipk on a USB stick.
Ensure no menus are showing on TV
Insert USB stick into receiver
You will get a prompt to install the plugin.
2.
Transfer the ipk to the /tmp/ directory using an FTP program such as Filezilla/WinSCP
Issue the following command using Telnet protocol in Putty or Terminal in OWIF
opkg install /tmp/*.ipk
Once it installs, best to restart the GUI/Enigma2.
To use the plugin, access the scanning menu.
Menu > Setup > Tuners, scanning & Reception
(May be named something slightly different depending on your image)
The plugin is called "XML update"
Select the type of file you want (satellite, cable, terrestrial)
The default and recommended location is /etc/tuxbox/
Press Green to fetch/download the file.
Enigma2 will restart as soon as it completes the download.
That worked fine. Help Info displayed locally instead of going to the website.
Many thanks
The website had some issues over last few days. I notified Huevos this morning and it has been fixed. You access the website using your web browser, not AnyDesk.
Please continue in your existing thread.
I will delete your posts in other parts of the forum that relate to your ongoing issue.
11934
submodule: rework submodule support
- Add --submodule <name> option to config.sh for unified submodule handling
- Automatically detects git repo vs tarball: uses 'git submodule update' in
git repos, falls back to 'git clone --depth 1' for source downloads
- Reads submodule URL from .gitmodules
- Use --remote flag only when branch is defined in .gitmodules (respect pinning)
- Simplify Makefile and CMakeLists.txt submodule handling to single call
- Make submodule init conditional on WEBIF_WIKI
- Remove duplicate GEN output from wiki_gen.c
I think it's good addition.
Are your versions going to include the offline webif help file?
Are your versions going to include the offline webif help file?
Are your versions going to include the offline webif help file?
I think that the patch generator posts should be moved to their own thread. What do you think?
Which Astra? 1, 2 or 3? Surely better to just say the orbital position? 19.2, 28.2, 23.5?
Which channel are you selecting? Is it free or encrypted?
Does your tuner configuration match what is attached to the tuner?
