There are no bluetooth specific controls for the SDK except for controlling bluetooth GPS and bluetooth remote control events (i.e. play/stop/volume up/down). It's not something that is programmed into the application at a low level. You can confirm this yourself by downloading the freely available SDK at developer.palm.com. Certain applications have special permissions to use undocumented SDK properties such as media locking which I'm sure helps a lot in terms of getting bluetooth audio working properly as it locks the app as a media application at startup. But, these are only available to a few select applications (and we aren't one of them).
Originally Posted by toaste
There's also a difference between a PDK application versus HTML5 applications and how the system handles bluetooth. Sound in the PDK is handled very rudimentarily with minimal routing directly to the audio processor of the operating system (which I believe is still gstreamer). The audio libraries are basically integrated into the application when it's compiled. HTML5 applications, on the other hand, use additional layers in order to get audio to work. You have the web audio layer on top of the Enyo layer which then backends to the Enyo libraries which then send to the audio processor. If any of these layers has a bug in it, there's going to be an issue. But, us developers can only really control one layer of it when it comes to audio and that's the web audio layer. There's really only one way of handling audio in a web app (two if you include the very basic Enyo.Sound library but that doesn't work well for streaming audio and is meant more for things like sound board applications or game web apps).
On the audio side of things, our Touchpad application uses the same audio setup as our Palm Pre/Pixi application (both use HTML5 audio with the audio class set to media). If you have a Pre/Pixi you should be able to confirm that bluetooth audio works pretty flawlessly in our Pre app with the occasional hiccup. This leads me to say that it has to be a bug in either Enyo or the operating system itself, particularly in the way that bluetooth audio is routed for media application without media locking and there's not really anything that we can do about it. If we could, we would. We'd like to be able to deliver a perfect application but our hands are tied working within the confines of a very limited SDK.