Bugzilla – Bug 14986
auto-dimming won't kick in when radio is switched off (soft switch off)
Last modified: 2010-04-23 11:02:00 UTC
i've enabled auto-dimming on my SB Radio device and it does auto-dim when on --- VERY NICE. however, once i do a soft switch off (brief tap on the power button), the display comes on quite bright and stays that way --- VERY ANNOYING when the SB Radio is next to your bed.
QA to verify all the screen savers. Dirk: what hardware version Radio do you have? on the radio, go to settings > advanced > Diagnostics. tell us the hardware revision # Also, which screen saver were you using?
firmware version: 7.4.1 r7915 hardware version: 4 screen saver when off: digital clock (black)
*** Bug 15088 has been marked as a duplicate of this bug. ***
I use the Digital Clock (Black) and I also have this problem. When the Radio is off it does dim but NOWHERE near as much as when they player is on.
Dimming works on my radio but the clock screensaver (black background) does not go dim enough and disturbs my sleep. I'd be happy if the minimum brightness was configurable, ala the Boom.
*** Bug 15211 has been marked as a duplicate of this bug. ***
I have found settings that make this reproducable. with unit set screen,screen savers, delay, 10 seconds screen,screen savers, when off, screen off place unit in diagnostics settings, advanced, diagnostics push power to go to standby mode. Wait for the screen delay 10sec and the backlight comes on with the screen black. there other conditions when this happens but this is reproducable.
This happens when on battery too which would drain the battery at a faster rate than expected
Note: Screensaver should not kick in on Diagnostics (request from factory).
Minimal brightness setting for Radio is covered in bug #11851.
== Auto-comment from SVN commit #8224 to the jive repo by felix == == https://svn.slimdevices.com/jive?view=revision&revision=8224 == Bug: 14986 Description: Fix backlight turning back on after a while when using blank SS.
okay not reproducible as in comment 7. in 7.5.0 8445 it still does it in 7.4.2 8423
== Auto-comment from SVN commit #8726 to the jive repo by bklaas == == http://svn.slimdevices.com/jive?view=revision&revision=8726 == Fixed Bug: 16023 Bug: 14986 Description: only ignore the _activate() screensaver method to fulfill bug 14986 if the_screensaver is the same as the currently running screensaver I've tested this as correctly fixing bug 16023, and attempted to test that 14986 still works as desired. AFAICT, bug 14986 is still fixed, but I could use some independent verification of that one.
== Auto-comment from SVN commit #8727 to the jive repo by bklaas == == http://svn.slimdevices.com/jive?view=revision&revision=8727 == Bug: 16023 Bug: 14986 Description: checkin r8726 fixed 16023 but regressed the fix for 14986 I've adopted a new approach, which is to allow a ssName to come in with the service method screensaverWindow(), and that name is attached to self.current when that ss window comes to screen Then in _activate(), the check is for whether a screensaver is active and whether self.current == 'BlankScreen'. If those conditions are met, don't do anything (this fixes bug 14986). If those conditions are not met, go ahead and activate the SS (this fixes 16023). note that in most cases, by the time _activate() is called, self.current will have been set to nil because the ss from the previous mode (e.g., going from when playing->when stopped) will already have been popped from the stack. That's fine, as in this case we'd want _activate() to continue going about its business.