Bugzilla – Bug 9050
Boom display brightness should not change during setup process
Last modified: 2009-09-08 09:25:45 UTC
The issue: Boom display brightness changes as soon as it starts communicating with SN. The display brightness picks up the default values in SN and changes while the user is trying to read the PIN. The display brightness value should not change until after the player has been registered with SN. See bug #8920 for more information.
Mike: Was there a problem where the screen wasn't readable or was this a cosmetic issue? (Note that the device _is_ connected to SN when it displays the PIN.)
Felix mentioned in yesterday's bug meeting that the screen will dim at inopportune times during the setup process. He was aware of the issues, and I thought we had concluded that Felix knew what to change and where? Felix -- can you confirm that my memory is correct?
If the PIN is unreadable, we have a more serious problem, which is that the PIN screen isn't special in any way (it's just a connected screen) and any screen from SN or SN will be unreadble.
It is correct that I know what could be the issue, but I don't know what the proper solution should be. As Dean states the PIN screen is just a connected screen which means the display brightness might change from what it was while in setup. Here is what I think happens: When Boom (actually any player with display) is powered up and setup, firmware seta a fixed brightness (i.e. not using the ambient light sensor). This means the brightness is stable during setup until when the player connects to SC or SN at which point the brightness gets set to whatever brightness level (including automatic) which is set for that player or in case of the PIN screen I guess whatever the brightness is set for new (never before) connected players. Now, dependent on the ambient light the player sits at that very moment it might happen that the brightness changes. If the player is in bright environment the brightness does not change, but if it's evening and the light in the room isn't turned on yet the brightness most likely will go down as the ambient light sensor is doing its work. I believe the issue is not that the brightness can/does change or that it is too low for the particular environmental situation (if that is the case, that's another bug), but that it changes exactly in that moment when important information (PIN) should be read from the screen. To solve this I could see three possibilities at the moment: - Use a lower fixed brightness in fw during setup so the chance of a change is lower (but might still happen in either direction) - SN does not update the brightness setting (i.e. change from fixed to automatic) for the PIN screen (but be aware that the brightness might change on subsequent connections). - The brightness default for new players on SC/SN is not automatic, but fixed (which the negative chance that some users might never find the automatic setting)
Keeping this at 7.2 target to make sure we don't lose track.
If anyone is still seeing this on recent HW and firmware, please re-open.
Verified fixed in SqueezeCenter 7.2-22900 Boom r32
This bug has been fixed in the latest release of SqueezeNetwork! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.