Here is a potential workaround solution for now (as this came from a user in Piunkaweb.com), as I have noticed in the past nearly hour (as of this writing) of usage that there has not been any screen flickering from my Mac or from the 2nd monitor. It is as follows:
A) While the Mac is up and running, connect the monitor to the Mac.
B) Then, disconnect the monitor's power source from the power outlet ONLY. I waited about 10 seconds or so.
C) Then, connect the monitor's power source plug back into the power outlet. Important Note: DO NOT disconnect the USB-C cable (or dongle) from your Mac at all. Leave this in place....
D) Then, I went into the Displays area of System Preferences, and set the screen resolution of the display to "Default for Display." In the Displays dialog box, it should show "Looks like 1920 x 1080".
All in all, it seems that this latest update in Big Sur (11.1) has broken support for all 4K monitors, perhaps making this one of the worst bugs in macOS that I've probably ever encountered to date. According to other users, any resolutions that are displayed above 1080p resolution is bringing forth a problem in screen flickering. Thus far, I haven't seen any flickering issues with the Mac or the 2nd monitor since doing this.
I am currently "cautiously optimistic" that this is a workaround solution to this problem, as I never had any problems with screen flickering in all the years that I have owned a Mac (going on 16 years now!!!), that is, until the 11.1 update to Big Sur. I must say: This is an absolutely unacceptable situation, given the fact that many of us have spent thousands of dollars on our machines, only to have a problem like this occurring. This affects people very adversely in that making professional presentations can be a problem with our own Macs, along with doing professional work on these machines.... So, in the meantime, I don't plan on updating Big Sur until a) I see that Apple has solved this problem, and b) that other users in the Apple community are seeing that the latest updates do not cause this problem any longer....
Topic:
App & System Services
SubTopic:
Core OS
Tags: