My base model 13" nTb with 10.2.1 was doing the blinking thing too when I woke it from an overnight sleep so I returned it.
I woke the computer from an extended sleep this morning with 1440X900 resolution with no issue. Will try again tomorrow...
Another awakening from 1440X900 this morning without issue.
Another awakening from 1440X900 this morning without issue.
It's been a little over two weeks and I still have not experienced the wake up glitch on 1440x900. I realize default for display and scaled 1440x900 are the exact same thing, but I think there's a possibility they may be different in relation to this potential software bug and wanted to state that I'm using the default for display radio button.
Have any others initiated a case with Apple on this? I did a few days ago. It is case #100095456915 if others would like to reference it. It might be good to have strength in numbers.
I created a case back on Dec 7 and have not heard anything since... They tried to say the upgrade would fix it. And after the update didnt fix it, i was told to "Go into settings, under the energy save tab, and to turn off sleep so it wouldnt happen again." After a lengthy discussion of how that ruins the battery and such, Engineering has never reply. Supposedly my case was resubmitted today as a "high priority." My Sen Adv said im guaranteed a response within 24 hours.. so Im hoping this gets resolved tomorrow.
80% of the threads in this subsection are devoted to defects, bugs and documented complaints about this revision.
Keep us posted.
whatever resolution the computer came with from the factory (I never adjusted it)What resolution were you running at?
whatever resolution the computer came with from the factory (I never adjusted it)
Keep us posted.
View attachment 681965 View attachment 681966 View attachment 681967
This was what engineering came back and said to do...
Just my opinion, but I think we need to take a hard line. I don't think anyone should be content to return their MacBook until someone at Apple understands the problem and can assure us that the replacement is sure to solve the problem. If the root cause indicates the solution is a software or driver fix anything else is an exercise in futility.
But seriously, it this a job for us or for Apple Inc.? How hard is it to get a MacBook with this issue in the hands of a competent Apple engineer or team of engineers to troubleshoot? They have several of them from people in this thread alone. They need to determine the root cause, not us. Why do we need to do anything for them?
I don't think anyone should be content to return their MacBook until someone at Apple understands the problem and can assure us that the replacement is sure to solve the problem.
If the root cause indicates the solution is a software or driver fix anything else is an exercise in futility.
[doublepost=1483837024][/doublepost]That's interesting. Mine has been doing it more the last few days. Coincidence, or ???My machine started having the problem with shorter and shorter sleep events. I ended up returning the machine today.
I'm thinking I will try one more and if that doesn't work right I will consider trying a TB one.
My machine started having the problem with shorter and shorter sleep events. I ended up returning the machine today.
I'm thinking I will try one more and if that doesn't work right I will consider trying a TB one.
That is interesting that your display behavior is changing. I have the Touch Bar model and still get the pixelated login display for 5 - 10 seconds every morning after wake up from overnight sleep. Apple must have several returned laptops with this problem to identify the cause. I plan to contact Apple support, summarize the experience on this thread, and ask them to refer the problem to engineering for a resolution.
Thanks for posting. At least we now know that going to TB won't help.
My guess is that engineering is probably several stages removed from the support folks that we have access to. The best we can hope is that the support folks accurately document the problem. The worst that can happen is frustration with the rep's inability to grasp what is happening. I saved myself the chance of a bad support experience. I try to deal with them only when absolutely necessary.
At the time of returning, they did not even ask why I'm returning. I told them there's a defect and used RCFlyers's case number but the rep wasn't interested and said the tech support folks will figure it out. I have no idea what they will figure out on a machine that they don't know is defective!
Got this on the 1280 resolution a few weeks ago while I was waiting at the Apple Store for another issue. I had Genius Bar test it out and they said all tests were fine.
Only had it once since until this morning when I logged in and saw it again (kept overnight in a place where was low 60s F).
...Edit: base nTB. I installed 10.12.3 beta after to see if this will help. Will report back (probably tomorrow morning)