Hi Pali, On Tue, May 7, 2019 at 11:52 AM Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > > On Monday 06 May 2019 15:02:25 Pali Rohár wrote: > > On Monday 06 May 2019 15:46:03 Luiz Augusto von Dentz wrote: > > > Hi Pali, > > > > > > I hope this fixes the problems you have been seeing, it should at > > > least take care of the issues with wrong order of SelectConfiguration > > > and restoring the exact same endpoint used last time. > > > > Hi Luiz! Great, this should make bluez to be more deterministic. > > Hi! Now I looked at it and in cache file I see: > > LastUsed=04:01 > > What would happen when A2DP application (e.g. pulseaudio) register DBus > endpoints in different order? Or e.g. do not register some endpoints due > to missing codec librayr (aptX). > > I guess that in this case LastUsed information stops working... It would most likely fail at SelectConfiguration and then try with the other endpoints. > > Should not be there stored rather dbus endpoint name identifier? Originally I tried to avoid having the local endpoints because of this problem, but now that SelectConfiguration can fail it shouldn't really be a problem. At least with the seid if you have a system that didn't changed the order or number of endpoints it will keep working as expected, if we choose to encode the D-Bus connection, etc, as soon as PA is restarted, the system is rebooted, etc, the D-Bus connection may have changed making the stored values in LastUsed invalid. Anyway chances are the LastUsed is only invalidated if you update PA, in which case there could be new endpoints or a change in their order and package can also provide a script to clear the LastUsed if that happens, but then again LastUsed setting does not actually store the configuration just the endpoint so SelectConfiguration has control over the configuration. -- Luiz Augusto von Dentz
