Live data from Hacker News

What went wrong with wireless USB

oldvcr.blogspot.com

141–150 of 219 posts

Re: What went wrong with wireless USB

#141
post #41

Earlier quoted context omitted.

Bluetooth had some early success in cellphones, mostly to support Bluetooth headsets and car radio integration, starting from about 1999. It could do other things, but the wireless headset was the killer app in its early days. Bluetooth didn’t really hit mainstream until the arrival of chipsets that multiplexed Bluetooth and WiFi on the same radio+antenna. My memory is that happened sometime around 2007-2010. At that…

> 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 t…

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.

Re: What went wrong with wireless USB

#142
post #41

Earlier quoted context omitted.

Bluetooth had some early success in cellphones, mostly to support Bluetooth headsets and car radio integration, starting from about 1999. It could do other things, but the wireless headset was the killer app in its early days. Bluetooth didn’t really hit mainstream until the arrival of chipsets that multiplexed Bluetooth and WiFi on the same radio+antenna. My memory is that happened sometime around 2007-2010. At that…

> 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 t…

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.

Re: What went wrong with wireless USB

#143
post #128
post #113

Earlier quoted context omitted.

Totally. Many accessories nowadays require bluetooth/wifi where actually they could be connected with a cable: they don't move and they need to be charged. Connecting over a cable is trivial: you detect the connection and that's it, and the user physically sees the connection between the devices. Connecting over radio requires pairing, that is very frustrating when it doesn't work. Pairing is annoying so devices try…

> Connecting over radio requires pairing, that is very frustrating when it doesn't work. Everything's frustrating when it doesn't work. > Connecting over radio requires pairing This is a solved problem, plagued by technology fragmentation. You could very well save the necessary information for discovery and pairing onto an NFC tag and use that to access the network (further authentication might happen, if configured)…

> Everything's frustrating when it doesn't work.

My point being that it cannot be frustrating if it doesn't exist.

> This is a solved problem

Tell that to my airpods that connect to the wrong device (so I need to manually go connect to them most of the time) and to my phone that doesn't automatically connect to my airpods when it is already connected to my watch.

Granted, I want wireless between my phone, watch and headset. But I wouldn't call it a solved problem.

Re: What went wrong with wireless USB

#144
post #71

We were a bit late when we discovered wireless USB had been a thing. Still, we managed to find one pair of emitter and receiver that also transmitted HDMI, power the "receiver" side with a battery, in a backpack, and hook it up with another power bank to an Oculus DK1. Unexpectedly, battery time was never an issue. The WUSB chip in the receiver would overheat long before that and start throttling, leading to jittery…

Seems like you could spend a smidgen of that battery power on a fan, no?

[I am not a physicist]

Wouldn’t a fan in a backpack just move hot air including the heat of its motor?

Re: What went wrong with wireless USB

#145
post #100

Earlier quoted context omitted.

I think I disagree with that. This "people don't want files, they want to share photos", to me, is what product people want to believe. The whole thing has been enforced on users and is self-reinforcing: of course if you don't show files to users, they will not know what a file is. Sure, I may be in a photo gallery and I may want to share a few photos with a friend who may want those photos to be treated as photos (i…

> is what product people want to believe It's quite clear what you never had to explain why 'only looking at a pictures/photos on the Internet' wasted the mobile traffic.

Were you born with the knowledge that a video takes more space than a photo that takes more space than a text?

Or is it rather that you consider yourself one of the few people smart enough to memorise it? I find that very condescending.

I don't believe that one needs 3 postdocs to understand it. In fact, I do happen to have explained it quite a few times, and I don't remember anyone not understanding it.

Re: What went wrong with wireless USB

#146

Earlier quoted context omitted.

Bluetooth is bad enough that wireless mice/keyboards usually have a USB dongle receiving what I guess is a proprietary RF protocol. Some wireless headphones have that too. And wifi requires too much power.

I don't know why USB dongles are popular for manufacturers (I assume to make their product more plug-and-play friendly), but I don't think they are a better solution than bluetooth. For example, it is common that if another USB device is plugged close to a USB dongle, it can cause interference to it, which results to unstable connection and eg makes a mouse "jump", keystrokes not register etc. Finding the right place…

The dongles are common because they predate widespread availability of bluetooth equipped laptops and desktops by about a decade…00’s versus 10’s.

Dongles are also plug and play (no pairing dance) and more readily support multiple devices on the same computer.

Bluetooth has gotten better over the years but it doesn’t provide a meaningfully better alternative for the it-aint-broke consumer mouse market.

Re: What went wrong with wireless USB

#147
post #41

Earlier quoted context omitted.

Bluetooth had some early success in cellphones, mostly to support Bluetooth headsets and car radio integration, starting from about 1999. It could do other things, but the wireless headset was the killer app in its early days. Bluetooth didn’t really hit mainstream until the arrival of chipsets that multiplexed Bluetooth and WiFi on the same radio+antenna. My memory is that happened sometime around 2007-2010. At that…

> 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 t…

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

Re: What went wrong with wireless USB

#148

To the aithor : careful, on one picture at least you blacked out the human-readable PIN of a device, but forgot to black out the corresponding barcode right below

That’s the MAC address barcode

...the MAC address barcode was below the MAC address, the PIN barcode was below the PIN.

They fixed it now.

Re: What went wrong with wireless USB

#149
post #54

That's one thing, but what happened to wireless HDMI? That would save a lot of cable pain in literally all households out there too.

Slightly off-topic, but I'm totally in favor of letting HDMI die the slow and agonizing death it's supposed to die.

https://arstechnica.com/gadgets/2024/02/hdmi-forum-to-amd-no...

Re: What went wrong with wireless USB

#150
post #10

I worked on the design of wireless USB chips around 2008 - 2010. They worked - you really could get USB 2.0 full rate connections wirelessly and we had some neat demos. I would say the major problem it had with adoption was that wired USB also provided power . (A lot more people use usb to charge their phone than to sync their phone.) So great - wireless connectivity... but you still have to plug the device into a ca…

> They worked - you really could get USB 2.0 full rate connections wirelessly and we had some neat demos.

TFA mentions that contemporary users of these things didn't get anywhere near Hi-Speed USB speeds. The author's present-day testing agrees with these reports, finding that at least one device's maximum performance was just barely better than USB FullSpeed.

If you were seeing 480Mbit performance with the hardware you were doing demos with, what went wrong between the demo table and the finished product?

Post reply on HN