I have the same issue. Batch 6 laptop received yesterday, running windows 10, bios 3.07 and the most recent framework drivers. The computer otherwise seems to work well apart from a slightly irritating buzzing sound from the fan at low frequencies.
1 Like
+1 for this on Ubuntu 21.04, I’ve tried all the common answers and haven’t found anything. Killing pulseaudio gets rid of the hissing/static, but then obviously also kills any actual sound.
2 Likes
Since there’s been no official public comment from Framework about this issue, I’ll share an email thread I had recently with Framework support about this issue.
I have a batch 6 laptop (two batch 6 laptops now since they sent me a new one that also has this issue)
Mods, if there’s something in the TOS that prohibits sharing this correspondence, sorry about that. I checked and didn’t see anything.
5 Likes
That doesn’t look too promising… I don’t consider myself an audiophile by any means but the hissing sound is impossible not to notice on my unit.
I don’t know what the power implications would be of keeping the codec on whenever something is connected to the headphone jack to avoid the regular on/off beeping sound, but even if the beeping disappeared, the hissing on its own is rather distracting.
4 Likes
I’ve looked into disabling power savings for the sound card in Windows like you can in Linux but I haven’t found anything yet
1 Like
I’ve been struggling with this issue for a while, but just found something that fixed my issue. I’m not hearing crackling on one side only, so there may be more than one issue at play for those on this chain. My issue was very pronounced when people were speaking, so seems to be similar to what @jeshikat was experiencing. For context, I’m using the Realtek ALC295 chipset.
I found a solution from Robert Joynt here: Comment #17 : Bug #1648183 : Bugs : alsa-driver package : Ubuntu, but I’ll list the steps here as well. For me the issue was fixed immediately after running the script included here. It’s not the most straightforward fix as you need to re-run the fix on every boot (can be automated using cron though).
Potential Fix
sudo apt install alsa-tools
Create and save a script in /usr/local/bin:
#!/bin/bash
hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67
hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x3000
Run the script as root in a terminal to immediately fix the problem.
To run the script on startup, use cron with the @reboot command:
sudo crontab -e
and then add line in crontab:
@reboot [full path to script]
To run script on resume from suspend, copy the script to /lib/systemd/system-sleep
2 Likes
I have found another bug with the headphone jack. the output will be garbled when the following things happen.
- the laptop is running on battery
- when the chrome extension ultimate Volume Booster is active
I discovered this watching a podcast that is usually a bit quite. i put the volume booster to 200% and it worked fine when plugged into wall power. but when i unplugged the power cable the headphone output became garbled. i then opened a new tab so the extension wouldn’t be active and the output was fine. i turned up the volume on the laptop and it was fine. but then i turned on the extension but kept it at 100% (no boosting) and the output was garbled with no power cable.
I ran into a similar problem in my main rig a while ago. it was running a 4690k and the volume booster extensions would be garbled. i then upgraded it to the i7 4790k (for other reasons) and the volume booster extensions didn’t have a garbled output anymore.
idk if this a problem with chrome, windows, audio drivers or something else. it probably would take more effort than it was worth to fix this specific issue.
1 Like
Noise from electrical interference is a very common issue with headphone (or aux out) audio jacks on any kind of laptop or PC.
One possible solution for this general type of issue would be to buy some kind of compact external DAC or DAC/AMP. It will show up in your OS as a sound device (and thus could also be called an “external sound card”). The really cheap ones are often just called “USB audio adapters”, or something like that. There are many, many different options out there to choose from, including some extremely compact and extremely cheap ones, all the way up to some insanely expensive ones, and the different options they have can vary a lot.
Even a very cheap one might eliminate a problem like this, and any half-decent one will very likely eliminate this issue, and might also give you some additional features which are helpful to you. What kind you should get also depends upon what kind of headphones you’re running. They come in many shapes and sizes, under many different brand names. Audiophiles really like these kinds of things, but trying to figure out which one is best for you can potentially become very time consuming what with all of the different options out there.
Depending on your needs, these types of things can be very useful even if there is nothing wrong with your onboard audio or headphone jack.
This is a really cheap one: https://www.amazon.com/DuKabel-ProSeries-Mic-Supported-Headphone-External/dp/B07RS11M1T/ref=sr_1_1?crid=3HS1KIPRP3VBY&keywords=usb%2Baudio%2Bjack&qid=1644429643&sprefix=usb%2Baudio%2Bjack%2Caps%2C113&sr=8-1&th=1
2 Likes
It seems that my issue was specific to a pair of headset I was using. I recently bought a different headset and it works flawlessly. That leads me to think there is something about certain headsets and the 3.5mm jack that they use perhaps? I am on Windows 11 with all the latest drivers as well as the latest firmware from Framework.
1 Like
An update from my issues I wrote about in October:
I had an issue with my SSD where I unfortunately had to reinstall Windows (and all the drivers) completely.
Some combination of the switch from BIOS 3.02 to 3.07, the newest driver package, and a fresh copy of Windows 10 seems to have fixed the issue for me. No crackling, and I could swear that the audio quality is better in general. No hardware changes other than a new SSD, same headphones.
2 Likes
Like many of the users in this thread, I hear a little sound on my headphones when the chip enters or leaves power saving mode. I’m willing to disable power save to as Passerine described above, but only when I have headphones plugged in (since there’s no problem when the sound’s coming out of the speakers). Here’s how I implemented this hack on Arch Linux:
First, I installed acipd (sudo pacman -S acpid) and removed the default acpid configuration, since I don’t need it (sudo rm /etc/acpi/handler.sh /etc/acpi/events/anything).
Next, I created two new files in /etc/acpi/events defining rules to toggle the power save state when headphones are inserted/removed:
/etc/acpi/events/headphone-power-save-off
event=jack/headphone HEADPHONE plug
action=echo 0 >/sys/module/snd_hda_intel/parameters/power_save
/etc/acpi/events/headphone-power-save-on
event=jack/headphone HEADPHONE unplug
action=echo 1 >/sys/module/snd_hda_intel/parameters/power_save
Once these files were in place, I made sure the acpid service was enabled and running (sudo systemctl enable --now acpid).
This seems like a problem I’d expect to be fixed in firmware, but until then, this is an acceptable compromise for me - no squeaks when I have headphones plugged in, better battery life when I’m just on speakers.
6 Likes
I haven’t (knock on wood) experienced this problem for a while now. Unfortunately, I’m not sure what resolved the issue, as I haven’t applied any meaningful software updates (as far as I know or remember). I did move a few months ago. Perhaps the issue really is due to interference, as some have suggested.
1 Like
I am also experiencing this issue, I did not use anything with audio for a few days after getting my framework, but I noticed it as soon as I did. There is an electronic “beep” that occurs when the sound chip powers up followed by a strong/sharp background hiss, loud enough to bury some finer detail. This persists for as long as audio is playing plus around ten seconds before the chip powers down with another beep. All of these sounds are always the same volume and changing the volume in the OS does not affect them. This happens on Ubuntu 20.04.4, Linux Mint 20.3 and Windows 10; it happens on battery and ac power and is unaffected by which expansion cards are installed or which headphones are being used.
(Batch 8 DIY)
No such problem on win 10 after 5 days. Updated to new drivers etc.
When I’m wearing my headphones with the framework laptop, randomly I’ll get this short squeak sound come out of the headphones. It usually happens just after I plug them in and then randomly every 6-7 mins or so.
Currently I have the Batch 9 Framework
Headphones are Hifiman Sundaras
I’ve tried this with both Windows 10 and Ubunutu, the problem doesn’t change. I also did install the drivers and updated the BIOS to the latest version.
This isin’t that much of a big deal but I’m just wondering if other people have gotten this or if its just me.
1 Like
Yeah I’m getting the same issue I just found out today when I plugged my headphones in for the first time
You are not the only one - I have it too - and so do all these folks
So I think @FrameworkSupport should address this - it is not a huge issue but it is pretty annoying for us - it is to do with the sound chip going into and out of power saving mode.
Easily reproducible - by starting and stopping a youtube clip - it squeaks as the sound starts and then about 30 s after it stops as long as no other sounds are playing through headphones at the time.
3 Likes
Ah! I didn’t realize there was already a thread for this, I guess I didn’t see it since it wasn’t on the Community support section lol
Hiya all, this isn’t a solution but it’s at least a clear update on what framework is doing.
P.S. Support responded in just under 20 minutes! Kudos to yall
tl;dr
Framework knows that this is a problem, it’s an expected behavior from the chip, and they are actively looking for a replacement to use in the future.
Edit:
More info: https://frame.work/blog/solving-for-silicon-shortages
Edit 2:
Disabling power save mode will stop the beeps but the hissing will stay on instead of switching off after a couple seconds
8 Likes
Sorry to bring this thread back to life, but it’s a bit strange the issue stopped for some people. I’m encountering this issue as well right now.
1 Like