Macbook - problems to connect w external screen

Yes it does.

I'm having trouble with the HDMI output on my MacBook 2016 too,

here is the thread I've created:

Macbook 2016 HDMI output flickering

I'm having the same, or very similar, problem like you have described with my MacBook 2016, it doesn't happen on the older MacBook 2015...

wow, I'm having the exact problem and questions...

It could be that this problem is fixed with the newet update 10.11.6

I still have the same problems with my Acer HU 277

I also have a similar problem:

External monitor flickering Macbook 2016

It seems to matter what monitor I use (my Dell has problems, my samsung doesn't).

Also it seems more stable in Mirror Displays mode.

For the record - the problem unfortunately isn't fixed with the update.

At least the problem with my setup (MacBook 2016 with the Minix Neo USB-C HDMI Adapter) is solved.

I had to install the Minix firmware update and now the external display is stable since at least 30 minutes.

Minix Firmware: http://www.asix.com.tw/download.php?sub=driverdetail&PItemID=131

Maybe Apple has to update the Firmware for his own adapter, or the fix comes with macOS Sierra.

Having the same problem. Incredibly annoying.

i have exactly the same issue. i cannot work with the macbook on an external display. every 2 minutes it will go to black for 15 seconds.

its also too unreliable to use for presentations.

we have more of these at the office and they have the exact same issue.

apple seems to be ignoring the issue.

i tried apple's hdmi out dongle, a display-port cable, a docking station and a 3rd party dongle.

no luck...

I have the same issue, resetting SMC/NVRAM does not help. This is very distracting, it is impeding my work, making it impossible. There seams to be no solution to that issue anytime soon.

Could I return my Macbook 2016 and get reimbursed? Any ideas? I am still under warranty and have AppleCare.

This is obviously a faulty product not performing up to its intended purposes, rendered useless to my purpose. It seams logical I should be able to return it.

I am so annoyed and put down by this issue, that I consider moving back to PC after a decade of Mac-use. PC's now have touch screens, at least.

Resetting NVRAM works for me until something corrupts it again. Then I need to reset it again and it works.

My suspicion, and it's a bit of a guess, is that if I close the computer, switched on, with the external monitor plugged in, that's when it gets confused/corrupted. When I get back to my desk and then plug the external in again it goes black every 2 minutes for 15 seconds. It drives me nuts.

Resetting the NVRAM with command Option P R will fix it again.

However after resetting NVRAM And it's working normal.again, If I unplug the external monitor first and then shut the Macbook down or close it I can plug it back in and it works normally.

This is terrible and very un-apple.

I now reset the NVRAM every morning when I get to the office and then it works smoothly.

I don't think what I have here is a fix but I hope it helps others to get a flicker free days work.

Same/similar issues with my brand new '16 macbook and the apple hdmi multiport adapter.

Doesn't work on any of my three monitors of various ages and resolutions. EXCEPT, it does work on my vizio 4k tv ONLY in the single hdmi port supporting 4k @ 60khz. This is funny because the macbook and adapter only support 4k @ 30khz, and won't display at all when plugged into a port with the 30 khz refresh rate.

I personally think this is a hardware thing -- my guess is the display chip in the computer.

But I had a thought: my friend just went through 3 rose gold macbooks to finally get one that didn't have the spacebar break within the first day... We thought maybe it was an assembly line issue on the rose golds of the same batch. I have the regular gold macbook and so does my brother who also has the same display issues... what colors macbooks do you all have with this problem? maybe there's a correlation?

Good point. My is pink macbook'16 (i.e. rose gold). It could be a software issue.