You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the UCM configuration for this board is the Chromebook Asus C300 one, but the volume levels set by default are far too low. It looks like when Pulseaudio loads on my system, it follows the initialization steps and results in a really low volume, as the Speaker is set to 27/100 and one must manually set the alsamixer levels to fix it. I could have a periodic task reload the volume state, but I find it better to override the UCM configuration manually and tell my package manager to ignore changes to that file during upgrade.
FWIW, my fix is to modify ucm2/codecs/max98090/EnableSeq.conf and change
(Alternatively, is setting the speaker volume necessary as part of this? It makes pulseaudio interfere with ALSA's state restoration logic, as ALSA will restore mixer levels at boot but pulseaudio will reset them thanks to the UCM config)
It looks like the UCM configuration for this board is the Chromebook Asus C300 one, but the volume levels set by default are far too low. It looks like when Pulseaudio loads on my system, it follows the initialization steps and results in a really low volume, as the Speaker is set to 27/100 and one must manually set the alsamixer levels to fix it. I could have a periodic task reload the volume state, but I find it better to override the UCM configuration manually and tell my package manager to ignore changes to that file during upgrade.
FWIW, my fix is to modify ucm2/codecs/max98090/EnableSeq.conf and change
to
Naturally, this is a bit of a nasty solution. It'd be nice to have an upstream fix in case other stuff is changed for this.
The text was updated successfully, but these errors were encountered: