"The Bluetooth SIG recently published Bluetooth 6.2. Key features include Shorter Connection Intervals, which enable ultra-low latency for wireless peripheral devices, and Channel Sounding Resilience, which enhances security in wireless key applications. However, many devices, especially peripherals such as headphones, earbuds, smartwatches, and gaming mice and keyboards, don't perform as well over a Bluetooth connection as you'd expect. The Bluetooth SIG often announces promising features, but they're not in your devices."
"Also: Your Android phone just got a major Bluetooth upgrade for free - how it works The Bluetooth team told me that implementing the latest Bluetooth features within a Bluetooth Core Specification is a decision made entirely by manufacturers, even if a device contains the latest Bluetooth version. Therefore, you shouldn't allow a device's Bluetooth version to carry too much weight, because there's a chance the manufacturer will omit the best features."
"Bluetooth is ubiquitous, but aside from connecting us to our devices wirelessly, the technology feels obscure and cryptic. Also: What is Bluetooth 6.0? Why the newest audio connectivity standard is worth getting excited about I talked with the Bluetooth team about all things Channel Sounding, Bluetooth 6.0, and Auracast, and the largest takeaway might surprise you: We're thinking about Bluetooth all wrong."
Bluetooth Core Specification 6.2 introduces features such as Shorter Connection Intervals for ultra-low latency and Channel Sounding Resilience to improve security. Many consumer peripherals like headphones, earbuds, smartwatches, and gaming mice often fail to deliver expected Bluetooth performance. Device makers decide which Bluetooth Core Specification features to implement, so a device's advertised Bluetooth version does not guarantee inclusion of new features. Channel Sounding adoption remains slow among manufacturers, while Auracast adoption is gaining momentum. Bluetooth technology remains widespread but can feel opaque, and users should focus on actual device feature support rather than version numbers.
Read at ZDNET
Unable to calculate read time
Collection
[
|
...
]