Hacker News Reader

> the wireless headset was the killer app in its early days

Don't forget music piracy.

At least over here, a lot of kids had phones that did Bluetooth, and the primary use case for it was sharing songs they liked with each other. You could use infrared (IRDA) for that, and some people did before Bluetooth was common, but it was much slower.

This was mostly on low-end Nokias, maybe with a bit of Sony Ericsson thrown into the mix. They definitely did not have WiFi, in fact, Nokia even tried to limit internet over Bluetooth for usual carrier monopoly reasons as far as I'm aware, but Bluetooth was definitely there.

For many here, the iPhone not doing file and ringtone sharing over Bluetooth was one of its main limitations, at least early on. It was a social network in its own way, and having a device that couldn't participate in it was no fun.

By "early days", I was more thinking about the 1999-2005 era, before low-end Nokias even got Bluetooth and the ability to play MP3s.

The wireless headset was the killer app that drove bluetooth adoption within cellphones, driving down costs until eventually the lower-end models receiving it too. While sharing files was possible in the 1999-2005 era (especially with PDAs), most phones were lacking enough flash storage to store anything worthwhile.

While I don't want to say file sharing wasn't a killer app, it does seem to have been limited to just schools during a certain time period.

A time period that I missed out on by a few years. At high school, we did all our file sharing by swapping burned CDs. Then we switched to dragging around laptops and USB hard drives at university (and using the private emule network on the university wired ethernet).

It may be worth articulating the Bluetooth headset specifically as the one-ear little clip headset executives and IT staff seemed to use to answer calls.

Remember companies like jawbone?

I vaguely remember a cultural stereotype of bmw drivers driving aggressively and wearing Bluetooth headsets. [edit: this is the clip https://youtu.be/UqfAMvXpSw4?t=25 from top gear of jeremy clarkson wearing a bluetooth headset in sunglasses in a bmw, supposedly from topgear season 10, episode 10]

Yes... there is a very interesting generational thing going on here.

Bluetooth headsets were very popular among a certain market segment (business people who made a lot of phone calls), but saw very little adoption outside of that. At that time, you often had to buy an expensive business grade phone to get bluetooth functionality.

Then once Bluetooth was common in cheaper phones, we see a completely different market segment (students at schools) rapidly adopting bluetooth for a completely different usecase (file sharing). It's hard to find two market segments that are more isolated from each other.

I don't think file sharing could have ever driven bluetooth to mass adoption on its own, partly because companies always overlook what school students are doing with technology. But mostly because the file sharing usecase required mass deployment of the technology before it could take off.

When I was in high school, I had a palm PDA with IrDA that could do file sharing. But did I ever use it for file sharing? No, because nobody else had devices with IrDA. IrDA never hit the market saturation it needed to be actually useful, so there never was much demand for it (despite the hardware being really cheap, especially compared to a dedicated bluetooth radio)

Bluetooth headsets worked as a killer app in those early days, because a single BMW driver could buy both a high-end phone with bluetooth and a headset from the cellphone store and get the complete experience. It worked without market saturation.

Jabra! In all seriousness the blackberry Bluetooth earpiece was the killer app (hardware / device).

BlackBerry HS-655 Bluetooth Headset

Worked perfectly paired with a bb.

Wow this unlocked a bunch of memories from middle school where we would send each other the latest songs and games via bluetooth. I remember pirating games for my sony ericsson and sharing them with my friends and we would play these games in class. You could just share and install the .jar files. Good times

> Don't forget music piracy.

What you describe is file sharing, not necessarily piracy :-). Just nitpicking, I understand what you mean of course!

At this point, the decision to add Bluetooth or not is literally just a product decision. If you don't want Bluetooth in your product, you actively have to disable the Bluetooth part of your WiFi chip, because you can't really get a WiFi chip without Bluetooth.

All of the BT+wifi chips I’ve worked with require active initialization of each feature; you have to signal the chip (over i2c or SPI or whatever) with what kind of BT operations you want.

No BT stack in your product, no BT radio initialization, no BT/wifi multiplexing. At least in the (admittedly limited) chips I’ve worked with.

> the wireless headset was the killer app [for Bluetooth] in its early days

But the wireless headset is now a horrifying millstone making Bluetooth look like the world's stupidest trash fire. If you enable your microphone, you lose all audio from anything that doesn't want to use the microphone as the headset switches into "headset" mode and drops anything that wants to use "headphones" mode. There is no reason for there to even be two different modes.

Why is this still happening?

It is happening because it works the way that is most useful to most people. The number of people who want to use bluetooth earbuds with a different microphone is line noise in the consumer market.

Implementing special requirements is always inconvenient for users because no B2C wants to risk bad the-microphone-didn’t-work reviews, customer returns, and support tickets.

