View previous topic :: View next topic |
Author |
Message |
keekkenen n00b
Joined: 05 Oct 2024 Posts: 28
|
Posted: Thu Jan 02, 2025 6:17 pm Post subject: pipewire with bluealsa under open-rc |
|
|
I tried to tune it with https://wiki.gentoo.org/wiki/PipeWire and https://wiki.gentoo.org/wiki/Bluetooth_headset a few times. I used the original method in these manuals or added something else to the configs, but I had the result - after pairing the headset worked right (all Bluetooth codecs were available) but after restart pc or Bluetooth I got only HSP/HFP mode.
I tried to delete /var/lib/bluetooth folder, restart Bluetooth and pair again. It works only for the first time only.
Why is it so hard to tune? _________________ 7950x3d / x670e MSI Tomagawk / Sapphire RX 7800XT 16Gb / G.Skill 64Gb 5600 / A-Data Legend 960 2Tb (x2), A-Data SX8200PNP 256Gb |
|
Back to top |
|
|
FranciscoJaimes n00b
Joined: 15 Jan 2025 Posts: 24 Location: Mexico
|
Posted: Wed Jan 15, 2025 10:09 pm Post subject: |
|
|
It sounds like you're encountering issues with Bluetooth profiles not persisting after reboot, likely due to PipeWire or Bluetooth service misconfiguration.
Here are a few things to try:
Ensure PipeWire is set up correctly: Make sure both pipewire and pipewire-alsa are installed and running, as well as pipewire-pulse for audio profiles.
Check Bluetooth configuration: In /etc/bluetooth/main.conf, ensure the AutoEnable=true setting is enabled to automatically use the best available profile.
Persistence of profiles: Sometimes, profiles like A2DP are overridden by HSP/HFP after reboot. You might need to enforce the preferred codec (A2DP) by manually selecting it in bluetoothctl or using a script after boot.
PipeWire and Bluetooth: If using PipeWire with Bluetooth, ensure the pipewire package is fully configured to handle Bluetooth audio. Sometimes using pulseaudio alongside PipeWire causes conflicts.
Update packages: Make sure your bluez and pipewire packages are up to date and that you're using the right configuration flags in Gentoo.
Try looking at log files (journalctl -xe and dmesg) for any error messages that could help pinpoint the issue. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|