Comment on Realized 99% of all my chargers are USB-C. This can only mean one thing. New USB bout to drop!

• bogobinto57@lemmy.myserv.one ⁨8⁩ ⁨months⁩ ago

  Yeah I think some of my cables charge my phone at different speeds.

  source

  • TrickDacy@lemmy.world ⁨8⁩ ⁨months⁩ ago

    I haven’t had that issue for years. From my perspective only the cheap or early cables had issues like that. Not your experience I take it?

    source
• Onomatopoeia@lemmy.cafe ⁨8⁩ ⁨months⁩ ago

  I’ve had exacrly 5x more failures of USB C ports than I’ve had of micro that is 5, and 1), and I’ve had way more micro devices over a much longer period (and still have some). It may technically be a “better” port, but my experience doesn’t reflect that.

  I have to label cables and chargers because some C devices today still don’t support all charging specs, so I have to verify a device charges on a charger to know for sure.

  At what point shouldn’t a device be able to negotiate down to the lowest charge capability, instead of not charge at all? That the spec permits this to happen is a major failure.

  It’s fantastic that C is the convergence standard, but let’s not act like it’s close to perfect. I have to verify with every device I use if the charger actually works for it, and not just “is the charger powerful enough”, but “does it actually charge even though I know it should because it supports all the capabilities as the device”.

  source

  • TrickDacy@lemmy.world ⁨8⁩ ⁨months⁩ ago

    I don’t know why but my luck has been nearly opposite to yours. The only thing close I’ve had to your experience was I had a USBC port on my phone get dirty once and I had to clean it out. 0 actual hardware failures and very few charger problems

    source
• rumba@lemmy.zip ⁨8⁩ ⁨months⁩ ago

  that means I try to charge something that either takes forever or never charges.

  That’s a pretty significant failure IMO.

  I don’t want to go back, but I want shit be labeled and work. You go to bed and wake up to a 7yo on a trip with a dead device, you’re going to have a bad day.

  source

  • onslaught545@lemmy.zip ⁨8⁩ ⁨months⁩ ago

    It’s not a failure to default to a safe level if it can’t negotiate properly. That’s a feature.

    source

    • rumba@lemmy.zip ⁨8⁩ ⁨months⁩ ago

      That’s if the manufacturer doesn’t just install a max wattage chip in every cable.

      Unfortunately this is not uncommon.

      source

      • onslaught545@lemmy.zip ⁨8⁩ ⁨months⁩ ago

        I n6ot extremely familiar with the USB-C handshake, but isn’t it between the device and power supply?

        source

        • -> View More Comments
  • TrickDacy@lemmy.world ⁨8⁩ ⁨months⁩ ago

    But it’s not really a failure of the cable. In a perfect world, it possibly plugging in means it works as expected I guess, but I think it’s a better tradeoff to expect users to know that some devices require a bit more power, and have a plug that still works universally. “This charger doesn’t have enough power” is easy enough to be understood by a 90 yo I would think.

    Chargers should be labelled with the output they provide (mine are), but you are right, devices probably should be labelled better with what they require.

    source

    • tyler@programming.dev ⁨8⁩ ⁨months⁩ ago

      Did you know that USB C cables can be unidirectional? As in, they only work plugged in in one direction. You know how I know that? Cause I’ve soldered usb-c cables myself. I own one that only plugs in in one direction (and works)! I’m honestly very surprised you’ve only had issues with charging, do you not need them for data? So many of my cables are charging only, they literally do not function for data at all. It’s a nightmare.

      source

      • TrickDacy@lemmy.world ⁨8⁩ ⁨months⁩ ago

        I have used them as data cables, such as for migrating Android phones. Don’t remember having any issues.

        source
    • rumba@lemmy.zip ⁨8⁩ ⁨months⁩ ago

      Admittedly, i’ve only had a couple cable problems and one of those would have likely been labeled wrong as they were cheap cables with max wattage programmed.

      One of my users came to me with a C-C phone cable that had used between a MacBook pro and a Mac charger. “This got really hot and started to stink when I used it”

      uhh, crap, here have this handed them a 6 foot 100w cable and please throw that old one away I’ll give you a new phone cable too.

      My other problem is with QC on random cables. I have some 6’ that won’t pass 25w. I have a Klein tester that will enumerate wattage. I throw away cables that won’t at least support fast charging.

      I also have a couple Samsung trio wireless multi-device chargers, they insonsistent. If I use the 45 watt Samsung brick that came with it it works fine. If I use any other brick, it refuses to use anything but a full on 65 watt charger. I don’t know if they ignore the spec, or enumerate differently, maybe they give a different output on 9v than others, but we need to have this overall issue with compatibility and semi-functional usage that just feels janky.

      I hope that eventually with GaN and other tech that everything will just do 100w or maybe all devices will go down to only needing 45 watt. It would be super nice if everything just played well together.

      source

      • brbposting@sh.itjust.works ⁨8⁩ ⁨months⁩ ago

        won’t pass 25w

        Reminded of what looked to be a great deal on USB-C cables from a major manufacturer (Anker I think).

        Fine print: not for MacBook Pro yaddayadda! Yeah the things can’t hang for it. Gotta spend way more.

        I wonder what the best cable labeling solution is for new cables purchased with known specs. Bet a handful of well-resourced geeks do their own printing right on them.

        source

        • -> View More Comments