Hi Tanu, > So, does this sound like correct behavior: > > module-bluetooth-discover loads module-bluetooth-device whenever > anything is CONNECTED. module-bluetooth-discover never sets any > particular profile explicitly. module-bluetooth-discover already knows what profiles are connected and can hint module-bluetooth-device into what profile to use thus saving some ipc at loading. > If the "profile" module argument is not set, module-bluetooth-device > activates a profile that is PLAYING at the time when the module is > loaded. see above However I agree that splitting profile decision over two modules is not easy to deal with. I'd suggest that module-bluetooth-discover be made responsible for loading/unloading and updating profiles for the various instances of module-bluetooth-device. module-bluetooth-device itself should only apply what is said to it. module-bluetooth-discover then could be able to manage profiles on several devices at a time for example if two headset are paired, switch the first to off and the second one to HSP for example. > Is it possible that there are multiple profiles PLAYING? In theory yes, but the current implementation do not allow it : when profile is switched, previous profile is suspended/disconnected, and also user experience would be strange. However, it is possible if two devices are in use (each doing one profile). > If so, what should be the priority of each profile relative to each other? Even if both profile are not playing at a time. Maybe priority lists could be used in order to initiate connections. module-bluetooth-discover again is good place to put such behavior. Regards, Fr?d?ric
