Pete,

1) Thanks.

2) As far as I know, the quality of the A2DP stream is not dependent on the media file being played. It would of course be possible for an application to packetize a pariticular media file appropriately and send it out over A2DP, but I don't believe that's how it's done. The A2DP spec says that the devices are supposed to choose the codec bitrate based on what is available on the channel, which implies on-demand re-encoding. Also, A2DP implementations are only required to support the SBC codec, which is NOT a standard codec for media files, again implying re-encoding. SBC is not very good compared to optional codecs of MPEG1, 2, or 4 audio. I don't know which codecs the Widcomm A2DP implementation supports, but the probem could be more than bandwidth. Since it is doing the encoding with software, it could be that it just can't encode fast enough to keep up with realtime. Or it could be that it isn't choosing a low enough bitrate. If Mpeg-4 were supported, even 96kbits sounds pretty good, and the i730 can handle that speed no problem.

The biggest problem for A2DP with the MS stack is that there is simply software implementation of the A2DP profile for any Windows CE 4.2 devices running the MS bluetooth stack. And unfortunately, implementing one would be very difficult or impossible. A2DP is a layer on top of AVDTP, a protocol which is not implemented in the Microsoft stack, and which is on top of L2CAP protocol, which is implemented but there is no interface to interact with it in Windows CE 4.2 (not documented interface, but there must be a way).