- removed issue_status
Unexpected deep standby after 300 minutes
A default power timer entry that puts the unit into Deep Standby after 300 minutes is pre-installed and active. You can find it under Menu > Setup / Power / Sleep Timer
This causes the T3 to disappear off the network unexpectedly. This is likely to generate support calls from users, complaining that the unit turns itself off overnight.
This power timer should either not be pre-installed or if it is, it should be set to disabled mode.
Reproduction steps
- Press standby before going to bed.
- Sleep for at least 5 hours.
- Check the unit - it will be in deep standby and required a full boot to become active again.
Comments (7)
-
Account Deleted -
reporter - removed issue_priority
The issue was updated with the following change(s):
- The priority has been updated, from Normal to High.
-
This bug can be worked around by deleting or disabling the pre-defined sleep timer.
-
reporter - removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Confirmed to Testing.
-
- removed issue_status
Item is still present and active in 20140221 firmware.
The issue was updated with the following change(s):
- The status has been updated, from Testing to Not Fixed.
-
The shutdown timer default setting is in /usr/share/enigma2/defaults/pm_timers.xml. The current shutdown timers are in /etc/enigma2/pm_timers.xml. The defaults are copied to the current values in a Factory Reset. I'm not sure how that relates to the creation of a firmware update package.
There's s single timer in the default shutdown timer file and it's enabled and autosleepinstandbyonly is "no".
My suggestion is that the default shutdown timer should remain, but it should be ' disabled="1" autosleepinstandbyonly="yes" '.
-
- removed issue_resolution
- removed issue_percent
- removed issue_close
- removed issue_status
The 300 Minute timer is absent in a fresh install of 20140224, restoring user preferences brings it back (unless you had deleted it :D )
The issue was updated with the following change(s):
- The status has been updated, from Not Fixed to Closed.
- This issue has been closed
- This issue's progression has been updated to 100 percent completed.
- The resolution has been updated, from Not determined to Fixed.
- Log in to comment
The issue was updated with the following change(s):