> Bluetooth audio codecs do lossy real-time re-encoding of the audio

Lossless transcoding is possible too. https://en.wikipedia.org/wiki/AptX#aptX_Lossless

iPhones and Macbooks support aptX now. Surely this isn't just a hardware change — once Apple discloses the details, it won't be at all surprising if aptX Lossless (at minimum) is required for MFi licensing going forward.

FWIW, the transcoding you mention isn't a requirement of Bluetooth audio. MP3 and AAC bitstreams could be delivered straight to headphones for decoding there. We don't yet know if that's something Apple is discussing with MFi program members.

Yes, there are better codecs than the defaults. Now go to the specifications page for a random popular bluetooth audio device, and see if they even list which codecs are supported. If by some astonishing miracle they do say so, then work out which codec they would use with a random popular mobile device. It is all theoretically possible, but in practise regular folk are going to have a hard time!

I looked up recommendations for Bluetooth devices at Wirecutter and then went to the relevant tech specs page:

Mentions "bluetooth" (sometimes a2dp) and no more:

* https://www.bose.com/en_us/products/speakers/wireless_speake...

* https://www.amazon.com/AmazonBasics-Mini-Bluetooth-Speaker-P...

* https://www.marshallheadphones.com/mh_us_en/acton-black

* http://www.pioneerelectronics.com/PUSA/Car/Digital+Media+Rec...

* http://www.kenwood.com/usa/car/excelon/kdc-x998/spec.html

* http://www.jabra.com/music/jabra-move-wireless

* http://www.jbl.com/over-ear-headphones/SYNCHROS+E40BT.html

* https://www.ultimateears.com/en-us/ueroll2

* http://www.logitech.com/en-us/product/x300-wireless-speaker

* http://www.apple.com/iphone-6s/specs/ - the Nexus 6P page doesn't even mention bluetooth

Mentions codecs:

* http://rivaaudio.com/riva-turbo-x/#specs

* http://www.peachtreeaudio.com/deepblue2.html (Says "aptX bluetooth")

* http://www.bowers-wilkins.com/Wireless-Speakers/Wireless-Spe...

> Now go to the specifications page for a random popular bluetooth audio device, and see if they even list which codecs are supported.

That's an excellent point.

Sadly, I don't think the average consumer knows or cares about the badness that is lossy-to-lossy transcoding.

For those who do, aptX support is pretty easy to find in the sense that vendors tend to make "aptX" searchable in the name and/or description. (If you Google "amazon aptx headphones", you'll see what I mean.)

Finally, this is a great example of how Apple gets to "own" the mindshare for tech they don't invent. If Apple decides to hang their hat on the aptX brand for the iPhone 7 launch, that'll be how most people hear about it for the first time. Since aptX isn't their brand, it's more likely that Apple will simply tout "perfect wireless audio" and make sure customers know to look for "Made for iPhone" headphones.

there's not enough bandwidth. it's a marketing lie.

and usually introducing quite a bit of latency

Assuming you want to listen to music, latency really doesn't matter much.

I mean, nobody would ever want to use a phone to talk to someone, amirite?

I certainly wouldn't.