Posts by abu baniaz

    CrossEPG has a bug where data obtained from OpenTV EPG followed by Rytec is marked as tainted and dumped. It also has a false lock on 23.5 if moving east. These two bugs have been like this for a while.


    The plugin is too convoluted with none of the origianl contributers around to assist or share the inner workings. Case in point is your discovery.


    With regards to my remark about commenting/uncommenting, I was referring to where users are asked to edit the file to suit their requirements. To me this is a complication. Have the main file where the common services are linked. People can then add their own ones. Two aliases files will be used.


    BTW, as far as my testing on cable has shown, the services not on the NetID do not work. Hardly anyone disables background scanning, so people always scan in channels that do not work. Pure regions are not affected. I wouldn't worry too much about ITVs having the wrong EPG if they don't work. The working one is the vital one.

    Just to add to the instructions in post 29,


    1. If you are using an oscam-emu that has the older libssl requirement, you will need to add a symlink to it. (Most images are using 1.02, so the people making these emu's should really adapt it)


    2. If you are using an oscam-emu that includes the older libssl incliuded in the binary, Vix's softcam manager will not start it as it exceeds 512kb memory allocation that Vix Softcam manager has. As the older libssl has the heartbleed vulnerability, be sure of what you are exposing yourself to.



    Best to start the cam manually and see what error you get.

    Use the script to install latest "feeds". You cannot use older ones (2, 3 or 6)

    Install softcams from server. Do not use older ipks.

    oscam configs are same, just different location. ATV only uses /usr/keys for mgcamd


    Oh, you will have to skin softcam setup.

    From my tests, any.conf files in the /aliases folder get used automatically once you enable aliases. There is no need for any commenting/uncommenting of lines either, just add multiple conf files you want. There was no need for any additional python files.


    Adding duplicated python files with just a path change is not the best way of doing things. The better way of doing it is to adapt the python file to offer the choice of different alias files.


    If the idea is to be able to update files immediately and independent of image/build process, iIt may be better to have a script/plugin to fetch the conf file from a repository/resource. Like ABM Mix importer.


    To avoid confusion, I won't be adding the virgin conf file to the OE-A CrossEPG repository.

    ive tried im on atv 6.3 it installs but wont show in plugins after i get a message saying cant find cache file when installing ?

    It is on the plugin server.

    You can install with following commands


    opkg update

    opkg install enigma2-plugin-systemplugins-autobouquetsmaker


    If using the remote, it is under system plugins

    ive tried im on atv 6.3 it installs but wont show in plugins after i get a message saying cant find cache file when installing ?

    It is not an error, it is a notification.


    echo "No cache file found, continuing."



    If installer does not have the continuing, it is an older one ( before 17 Dec 2017) and person is using an image with no newer packages. In that case, ABM can be downloaded from


    ABM AutoBouquetsMaker plugin For ALL Enigma2 Receivers

    nextman, which image are you running please? Please say the series and date


    The libcrypto compat 0.97 package is not built, so we will have to manually add the symlink if you are on an old image.

    ln -sf /usr/lib/libcrypto.so.1.0.2 /usr/lib/libcrypto.so.0.9.7


    If you have a different libcrypto, i.e not 1.0.2, in /usr/lib we will have to amend the symlink.


    I am sure the ones on the feed work, albeit with an issue without the manual addition of links.

    When I downloaded the cam ipk and unpacked it, the binary is just mgcamd, however, this was from a different box. I am not too sure how to best advise as you are jumping between different approaches.


    If you have a softcam ipk that works, why would you install a softcam feed? A softcam feed just allows access to a softcam feed from which to install.

    If installing one package and replacing the binary, I would rename the old with new one and use old name. That way all other scripts are using what they expect. Rules of tinkering are to always make a backup.


    An option for you:

    Flash a new image, do not restore anything.

    Do not install the softcam feed

    Install the softcam ipk you already have.

    The cams are in /usr/bin


    To start them manually, you would issue these commands using putty or similar. I am assuming your cam name is mgcamd, please double check


    cd /usr/bin

    ./mgcamd



    If they have uploaded the wrong architecture file in the ipk, you will have to source a correct one and install it manually.