3. Run all apps only on the monitor not the laptop screen.
Could you describe exactly how you do that?
3. Run all apps only on the monitor not the laptop screen.
The dGpu drew 20W~21W in the process while the cpu remained below 10% usage. Entire right side (where the dGpu is located) is too hot touch while the left side (where the CPU is located) remained relatively cool.
And to even think that the MBP 16 supports up to FOUR 4K displays when even one 4k display is enough to cripple it.
It won't go to 80W because you attach 4x 4K screens. As I understand it, it hops to 20W and sits there no matter how many screens you connect. It's only when you start using all the processing power of the GPU (e.g. 3D graphics or AI) that the power will go beyond 20W.
Could you describe exactly how you do that?
Not at all! I used the "trick" with SwitchResX mentioned here to get my external screen working, in clamshell mode, at 5W or less. The problem seems to be that once there is more than one screen managed by the GPU (so not via AirPlay like an iPad in SideCar), then the Radeon kicks in at full throttle because it can't work with different clocks for the two screens. It's a crappy way of doing things and it should be fixed. But I agree with Apple that it's not the most important. My MBP16 has been crashing for no reason at all because of the GPU panics (PowerPlay failed to resume) and it makes it hard to use the computer at all. Not just less optimal.Thanks for the clarification! May I ask, is it normal for a MBP 16's dGpu to use about 20W regardless once an external display has been connected?
Although this isn't exactly regarding the current topic: I also often had the "PowerPlay failed to resume/initialize" error (even after full reinstalls). I just returned my MBP (through Amazon) and got another base model which didn't have any issues (even on the same OS versions) in the last couple of months. (Ofc still has the 20W issue mentioned here)Not at all! I used the "trick" with SwitchResX mentioned here to get my external screen working, in clamshell mode, at 5W or less. The problem seems to be that once there is more than one screen managed by the GPU (so not via AirPlay like an iPad in SideCar), then the Radeon kicks in at full throttle because it can't work with different clocks for the two screens. It's a crappy way of doing things and it should be fixed. But I agree with Apple that it's not the most important. My MBP16 has been crashing for no reason at all because of the GPU panics (PowerPlay failed to resume) and it makes it hard to use the computer at all. Not just less optimal.
Not at all! I used the "trick" with SwitchResX mentioned here to get my external screen working, in clamshell mode, at 5W or less. The problem seems to be that once there is more than one screen managed by the GPU (so not via AirPlay like an iPad in SideCar), then the Radeon kicks in at full throttle because it can't work with different clocks for the two screens. It's a crappy way of doing things and it should be fixed. But I agree with Apple that it's not the most important. My MBP16 has been crashing for no reason at all because of the GPU panics (PowerPlay failed to resume) and it makes it hard to use the computer at all. Not just less optimal.
Not at all! I used the "trick" with SwitchResX mentioned here to get my external screen working, in clamshell mode, at 5W or less. The problem seems to be that once there is more than one screen managed by the GPU (so not via AirPlay like an iPad in SideCar), then the Radeon kicks in at full throttle because it can't work with different clocks for the two screens. It's a crappy way of doing things and it should be fixed. But I agree with Apple that it's not the most important. My MBP16 has been crashing for no reason at all because of the GPU panics (PowerPlay failed to resume) and it makes it hard to use the computer at all. Not just less optimal.
This is soo true. We paid for a top tier laptop, we shouldn't be resorting to using third party programs and disabling software. Hope one of these days Apple makes an announcement about this or something, cause this is ridiculous.While I agree that it's not the most important issue, it has been 7 months since launch. I'm starting to think that Apple is just unable to fix this. Deeply disappointed with how Apple handled it. The thermals for the MBP 16 is already less than stellar to begin with. Adding this into the mix just further complicates it.
We users of MBP 16 (which is a >$2400 machine) should not resort to using a 3rd party app to keep the temperature in check. The buggy release of Catalina is just a final nail to the coffin.
This is soo true. We paid for a top tier laptop, we shouldn't be resorting to using third party programs and disabling software. Hope one of these days Apple makes an announcement about this or something, cause this is ridiculous.
Don't get your hopes up. I've been told by multiple senior advisors that it is working as intended. But with further testing in my office with an eGpu (5700XT) connected, identical external display and connection method, the 5700XT sips around 11W~15W. Far less than the dGpu (5300M) which is 20W in an open lid test.
Mind you that's a full fat desktop 5700XT consuming less wattage on idle as compared to a 5300M powering the same amount of pixels.
This is soo true. We paid for a top tier laptop, we shouldn't be resorting to using third party programs and disabling software. Hope one of these days Apple makes an announcement about this or something, cause this is ridiculous.
Don't get your hopes up. I've been told by multiple senior advisors that it is working as intended.
新显卡的发布意味着以前的外接显示器问题已经解决?
Here is my interpretation of the situation:
1) We external monitor users are a minority of 16" MBP owners, maybe 5% (pulling numbers out of my a$$).
2) Of those 5%, not many will know that there's a problem with dGPU power. Heck, I consider myself pretty computer savvy but unless my (soon to be purchased) 16" MBP had blasting fan noise under low usage conditions, I seriously doubt I would know about this problem without this thread.
3) The "working as intended" bothers me. I could see that meaning it's a fundamental design and spec problem. Maybe Apple has a spec about max power draw for dGPUs under load when connected to the mains, but nothing about consumption at idle. Maybe it's a problem that Apple can't fix itself with the drivers, and it's a code for AMD needs to fix the problem, with the $2.4K question being whether it's a hardware, firmware or software problem.
1) I have no research or evidence whatsoever to back my opinion up but am fairly convinced that more than 5% of MBP16 owners are using external monitors. I'd estimate somewhere between 25-40%.
Currently dealing with the same issues as everyone in this thread. My Apple store in NJ is opening tmrw and I was able to get a Genius Bar appt before all the slots got taken. I’ve been dealing with this for weeks and am still in the return period for my machine. I’ll report back what the Genius Bar comes back with. Anyone have any suggestions on what exactly to tell them? Want to make sure I do this problem justice by pointing them in the right direction.
@AFPBoy I think it really depends on "work environment". I'm a developer and everyone in my office has a company laptop and I'd say that 90% of those use an external monitor AND the laptop monitor. That 10% is when people are in meetings, or working in the lunchroom at just the laptop. lol
Currently dealing with the same issues as everyone in this thread. My Apple store in NJ is opening tmrw and I was able to get a Genius Bar appt before all the slots got taken. I’ve been dealing with this for weeks and am still in the return period for my machine. I’ll report back what the Genius Bar comes back with. Anyone have any suggestions on what exactly to tell them? Want to make sure I do this problem justice by pointing them in the right direction.