> By "that mode", do you mean "1.5A @ 5V" permitted by BC

Neither - OP means devices with missing CC resistors which will fail to charge with a compliant PD source. (The A-to-C cable works because it provides 5V Vbus unconditionally.)

▲

exmadscientist 3 hours ago | parent [-]

The A-to-C cable often does not work because the resistors are supposed to be in there.

So if you are having complete charge failures, try a different cable.

▲

megous 3 hours ago | parent [-]

A-C cable assembly always works, CC signal is connected within the cable to Vbus via 56kOhm resistor, but that's only relevant to the downstream port, not to the upstream USB-A power sourcing port which does not have access to the CC signal. Upstream port provides power unconditionally within some limits depending on port type (CDP/DCP/USB3.0/2.0 data port/...).

▲

exmadscientist 3 hours ago | parent [-]

That's how it's supposed to work, yeah.

But there is some trash out there in the world. A lot of it, actually.

Some naughty cables work with some naughty chargers work with some naughty devices. Postel's Law in action, I guess?

Usually the best place to fix it is by getting rid of the bad cables. Usually.

	▲	mschuster91 2 hours ago \| parent [-]
		> Usually the best place to fix it is by getting rid of the bad cables. Usually. No. There is no USB-C to C cable that will charge a badly implemented device with a standards compliant charger. That is the entire point. An USB A to C cable is completely standards-compliant and safe, even if it always supplies 5V on the C end - any standards compliant USB-C device should not activate the MOSFET on its Vbus line unless it successfully negotiates via CC.