openAtv 7.4 devel Images

There are 734 replies in this Thread which was already clicked 110,638 times. The last Post () by Mahmoud Hussein.

    Quote from Mahmoud Hussein

    Captain , ziko


    is it possible to update the message displayed after skin selection to include the skin name? The reason is common, many skins are made in a rush and miss the correct screen for skin selection and you have to select another skin to get out blindly....

    This leads me to another suggestion,


    if the system counts like two reboots, due to skin failure, is it possible to offer a skin selection screen message? to select another working skin instead of the traditional way of deleting the skin manually and rebooting to the default skin after shutting down the system......etc.

    I also get the reason you have asked your question. But as a skinner I will answer some of your points.

    Skins are rarely made in a rush. It takes months to write a skin due to the fact there is literally hundreds of screens that can potentially be skinned. More screens if you include popular skinable plugins.

    If a skinner hasn't put in a screen in their skin. It will fallback to the default skin screen. So you should always see something. So the scenario you talk about with the skin selector screen shouldn't happen.

    If a skinner has made an error in a screen, that will cause it to not load at all or load partially.
    This isn't necessarily the skinners fault. Its usually the image creators (especially OpenATV - and especially one person in particular) who have unnecessary changed the variables used, or suddenly put in a totally unnecessary required element in that screen, (Its up to the skinner what they put into a screen and should never be forced to put in a required element). Skinners are not going to update their skins every month because the image provider decided to change something for no reason. Especially as there are a combination of users using 6.4 to 7.4. In that scenario it is up to the image provider to write in fallback code if they change variable names, so legacy code will continue to work.

    Openatv for a very long time have a default option in log settings. "Crash on skin error for debug reason" that has always been set to True. This should always be changed to "NO" as the very first thing you do.
    Otherwise you can very easily get into a boot loop if there is a skin error. One day openatv will realise what a ridiculous option this is and will one day set it to "NO" as default.

    Openatv also have another option always set to True. "Handle Python crashes". That should always be set to "NO". If there is an error in the python code it needs fixing.
    This option might have come about when we were transitioning from python2 to python3. But there is absolutely no need for this option anymore.

    Finally skinners used to skin for oe-alliance. Most of the code used to be shared. Realistically there is no oe-alliance anymore. Every image provider is doing something completely standalone now. Getting skins to work on more than one image is becoming a near impossible task. And a skinner isn't really going to put in months of work creating a skin for it to only work on one particularly release of an image.

    ** A person who feels appreciated will always do more than what is expected **

    clapping hands 1 Like 3
    Quote from KiddaC
    Quote from Mahmoud Hussein

    openatv also have another option always set to True. "Handle Python crashes". That should always be set to "NO". If there is an error in the python code it needs fixing.

    This option might have come about when we were transitioning from python2 to python3. But there is absolutely no need for this option anymore.

    Finally skinners used to skin for oe-alliance. Most of the code used to be shared. Realistically there is no oe-alliance anymore. Every image provider is doing something completely standalone now. Getting skins to work on more than one image is becoming a near impossible task. And a skinner isn't really going to put in months of work creating a skin for it to only work on one particularly release of an image.

    what kiddac wrote, it's totally true, the ATV team seems to have gone crazy, continuing to modify insignificant functions and variables, delaying or not providing the code of the changes. I stopped updating the skins on ATV because it is impossible to keep up with these changes, often useful, very often useless, changing the name of a variable makes no sense, destroys portability and makes the previous work useless, in a meaningless operation.

    Quote from Mmark
    Quote from KiddaC
    Quote from Mahmoud Hussein

    openatv також має іншу опцію, яка завжди має значення True. «Обробка збоїв Python». Для нього завжди має бути встановлене значення «НІ». Якщо в коді Python є помилка, її потрібно виправити.

    Цей варіант міг з'явитися, коли ми перейшли з python2 на python3. Але ця опція вже абсолютно не потрібна.

    Останні шкуродери звикли знімати за допомогою oe-alliance. Більша частина коду раніше була спільнотою. Насправді ое-альянсу більше немає. Зараз кожен постачальник зображення робить щось абсолютно автономне. Змусити шкіру працювати на кількох зображеннях стає майже неможливим завданням. І скінер насправді не збирається витрачати місяці на створення скіни, щоб працювати тільки над одним конкретним випуском зображення.

    те, що написав kiddac, це абсолютно правда, команда ATV, здається, збожеволіла, продовжуючи модифікувати незначні функції та змінні, затримуючи або не надаючи код змін. Я переставляю оновлювати скіни на ATV, тому що неможливо втягнутися за ці зміни, часто корисними, дуже часто марними, зміна назви змінної не має сенсу, руйнує переносимість і робить попередню роботу марною, у безглузді операції.

    Quote from Mmark

    це абсолютно правда, команда ATV, здається, збожеволіла, продовжуючи модифікувати незначні функції та змінні, затримуючи або не надаючи код змін

    Thanks to the ATV team for trying to add something new, change it, make it simpler. They need to be supported in that direction.

    Quote from wlad-sat
    Quote from Mmark
    Quote from KiddaC
    Quote from Mahmoud Hussein

    openatv також має іншу опцію, яка завжди має значення True. «Обробка збоїв Python». Для нього завжди має бути встановлене значення «НІ». Якщо в коді Python є помилка, її потрібно виправити.

    Цей варіант міг з'явитися, коли ми перейшли з python2 на python3. Але ця опція вже абсолютно не потрібна.

    Останні шкуродери звикли знімати за допомогою oe-alliance. Більша частина коду раніше була спільнотою. Насправді ое-альянсу більше немає. Зараз кожен постачальник зображення робить щось абсолютно автономне. Змусити шкіру працювати на кількох зображеннях стає майже неможливим завданням. І скінер насправді не збирається витрачати місяці на створення скіни, щоб працювати тільки над одним конкретним випуском зображення.

    те, що написав kiddac, це абсолютно правда, команда ATV, здається, збожеволіла, продовжуючи модифікувати незначні функції та змінні, затримуючи або не надаючи код змін. Я переставляю оновлювати скіни на ATV, тому що неможливо втягнутися за ці зміни, часто корисними, дуже часто марними, зміна назви змінної не має сенсу, руйнує переносимість і робить попередню роботу марною, у безглузді операції.

    Quote from Mmark

    це абсолютно правда, команда ATV, здається, збожеволіла, продовжуючи модифікувати незначні функції та змінні, затримуючи або не надаючи код змін

    Thanks to the ATV team for trying to add something new, change it, make it simpler. They need to be supported in that direction.

    Are you joking If i needed fancy skins then go android or at least make sure any changes are backwords compatible as KiddaC and Mmark wrote is true at one time skins would work across oe-alliance, but now constant changes no skinners can keep up . I still remember a few years back because of a certain person changing things meant a lot of plugins did not work.

    Lets not start a flaming war. Most of us skinners/plugin writers are actually in conversation with openatv/openvix etc. Especially when something gets broke.

    We are not against moving forward. I quite like all the new skin options. Although I am yet to experiment with them. But that is the exact problem now. People used to always be eager to update to new image. Now people wait 12 months if not more waiting for all these unnecessary amends of old code to be stabilised. So although image providers think every one is on latest image, everyone has a quad core modern box, everyone is on the same page. We all know the reality is far different.

    ** A person who feels appreciated will always do more than what is expected **

    Thanks 1 thumbs up 1
    Quote from KiddaC

    Lets not start a flaming war. Most of us skinners/plugin writes are actually in conversation with openatv/openvix etc. Especially when something gets broke.

    We are not against moving forward. I quite like all the new skin options. Although I am yet to experiment with them. But that is the exact problem now. People used to always be eager to update to new image. Now people wait 12 months if not more waiting for all these unnecessary amends of old cold to be stabilised. So although image providers think every one is on latest image, everyone has a quad core modern box, everyone is on the same page. We all know the reality is far different.

    I appologise for my comments , no harm intent.

    @Captain


    YouTube TV Not Work in OepnATV 7.4


    Code
    File "/usr/lib/enigma2/python/StartEnigma.py", line 933, in <module>
    runScreenTest()  # Start running the first screen.File "/usr/lib/enigma2/python/StartEnigma.py", line 453, in runScreenTest
    runReactor()File "/usr/lib/enigma2/python/StartEnigma.py", line 622, in runReactor
    reactor.run(installSignalHandlers=False)File "/usr/lib/python3.12/site-packages/twisted/internet/base.py", line 695, in runFile "/usr/lib/python3.12/site-packages/twisted/internet/base.py", line 708, in mainLoopFile "/usr/lib/enigma2/python/e2reactor.py", line 173, in doPollFile "/usr/lib/python3.12/site-packages/twisted/python/log.py", line 96, in callWithLoggerFile "/usr/lib/python3.12/site-packages/twisted/python/log.py", line 80, in callWithContextFile "/usr/lib/python3.12/site-packages/twisted/python/context.py", line 117, in callWithContextFile "/usr/lib/python3.12/site-packages/twisted/python/context.py", line 82, in callWithContextFile "/usr/lib/enigma2/python/e2reactor.py", line 209, in _doReadOrWriteFile "/usr/lib/python3.12/site-packages/twisted/internet/posixbase.py", line 107, in _disconnectSelectableFile "/usr/lib/python3.12/site-packages/twisted/internet/tcp.py", line 309, in readConnectionLostFile "/usr/lib/python3.12/site-packages/twisted/internet/tcp.py", line 326, in connectionLostFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/datasocket.py", line 47, in connectionLostFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/browser.py", line 87, in onBrowserClosedFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/chromium.py", line 141, in onExitFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/chromium.py", line 113, in doExitFile "/usr/lib/enigma2/python/StartEnigma.py", line 933, in <module>
    runScreenTest()  # Start running the first screen.File "/usr/lib/enigma2/python/StartEnigma.py", line 453, in runScreenTest
    runReactor()File "/usr/lib/enigma2/python/StartEnigma.py", line 622, in runReactor
    reactor.run(installSignalHandlers=False)File "/usr/lib/python3.12/site-packages/twisted/internet/base.py", line 695, in runFile "/usr/lib/python3.12/site-packages/twisted/internet/base.py", line 708, in mainLoopFile "/usr/lib/enigma2/python/e2reactor.py", line 173, in doPollFile "/usr/lib/python3.12/site-packages/twisted/python/log.py", line 96, in callWithLoggerFile "/usr/lib/python3.12/site-packages/twisted/python/log.py", line 80, in callWithContextFile "/usr/lib/python3.12/site-packages/twisted/python/context.py", line 117, in callWithContextFile "/usr/lib/python3.12/site-packages/twisted/python/context.py", line 82, in callWithContextFile "/usr/lib/enigma2/python/e2reactor.py", line 209, in _doReadOrWriteFile "/usr/lib/python3.12/site-packages/twisted/internet/posixbase.py", line 107, in _disconnectSelectableFile "/usr/lib/python3.12/site-packages/twisted/internet/tcp.py", line 309, in readConnectionLostFile "/usr/lib/python3.12/site-packages/twisted/internet/tcp.py", line 326, in connectionLostFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/datasocket.py", line 47, in connectionLostFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/browser.py", line 87, in onBrowserClosedFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/chromium.py", line 141, in onExitFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/chromium.py", line 113, in doExitFile "/usr/lib/enigma2/python/StartEnigma.py", line 933, in <module>
    runScreenTest()  # Start running the first screen.File "/usr/lib/enigma2/python/StartEnigma.py", line 453, in runScreenTest
    runReactor()File "/usr/lib/enigma2/python/StartEnigma.py", line 622, in runReactor
    reactor.run(installSignalHandlers=False)File "/usr/lib/python3.12/site-packages/twisted/internet/base.py", line 695, in runFile "/usr/lib/python3.12/site-packages/twisted/internet/base.py", line 708, in mainLoopFile "/usr/lib/enigma2/python/e2reactor.py", line 173, in doPollFile "/usr/lib/python3.12/site-packages/twisted/python/log.py", line 96, in callWithLoggerFile "/usr/lib/python3.12/site-packages/twisted/python/log.py", line 80, in callWithContextFile "/usr/lib/python3.12/site-packages/twisted/python/context.py", line 117, in callWithContextFile "/usr/lib/python3.12/site-packages/twisted/python/context.py", line 82, in callWithContextFile "/usr/lib/enigma2/python/e2reactor.py", line 209, in _doReadOrWriteFile "/usr/lib/python3.12/site-packages/twisted/internet/posixbase.py", line 107, in _disconnectSelectableFile "/usr/lib/python3.12/site-packages/twisted/internet/tcp.py", line 309, in readConnectionLostFile "/usr/lib/python3.12/site-packages/twisted/internet/tcp.py", line 326, in connectionLostFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/datasocket.py", line 47, in connectionLostFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/browser.py", line 87, in onBrowserClosedFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/chromium.py", line 141, in onExitFile "/home/oe1/atv7.4/build-enviroment/builds/openatv/release/multiboxpro/tmp/work/multiboxpro-oe-linux-gnueabi/enigma2-plugin-extensions-chromium2/1.0+20240101/image/usr/lib/enigma2/python/Plugins/Extensions/Chromium/chromium.py", line 113, in doExit
    Quote from tmurgel1
    Code
    Can I download openatv 7.4/7.5 devel to USB and transfer it to Octagon sf8008? Which site can I download it from? Thank you.
    Code

    Devel is not stand alone version, the only option


    1. Install clean openatv 7.4 beta

    2. Install Devel feed

    3. Update then upgrade

    4. Install anthing you can use

    5. Make backup image


    Flash the backup

    Thank you very much. From where can i install Devel feed? I am really confuse.

    nothing special

    you need to do it via terminal i.e.putty or openwebif terminal logged in to you device ipaddress. ut just remember these are development not for normal use so install to spare partition,

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