4 ms·

My favorite is I have an HP Envy USB-C monitor to use with my Macbook, and using the HP factory supplied cable, every time I power it on I get a warning that I

by lbotos 9y ago

My favorite is I have an HP Envy USB-C monitor to use with my Macbook, and using the HP factory supplied cable, every time I power it on I get a warning that I should use an "official HP USB-C cable". It's literally the one straight from the box!

lou1306 9y ago
What they meant is that you should use an official HP Envy laptop :)
LanceH 9y ago
My macbook won't wake up my usb-c monitors consistently. I have tried 8 cables at this point. I have to unplug the cable and plug it back in. I also refuses to mount my phone straight usb-c, and the known workaround is to go usbc -> a -> c. At this point in my relationship with Apple, I can only assume this is deliberate.
- indecisive_user 9y ago
  So _that's_ why my monitor doesn't wake up. I got the new xps13, it only has thunderbolt/USBc-C ports and it's pretty much 50/50 whether my external monitor will wake up. I figured it was the cable and was about to buy another one but you saved me the trouble. I also got a hootoo adapter that's supposed to support power delivery but that hasn't worked either :/
  - olyjohn 9y ago
    This isn't just a problem with USB-C. There are also tons of video adapters on the market that say they support 4k, but really don't. We have grips of 2560x1440 monitors at work, and they had tons of issues like this where the monitors may or may not wake up, may handle the native res for a while, then power down or switch back to 1080p. The only consistent fix for them has been to buy one particular brand of adapter that we found works and making sure it's active. So I guess what I'm saying is, display tech has already been having issues for a long time with crappy components, and USB-C is just adding one problem into the mix now.
lkozloff 9y ago
I think this error is caused by a mismatch between the monitors capacity to deliver power and your Macbooks desire for it. The HP Envy 27 is rated to deliver 65W, but MBPs want 85W. The MBP will negotiate down to 65W (although the battery may discharge under heavy usage). I could be wrong though. I've got a similar setup and I've only seen the error once or twice.

by lbotos 9y ago

lou1306 9y ago

What they meant is that you should use an official HP Envy laptop :)

LanceH 9y ago

My macbook won't wake up my usb-c monitors consistently. I have tried 8 cables at this point. I have to unplug the cable and plug it back in. I also refuses to mount my phone straight usb-c, and the known workaround is to go usbc -> a -> c. At this point in my relationship with Apple, I can only assume this is deliberate.

indecisive_user 9y ago
So _that's_ why my monitor doesn't wake up. I got the new xps13, it only has thunderbolt/USBc-C ports and it's pretty much 50/50 whether my external monitor will wake up. I figured it was the cable and was about to buy another one but you saved me the trouble. I also got a hootoo adapter that's supposed to support power delivery but that hasn't worked either :/
- olyjohn 9y ago
  This isn't just a problem with USB-C. There are also tons of video adapters on the market that say they support 4k, but really don't. We have grips of 2560x1440 monitors at work, and they had tons of issues like this where the monitors may or may not wake up, may handle the native res for a while, then power down or switch back to 1080p. The only consistent fix for them has been to buy one particular brand of adapter that we found works and making sure it's active. So I guess what I'm saying is, display tech has already been having issues for a long time with crappy components, and USB-C is just adding one problem into the mix now.

lkozloff 9y ago

I think this error is caused by a mismatch between the monitors capacity to deliver power and your Macbooks desire for it. The HP Envy 27 is rated to deliver 65W, but MBPs want 85W. The MBP will negotiate down to 65W (although the battery may discharge under heavy usage). I could be wrong though. I've got a similar setup and I've only seen the error once or twice.