01-10-2020, 09:17 PM
After re-reading the thread it appears that (1) the blues-alsa maintainer considers this a Pulsaudio issue, (2) the Pulseaudio maintainer has fixed it, and (3) there is a workaround (recompile bluez-alsa) for older Chromebooks that have the "bad" version of Pulseaudio.
I'm not seeing a reason to change the build recipe for bluez-alsa in moOde and risk regressions and support issues.
-Tim
I'm not seeing a reason to change the build recipe for bluez-alsa in moOde and risk regressions and support issues.
-Tim