Bug 15365 - SB2 with blank "off" display does not show firmware upgrade message, appears dead
: SB2 with blank "off" display does not show firmware upgrade message, appears ...
Status: NEW
Product: SB 2/3
Classification: Unclassified
Component: Graphics
: 130
: Macintosh MacOS X 10.4
: P4 minor (vote)
: ---
Assigned To: Felix Mueller
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-23 04:44 UTC by Daniel Barrett
Modified: 2011-01-14 00:42 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Barrett 2009-12-23 04:44:52 UTC
I have my squeezebox V2 configured to have a blank display when turned off. When the Squeezebox Server software is upgraded, the SB2 screen SHOULD display a message about a firmware upgrade and to "press and hold the Brightness key." However, it does not -- the SB2 screen stays blank, no matter what keys are pressed on the remote. To the user, this makes the SB2 appear to be dead.

Pressing and holding Brightness does the right thing -- initiates the firmware upgrade -- but unless you know what to do, it's confusing for the user.  Frankly, it's fooled me twice -- I thought my SB2 had been killed by the server upgrade.
Comment 1 Michael Herger 2009-12-23 05:26:44 UTC
I doubt this is going to happen. We have had people shout "I'll sue you!" at us because we displayed network outage messages on their display on the bedside table... But that's just my thought...
Comment 2 Daniel Barrett 2009-12-23 05:38:45 UTC
Well, if you won't show the firmware upgrade message, can you at least make it appear if someone presses the power button?
Comment 3 Michael Herger 2009-12-23 06:10:55 UTC
> Well, if you won't show the firmware upgrade message, can you at least  
> make it appear if someone presses the power button?

Excellent point.
Comment 4 Alan Young 2010-05-07 10:49:27 UTC
Is this a duplicate a bug 4329.
Comment 5 Daniel Barrett 2010-05-07 12:51:40 UTC
It may be a duplicate, but please don't lose my suggestion (comments #2 and #3 here) about using the power button, which I think is a better solution than those discussed in bug 4329.