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.

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

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.

Good link that, I’ll have to add those flags to my list of aliases

The more frustrated you are when running git blame the more likely the command turns out to be a mirror.

Wouldn’t be surprised if he’d take the comparison as a compliment