Bugzilla – Bug 8280
Screen very dim after initial setup - During firmware update
Last modified: 2009-09-08 09:21:44 UTC
After the initial setup, the screen will go to a very dim (1) setting. This makes it very hard to see, and people may think the device has shut off This happens when connecting to SN
I have not noticed this problem when connecting to SC, only SN
(In reply to comment #1) > I have not noticed this problem when connecting to SC, only SN > Ignore the above, it happens on SC 7.2 - 20285 as well as SN r3676/r20309
this should be better after recent fixes to the defaults around change 20390. As the defaults are the ambient sensor, make sure you aren't in a dark room or you will get dim output by design.
James and Felix to look at this after the meeting.
James will investigate the different light sensor / filter options
This issue was also found during CAT testing, especially when doing the firmware upgrade: ======= Description * When connecting to the SqueezeNetwork the first time the unit updates its firmware. When it does this it displays an "Updating Firmware" message on the screen. It is so dark that I couldn't see it from a few feet away and thought that it had frozen. For most hardware it would be very bad to shut it off in the middle of a firmware update. I'm only assuming that it would be the same here. Even if not it would be nice to know what it's doing and therefore a brighter message would be nice. Steps to Duplicate * I was, of course, unable to duplicate the problem as the firmware only needs to be updated once, but this is what I did. Take a non-updated Boom and connect it to the SqueezeNetwork. At this point the newest firmware should download and install, when it does this it should say "Updating Firmware". I believe that the message isn't bight enough during this. ======
Felix, this doesn't really seem like a firmware issue, is it? I have increased the severity due to the fact that so many users have complained about it.
I think it has to do with different code in SN/SC and firmware offered. The brightness of the display depends on various parameters: - Firmware - SC/SN - Lens (PQP1, PQP2 and PQP3 units have different lenses - front panels) - Lightsensor ( prePQP3 and PQP3 units have different light sensors) - Ambient light All this makes it very difficult to come up with a proper formula/parameters to calculate the brightness of the display and buttons. This is the current formula: brightness = lightsensor / divider + offset The divider and offset have default values in firmware and can be changed from SC/SN. I think this is what happens: - Boom with firmware A boots up, setup uses a fixed brightness at that stage - Boom is connected to SN which might change divider and/or offset - Boom does a firmware upgrade (using the new divider and/or offset) - Boom reboots with new firmware B (using fixed values again) - Boom reconnects to SN which again might change divider and/or offset Any ideas how to make this less complex are very welcome.
BUG 8237 may be related to this bug
*** Bug 8373 has been marked as a duplicate of this bug. ***
Set maximum brightness during firmware upgrade so the progress bar and message can be read (i.e. do not use ambient light sensor value during fw upgrade). Fixed in rev4534. Will be in Boom fw 19.
Verified functioning properly with r19 & 7.2-22118
This bug has been fixed in the 7.3.0 release version of SqueezeCenter! Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already. If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.