From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Acer Aspire Go 16 (Conexant CX11970): Line Output has higher priority than Speaker causing wrong auto-switch after unplugging headphones
Date: Sat, 18 Jul 2026 22:45:04 +0200 (CEST) [thread overview]
Message-ID: <18c37d2ace4c1f00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18c37d2acd93e800-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #813 was opened from freewilly55a-boop:
## Hardware
Notebook: Acer Aspire Go 16 AG16-71P
Audio controller:
Intel Raptor Lake-P/U/H cAVS (SOF)
Codec:
Conexant CX11970
Distribution:
Debian 13 (Trixie)
alsa-ucm-conf:
1.2.14-1
PipeWire:
1.4.2
WirePlumber:
0.5.8
## Problem
The headphone jack detection works correctly.
When headphones are plugged in, the active sink becomes "Headphones".
After unplugging the headphones, the active sink becomes "Line Output" instead of "Speaker".
As a result, the internal speakers remain silent although no headphones are connected.
## Investigation
The problem is caused by the priorities in
/usr/share/alsa/ucm2/HDA/HiFi-analog.conf
Current values:
Line Output:
PlaybackPriority 300
Headphones:
PlaybackPriority 200
Speaker:
PlaybackPriority 100
## Test
Changing
PlaybackPriority 300
to
PlaybackPriority 50
immediately fixes the problem.
After restarting PipeWire:
Headphones plugged:
→ Headphones selected automatically.
Headphones unplugged:
→ Speaker selected automatically.
Automatic switching works perfectly afterwards.
## Suggestion
Please consider lowering the Line Output priority (or disabling Line Output) for notebooks using this SOF + Conexant CX11970 configuration.
If required, I can provide additional information or test patches.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/813
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-07-18 20:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <18c37d2acd93e800-webhooks-bot@alsa-project.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18c37d2ace4c1f00-webhooks-bot@alsa-project.org \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.