Nevermind coordinating with arbitrary USB microphone latency…I’ve got one with 250ms of it.

> It is happening because it works the way that is most useful to most people. The number of people who want to use bluetooth earbuds with a different microphone is line noise in the consumer market.

I don't think you have any idea what you're saying. The scenario I'm describing is when you want to use a bluetooth headset that includes a microphone. Using a different microphone is how you solve the problem.

I have never had a microphone problem with a bluetooth headset. They all always just work until something mechanical breaks through use.

If I had an issue, wired headphones seem a simpler solution than changing the bluetooth standard and more likely to work than wishing manufacturers changed their devices.

So, the standard defines behavior that is obviously pathological, actively working against the needs of all users. But because it's already codified, it's a bad idea to change it?

Works for my needs.

If it didn't, I'd use wires.

Or something else.

it happens because bluetooth profile for audio+microphone uses different codecs and has less bandwidth, due to being used for realtime communication.

the bluetooth audio streaming profile enables more codecs, but only playback, and allows significantly higher latency that you wouldnt accept on a call

> and allows significantly higher latency that you wouldnt accept on a call

That latency is also a millstone. We can do much better, but the standard lags and implementations lag even more.

My personal bluetooth ear clips do something much worse than adding latency - if they're not currently playing something, and a sound is supposed to come through, they omit the beginning of the sound while they get ready to become active or whatever it is they're doing.

Just delaying the sound and playing all of it would be a big improvement.

(Though that would fail badly for watching videos. That's something that uses 'headphones' mode anyway - why is latency OK there? It isn't.

My ear clips do add some latency, a noticeable amount, when I'm watching a video with mpv, and I adjust that by altering the A/V sync setting. They don't do the same thing when I'm watching something on youtube. I'd like to know what's going on there.)

well you wont get any argument from me that things could be significantly better.

> why is latency OK there? It isn't.

well.. if you listen to music, you probably dont care too much, but if you're talking to someone, you do.

whats much worse is also that latency is not constant.

The absolute madness that is Bluetooth pairing between cars and cellphones is wild. If I get into my car and it decides to randomly pair with my wife's phone (who is inside the house) and I drive off, the whole infotainment system is locks up and dies until I get to my destination and turn off the car.

What car do you drive? Then I make sure to not buy it

Mine connects and starts playing silently, and you need to press play and pause on the headunit to make it make sound. Every two months or so it fails to connect to the phone and needs a complete forget and repair to happen. Toyota unit and iphone.

My partner's hearing aid connects (via some radio protocol) to a device that then connects via bluetooth. Unfortunately, it presents itself as a headset, which causes... problems. For Android, they have to use an app from the play store that presents itself as an audio device and then sends that to the 'headset'.

Except for the "headphone" versus "headset" mode dichotomy that is inherent to Bluetooth, all those other issues are due to stupid product decisions that most OSes do to themselves independently on the same way.

If you use Linux + KDE, you can still use any microphone or headphone, many at the same time, or in whatever mode you want.

Linux + KDE user here.

It used to work on kde/plasma 5 at some point. And after a minor version update it stopped working.

Now the mic of my headset doesn't work because KDE insists that only the high quality sound output without mic is available. The mic + low quality output is gone from the settings.

Lucky for me this update also brought proper handling of the stereo positioned noise cancelling microphones on my thinkpad. So now I can actually enjoy the luxury of built-in microphones that work. Until the day it wont I guess.

if you use pipewire it works fine both in plasma 5 and 6.

but the audio quality in the sound + mic profile is very poor, the codec is only meant for speech

I am using pipe wire. The option to select the handset mode is gone! I can only select the various output codecs with my increasing quality. But not the mic & output mode. It's gone from the list...

Wow brings back memories when this used to be a problem on gnome like five years ago.

> If you use Linux + KDE, you can still use any microphone or headphone, many at the same time, or in whatever mode you want.

This doesn't really seem to respond to the problem. The problem is that I'd like to use a single bluetooth device that includes earpieces and a microphone. That doesn't work, because of the headphone-headset mode dichotomy. As I replied to another comment, using multiple devices would be a solution to the problem. It wouldn't be an example of the problem that I want solved.

Bluetooth is apparently incapable of simply delivering an audio stream to the earpieces while accepting one from the microphone. This is a baffling design. The assumption appears to be that there will never be more than one source of audio for output. But that's crazy.

obligatory xkcd: https://xkcd.com/2055/

Except this isn't a problem of trying to manage multiple connections. Bluetooth can't even handle maintaining a single connection between two devices.

Bluetooth was the main way to transfer music from dumbphone to a dumbphone

The ironic thing is the Bluetooth ignored it's audio use as much as possible for as long as possible. They wanted it to be used for tracking shoppers in stores...

how to use a phone in car without headset / bluetooth to talk legally?