Yeah I have some devices that expect the manufacturer charger (I guess it's pre-negotiated to 19V or something) and I'm not even sure what was the point in giving it a USB C connector.
I have a couple of devices that are 12V over usb-c. The devices themselves are fine, but the wallwarts the mffr provided are just that - 12v over usb-c. No PD. If a device is expecting 5V, there's a healthy chance it'll .. stop expecting 5V.
We blame usb-c for all this, but it does feel like some mffrs are going out of their way to screw it up.
Imagine if all USB-C cables had a patent owned by the consortium and an identification chip made by the consortium. The spec could require that devices would not use the cable at all unless the chip is cryptographically verified, and bad cable manufacturers could be sued into oblivion for breaking the patent.
The more I age, and the more I expect my devices to justwork™, the more I appreciate Apple’s pro consumer monopolistic moves.
This kind of defect is extremely rare since this would basically be a USB killer frying every other device you plug it in to. 99% of the time it's the device is missing some resistors on the cc pins which signal to the charger to send 5v. Since usb-c it defaults to 0v until you request something. But USB-A has no CC pins so it just puts 5v out at all times.
We blame usb-c for all this, but it does feel like some mffrs are going out of their way to screw it up.