lemm.ee

8 points

1 year ago

So I have a:

Sony WH-1000XM5 (which I use in both wired and Bluetooth modes)
Galaxy Fold 4
MacBook Air M1

These are all fairly recent devices, with the Sony one being the most recent headphones in it’s series, running the latest firmware too, which was released last month.

Now here are my issues:

- Fold 4: When I get a call on Google Meet or Duo and I turn on my headphones, the audio doesn’t work. I have to disconnect the call, close the app, and reconnect for it to work.

- MacBook: Similar thing happens with Microsoft Teams. In this case though, my headphones is already paired with my MacBook and connected, so I fire up Teams (from scratch) and dial in to a meeting. You’d expect it to work fine right, but the audio doesn’t work, even though Teams detects my headphones as the output device. I have to turn my headphones off and on during the call (or reboot my MacBook) for it to work properly.

I can reproduce these issues consistently. I’m not a 100% sure if it’s an issue with my Sony headphones, but the point is, all these products that I’ve listed are fairly recent and fairly expensive, and I deserve a better user experience. Bluetooth has indeed come a long way, and at least for me, audio quality isn’t really an issue, but the fact that these sort of connectivity issues are still occurring on recent, premium devices, is unacceptable.

report

[ - ]

Atomic@sh.itjust.works

1 point

1 year ago

Those all sound like software issues from Sony on their headset, rather than limitations of Bluetooth. I have a pair of BOSS that is connected to both my laptop and phone at the same time, and the switch between them is seemless.

Listen to music on phone. Pause, go to laptop. Put on a video on YouTube. And it instantly switches to my laptop for sound.

Be on a call on discord from my phone while I’m out. Get home, enter the call from laptop, and boom. Automatically switched from phone to laptop and I don’t have to change a single setting.

Sorry you have a bad experience with SONY. But I can assure you. It’s not a Bluetooth problem. It’s a SONY problem.

report

[ - ]

1 point

1 year ago

Well, my point still stands. How is one supposed to know that this particular headset had these sort of issues? I did extensive research before buying mine, and no one reported any such issues. Admittedly, it was still fairly new when I purchased it so there may not have that many reviews, but Sony isn’t some random brand and their audio gear is generally well received.

On the other hand, I could just pick up any cheapo TRRS headset and know that it’ll work without a cinch. We’re just not there yet with wireless headsets if we can’t even rely on reputed brands to work consistently.

report

[ - ]

Atomic@sh.itjust.works

1 point

1 year ago

I don’t think your point stands at all.

If you’re asking how someone is supposed to know without knowing then the answer is you can’t. Obviously.

You looked at biased reviews that had clearly not tested the product in the manner of which you wanted to use it. You made a bad purchase. I’m sorry. But that’s not the fault of Bluetooth. That’s the fault of Sony.

Are you going to claim that smartphones are hot garbage just because Nokia made a really shitty one? They were a reputable phone brand too. Until they weren’t. Maybe you just learned that the hard way with Sony.

report

[ - ]

1 point

1 year ago

The thing is, it’s not just me/Sony. There’s been several reports of similar sort of issues for wireless headphones in general.

And in comparison, there’s very little issues with wired, so my point still stands - wireless audio still has issues - I don’t care if it’s a fault with Bluetooth or an implementation bug on the headphones or the app or the OS, the point is, there are still issues that you may be unaware of when buying a wireless headphones, when there’s next to none with wired.

You’re quick to blame Sony, but if you can’t trust a reputable Japanese brand who’ve been making audio equipment for over 70 years now, who can you trust? Afterall, reviews are “biased” and can’t be trusted, so I guess it’s down to pure luck then, right? And even if you get lucky and think you’ve made a good buy, there’s no guarantee that something won’t break with a future update. For instance, here’s a thread where someone’s mic stopped working after a Windows update - turns out that the fault was with the Intel Bluetooth drivers, and downgrading the drivers or the update fixes it. Who wants to put up with this sort of nonsense when you’ve got a meeting or an interview to attend to, and suddenly you find your headphones no longer work because of a fricking update?

This sort of unreliability is precisely why many people prefer sticking to the tried and trusted wired headphones.

report

[ - ]

Mike@lemmy.ml

1 point

1 year ago

It’s not worth arguing with @atomic Apparently my pixel, with pixel buds and watch with wearos is also a software issue. As if the software issue might not lie within the software that drives the Bluetooth protocol, I. E. Bluetooth itself🙄

report

[ - ]

Atomic@sh.itjust.works

1 point

1 year ago

Your argument is irrational. So because Ford makes terrible quality cars all cars are bad? I mean. If we can’t trust the company that made the first industrially made car, then who can we trust? After all, there’s so very little that can go wrong with a bicycle or ones own legs.

I talked about Sony because YOU said you had problem with them. Where you admit that you bought it very close after launch where not many reviews had come out.

You think wired headsets can’t get fucked by faulty drivers? Have you ever had an issue with your audio drivers as a whole? I have. Doesn’t matter if you use wired or wireless then.

I’m telling you point blank. There are good products where it works seemless between different devices. But you just won’t have it cause you had a bad experience once with a poor purchase from your end.

If you wanna use wired by my guest. More products on the shelf for me. But your stance against Bluetooth as a whole is ridiculous. Shall we say wired headsets are garbage because what it the wire gets damaged? Man cable close to the the male connection always end up breaking! Terribly unreliable!

report

[ - ]

1 point

1 year ago

In all my life I’ve never had a problem with wired headset not working due to driver issues. Sure there were the occasional overall sound card issues, but those were dating back to the Windows 9x days. Also, theoretically and statistically speaking, a wireless setup has more parts and more complexities, so it’s more likely to fail.

There are good products where it works seemless between different devices

Citation needed. And I repeat my previous question - how exactly is one supposed to discover these set of devices? What if you say use a particular model of Thinkpad and the device wasn’t tested against it? I doubt there exists a database somewhere that has list of every wireless headset tested against every Bluetooth capable device. So ultimately it’s up to the luck of draw, and that’s not a very good user experience. Whereas with wired, I can he 100% sure a wired headset will work if a device has the matching aux jack.

Also, the wire getting damaged isn’t really a problem, any decent wired headset would have a replaceable wire, so you can always swap it out with any standard TRS/TRRS cable and you’re good to go. Whereas with wireless, the battery is almost guaranteed to degrade after a few years, and it can be really hard or even impossible to replace, depending on the model.

report