I need some help with my recently purchased Headset . It’s a trimode headset, and I’ve been struggling to get it working properly on my Fedora 41 system, which uses Pipewire.
When the headset is paired via 2.4GHz mode, it doesn’t work right away. Only the right side of the headset works. I can hear sound only on the right ear, while the left ear does not output audio. However, when I use the headset with a cable (USB-C or 3.5mm), both sides work perfectly fine.
I’ve also tested this same headset on windows with the 2.4GHz mode and it works fine.
Troubleshooting steps already taken:
Pipewire settings: I’ve tried adjusting settings via alsamixer and Pipewire configurations, including changing profiles and balance settings, but it hasn’t helped.
PulseAudio: I even tried switching back to PulseAudio (which didn’t work on my system)
Other suggestions: I’ve gone through various solutions I found online, but nothing seems to fix the problem.
System logs: I checked journalctl for any related error messages, but there was nothing useful that pointed to a clear cause of the issue.
I would appreciate it if anyone has faced a similar issue with this headset or with wireless headsets in general, especially when using the 2.4GHz mode with Pipewire on Fedora. I’d love to hear any suggestions or solutions that might resolve the audio issue in wireless mode.
Thank you in advance for your time and help!
System Info:
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
It’s been really hard to figure out whats up with this… Also the headset can change between Stereo and Surround (up to 7.1 or smth like this.) with a double click on the mic mute button, but this does nothing and the issue keeps with only the right side working.
If you are getting only the right channel with digital stereo output, I’d be tempted to blame the headphones. Isn’t it the chip in the headphones that decodes the stereo signal when the signal is digital? Do you have some other stereo bluetooth device you can test with?
I think Windows might be using different (proprietary) bluetooth audio codecs, so it might be possible that a bug in the headset’s chip/firmware would be decoding some signals/codecs correctly, but not others.
I do have another bluetooth device which is an earphone but sadly I can’t test with my pc as I dont have any bluetooth adapter or support.
Also remember I’m using it on 2.4ghz mode and I can confirm the headphone works perfectly on 2.4ghz on Windows, maybe because it was more tested there or even developed to work with Windows, but idk.
I’ll try another distro by a live ISO to see if the issue persists
Btw I just noticed that when it makes the connection it quickly makes sound at the left side (none at the right) and then no signal of sound, then to make it get back I need to adjust the volume through the plasma-pa panel some times, but it gets back only with the right side.
Edit: Just tested this issue on a CachyOS live iso and its the same
If anyone wants to check this is the headset I’m trying out:
It probably lacks support on Linux for some reason
You got me. FWIW, I just tried to find some info about how all this works with bluetooth and I found this thread interesting/informative. The gist of it is that the signal is likely decoded and re-encoded several times.
… Assuming the transmitter takes in a 3.5mm phono or RCA jack, the input is analog. It’s converted to digital inside the box before transmitted to the headphones. The headphones have a DAC in them to decode the data from the Bluetooth signal into an analog one to drive the headphones. …
… I wasn’t aware Bluetooth supports AAC as-is, because normally that’s what the music file is encoded as. However, this doesn’t mean the Bluetooth transmitter will take an AAC encoded music file and transfer it as-is, because by the time the transmitter gets it, it was decoded into some other format in the case of using TOSLINK or it’s in analog in the case of using 3.5mm.
So basically if you were playing an AAC encoded file, it’ll get decoded, then re-encoded. It’s the same thing as if you saved a JPEG as a PNG or BMP file, then resaved it as a JPEG.
Edit: Nevermind, you are using wireless (2.4GHz), so the bluetooth path/codecs wouldn’t apply.
Well, just seems that this headset is borked for Linux drivers rn, it’s very buggy, when I adjust the volume through its buttons the sound stop working and it will only get back when I adjust through plasma on the plasma-pa, very weird behavior, using it with bluetooth instead 2.4GHz may be better, but I can’t test this rn unfortunately.
Got to solve it using alsamixer, when I tried it at the first I didnt notice I needed to select the device, I thought it would be already selected because it was the default device.
It’s a very common issue on linux with alot types of 2.4ghz headsets, and oddly you can only solve it with ALSA Mixer.