Picked these up when Woot had them earlier. For some reason my phone (and only my phone) doesn’t seem to recognize these cables. My other USB-C devices charge perfectly fine with them, but the phone just sits there and doesn’t charge.
Any idea why this sort of things could be happening?
(not looking to return them – I’ll get enough use out of them with everything else. Just curious if there’s a way to make them work with my phone).
Without the ability to troubleshoot with you, the best that I can offer are some general tips for USB charging, and speculation as to why it wouldn’t work for your current device.
USB, contrary to current usage, was just not designed for delivering power in any large capacity originally. Despite the primary design purpose of data, we have slowly morphed that into charging and powering devices of all sorts, with several “standards” for power, such as USB-PD (power delivery, Qualcomm’s QC (Quick Charge of various revisions), etc… When all components can correctly communicate with one another, that can mean that more power is available beyond the standard 5V, and commonly 2.4A (5 Volts x 2.4 Amps = 12 Watts). This power is limited by the lowest capability from each of the components - The power brick, cable, and device. If all have the ability to use the higher tiers of USB-PD, at up to 28V, then it may, as long as the device needs or calls for that, provide UP TO that voltage, in the steps defined by whichever fast charging protocol is available to each of the links in the chain. For instance, a really nice GaN power brick may support 48V in USB-PD, but if the cable doesn’t support higher than 9 or 15V, or only has the appropriate marker chip (that tells devices what it can do) for QC 2.0, then it will only want to use 5/9/12V… And if the device only “knows” a different fast charging standard, everything grinds to a halt, or at least the slower and basic standards. This is made more difficult in some scenarios in which some devices are “picky” about standards, like the Nintendo Switch, or some phones that use proprietary protocols. This becomes even dicier with different connectors, like USB-C and USB-A on the same cable, since the default there is often to use the older, lower power specs of the USB-A device. And that just doesn’t always work.
Regarding your situation, I would guess that somehow either the power brick, or your phone are somehow not talking well with your cable, and the e-marker chip that correctly indicates how much it can do. In those instances, sometimes a different power brick can help, if they use the same standard. Or sometimes the cable needs to be replaced since it is not capable of what both the power brick and phone want. But it is a complicated dance in which the consumers are often not aware of which type of “fast charging” cable they have, and whether or not it will play nicely with the charger or the device at either end of the line. Not your fault, so much as it is just what happens when we have an ecosystem for charging that has sprung up in the last decade, but with so many different “standards” in use to try to make a data cable become a power delivery method.
Sorry, but I hope that this helps answer the question 
