![]() |
|
![]() |
| You can have a device listening only 1% of the time while only waiting a millisecond. Just listen for 10 microseconds and energy-save for 1 millisecond. Why aren’t they doing that? |
![]() |
| BLE is 3 advertising channels. IIRC they are dedicated to advertising. There are something like 40 other channels used for data (and it uses all of them via frequency hopping). |
![]() |
| So my Airpods 2 have an outdated firmware version, but as a user I can't explicitly have iOS update the firmware, and there is no indication when an update happens. I wish I would have more control. |
![]() |
| They could also just drop a device with a microphone in your bag and listen to both sides of every conversation. Involving bluetooth seems like an extra complication. |
![]() |
| > I believe it is a courtesy to remove one's headphone when talking to another person.
Social norms change over time; expecting someone to remove headphones will become less of a thing in day to day life. AirPods Pro 2nd generation supports the Conversation Awareness feature that lowers the volume of what the person is listening to and raises the volume of the person speaking automatically when it's enabled. Apple is expected to be approved by the FDA for some uses as a hearing aid [1] and they have patents for adding medical monitoring in future AirPods [2]. So when we're talking to someone wearing AirPods as times goes on, we won't know if they actually need the AirPods to assist them in being able to function in the world. [1]: https://arstechnica.com/gadgets/2024/03/apples-airpods-pro-c... [2]: https://applemagazine.com/apple-patents-suggest-future-airpo... |
![]() |
| How would you as an observer tell if somebody is using their AirPods to listen to music or whether they're just in their ears for noise cancellation and thus "look ridiculous"? |
![]() |
| >AirPods Firmware Update 6A326, AirPods Firmware Update 6F8, and Beats Firmware Update 6F8
I'm on 6F8, which I presume is for AirPods Pro 2nd gen. |
![]() |
| I understand that chances are pretty slim but I still hope that this will make Apple do something regarding AirPods updates on other OSes or at least on Android. |
![]() |
| Have you tried PipeWire? As long as bt driver for you adapter is decent PipeWire makes using all sorts of bluetooth audio devices a breeze. At least for me it works great, all the time. |
![]() |
| I can tell you I absolutely could not get my fancy Sony WH-1000XM5 to connect reliably for more than a few seconds to desktop Linux, so not those ones. (They work fine for Android) |
![]() |
| how much do you know about bluetooth device and codec profiles? ooh, boy, I envy you, you see, the bluetooth connection was never about the bluetooth at all...
https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles (absolutely there is some codec that apple licenses that you as a linux user don't and don't get etc, this is some profile thing they're doing and honestly that's just the price of linux. Free as in free from HDMI 2.1 support. And fraunhofer, and Dolby, and MPEG-LA licensing. Being willing to pay the $2 per device for the licenses has its perks.) |
![]() |
| > Such as?
AAC-ELD is unsupported. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/14... > Linux has had functioning AAC, MOV and MP4 drivers for almost a decade at this point. ok that’s nice but that’s not AAC-ELD. There’s no door prize for “part of the name is the same”, codecs and Bluetooth stream configurations are either supported or not. It’s also not compatible with open-licensing either way, even though those licenses are commonly breached, ie it’s nonfree at best even if someone hacked together a toolchain, which was my point about the “free as in free from hdmi 2.1” part. Fraunhofer says you need to pay for a license even if you choose to pirate it anyway. Linux, by default, does not pay that for you (naturally). |
![]() |
| Hard to think of a company with as poor security as Apple. No one else hits the headlines as much and creates so much real world consequences. |
> With this trick, they can establish that both devices are speaking the Fast Connect protocol without violating the Bluetooth specification, and then go on to exchange 3 more back-and-forth messages, negotiating all the things necessary to fully connect the two devices.
> The fact that this only takes 4 messages back-and-forth in total is what makes Fast Connect fancy, because usually in Bluetooth the phase of wiring up the individual channels for a connection is quite a complex negotiation and involves sending various SDP descriptors that describe which protocols/features both sides support.
Two devices in the same room communicating over even a very narrow slice of the electromagnetic spectrum could exchange many thousands of messages per second. What is it about Bluetooth that causes each message to take a hundred milliseconds rather than, say, a microsecond? What is setting the timescale for this process?