[dishe]

Not that I want to defend the widcomm stack anymore, but I've noticed one great feature: A2DP starts up / turns off when it is supposed to, even during a stream.

The MS stack had a problem with 3rd party applications that send audio out to the speaker. For example- If an A2DP stereo headset was connected before I started CorePlayer, it would stream to the headset. However, if I started CorePlayer, and audio is coming out of the device, then I start the headset, it will continue playing out of the device. I have to shut down coreplayer and open it again to make it start using the headset.

This bug has plagued me for years, especially since I have A2DP stereo receivers in both my cars. When I turn off the car, the audio is STILL trying to send out to the BT stack, even though the connection to the device is gone. And if I was listening to wired headphones before I get into the car, I can't just switch to the car speakers over BT without closing the app. A real PITA.

Its something I learned to just deal with until the Widcomm stack- wow, now even in the middle of a song I can turn on my BT stereo and have it stream. Turn it off, it goes back to the handset. Perfect! At least they did SOMETHING right! People on XDA have been trying to fix that part of the MS stack for a long time, but there was a problem with the way streams are handled that prevented it from working.

I'm not saying I wouldn't like the option of an MS stack, but it might be more possible to fix the little bugs in widcomm- these seem like bugs that can totally be patched.