Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.

View Entry Info: After upgrading to 5.0.016 AutoTimer fails

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
5.0.016
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Attachments
Page 1 of 3 123 LastLast
Results 1 to 15 of 35

Thread: After upgrading to 5.0.016 AutoTimer fails

  1. #1

    Title
    Junior Member
    Join Date
    Sep 2014
    Posts
    21
    Thanks
    8
    Thanked 0 Times in 0 Posts

    After upgrading to 5.0.016 AutoTimer fails

    The title pretty much says it all. Below is the screenshot of the error message:

    AutoTimer_error.jpg

    Downgrading to 5.0.014 fixes the problem.

  2. #2
    bellejt's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Dec 2013
    Posts
    1,726
    Thanks
    58
    Thanked 317 Times in 273 Posts
    working fine on duo 2
    VU+ DUO2 quad tuner with HDD 1 TB + Latest Openvix and VU+ DUO2 FB tuner + Octagon SF8008 FB tuner
    Triax 88 cm rotor single LNB 30 E- 40 W
    1 Gibertini 1.00 m fixed - 3 quad LNB 19E-23.5E-28.2E

  3. #3

    Title
    Senior Member
    Join Date
    Mar 2017
    Posts
    211
    Thanks
    91
    Thanked 20 Times in 18 Posts
    As op or getting clash warnings where none exist, no disabled timers set and no timers set where clashes do not exist.
    Restore to .14 results in normal function.

    Sent from my SM-G950F using Tapatalk

  4. #4

    Title
    Member
    Join Date
    Apr 2016
    Location
    Helsinki
    Posts
    98
    Thanks
    25
    Thanked 18 Times in 15 Posts
    The same happened to my Ultimo. The error message didn't even disappear with th exit key.
    Flashed back to 014, waiting for 017.

  5. #5
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,362
    Thanks
    6,443
    Thanked 9,160 Times in 6,235 Posts
    Autotimer is a shared plugin between the images. There have been changes to it.

    Unless people are going to post debug logs and step by step instructions on how to reproduce the problem/s, it is going to be difficult to report the matter to the person who has tried to make other improvements.

  6. #6
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,362
    Thanks
    6,443
    Thanked 9,160 Times in 6,235 Posts

  7. The Following User Says Thank You to abu baniaz For This Useful Post:

    Bangord30 (30-05-17)

  8. #7
    adm's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,656
    Thanks
    65
    Thanked 655 Times in 511 Posts
    Quote Originally Posted by abu baniaz View Post
    Autotimer is a shared plugin between the images. There have been changes to it.

    Unless people are going to post debug logs and step by step instructions on how to reproduce the problem/s, it is going to be difficult to report the matter to the person who has tried to make other improvements.
    I'm getting the same on an Extrend 1OK (build 5.0.016)

    No debug or crash logs are being produced when the error occurs (and yes debug logs are enabled in the logs setting menu)

    How to make it happen....
    Upgrade to 5.0.016
    Restore settings
    Wait 4 minutes and the error message appears
    Hit exit and the error message disappears
    wait 10 minutes and the error message appears again

    Edit 2
    On my box the error message can be triggered just by setting up a new autotimer. I suspect that it occurs when trying to match/find programs in the EPG
    Attached Images Attached Images
    Last edited by adm; 30-05-17 at 21:35.
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  9. The Following User Says Thank You to adm For This Useful Post:

    abu baniaz (31-05-17)

  10. #8
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    I'm not seeing this on my et10k - I couch flashed 14 to 16 and restored settings and plugins.

    Mine waits 3 minutes and then runs every 25 minutes.

    Only Freeview dvb-t2 tuners.

  11. #9
    adm's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,656
    Thanks
    65
    Thanked 655 Times in 511 Posts
    Quote Originally Posted by ccs View Post
    I'm not seeing this on my et10k - I couch flashed 14 to 16 and restored settings and plugins.

    Only Freeview dvb-t2 tuners.
    I couch flashed 13 to 16 and restored settings and plugins and have the problems.
    Mine automatically polls at 3 minutes and thereafter 30 minutes
    Most of my autotimers are on the satellite tuners (UK Freesat channels) although I have a few on T2 tuners (UK Freeview) channels.

    I'm just about to flash back to 13 as the error message keeps appearing [edit] with a period of a lot less than 30 minutes (more like 10 minutes)
    Last edited by adm; 30-05-17 at 21:55.
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  12. #10
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,362
    Thanks
    6,443
    Thanked 9,160 Times in 6,235 Posts
    Quote Originally Posted by adm View Post
    Edit 2
    On my box the error message can be triggered just by setting up a new autotimer. I suspect that it occurs when trying to match/find programs in the EPG
    This is indeed one of the new checks.

    I have tried to recreate your steps, (Was on Dev, flashed 016 Release and restored settings/plugins) but mine is not returning that error. Tried setting up new Autotimer, that was fine too. Perhaps different EPG searches.

    Would you mind trying this file?
    https://github.com/oe-alliance/enigm...merResource.py

  13. #11
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,362
    Thanks
    6,443
    Thanked 9,160 Times in 6,235 Posts

    After upgrading to 5.0.016 AutoTimer fails

    BTW, debug logs would be created constantly. A restart is required after enabling the option.



    Attached is my debug log. I added "Fajr Prayer- Sehri 1st" as the autotimer in the test above.

    EDIT:
    Added using Blue button in Graphical EPG.
    Attached Files Attached Files

  14. #12

    Title
    Junior Member
    Join Date
    Sep 2014
    Posts
    21
    Thanks
    8
    Thanked 0 Times in 0 Posts
    Attached is the debug log just after the error had happened:

    Enigma2_debug_2017-05-31_08-30-44.log

    And yes, this happens in 5.0.016 every time AutoTimer searches or tries to search EPG.

  15. #13
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,632
    Thanks
    2,007
    Thanked 4,956 Times in 3,276 Posts
    Recheck using the old drivers.
    Help keep OpenViX servers online.Please donate!

  16. #14
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,798
    Thanks
    237
    Thanked 1,659 Times in 1,307 Posts
    The only change I can see in the changes that affects extdesc is this in AutoTimer.py (old line 704, new line 732):

    Code:
    -                                       extdesc = event and event.getExtendedDescription() or ''
    -                                       timer.extdesc = extdesc
    +                                       if event:
    +                                               timer.extdesc = event.getExtendedDescription() or ''
    +                                       else:
    +                                               remove.append(timer)
    so whereas previously the timer always had a extdesc attribute, now it only has one if there is an event.
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  17. The Following User Says Thank You to birdman For This Useful Post:

    BubbleBalls (31-05-17)

  18. #15
    adm's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,656
    Thanks
    65
    Thanked 655 Times in 511 Posts
    Quote Originally Posted by abu baniaz View Post
    I only have a compiled Python file of that name on my box - I don't have a compiler.

    log file attached
    Attached Files Attached Files
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

  19. The Following User Says Thank You to adm For This Useful Post:

    abu baniaz (31-05-17)

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.