Earbuds are only 1 month old, they did not have this issue before

Now when the buds reach 60% battery it drains and goes from 60 to 0 in 10 or 20 minutes (not joking), thus only giving me 2 hours of battery life.

Earbuds and phone (Galaxy A55 5G) are up to date. ANC is on as well but still it shouldn’t cause them to drain the battery so fast

https://files.catbox.moe/yysrxw.mp4

  • antimidas
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 day ago

    Couple things I could think of, that can lead to this sort of behavior:

    1. Using them in a cold environment, like -20 to -30 degrees Celsius.
    2. Headphones dropping down to an older standard for some reason, and connecting e.g. via bt 4.x or using an incorrect codec (would explain why one of them is draining so much faster) – should be possible to check in BT settings
    3. The headphones just have a bad battery, I’ve run into multiple headphones which just turn off once the battery reaches 50-60 %, especially when it’s cold out

    But these are just suggestions and speculation, I’m not really an expert on the subject.

    • N00b22@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      It’s probably the 3rd one because the temperature seems to be normal

    • antimidas
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      But I’ve previously encountered multiple cases of people complaining headphones not being able to match the advertised battery life – and the reason ended up being either too old a phone (meaning it lacks the newer codecs and versions for Bluetooth), or some bug in pairing leading to using the wrong codecs and/or protocol

      • N00b22@lemmy.mlOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        and the reason ended up being either too old a phone (meaning it lacks the newer codecs and versions for Bluetooth)

        I have a Galaxy A55 5G that is new enough to handle the Buds FE

        or some bug in pairing leading to using the wrong codecs and/or protocol

        Not sure since I’m not a codec expert but I checked and it’s set to this: 1000018652

        • antimidas
          link
          fedilink
          arrow-up
          1
          ·
          1 day ago

          Yep, I don’t think the A55 is the culprit either – just outlined the reasoning behind that. Sometimes pairing also gets things wrong which leads to the headphones using an older protocol version.

          But that doesn’t seem to be the case as it’s using SSC, at this point I’d also just guess it’s a bad battery. You can try pairing them again but I wouldn’t be surprised if it doesn’t help. Still, couldn’t really hurt to try.