Currently Being ModeratedNov 17, 2012 5:39 AM (in response to DopeyRanger)
I have a similar, but more serious, problem. My 2012 MBA as of this morning will not light the display. The proper screens are present and can be seen when I shine a light through the apple on the lid, but the backlight won't come on. When I restart, the backlight flashes momentarily, then remains off. Battery is fully charged. It's on the current release of Mountain Lion.
Currently Being ModeratedNov 17, 2012 7:29 PM (in response to DopeyRanger)
I have this exact same issue, and it happens to me frequently (multiple times a week, today 2x). Can't reproduce on command, but usually after periods of sleep (anywhere from overnight to 1 hour). Unable to find other people with this issue online, but I'm going to the Genius Bar tomorrow with recorded video evidence. You might want to do the same after backing up — it may warrant a replacement.
Currently Being ModeratedNov 17, 2012 8:03 PM (in response to DopeyRanger)
Currently Being ModeratedNov 17, 2012 8:18 PM (in response to mcsound)
Just did that, will report back on effectiveness.
Currently Being ModeratedNov 18, 2012 7:38 AM (in response to DopeyRanger)
I found a workaround to this problem. What I did was, I set the screen timeout value to be the same as my sleep timeout value. So when my screen times out, my MA goes to sleep. This problem does not persist for sleeps, it only holds for screen timeouts.
Until Apple bring out an update, this is a good workaround.
Currently Being ModeratedNov 18, 2012 10:10 AM (in response to DopeyRanger)
That's what I had before, and it was having the problems constantly. Anyway, will report back after Genius Bar visit.
Currently Being ModeratedNov 26, 2012 8:39 AM (in response to DopeyRanger)
I took it to the Genius Bar, and they identified it as a hardware issue. Just got it back today. Parts replaced were:
620-5629 Display Module — Symptom: Distored/blurred/focus video issue
605-3284 Top Case with Keyboard — Symptom: specific key(s) do not work
So far so good. I'd suggest taking it in and not trying to work around it — it's a rare hardware issue (given the number of threads about it) and should be replaced.