2 ms·
"it depends" is a fine answer for whether a device supports something. that's how USB-A/B worked. you didn't know if the device supported quick charging, work
by notatoad 8y ago
"it depends" is a fine answer for whether a device supports something. that's how USB-A/B worked. you didn't know if the device supported quick charging, worked at better than USB 1.1 speed, or even if it supported data transfer. there's lots of power-only USB devices.
But you at least could make a fair assumption that the cable you were trying to use supported all of that (beyond the rare power-only cables). For me the real killer with USB-C is the wide variety of cables that all look physically identical. it's fairly easy to keep track of what features a computer, phone, or peripheral has. but having to keep track of which features each cable supports is a huge pain in the ass. It means i can't just have a box of random USB cables on my shelf, and grab one when i need one.
- jrockway 8y agoQuick charging is a little different. You can take any USB phone and plug it into any USB port and it will try to charge. Maybe slowly, but something will happen. That is not the case with Type-C alternate modes and power delivery. If what you're connected to doesn't support what the device needs, it won't work, and won't tell you why. That is what's annoying. Is it the power adaptor? Is your device dead? Does it not agree on which alternate modes to use? Is the cable incompatible? Nobody knows without a $100 debugging device to sniff out the negotiation packets.