Björn Daase

> I did not take a look at PipeWire's code but they probably take what ALSA is giving them and customize a little to make it more user friendly. So...

Thanks for your help! > If you recreate the profile it should work again. What I already tried was to delete the presets autoloading entry for that speaker, recreat it,...

> No. I was talking about recreating the autoloading profile. Sorry, I still don't get which profile/files you are talking about. The JSON files describing the actual profiles? > What...

> After this at the end of the log a usb device is connected. I imagine this is the one you are using to send audio to an external amplifier...

This is what I get from `pw-cli list-objects Device` ``` ➜ ~ pw-cli list-objects Device id 41, type PipeWire:Interface:Device/3 object.serial = "42" factory.id = "14" client.id = "33" device.api =...

What are the implications of this inability to tweaks these values (I am wondering since I see the above log messages)? Do we still expect to see improvements from system76-scheduler?

> Please add the HCI traces using btmon, Here you go, I hope that's what you were asking for: [hcitrace.txt](https://github.com/bluez/bluez/files/7218946/hcitrace.txt). It should only contain the profile switching and no further...

> You probably need to start recording from the start otherwise btmon wont be able to decode the RFCOMM commands, anyway I suspect the remote is sending a disconnect. Alright,...

Additionally, here is the trace of a normal connect which didn't have mSBC available: [hcitrace.txt](https://github.com/bluez/bluez/files/7234395/hcitrace.txt)

FWIW, this still happens with a 5.17.rc3 kernel.