Bugzilla – Bug 16041
Power doesn't turn off Radio and Touch when idle
Last modified: 2012-03-09 07:24:30 UTC
SbS 7.6, r8673 FW When Radio or Touch are showing the idle clock screensaver, a power-toggle from either the Radio FP or a remote does not turn off the player. Instead it exits the screensaver and leaves it on. Perhaps this is by design - I can image that some might prefer this. Some might not. Note that this will break any universal remote macros that use the power-toggle code. I assume that the power-off discrete code will really turn it off, but I don't have a remote to test with right now.
This behavior seems even more non-intuitive when using, for example, an SBC to control a radio. With a radio on, but showing the idle clock SS: 1) Select "Turn Off Radio" from the SBC - Note that the SBC menu item changes to "Turn On", suggesting the Radio is now off - Note that there is no change to radio display, suggesting it is still on but idle. To a novice this might suggest that the radio was already off and is still off, which is also not true. 2) Turn the knob on the radio - Note that the radio exits the SS and shows the menu - Note that the SBC menu item changes to "Turn Off" suggesting the radio has been turned on by just turning the knob This means that it takes 3 clicks on an SBC to turn a radio off from this state: 1) "Turn Off" which really does nothing 2) "Turn On" which really just exits the SS on the radio 3) "Turn Off" which finally turns it off
I can see there is room for confusion. I don't know what the spec is or what thought went into this decision. I will target this for the next release and try and figure out how we came to this pass. Do you know, Ben?
The spec is that when you're in the screensaver we trap the first action, hide the screensaver, and consume the action. We don't handle power any different than any other action to my knowledge. I'm amenable to approaching this as a bug, and write some code to handle a power toggle action differently than any other. Note to self: make sure this doesn't break anything on SB Touch with SS behavior.
It occurs to me, in the cold light of morning, that maybe the 'right' thing to do is consider changing the 'idle' screensaver to something that doesn't look so tantalizingly similar to 'off'
I'd be hard-pressed to agree that anything other than a clock is the correct default idle screensaver. I'm not a fan of the gray background clock and never have been, so that could change to transparent perhaps. But I'm not sure that would look any less like off than the current one...
(In reply to comment #4) > It occurs to me, in the cold light of morning, that maybe the 'right' thing to > do is consider changing the 'idle' screensaver to something that doesn't look > so tantalizingly similar to 'off' IMO, changing the default screensavers doesn't address the issue. The user can always change these anyway. The fact remains that with the current implementation, the idle and off modes seem somewhat munged.
(In reply to comment #3) > The spec is that when you're in the screensaver we trap the first action, hide > the screensaver, and consume the action. We don't handle power any different > than any other action to my knowledge. > > I'm amenable to approaching this as a bug, and write some code to handle a > power toggle action differently than any other. Note to self: make sure this > doesn't break anything on SB Touch with SS behavior. I just got my SB Radio which has the firmware 7.5.1.r9218. The POWER button still has the described behavior when the screensaver is active. However all the PRESET buttons work properly --- i.e. when the screensaver is on and the player is in its playing mode, pushing one preset button will not only causing the exit of screensaver, but also playing the new station stored in that preset. The action of those buttons was not consumed. I think the POWER button should be handled in same way -- Pressing the button will turn off the SBR(i.e. entering the standby mode)regardless the status of screensaver.