> A2DP is really more a hardware issue (even though on
the PC side they talk about the supporting stack of
A2DP and installing the drivers for your BT dongle).
I don't think that's entirely accurate. A2DP is just a profile, and from what I can tell it's a firmware profile. BT hardware doesn't need to know or care about the profile being used. Data is sent/received from/to the BT device, and that's all the hardware really should care about. The drivers and profiles are all software and/or firmware.
http://en.wikipedia.org/wiki/A2DP#Bluetooth_profiles
<SNIP>
> So most (not all) BT hardware can handle the data
rate, and I think what we're really waiting for is BT
to standardize A2DP so that properly implemented
cross-vendor devices can communicate with one another
using full A2DP.
I think that A2DP
is a standard already. Any complete implementation of that standard
should work with any A2DP device. Here's some info on BT profiles from the BT SIG:
http://bluetooth.com/Bluetooth/Learn/Works/Profiles_Overview.htm
> It's not Apple's fault.
Well, it's not entirely Apple's fault, but they're certainly responsible for getting us an update.
In the case of the BT hardware in our iBooks, I believe it's a matter of just upgrading the firmware. The hardware is a Cambridge Silicon Radio BlueCore 3, which from what I can see clearly can handle A2DP and they do have firmware updates on their support site. I have no idea how to apply any of these updates at all, and quite frankly don't really want to try. I like my warranty. 🙂
Personally, I think all Apple needs to do is get an updated firmware package from CSR that has the stacks in it that we need, create an updater, and send it out with the next OS X patch. That's not a 100% verifiable fact, so take it with a grain of salt.
cheers,
/gam/