On Thu, 2012-07-26 at 12:20 +0200, Mikel Astiz wrote: > Currently (and IMO incorrectly) module-bluetooth-device and > module-bluetooth-discover include some policies to handle the initial > state and the transitions. This needs to be revisited though: my > proposal would be to move all policies outside these modules (so no > automatic profile switching), and use the port availability flags to > expose which streams are playing (and thus the profile should probably > be switched accordingly, but from some other policy module). If the receiving end can initiate the A2DP streaming, then it would seem logical to mark the port available even if the stream is not currently playing. -- Tanu
