My 3.5mm charging+data standard would work like this - Start with a legacy analog audio connection. There should always be an input/output mode toggle (ideally with circuitry well-protected from an accidental misconfiguration) for TS/TRS connections (1-way audio). Inclusion of a reverse toggle isn't required for TRRS (2-way) connections. If the data mode switch is activated, try to handshake for a digital data connection over TS (mono audio circuit) before enabling it. Optionally use TRS/TRRS/TRRRS (stereo circuit, mic line, etc) for more bandwidth, but always keeping with the initial TS handshake for compatibility. If data mode is working and the device supports power transfer, allow power transfer mode to be activated using data mode to initiate the handshake. Always require a 2-way power connection and ramp up 2-way tests starting from like a milliwatt, never allowing more power in one direction than the other direction has shown it can also provide in the testing ramp-up phase. This is to prevent blowing speakers with accidental power output. Like USB-C, require specially made cables (with built-in reporting of wattage ratings) for power transfer rates that would be dangerous with cheap, thin cables. For safer wattages, allow any normal 3.5mm cable. Whenever data/power connections are deactivated, default back to an audio connection, but set the volume to 0 until the user turns it back up. When the device is in audio mode and a powerful enough audio input is detected, allow the user to enter "power stealing mode" where that energy is captured. If the device's battery continues to drain while capturing this power, or an estimate says it will, then give the user an indicator and suggest turning the device off to "trickle charge." If the device has a display, always make sure it supports legacy analog video input over 3.5mm as well as digital video over data mode. Likewise for output of any graphics the device can generate if it has a GPU. If the device has both a display and speakers, the display support requirement does not mean you can drop support for audio. The only time you can have a connector with no legacy audio mode is on a power adapter or a thumb drive or other device that has no audio functionality. Like with power, audio, and video, apply the 2-way toggle philosophy wherever possible. Never pointlessly limit a connector under this standard to a 1-way connection if the user might want to use it the other direction. This consideration may show up in unique ways for devices with unique features. The name doesn't really matter. It could be called Digital Barrel Connector (DBC) or something. There could be data-only connectors, but not data-only cables - every cable should work with every connector. There would not be truly power-only connectors - even a power adapter would use data mode for the power transfer handshake. Maybe this could still be presented as a "power-only connector" to users because it can't be used for their own data transfer purposes. A device with one port should still be able to do everything, so I'll count this as "one connector for everything," finally delivering on the promise USB-C was never going to. Each type should still have a clear standardized marking to set it apart, like the blue markings of USB3. If data-only connectors are implemented, they have to look different from data+power connectors. This way, there remains a recognizable "one connector for everything." USB-C cannot be fixed because it is too deeply ruined. The creators gave too much momentum to the dishonest approach. Literally fucking recognizing power-only cables as an acceptable version of the standard, what the fuck? USB-C will never recover from that. It will never be one connector for everything. My plan doesn't give away that momentum. If you want to make a version of this connector that doesn't work, I will say it's fucking broken and shouldn't be carried in stores, instead of calling it an acceptable version of the standard. To solidify it, the first device to implement this standard needs a manufacturer who's really clear about the requirements for compliance. The manufacturer also needs to encourage customers to help enforce compliance by testing, returning, and reviewing scam products - this is why it's important for the connector to have its own unique color code.