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.
Results 1 to 15 of 29

Thread: MB Premium Twin gains time in Deep Standby - debug assistance needed!

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Joe_90's Avatar
    Title
    Moderator
    Join Date
    Mar 2014
    Location
    Wicklow, Ireland
    Posts
    4,127
    Thanks
    1,280
    Thanked 1,126 Times in 888 Posts
    @birdman - the code that generates that RECTIMER message comes from Navigation.py:

    Code:
    	if getFPWasTimerWakeup():
    			self.__wasTimerWakeup = True
    			if nextRecordTimerAfterEventActionAuto and abs(self.RecordTimer.getNextRecordingTime() - time()) <= 360:
    				print 'RECTIMER: wakeup to standby detected.'
    				f = open("/tmp/was_rectimer_wakeup", "w")
    				f.write('1')
    				f.close()
    				# as we woke the box to record, place the box in standby.
    				self.standbytimer = eTimer()
    				self.standbytimer.callback.append(self.gotostandby)
    				self.standbytimer.start(15000, True)
    Do I take it that the test above checks for wasTimerWakeup to be true AND the "after event" setting in the timer to be "auto" AND the time to the recording to be <= 6 minutes?
    The recording is due to start in my case in 194 seconds and the "after event" setting is auto. Bit of a puzzle really.
    GB Quad Plus, Mut@nt HD51, AX HD61, 80cm dish and Supreme Dark motor. Sony STR-DN 1060, Sony UHP-H1 Bluray, Odroid N2+ (CoreElec), Monitor Audio Bronze 5.1 speakers

  2. #2
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,829
    Thanks
    239
    Thanked 1,664 Times in 1,311 Posts
    Quote Originally Posted by fat-tony View Post
    @birdman - the code that generates that RECTIMER message comes from Navigation.py:
    ...
    Do I take it that the test above checks for wasTimerWakeup to be true AND the "after event" setting in the timer to be "auto" AND the time to the recording to be <= 6 minutes?
    That's what the code says, yes.
    Arguably the wasTimerWakeup is completely superfluous! If the box is booting and there is a recording starting in <= 6mins then it was woken up by a timer, since the timer reboot should happen around then anyway. The chance of someone shutting down the box (and ignoring the warning about a pending recording start) is surely minimal.

    My MBTwin does show this line from time to time - the reason it doesn't always do so is that if there has been a long(ish) time off before the recoding it will wake up "early" and fail the <= 6min test. (It did show it last night for the test timer restart I put in place as it was only 5 mins from shutdown to timer reboot).

    So the fact that the MBTwin marks all startups as a timer wakeup doesn't actually matter. All enigma2 really needs to know is "has the remote been used since boot time" for a standby decision and also "is someone using NFS/Samba/command-line login now" for a deep-standby decision.
    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

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.