Open GoogleCodeExporter opened 9 years ago
Cannot reproduce:( do you still have the issue?
Original comment by integral...@gmail.com
on 23 Apr 2012 at 10:16
Original comment by integral...@gmail.com
on 23 Apr 2012 at 10:32
I do still have this issue. I should have noted before that FileVault is in
use. The computer must be restarted to relight the keyboard.
Original comment by cind...@gmail.com
on 23 Apr 2012 at 3:34
Hitting F5/F6 turn the keyboard backlight back on for me.
Original comment by sattya....@gmail.com
on 26 Jun 2012 at 11:40
I have seen this too under 10.7.5 on a Mid 2011 MBA 11", pushing either F5 or
F6 brings the backlight back on. However this seems to be related to the
automatic control of the Keyboard backlight and not related specifically to the
extension.
I suspect but have not been able to confirm that all "Ambient Light Sensor"
functions are impaired (ie things that use the iSight camera to determine how
dark the room is)
Original comment by b...@qsterx.com
on 20 Oct 2012 at 7:18
Well that was dumb of me, used the LED on my iPhone to test, it's not
refreshing properly when the screen comes back on, applying any change in light
to the sensor that would trigger a change in the level causes the backlight for
the keyboard to snap back.
Also can confirm (on AC at least) that the Ambient Light Sensor itself is
working properly on Lid Open but not the automated controls, they seem to
activate but not make changes until there is a shift in the light level.
Original comment by b...@qsterx.com
on 20 Oct 2012 at 7:22
Yes, I am finding exactly the same probelms as noted above.
I did not see it for the first few months of use. Perhaps a few roundabout OSX
updates changed this.
Original comment by david.es...@gmail.com
on 11 Oct 2013 at 7:01
Confirming this in Mountain Lion with 1.3.3, will post again if behaviour is
noticed in Mavericks.
Original comment by chri...@ichristo.com
on 24 Oct 2013 at 3:39
I have this issue for some time on Mavericks
Original comment by koste...@me.com
on 21 Jun 2014 at 2:09
Original issue reported on code.google.com by
cind...@gmail.com
on 16 Mar 2012 at 2:46