From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: HDA: swap Speaker/Headphones PlaybackPriority
Date: Thu, 12 Mar 2026 09:53:16 +0100 (CET) [thread overview]
Message-ID: <189c0c0ab960cb00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/721@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #721 was opened from zommuter:
Fixes #720, assisted by Claude Code Opus 4.6
## Summary
- Swap `PlaybackPriority` in `ucm2/HDA/HiFi-analog.conf`: Speaker 100→200, Headphones 200→100
## Problem
On devices where Speaker and Headphones share the same PCM (e.g. `hw:sofhdadsp`), PipeWire/ACP generates separate mutually exclusive profiles. With the current priorities, the Headphones profile (10300) is preferred over the Speaker profile (10200) whenever both are `available`.
This causes the Speaker sink to **completely vanish** when an HDMI monitor is connected: the HDMI port becoming available makes both profiles `available: yes`, and WirePlumber selects the higher-priority Headphones profile — even when the Headphone Jack reports `off` (nothing plugged in).
Without HDMI, the Headphones profile is correctly `available: no` (no ports with availability groups report available), so the bug only manifests with HDMI connected.
## Fix
Swap the priorities so Speaker (200) > Headphones (100). Built-in speakers are the natural default output. When headphones are plugged in, WirePlumber detects the Headphone Jack becoming available and switches to the Headphones profile accordingly.
## Testing
Tested on HP OmniBook X Flip 14 (Intel Lunar Lake, Realtek ALC245, sof-hda-dsp) with PipeWire 1.4.10 and WirePlumber 0.5.13:
- HDMI connected, no saved WirePlumber state, no headphones plugged in
- **Before:** Active profile = Headphones, Speaker sink missing
- **After:** Active profile = Speaker, Speaker sink present
Note: Headphone jack switching (plugging in actual headphones) has not been tested on this hardware. The expectation is that WirePlumber's jack-based profile switching handles this regardless of base priority.
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/721
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/721.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-03-12 8:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/721@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=189c0c0ab960cb00-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox