Tried to charge my phone (with USB-C), but my laptop started getting charged
twitter.com
twitter.com
http://blog.teledynelecroy.com/2016/02/usb-type-c-cable-dete...
Different device types (like a powered hub or desktop monitor) can request different roles, and they'll have to sort it out during negotiation if there's a conflict. Sometimes a user-facing popup will ask you if you want to provide or take power from the other device.
Cable detection: http://blog.teledynelecroy.com/2016/02/usb-type-c-cable-dete...
Overview of USB power delivery negotiation: https://www.embedded.com/usb-type-c-and-power-delivery-101-p...
And then after the initial connection, the devices can renegotiate their roles if you want to reverse the charge.
It's great when it actually works. In the real world there are so many incompatible implementations that USB-C is a real clusterfuck.
While I don't doubt the foresight of Apple HW engineers, the possibility strikes me that this is entirely accidental and derived from the design of the USBPD spec. If so, these "stars align (but only because the spec was functionally designed)" moments are some of my favorites.
In Android there is a "Charge connected device" setting that you can turn on or off. Mine is off by default.
Well, assuming batteries with similar % charge <-> voltage correspondence.