View Full Version : [VU+ Duo] Build 430 - Reboot is followed by standby
Just reporting that I've upgraded from build 423 to build 430. There is now an unexpected change in behaviour.
When I do a restart from a full on situation, the box does the reboot then about 5 seconds after pictures return, the box drops into standby. This is easily retrieved back to full on / awake. Just seems a bit odd!
I disabled HDMI-CEC and deleted all power timers. The new reboot behaviour remained.
Has anyone else noticed this new behaviour?
cheers
mickyblueys
21-11-12, 05:52
Yes I noticed this. I'm sure Andy will sort it, when he gets a chance, now that it has been highlighted.
Sent from my GT-I9100 using Tapatalk 2
Rob van der Does
21-11-12, 06:43
I tried to reproduce this but so far I failed (on all my boxes).
Could you please provide us a debuglog?
Also: do you have any powertimers active? And if so, please provide us the settings.
I tried to reproduce this but so far I failed (on all my boxes).
Could you please provide us a debuglog?
Also: do you have any powertimers active? And if so, please provide us the settings.
I've replicated on Ultimo. Posted logs in dev room.
mickyblueys
21-11-12, 08:46
I tried to reproduce this but so far I failed (on all my boxes).
Could you please provide us a debuglog?
Also: do you have any powertimers active? And if so, please provide us the settings.
I've replicated on my duo, have sent debug log, Nr 1353483902.45
Sent from my GT-I9100 using Tapatalk 2
mickyblueys
21-11-12, 08:48
Forgot to post my power timer setup so here it is
21083
Sent from my GT-I9100 using Tapatalk 2
do you have any powertimers active? And if so, please provide us the settings.
The behaviour occurs with or without power timers and with or without HDMI-CEC as stated in OP. Several others have already beat me to the punch with debug logs... so I'll leave it unless further info is requested.
this is down to a wakeup to standby power timer having been set, i will take a look
just added more debug code, if after next update you still have this issues, please post your logs.
thanks.
just added more debug code, if after next update you still have this issues, please post your logs.
thanks.
Now on build 432... still goes to standby after reboot (line 473 of debug).
Short power button turns it on (line 510 of debug).
Debug log sent Ref: 1353512989.61
Nil power timers set
HDMI-CEC disabled
regards
Now on build 432 goes to standby after reboot, debug says TIMER: Going to stand-bye
Power button turns it on again :)
Now on build 432... still goes to standby after reboot (line 473 of debug).
Short power button turns it on (line 510 of debug).
Debug log sent Ref: 1353512989.61
Nil power timers set
HDMI-CEC disabled
regards
getFPWasTimerWakeup: True
driver states it was woke by a timer.
just an update, i have spent the 2 hours debugging, and guess what....
it is not powertimer sending to standby but the normal Timer with the after even sent to AUTO.
to confirm remove all rec timers and test ;)
nextRecordTimerAfterEventActionAuto True
nextPowerManagerAfterEventActionAuto False
[TIMER] record time changed, start prepare is now: Wed Nov 21 18:56:40 2012
[Timer] Record RecordTimerEntry(name=BF1 Fast Track: United StatesB, begin=Wed Nov 21 18:57:00 2012, serviceref=1:0:19:EFB:7F2:2:11A0000:0:0:0:, justplay=0)
[POWERTIMER] time changed, start prepare is now: Wed Nov 21 18:27:40 2012
[POWERTIMER] PowerTimerEntry(type=wakeuptostandby, begin=Wed Nov 21 18:28:00 2012)
getFPWasTimerWakeup: !!!!!!!!!!!!!!!!!!!!wasTimerWakeup: 1
!!!!!!!!clearFPWasTimerWakeup
True
RECTIMER: wakeup to standby detected.
ok after further debuggin i have come the conclusion it is a bug in the drivers.
here is an explanation
there is a '/proc/stb/fp/was_timer_wakeup' this file is controlled via drivers that e2 if box was awoke up by a timer or by the user.
if the box is woke the a timer the file is set to 1, which is correct. e2 sets the file 0 on start, to rest it.
but if you restart the box via the gui menu RESTART, the file reverts back to 1, again e2 set the file 0 again, but e2 has already been told that a timer woke the box, but it was not, it was just a restart.
it seems that this is only changed if you go to deep standby and start the box manually, then the file is reset to 0, i think this file should be reset to 0 on a restart also.
andy.
guy's,
just an update, i think i have managed to code around the drivers issue. i have been speaking to Black_64 (AAF) and i think we have found something we can use. just testing it now
good news guy's, i have found and fixed the issue, was a mix of driver issues and badly coded Recording Timer code in E2 from dreambox original code. i have recoded it.
this new code also fixes the afterevent of AUTO, it now actually works, it detects the code at rec timer start and returns to that state, ie if in deep is returns to deep, if in standby returns to standby.
i have added lots of debug code to help solve any issues that may arise from my new code.
building now, i will set state to unstable until rec timer have been thoroughly tested, if you do want to tae the chance of failed recording's do not update until feeds are stable again.
andy.
Now on build 439... still goes to standby after reboot
Short power button turns it on
Debug log sent Ref: 1353622871.82
regards
Now on build 439... still goes to standby after reboot
Short power button turns it on
Debug log sent Ref: 1353622871.82
regards
look like it has not fully updated, i can tell by the log, missing lots of debug info. please try to reflash.
EDIT:
i have found something that might help, i will update tomorrow.
look like it has not fully updated, i can tell by the log, missing lots of debug info. please try to reflash.
Used telnet:
init 4 && opkg update && opkg upgrade && init 6
I'm not sure whether it picked up much more; however, still the same.
Sent log Ref: 1353644865.41
Good Luck with it tomorrow.
cheers
update have been uploaded, just building a new few again, but give them a try please.
Thanks Andy,
Build 444 and 445 are back to normal for me: reboot doesn't go to standby.
cheers
mickyblueys
03-12-12, 17:42
Just updated to 473....and noticed when my box rebooted after a few seconds it placed itself into stand by.....this happened a few builds ago. (thought it was sorted).
Is any body else experiencing this?
I have one power timer set to turn box to deep stand by at 02:00 and to wake to stand by at 07:25. (for info).
Log sent 1354552991.03
Sent from my GT-I9100 using Tapatalk 2
Just updated to 473....and noticed when my box rebooted after a few seconds it placed itself into stand by.....this happened a few builds ago. (thought it was sorted).
Is any body else experiencing this?
I have one power timer set to turn box to deep stand by at 02:00 and to wake to stand by at 07:25. (for info).
Log sent 1354552991.03
Sent from my GT-I9100 using Tapatalk 2
must be wrong log, can't see nothing in that.
mickyblueys
04-12-12, 08:28
I'll check log times when I get home this afternoon and get back to you.
Sent from my GT-I9100 using Tapatalk 2
mickyblueys
04-12-12, 17:42
Just updated again to 478.....went fine this time ..no stand by issue.
Must've been a dumb blonde moment by me yesterday.
Sorry for wasting you're time...:D
Sent from my GT-I9100 using Tapatalk 2
Just updated again to 478.....went fine this time ..no stand by issue.
Must've been a dumb blonde moment by me yesterday.
Sorry for wasting you're time...:D
Sent from my GT-I9100 using Tapatalk 2
dont worry about it and please remember that submitting a crash / bug report is never a waste of time.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.