This is good to know. I was starting to wonder if I needed to downgrade the memory/SSD or upgrade the processor.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2nd MBP nTB with display issues--what to do?
- Thread starter ghanwani
- Start date
- Sort by reaction score
This is good to know. I was starting to wonder if I needed to downgrade the memory/SSD or upgrade the processor.
Yes, I also think this is good news.
BTW. I have a 64GB iPhone SE and an early 2011 MBP. What is it they say about great minds?
Having this same issue. Did a phone call, went to the Apple Store. They recommend to take it back to Best Buy for an exchange/refund.
Does anyone with the sleep/wake graphics issue (not the one above) run BootCamp? I do and I don't have any graphics issues on the Windows side.
The first thing that came to mind was that Apple had supposedly addressed issues like battery life and graphic problems with the 10.12.2 update:
https://forums.macrumors.com/thread...proved-battery-life-on-macos-10-12-2.2021719/
So now one perhaps wonders.
I'll tell you straight out that I do not like the 2016 MBP or the direction Apple is headed specifically with Macintosh as well in general. So that caveat. Yet can emphasize with anyone excited about an anticipated new Apple product, simply wanting it to do all the wonderful things advertised—without fail and without problems. Thus anything less is at minimum a disappointment.
Nevertheless—particularly in light of what it might of been—that Apple made too many compromises with the 2016 MBP. Witness the lack of legacy ports, undersized GPU, etc., etc. For that alone I would not recommend it. But even if one happens to be happy with the specifications of this computer, in consideration if it will provide a largely trouble free experience over its lifetime?
My feeling is, no. For one there is Apple's past regrettable history with Version A products and their seemingly inevitable teething problems both with hardware and software. If anything this seems amplified with the 2016 MBP. Perhaps much of this will get ironed out relatively soon, yet issues like the battery were baked into the hardware and no amount of software adjustments can fully compensate for their decision to significantly downsize the battery capacity from former models.
Then the issue with graphics. If Apple suggested 10.12.2 would solve such an issue and it has not, on what grounds does one retain their optimism?
Not to mention repairability, or lack thereof. The 2016 MBP is basically a disposable appliance. Most everything, including the battery, is glued into it. Given this, one will be entirely dependent upon Apple in addressing any issues remaining or new that come up. For three years, that is; after that you're on your own, and with what resale value God knows.
With all this in mind, my suggestion you forsake the 2016 MBP; return it to Apple for a full refund if you can. As replacement, you may be happiest with a 2015 MBP. They come and go, but the best option in this is to buy the model of your choice from Apple as refurbished.
So, yes, a hard pill to swallow if so. Your new computer gone to one used, and by some measures like SSD speed and the screen, less than. But also in more than a few respects better than, and quite possibly reliable (maybe all the more so if not using Sierra). Thus you could retreat with that to lick your wounds, yet salve in knowing yours are healing while others having retained the 2016 MBP could have such ongoing for who knows how long.
Wouldn't count on it, but the 2017 MBP—if there is one—might actually be something one would want to own for good reason.
https://forums.macrumors.com/thread...proved-battery-life-on-macos-10-12-2.2021719/
So now one perhaps wonders.
I'll tell you straight out that I do not like the 2016 MBP or the direction Apple is headed specifically with Macintosh as well in general. So that caveat. Yet can emphasize with anyone excited about an anticipated new Apple product, simply wanting it to do all the wonderful things advertised—without fail and without problems. Thus anything less is at minimum a disappointment.
Nevertheless—particularly in light of what it might of been—that Apple made too many compromises with the 2016 MBP. Witness the lack of legacy ports, undersized GPU, etc., etc. For that alone I would not recommend it. But even if one happens to be happy with the specifications of this computer, in consideration if it will provide a largely trouble free experience over its lifetime?
My feeling is, no. For one there is Apple's past regrettable history with Version A products and their seemingly inevitable teething problems both with hardware and software. If anything this seems amplified with the 2016 MBP. Perhaps much of this will get ironed out relatively soon, yet issues like the battery were baked into the hardware and no amount of software adjustments can fully compensate for their decision to significantly downsize the battery capacity from former models.
Then the issue with graphics. If Apple suggested 10.12.2 would solve such an issue and it has not, on what grounds does one retain their optimism?
Not to mention repairability, or lack thereof. The 2016 MBP is basically a disposable appliance. Most everything, including the battery, is glued into it. Given this, one will be entirely dependent upon Apple in addressing any issues remaining or new that come up. For three years, that is; after that you're on your own, and with what resale value God knows.
With all this in mind, my suggestion you forsake the 2016 MBP; return it to Apple for a full refund if you can. As replacement, you may be happiest with a 2015 MBP. They come and go, but the best option in this is to buy the model of your choice from Apple as refurbished.
So, yes, a hard pill to swallow if so. Your new computer gone to one used, and by some measures like SSD speed and the screen, less than. But also in more than a few respects better than, and quite possibly reliable (maybe all the more so if not using Sierra). Thus you could retreat with that to lick your wounds, yet salve in knowing yours are healing while others having retained the 2016 MBP could have such ongoing for who knows how long.
Wouldn't count on it, but the 2017 MBP—if there is one—might actually be something one would want to own for good reason.
Last edited:
Or just wait for a software update.
[doublepost=1481914455][/doublepost]
Interesting. For the sleep/wake graphics issue or another one?
I just opened the lid on my MBP after a long sleep and got the usual flashing distorted graphics. I paid more attention to the timing. It is in sync with the blinking cursor in the password box - not 1:1 in sync as it skips some blinks but definitely in time.
I don't know what can be concluded from this.
I don't know what can be concluded from this.
Problem is -- that didn't fix the issue for me. My second machine has the same issue.
I have found 7 videos on YouTube so far from different people with this same problem so it is pretty common. I bet a good number of people have the issue and don't know it. If you always shut down instead of using sleep or leave power connected etc. you may never see it.
BTW another characteristic for me is it often doesn't start blinking after opening until after I start to type in the password.
BTW another characteristic for me is it often doesn't start blinking after opening until after I start to type in the password.
Did you do a clean install on both machines or did you migrate on both machines? In case of a migration you should try doing a clean install instead and see if that still triggers the issue. If not then you don't have to go through the swapping mess.
Aside from installing Dropbox and an ad blocker, the machine was stock. That said, I think it get some of my browsing data from iCloud, but otherwise I don't use iCloud at all, other than for iPhone backups. I didn't bring over apps or data from my 2010 mbp.
[doublepost=1482185511][/doublepost]
Were all of those for nTB machine or were any TB machines affected?
I have the exact same issue. nTB MBP.
Seems purely software.
Quick facts : I dont have Adobe CC, No BootCamp, Did a clean install once (unrelated to this) without migration.
This particular bug doesnt seem at all related to the bug on 15' MBP with dGPU.
I am going to wait for an update, it seems clear right now that a switch or repair wont affect this, and honestly it's pretty minor (going to sleep and waking up always solve the problem, plus only happen when waking from sleep, doesn't affect day to day usage.)
Seems purely software.
Quick facts : I dont have Adobe CC, No BootCamp, Did a clean install once (unrelated to this) without migration.
This particular bug doesnt seem at all related to the bug on 15' MBP with dGPU.
I am going to wait for an update, it seems clear right now that a switch or repair wont affect this, and honestly it's pretty minor (going to sleep and waking up always solve the problem, plus only happen when waking from sleep, doesn't affect day to day usage.)
I'd have to check to be sure. Some were clear it was the nTB.
[doublepost=1482237917][/doublepost]
My sentiments exactly.
juanpenafoto - FYI. You accidentally edited your last post as if it was a quote from me.
Has anyone tried resetting the SMC and NVRAM to try to address this sleep-wake glitch? I did it last night and this morning I didn't get the glitch when waking the computer. Not sure if this one instance means anything...
Honestly, so far i've seen 3-4 videos of the "waking up" graphic glitch, yours doesn't look like it. I think it may be a totally different problem.
Bootcamp only use the amd gpu, and it is the intel gpu that has the errors that no one know if its hardware or software fault
Likewise on not seeing the problem every time. This is why I can't say the problem is fixed yet.
Update:- Well, the computer was asleep all night and again this morning I didn't get any glitch. Maybe we're on to something. I suggest you give it a shot...
Update:- I just woke the laptop from a several-hour sleep and the glitch was back.