There absolutely does, Android did with low power audio. They even goes a step further by offloading bluetooth processing into DSP.

I’m not in this space anymore but as of Android 5-6 era aac and bt is offloaded to hexagon dsp on qualcomm device.

You might be referring to this but on top of hardware decode some Bluetooth setups can send the actual AAC file to the headphones and decode it there.

Traditionally Bluetooth audio meant decoding and reencoding it into a crappier codec before transmission. So it's an efficiency and quality win.

I think some Google Pixel Bud Pro earphones do this for Opus but that is rarer (there's a few other codecs that have been done like this over the years by different manufacturers).

Yap it’s called GDC and I’ve set it up for customer that requires it because of regulatory compliance.

It’s very expensive but you got the box ready in your data center and is managed by both Google and partner.

How hard was it to setup ? Any tips ?

Yet they’re lacking in the model spaces.

Things changed since Apple Intelligence but I was hoping there’ll be more things like live captions and what-not than chatbot use cases. I feel pixel is also moving towards that and abandoning the old way unfortunately.

TPUs are not that portable and easy for both inferencing and training. It has since improved a lot with their effort on the torch backend (XLA/TorchTPU) and JAX though.

But as far as i know it currently supports just that + tensorflow (which nobody uses it anymore, least here). And last we tried, so much of our kernels needs rework that it’s not worth the effort.

This may change since ironwood but we haven’t tried that generation.

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?