Bugzilla – Bug 15021
Auto power off after inactivity timer reached
Last modified: 2009-11-06 13:13:18 UTC
Since one of the primary uses of the radio is as an alarm/clock, it would be very helpful to have the option of having the unit automatically power itself down and resume clock display after a certain period of time of inactivity has been reached. There is a "stopped" screen saver clock that can be selected, but I think this is a 1/2 measure. Several times I have been in the process of changing a setting, etc, and left the room the SB Radio is in for several hours. Upon returning I was surprised to discover that the same screen on the radio was still displayed. It would be far more helpful if the player, upon detecting no user interaction or media playback for a period of 5-10 minutes, simply turned itself off to go back to displaying the familiar clock screen.
I think many people use a clock as their stopped screensaver anyway. > Several times I have been in the process of changing a setting, etc, and > left the room the SB Radio is in for several hours. Upon returning I was > surprised to discover that the same screen on the radio was still displayed. Isn't this a bug? Shouldn't it timeout and go into either the stopped screensaver if nothing is playing, or else into the NP screensaver if something is? Regardless of whether the user was navigating a library or menu.
Assigning to Tom for comment
I just tried it (r7915) and it _does_ normally kick into the stopped screensaver, both when browsing the library and in settings. I don't see a need to automatically go to Off/Standby.
(In reply to comment #3) > I just tried it (r7915) and it _does_ normally kick into the stopped > screensaver, both when browsing the library and in settings. I don't see a > need to automatically go to Off/Standby. (In reply to comment #3) > I just tried it (r7915) and it _does_ normally kick into the stopped > screensaver, both when browsing the library and in settings. I don't see a > need to automatically go to Off/Standby. I have just tested again myself and now I can't recreate the issue. The "stopped" screen saver does seem to activate in all test conditions. Bug can be closed.
per the OP's comment