https://bugs.freedesktop.org/show_bug.cgi?id=87081
--- Comment #7 from Tanu Kaskinen <[email protected]> --- I mean when the profile is added. That's the hook that module-card-restore uses. This dynamic profile adding was implemented to deal with new uuids being announced after the device has been created. The BlueZ 5 code doesn't seem to use pa_card_add_profile() at all. I think Mikel Astiz used that in the original BlueZ 5 patches, but Mikel's code got reverted. The current BlueZ 5 code doesn't seem to handle the case of new uuids appearing, which probably causes problems to some people, but that's not the problem in this case, because the a2dp uuid has already been announced by the device at the point where pulseaudio loads the device module. So, the problem appears to be that the a2dp profile is not yet connected when the device module is loaded. It makes sense to create the card profile, but its state is unavailable. How should module-card-restore behave in such situation? What if a2dp never gets connected? I think it's quite likely that if the card had previously the a2dp profile selected, the profile will get connected again, so I think module-card-restore should allow unavailable profiles to be selected, at least in case of bluetooth devices (I'm not sure that makes sense with alsa, but alsa profiles don't currently have availability information anyway). In the unlikely case that a2dp doesn't get connected, well, then the user has to switch the profile manually. I guess it's not module-card-restore that sets the profile to "off", though. Instead, it's the bluetooth card itself. If we want to allow the a2dp profile to be selected while it's unavailable, then module-bluez5-device has to be modified to not do the automatic switch to "off". So, my answer to "what if we instead allow the card to stay at the broken profile?" is that we should do that. I don't know how difficult it will be - I guess we want to keep the sink around too, so the sink will need to handle the situation where there's no transport available. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
