On Sat, 2012-01-21 at 17:36 +0200, Tanu Kaskinen wrote: > It's not clear to me how this kind of situation should be handled. What > to do when the user requests moving the audio away from the bluetooth > device and bluetoothd closes the stream? My proposal is to mark the HSP > ports as unavailable when the stream gets closed by bluetoothd. The > expectation is that some policy module will detect that and move the > phone streams elsewhere. If there isn't a suitable policy module loaded, > the HSP sink and source shall just sit there without processing any > audio. When not using SCO over PCM, the current behavior seems to be change the profile to "off". Until priority list routing and automatic port activation based on availability status is implemented, the behavior is probably ok. The immediate problem is then just to do the same thing with the SCO over PCM mode. With automatic port activation, there will be a problem: the HSP ports will still be technically available, so there's a danger that when the user tries move the audio away from the headset, it will immediately be moved back, because the routing logic will see that the HSP ports still have the highest priority and they are still available. This is the problem that I tried to solve in that quoted text. -- Tanu
