|
|
|
|
|
by sackofmugs
2204 days ago
|
|
This article misses the biggest issue with usb-c cables, which a lot of people don't even realize. A lot of cheaper devices can only be charged with a usb-c to usb-a cable, and not a regular usb-c to usb-c cable (C2C). Basically, they don't support C2C but people don't test or check this until they travel and realize the cable they brought doesn't work on these devices. The cause is that the devices themselves are incorrectly implemented. This ranges from toothbrushes, to flashlights (where 99% of usb-c flashlights can't do C2C), to shavers, and small electronics/appliances. The problem is there isn't a standard way to know about this (or a name for this problem), so it's hard to tell what supports it or not. Generally, devices made by well known brands support C2C, but not cheaper Chinese-made devices, but there are exceptions in both cases. |
|
And yet, even the Raspberry Pi foundation messed this up when they designed the first revision of Raspberry Pi 4.
It's easy to say "USB-C is a mess", but we should really be shaming the individual companies who mess this up. The spec is public, parsable by any competent EE, and there's tons of vendor support for standards-compliant solutions.