- Switch the USB-C port from one to another - Open up my laptop from clamshell mode and switch the cables around - Unplug my monitor - Restart my computer
The nuclear option of rebooting my computer and monitor always seems to work.
I know its a problem with the macOS somewhere but Apple just doesn't seem to be focused on fixing these types of things. Even if you file a bug report it disappears into the ether and is never heard from again.
but hey at least it works. on my linux laptop it allways forgets the layout that i had and resorts to puting the external monitor right, and dont ger me started on X and fractional scalling.
Scaling is a mess though, totally agree with that.
i dont know why it does need to run the external monitor to 2x if i want 1x. and i lost way to much time playing with the setup. ubuntu 1904, if you have any new ideas im willing to try it.
For proper mixed dpi under Linux, you must use Wayland. But then, under Wayland, the fractional scaling is still not done (the wayland apps will work fine at given fractional scale, but x11 app will be @1 upsampled, i.e. blurry. That includes the browsers).
(No, I don't know why it still isn't fixed yet.)
i cannot run it at 200, 150 is perfect, i need fractional scaling
Last year I had a lot of problems with this. It was pretty common[1] that USB-C to HDMI cables would work at first and then stop working in a particular port. Sometimes rebooting helped. Sometimes swapping the cable for another in the same port helped. Sometimes using another port immediately helped. There was never a good explanation for why this was happening; most resources blamed the cables. After some software update last year, suddenly all these bad cables are fine in any port.
As of this summer, there's a shiny new issue where connecting to GMail (at least) from System Preferences doesn't work, which I discovered through changing my password recently. SysPref claims it needs to open a Google login in Safari (even though that isn't my system browser!), but when Safari opens, it's to a blank page. Again, searching makes this seem like a pretty well-known problem, but no one has a solution, and Apple seems silent on it, and enough people do not have the problem that a common response is that those of us experiencing the issue must be doing or have done something wrong. And maybe we are(!), but I'd sure like to know what.
> 3. If you have a tech support issue go into the Apple Store and work with them 1-1.
Well, that literally hadn't occurred to me (for problem 2, above); I would have assumed store employees don't know anything one couldn't google immediately?
[1] I was quite annoyed that this went on long enough for me to have an opinion like "pretty common" for these connections not to work sometimes, over more than half a dozen such cables.