Q: Macbook 2016 HDMI output flickering

Yup... sounds like the exact same issue.

Apple have sent me a program called "Capture Data" that does a comprehensive log of the system and they've asked me to run it while the problem is happening - which I've done. Hopefully it will have caught the issue and they can patch it.

-ambanmba

Thanks for posting! I was already wondering if the OWC dock might fix the issue but obviously not. Looks like many people have the problem and have tried various different USB-C adapters, HDMI cables, and monitors without any success. So, let's hope Apple will provide a fix....

Thanks for the tip!

I now also can use the external screen consistently in a stable way! A full power-off/on of the MacBook connected to the monitor and I do not let the monitor go to sleep (or turn off or switch inputs).

It only works (for me) when the laptop isn't sending anything to the monitor at all.  Otherwise you're right

I've started using InsomniaX app (disable idle sleep on AC) and it's been flawless for 12 hours now.  Not very energy efficient though!

You can get the program here: http://ac-netstorage.apple.com/SendFiles/Capture_Data.dmg

But unless you know what you are doing with the logs, it's not much use. Once you capture the logs, you are meant to send it back to Apple using a link that they supply (that is linked to your case ID #). It's also a one-time use link that has to be re-issued when you send them the log.

-Ambanmba

I also got this problem.

Have tested with two different macbook 2016 with the official apple usb-c -> hdmi adapter and the problem is the same on both. Everything is up-to-date(10.11.6 osx and 2.33 on multiport although under graphics it says 2.35?).

A full restart or/and PRAM works until next sleep as stated from others aswell.

My screen is a Samsung S27C650 with resolution 1920x1080 and i only have the screen on the external monitor.

Hope apple can figure out a solution soon, kind of annoying when the screen goes black for a sec.

I dont know if its even related but my external screen also got blurry text everywhere.
Ran defaults -currentHost write -globalDomain AppleFontSmoothing -int 2 but it did minor improvments.

Has anyone else noticed that if you tolerate the display issues after several hours it leads to general instability, hang ups and you end up having to force reboot anyway? I've had it a few times now. It's wildly annoying. Think I might speak to Apple about it tomorrow as it's impacting usage pretty significantly.

I know Apple fixed a memory bug in 10.11.5(which really annoyed me) so if you dont run the latest version i would suggest you update.

You can run "top -o cpu" in a terminal to identify which application is stealing cpu-power, if its idle and you still got problem, then there might be a memory issue. Could be related to bad drivers if you are not using the official multiport.

Back to your question, no, atleast i havent experienced any symptoms that you describe yet. Maybe others could verify their experience to see if you need to open another case to Apple about it.

Apple has now sent me a program called Timing Snoop which does all sorts of detailed logging on the video settings. They had me delete the following files:

com.apple.windowserver.plist (in Macintosh HD\Library\Preferences\)

com.apple.windowserver.*.plist (in user\Library\Preferences\ByHost\)

They also had me reset the PRAM.

I then rebooted and triggered the flashing screen problem then ran Timing Snoop, then rebooted (thereby solving the flashing screen issue) and ran Timing Snoop again and I then sent them the log files.

I also did a file compare on the two log files and you can see that there is a definite difference in the driver timings. This is good because it brings us a step closer to solving the issue (we just need to figure out what is causing the incorrect driver timings).

To whet your appetite, attached is a screen grab from comparing the two files. The "Flashings" settings on the left and the working settings on the right. There is actually a lot more that is different, but this gives some insight into the issue.

-ambanmba

Thanks for sharing with us and updating Apple about the issue.

Hope to hear a solution soon