Hacker News Reader

Comment by deckplecksetter | Hacker News Reader

For me, using Bluetooth headphones with my (Samsung) phone is smooth and trouble-free. The experience is miles better than wired headphones, and I would never go back. Meanwhile, connecting to my TV with Bluetooth is an exercise in pure frustration.

So it seems to me like the problem isn't Bluetooth, it's shitty implementations of it.

And it's not just cheap devices. My TV is a fancy LG OLED. For the price I paid it should handle Bluetooth just fine.

It's a real shame. When Bluetooth works, it's awesome, but a lot of people have had their opinions tainted by bad devices.

View on HN

Yeah, I'm reading these comments and I would have agreed 10 years ago, but I'm regularly using three different pairs of wireless headphones plus a Bluetooth speaker and have literally zero issues. My Bose headphones are usually even paired with two phones.

Yeah, charging is a bit annoying, but the added comfort is worth it to me and I can't tell that the audio quality is any different.

It's super inconsistent across devices and implementations. I've had so many issues with it over the years.

I've had headphones where a slight change in the environment around me while walking would disconnect audio. Or IEMs not syncing properly the L and R channels.

Even in the best of cases using headphones with multiple devices is just terrible. Also syncing audio to picture rarely works as it should.

> So it seems to me like the problem isn't Bluetooth, it's shitty implementations of it.

Perhaps, but it kinda seems to me that there must be some inherent limitation of the standard which make it particular hard to create a high-quality experience?

The latency for instance - in my (somewhat limited) experience audio over BT does not sync perfectly with video.

The channels/codecs is/was so limited in bandwidth that until recently (few years back IIRC) headsets couldn't even send and receive decent quality audio at the same time. Even recent headsets like the Shokz Openrun Pro 2 has this limitation. (Which you could argue is an instance of "shitty implementation" since it was released after the availability of necessary tech (LE/LC3))

>So it seems to me like the problem isn't Bluetooth, it's shitty implementations of it.

Yep, but this is a problem that is present everywhere. For example, electric cars are supposed to be simpler, because its one moving part. In reality, you get essentially vertical integration of all the components like battery management, motor controllers, infotainment, gauge cluster and the software that connects all of that, and when bugs are present you can't even get into your car.

Reply on news.ycombinator.com