librepods-org / librepods-org/librepods
Connected device detection broken when using wireplumber 0.5.13
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
The latest wireplumber version appears to break the MediaController class's "isActiveOutputDeviceAirPods" check, affecting features such as ear detection and conversational awareness. This appears to be due to a name formatting change when querying the default sink name.
Steps to reproduce in the current version:
- With wireplumber 0.5.13 installed, start librepods and connect AirPods
- Start playing some audio on your system
- Remove an AirPod. Ear detection should fail
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MediaController class and its isActiveOutputDeviceAirPods check, then reproduce the issue with wireplumber 0.5.13 while tracing the queried default sink name. Done means connected AirPods are detected and ear detection works after removing an AirPod during playback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100