Hacker News new | ask | show | jobs
by jwtorres 946 days ago
This article is not about Bluetooth in general, it is a deep dive into the bugs buried within the Android Bluetooth stack.

And what the writer is not acknowledging at all is that the underlying hardware being used is highly variable. Android runs on top of numerous Bluetooth chipsets. So when he gets a patch to seem to work on his hardware, there is no saying that it will work for a different Android phone.

Furthermore, this all depends on what else the device is up to at the current moment. If you have shared BT+Wifi chipset and you are streaming a video over wifi, then streaming the audio to your headphones, the device is having to allocate resources based on wifi usage and BT. So playing audio stored locally and audio via a stream is not necessarily going to get the same CODEC parameters.

There is so much nuance to this subject that the author just hasn't considered. Please be careful what you read.

4 comments

Former custom ROM developer here who has reviewed and integrated valdikSS modification.

It’s not a bug that the patchset is doing, but enables dual-channel SBC to be negotiated in the source and sink connection. This enables the higher bit-rate without exceeding the maximum bitpool both Android and BT receiver impose.

There’s still negotiation occurs between the source and sink and if either one of them doesn’t support dual-channel SBc, it’ll fallback to whatever its supported. All the device that i had maintained supports it, while some cheap speaker that i test at that time doesn’t and able to negotiate joint stereo session.

Right, it’s more of a configuration that is being changed. But my point was that this is all above the HCI layer, so at the end of the day it’s related to the specific host-stack implementation and not to do with Bluetooth in general.

I guess I’m basically saying the title should be changed

I’m so glad Bluetooth SIG charges $10,000 per model of Bluetooth device sold just to prevent any interoperability issues!
No one owns the airwaves. If you don't want to pay the SIG fees, simply do not use their logo or name.
well yeah but then how do you communicate to your customers that your device interoperates with Bluetooth?
>This article is not about Bluetooth in general

Here you are https://habr.com/en/articles/456182/

Unrelated: Every once in a while you'd see a familiar name on this website. Thank you for goodbyedpi, it saved me when all isps in my country started blocking raw.githubusercontent.com among others ofc :)
Good work putting all this together. Not saying anything is wrong necessarily, but missing part of the picture.
Didn't think about this, do you have more information about this?
Not really. Just experience
Do you have any links?
Nope