> certain cables won't charge certain devices

not sure how you can make a cable that doesnt connect power from end to end. I can see if it doesnt charge as fast as others if it doesnt have the bits required for higher current support. and if a device requires >5V to charge, thats on the device not the cable.

> other cables won't transfer data

again, not sure you can make a cable that doesnt connect the USB2 pair from end to end. but if device doesnt use USB2 and requires something else without mentioning it then that again seems to be on the device not the cable.

▲

craftkiller 7 hours ago | parent | next [-]

FWIW the PS5 controller is super particular about what charger you use due to Sony being dumb, but the deciding factor there is the charger, not the cable.

Source is the eternal benevolent champion of usbc compliance testing, Benson Leung: https://www.reddit.com/r/UsbCHardware/comments/tdduha/commen...

(and also my personal experience, but Benson explains why)

▲

eigencoder 8 hours ago | parent | prev | next [-]

It's probably a problem with my devices. I've never seen these problems with more expensive devices, but my cheap bluetooth speakers will only charge with certain cables.

I also have cheap cables that don't seem able to do data transfer. Guessing it's not actually following the USB-C spec.

	▲	craftkiller 7 hours ago \| parent [-]
		Are your bluetooth speakers connected over a C-to-C cable or is there any legacy USB in the mix (type-A and/or microusb)? The reason I ask is legacy USB expected 5 volts to be supplied by default, whereas in type-C you have to specifically request any current. So some C-to-A / A-to-C adapters/cables include the resistors to request the current whereas others do not, leading to legacy USB devices not getting power through some adapters/cables.

▲

dhosek 8 hours ago | parent | prev [-]

USB c cables aren’t merely wires and connectors but have some electronics embedded on them.