Posts by abu baniaz

    Might have been an idea to post in the existing thread, I'll move post later.


    Which receiver are you using? Which image are you using? Which version of plugin are you using? Please upload the crashlog.


    There were plugin updates last night to fix a crash.

    The e2openplugins repositories were created many many years ago as a repository for different image teams to use. A whitelist file is hosted there too. If people want to contribute to the community, please submit additions/corrections there directly or post here and we can update them.


    https://github.com/E2OpenPlugins/oscam-whitelist


    To download the file, the commands on receiver is

    Code
    init 4 && sleep 5 && [ ! -d "/etc/enigma2/whitelist_streamrelay" ] && wget -O /etc/enigma2/whitelist_streamrelay https://raw.githubusercontent.com/E2OpenPlugins/oscam-whitelist/refs/heads/main/whitelist_streamrelay  && init 3


    Click on the "copy contents" box at top right of code box and then paste in terminal/putty

    This will stop enigma2 because the file is held in RAM, white 5 seconds, download the whitelist_streamrelay file and then restart the receiver.

    There is no script on the receiver, (I hope). When you run the script it did its work and that's it.


    The satellites.xml has been replaced with a shortened one, this is why you cannot scan other satellites. Check the scanning menu and see if there is an xml update. If teher isnt' install it from the plugin menu and run(use) it. It will download the latest satellites.xml file and restart your receiver. You should be able to scan other satellites then.


    Install the channel list like you did before. Menu , Plugins, Green for download, settings, select the one you want.

    The script removes other channel lists. It does not uninstall them. So maybe not a good idea to use it, or you selected wrong option. You have just repeated what you did. I am asking you to tell us what you want to do. Tell us what you want to do and we will help you do that. It's no point us telling you do A, but you want to do B. And someone else tells you to do C.


    Hopefully people contributing will assist you without giving contradictory suggestions.

    Where did you add this?

    The file is here:

    linuxsat-support.com/thread/?postID=877040#post877040


    OpenATV has a Grid EPG too. There are many EPG screens. Grid EPG is one of them. See screenshot of it with the user file being used to adapt it. I have highlighted the change in red. Pity there is little chance of making it into official skins even though it won't affect anything else.


    atv screen mod.jpg

    With regards to the issue on PLI: A software update regresses/downgrades the user installed version.

    The root cause is the versioning in use by the PLI bitbake files


    The Pli release versions are named

    enigma2-plugin-extensions-xstreamity_527+dd9fc8b-r0.12_all.ipk


    Versions uploaded by Kiddac are named

    enigma2-plugin-extensions-xstreamity_5.05.20250716_all.ipk


    527 is larger than 5.05, so opkg sees the one on the image's plugin server as being newer despite being older. It is therefore seen as an upgrade, hence the change


    They have updated the commit hash so newer version will be on feeds when next build is run.

    https://github.com/OpenPLi/openpli-oe-core/commit/d0a1aac58f471299cec357f3cced7edb314af7a6


    Until they implement what is opined to be the correct implementation, please continue to use the dxhold command to prevent a downgrade. Or use the developer image.

    See this thread:

    The problem is only fixable by compiling the image from the source files. ATV have made some changes to their beta branch (7.6 Beta images). Hopefully there will be improvements made.


    I presume they have been testing only with unicable devices. Therefore the issues you are experiencing have not been encountered by them yet. Anyway, lets hope for an improvement.

    I have moved your posts into one thread. I have just tested again and can see the problem. I have communicated with Captain on the OE_A Teams chat. Hopefully he understands the issue.


    You have an FBC tuner, you cannot change that. Th FBC feature you are using when using Universal LNBs is "FBC automatic" which is "Internal loop through, when required". Unicable is a different technology to FBC tuners.


    There is no official PLI support/code for these Dreamboxes. For people making custom PLI builds, they will have to use the same code that official PLI images use for the Vu and Gigablues that have FBC tuners.


    1. There is only internal linkage between the same tuner card/module. So " Connected to" must be restricted to the same card/module.

    2. When configuring unicable, A/B can be "connected to each other". C-H can be "connected to either A or B depending on which has the desired satellite signal.

    The letters in this example applies to a module in slot A. For a card in slot B, the tuner letters change.

    3. When using Universal LNBs, Tuner A and B cannot be "connected to" B/A. Otherwise you can physically connect Universal 19.2 to input 1. Universal 13 to input 2. And then swap the tuners around ad expect it to work.