Bugzilla – Bug 9404
Auto Brightness not working
Last modified: 2009-02-21 09:57:31 UTC
Auto brightness used to work on at least one of my two beta Boom units (I think both of them, but can't remember for sure). Auto brightness is now not working on both units. When I select "Automatic" brightness, the display is at full brightness all of the time. I am using 7.2/trunk, currently SVN 23048, but it has not worked for me for several weeks. I have removed all third-party plugins.
What version beta units do you have? There was a hardware change during beta to a different ambient light sensor. The current Boom firmware only supports the latest sensor. In my case, a PQP3 unit works, but a PQP2 does not.
I don't know how to determine the version of each of my beta units. I know that I have an old sensor in my first unit, and a new sensor in my second unit. On both units, the factory test shows the sensor number changes when I put my hand over the sensor. My first unit reports Board Revision 00 03, the second one reports Board Revision 00 26.
If you go to 'Current Settings' - 'Factory Test' - 'Ambient light (lux)' you should see something like "b @ 0/10+2=2 +0=2" in a complete dark room. The first entry tells about the lightsensor: 'b' means new (current), "1" means old (not supported anymore). The number after the '@' is the value the lightsensor reports. What do you get in a complete dark room? Should be 0.
Felix, I think a lot of us Beta testers would really appreciate it if support for the older sensors could be added back in a future firmware release.
In a dark room, I see "b @ 164/10 + 2". When I turn the lights on, it goes up to "b @ 1530/10 + 2".
Caleb needs to do tests with the spectrometer and felix needs to define the pref and michael needs to make a slider in the UI for the dim-light brightness setting.
In general I have not heard any new complaints about auto brightness on Boom not working since my change in fw 33. Caleb: What is the plan with the spectrometer? Philip: Do you still have issues with auto brightness and the latest Boom fw?
I just responded to bug 9353. Looking better at the moment.
Added minimum and sensitivity settings (web, player ui, jive) for automatic brightness. (SC 7.3 rev23687) Minimum brightness setting allows to configure the brightness when the room is dark. Sensitivity setting controls how much light is needed to get a particular brightness level. I.e. if set to minimum more light is needed for full brightness and if set to maximum less light is needed for full brightness. Currently (up to SBB fw 37) when changing one of the two settings you need to wait about 4 seconds for the change to become effective. A small firmware change (already commited - rev5052 - SBB fw 38) will enable immediate visual feedback.
Michael: I've added two sliders to the web ui etc. Could you please check what's needed in addition to make them work on SN, thanks.
change 4955 - add Auto Brightness settings to SN. No sexy sliders, but working.
I am unable to verify auto brightness, as there appears to a disconnect between Boom UI > and SN/SC Web UI On SN WEB UI: Minimal Brightness (Automatic): has a range of 1-7 ON Boom UI: Minimal Brightness (Automatic): has a range of 1-5 On SC 7.3 WEB UI: Minimal Brightness (Automatic): has a range of 1-5 When I have my player attached to SN and the minimal Minimal Brightness is set to 6,7 then the boom does not respond to the light sensor. When I have my player attached to SC and the Minimal Brightness is set to 1-5 then the light sensor works properly. PowerOn / PowerOff / Idle all set to Automatic
change 5239
Marking SqueezeNetwork bugs as closed. The latest version, r5879/r25112 should have fixed this issue. If you still experience the listed problem please feel free to reopen the bug.