OpenATV 7.6 – Discussion & New Features

There are 1,057 replies in this Thread which was already clicked 250,823 times. The last Post () by haldborg.

    Useless

    F4 device OCTAGON SF8008

    SF8008 OpenATV 7.8 Alpha // SF8008 OpenATV 7.6 - Motor 70°E 34°W

    Still I had to buy a new stick. That's why I had all these problems. I successfully installed Oatv version - 7.6 beta and everything works great (with old script). With the latest Python 3.13 and everything works smoothly.

    I also updated exteplayer and gstplayer to v.177 from another forum.

    Sami Ertaga & others


    OK , I will post anyway , because isn't secret.


    I updated exteplayer 3 and ffmpeg for ServiceApp. The files are for mipsel and arm architecture. You need to uninstall exteplayer 3 and ffmpeg with the telnet command, reboot the box, and then copy both files to /tmp. I copied exteplayer 3 first and rebooted, then copied ffmpeg and rebooted the box again. You can also copy both files to /tmp. , but exteplayer 3 should be installed first. Now all videos in Youtube (by Taapat) work forward and rewind up to 1920 x 1080 resolution. Dash mp4 must be enabled and default player 'Exteplayer'.In HDFRadio default player must be gstplayer or Default.

    Now remain problem with Vavoo plugin because not work with exteplayer(only gstplayer 4097).In SamsungTV Plus i changed Bouquet player sevice to 5001 or 5002 (extplayer 3) and it works well.In screenshots you will see that is now Exteplayer 3 version 177.


    Many thanks @skyjet18 developer who is updated ServiceApp


    Also many thanks Alpha & O from the Boxpirates forum


    Both (exteplayer3, ffmpeg) are copied together to tmp and installed.

    It is better if you install the .ipk one after the other, then in the output you can see what/where is installed.


    Important:

    If you install the .ipk one after the other, exteplayer3 must be installed first,

    because ffmpeg depends on exteplayer3 !


    Captain,




    Software Update Enhancement Suggestions for OpenATV (Enigma2)



    As a dedicated user of OpenATV and Enigma2, I would like to share some thoughtful suggestions to enhance the software update functionality. These ideas aim to improve user experience, efficiency, and customization while reducing disruptions during the update process. I hope these suggestions contribute to the ongoing improvement of this fantastic platform.



    1. Scheduled Updates

    Introducing a scheduling feature for updates would greatly enhance convenience for users. Allowing updates to be scheduled based on:


    - **Time intervals** (daily, weekly, or monthly)

    - **Device events** (after reboot, during standby, or when the device is idle)


    This would ensure updates occur at optimal times, minimizing disruptions to viewing or other activities.



    2. Background Updates

    Implementing a background update option would allow updates to proceed silently without interrupting the user’s experience. Currently, halting all activities during updates can be frustrating, especially when users are unable to continue watching or using their devices. Background updates would make the process seamless and less intrusive.


    3. Selective Update Exclusion

    Adding the ability to exclude specific items (e.g., plugins, skins, or unnecessary language packs) from updates would be highly beneficial. This would:


    - Reduce unnecessary downloads for users with limited internet speed or data plans.

    - Allow users to maintain their preferred configurations without being forced to update unused or unwanted components.


    4. Categorized Updates

    Categorizing updates into clear classifications would help users prioritize and understand the nature of each update. Suggested categories include:


    - **System Updates** (critical fixes and core improvements)

    - **Recommended Updates** (important but non-critical enhancements)

    - **Optional Updates** (additional features or minor improvements)

    - **Extra Updates** (third-party plugins or non-essential items)


    This structure would empower users to make informed decisions about which updates to install.


    5. Visual Update Status Notifications

    Introducing a visual indicator system for update statuses would provide users with immediate clarity. For example:


    - **Green** = Up to Date

    - **Orange** = Update Available

    - **Red** = Urgent Update Required


    This simple yet effective system would help users quickly assess the status of their software and components.


    I deeply appreciate the hard work and dedication of the OpenATV team in delivering such a robust and reliable platform. While I understand that not all suggestions may be feasible, I hope these ideas spark meaningful discussions and contribute to the continuous evolution of OpenATV. Thank you for your outstanding efforts and commitment to the community!


    Regards

    Dear Mahmoud Hussein,

    Thank you very much for taking the time to share your thoughtful and detailed suggestions for improving the software update functionality in OpenATV. We truly appreciate your passion and commitment to making the platform even better for the community.

    We’d like to share a bit of context regarding the current situation and the challenges we face as a development team:

    • OpenATV is a hobby project, and all of us contribute in our spare time. We’re not a commercial organization, and we don’t have any sponsors supporting us financially.

    • Our server infrastructure, including the build servers, is paid month to month, entirely from donations. Unfortunately, user donations are very limited, which recently forced us to introduce advertising on our forum — something we had hoped to avoid.

    • We rely on OpenEmbedded for our build system, which means we often have very limited information about the nature or importance of upstream updates.

    • The package manager we use, opkg, has only basic update functionality. Features like categorization, background updating, or selective exclusions are currently not supported by opkg and would require significant development effort or a change in the underlying package system.

    That being said, we genuinely value your ideas, especially:

    • Scheduled and background updates to reduce interruptions.

    • Visual indicators to make update status more transparent.

    • More control over what gets updated (e.g., excluding language packs or unused plugins).

    These are all excellent concepts, and while we can't promise implementation in the short term due to our limited resources, we will certainly keep them in mind for future development discussions. Input like yours helps us understand what users need most, and we’re grateful for it.

    Once again, thank you for your support and engagement with OpenATV. We’re glad to have such a dedicated community, and we’ll continue doing our best — even with the limited resources we have — to deliver a reliable and enjoyable experience for all.

    Best regards,

    The OpenATV Team


    Dear Captain

    Dear OpenATV Team


    Thank you so much for your thoughtful and transparent response! I truly appreciate you taking the time to explain the current challenges and technical considerations behind the update system. It's heartening to see how passionate and committed your team is despite working on this project in your spare time.


    I completely understand the resource constraints you're facing - the fact that OpenATV continues to deliver such a robust platform through donations and volunteer efforts is truly impressive. The community is lucky to have such dedicated developers!


    The context you shared about opkg's limitations and server costs puts everything into perspective. I am glad to know these suggestions are being considered for future discussion. The three priorities you highlighted (scheduled updates, visual indicators, and update control) would indeed make a huge difference for users.


    Please know that your hard work doesn't go unnoticed. The stability and functionality OpenATV provides already far exceeds many commercial alternatives.


    Wishing you all the best as you continue to improve this fantastic platform. The community is behind you!


    Warm regards,

    Mahmoud


    ---

    Quote from trepqa89

    And my last question for today, I have installed OSCam:118884-802 but cant get the channels to work, do I need another version of OSCam? Thanks for the help!

    ???...channels is a question or a riddle


    11884..I know it's not good for the Germans.

    VuSolo_VuSOLO.PRO_VuZero_VuSOLO2 SE_DR.800sim japar ed 800SEsim a8p_Mutant 51_4k_GB.UE.4k_DM.920+900
    H9combo_H9.2H-SE_H7s_H2H_H5
    Quote from trepqa89
    Quote from piterfree
    Quote from trepqa89

    And my last question for today, I have installed OSCam:118884-802 but cant get the channels to work, do I need another version of OSCam? Thanks for the help!

    ???...channels is a question or a riddle


    11884..I know it's not good for the Germans.

    I understand, wich one do you recomemnd?

    u2c Forum
    u2c
    u2c.tv

    The file is missing, you need to add….

    Edited 3 times, last by Grygori: The file is missing, you need to add…. ().

OpenATV Team Images Support Forum ~ based on OE-Alliance

OpenATV Supported Models ~ Airdigital, Amiko, Anadol, Atemio, Atto, AX Technology, Axas, Beyonwiz, Dinobot, Dreambox, Edision, EVO, Ferguson, Formuler, Galaxy Innovations, Gigablue, Golden Interstar, HDBox, Hitube, James Donkey, IQON, Izibox, Jepssen, Maxdigital, Medialink, MaXytec, MediaArt, Megaset, Miraclebox, MK-Digital, Mut@nt, Novaler, Octagon, Odin, Optibox, Protek, PULSe, Qviart, Red-Eagle, Relook, Roxxs, SAB, Sezam, Sogno, Space, Spycat, Technomate, Telestar, Tiviar, T-Rex, Uclan, Venton Unibox, Vimastec, VisionNet, VU+, VUplus, World Vision, Vizyon, WWio, Xsarius, and Xtrend.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login