alt Hacker NewsAnd on top of that, Apple has that thing where only some devices can charge from their adapters. I have a special adapter just for non-Apple things because the white bricks (despite the usb-c) sometimes just refuse to give power to things. So frustrating.
Replies
Apple implements the USB-C/USB PD specs to a t and is unforgiving if you don't do either.
At work, our quick test for if a device implements USB PD correctly is to plug it into an Apple power supply (optionally with a PD protocol sniffer in line). If it doesn't work (either no/intermittent VBUS or the wrong VBUS), it's always been the case that the device is doing something wrong.
It can be annoying but strictly speaking their fault.
Whaaaaaaaaat?!
Apple, somewhat famously, build their power adapters incredibly well.
If they’re not charging something my default assumption will be: that thing doesn’t support PD.
It's even worse. The same USB-A-to-USB-C cable will either charge or not charge my iPhone, depending on where I plug in the USB-A part. But the port that won't charge my phone will happily charge my headset, using the very same cable. That kind of excludes the cable as the source of the suckage, and puts the blame on either the (supposed) power source or the phone. I've observed the same effect with other devices I wanted to charge, too. Some devices just won't accept certain USB power sources while others are more promiscuous.
Mostly, that's non-compliant devices. Doesn't make it work any better, but I wouldn't assume Apple is doing it wrong here.
USB-C ports aren't allowed to provide power until after configuration, but a lot of USB-C chargers provide 5V regardless. This is wrong, but it does mean you can use a dumb C-to-micro cable which doesn't include the necessary electronics. (A pull-down resistor at least.)
And of course there's no way to tell by the looks of the cable.