Hi Marijn, On Mon, Aug 9, 2021 at 1:31 PM Marijn Suijten <marijn.suijten@xxxxxxxxxxxxxx> wrote: > > Hi Sonny, > > On 8/9/21 7:46 PM, Sonny Sasaka wrote: > > Hi Marijn, > > > > Thank you for following up. Chrome OS has temporarily adopted my patch > > to resolve the issue without changing the audio client. We will pick > > up your patch at the next uprev. > > Note that these patches are still draft in search for initial feedback > on the approach, even if the implementation itself is trivial. Does > this mean you won't be able to test this locally until the next uprev? > Either way I will have to confirm their usefulness in PulseAudio too > before actually committing to this, so there's no hurry. Yes, Chrome OS is currently not working on solving this issue since there is already a local fix. We will adopt the BlueZ fix after your patch gets merged and is available in BlueZ future version when we rebase with upstream in the next uprev. > > Marijn
