F5F Stay Refreshed Hardware Desktop Issue with headphone jack not working on Linux Mint running on a Samsung Chromebook 4.

Issue with headphone jack not working on Linux Mint running on a Samsung Chromebook 4.

Issue with headphone jack not working on Linux Mint running on a Samsung Chromebook 4.

C
Cherry_Bell
Member
161
01-22-2026, 07:10 AM
#1
I converted a Chromebook from my ISP into a Linux workstation because I prefer not to use ChromeOS. Initially, everything functioned smoothly with fresh firmware and a UEFI BIOS installed alongside my preferred distribution, Linux Mint. However, when trying to play music on the device, the headphone jack failed to respond. I explored using alsamixer, discovered a script tailored to my soundcard (though it didn’t help), reinstalled PulseAudio, and tried various troubleshooting steps. Despite these efforts, the headphone jack remains non-functional. On the other hand, the speakers work fine, and there’s an entry in alsamixer for a "Headphone Jack" stuck at 00. My device is a Samsung Chromebook 4 with the "sof-glkda7219max" sound card and an Intel Gemini Lake HDMI chip. If you have any additional details or logs, please share. Thanks ahead, Chocolate_Moose
C
Cherry_Bell
01-22-2026, 07:10 AM #1

I converted a Chromebook from my ISP into a Linux workstation because I prefer not to use ChromeOS. Initially, everything functioned smoothly with fresh firmware and a UEFI BIOS installed alongside my preferred distribution, Linux Mint. However, when trying to play music on the device, the headphone jack failed to respond. I explored using alsamixer, discovered a script tailored to my soundcard (though it didn’t help), reinstalled PulseAudio, and tried various troubleshooting steps. Despite these efforts, the headphone jack remains non-functional. On the other hand, the speakers work fine, and there’s an entry in alsamixer for a "Headphone Jack" stuck at 00. My device is a Samsung Chromebook 4 with the "sof-glkda7219max" sound card and an Intel Gemini Lake HDMI chip. If you have any additional details or logs, please share. Thanks ahead, Chocolate_Moose

S
SoapPvP
Member
55
02-03-2026, 09:11 AM
#2
Some believe Android is still Linux-based, but that's not true. The situation has changed over the years. I’m more used to issues like hackintoshops than Linux itself. The real problem often lies with drivers not being available for a specific hardware version. For a driver to exist, someone needs expertise in writing Linux drivers and purchases one, only to face delays. Usually, it takes time. A practical solution is using a USB dongle if Bluetooth isn’t working—this lets you connect wirelessly and still enjoy audio.
S
SoapPvP
02-03-2026, 09:11 AM #2

Some believe Android is still Linux-based, but that's not true. The situation has changed over the years. I’m more used to issues like hackintoshops than Linux itself. The real problem often lies with drivers not being available for a specific hardware version. For a driver to exist, someone needs expertise in writing Linux drivers and purchases one, only to face delays. Usually, it takes time. A practical solution is using a USB dongle if Bluetooth isn’t working—this lets you connect wirelessly and still enjoy audio.

E
ELITEDRAG
Member
58
02-03-2026, 09:34 AM
#3
I'm trying to understand how Android fits into this setup because Chrome OS runs on Linux. Would you like more details? If no software option exists, you might consider using a USB dongle to connect audio directly.
E
ELITEDRAG
02-03-2026, 09:34 AM #3

I'm trying to understand how Android fits into this setup because Chrome OS runs on Linux. Would you like more details? If no software option exists, you might consider using a USB dongle to connect audio directly.

P
PetqPqn
Member
68
02-04-2026, 09:37 AM
#4
They’re essentially both developed by Google and built upon Linux. Or perhaps Chrome started from something simpler. Android did have an open-source phase. I think ChromeOS never had that, though some still associate it with Android. A tangible button would be preferable, but it would require disassembling and soldering. More costly, or possibly even more so if things go wrong. Edited October 27, 2022 by Bombastinator
P
PetqPqn
02-04-2026, 09:37 AM #4

They’re essentially both developed by Google and built upon Linux. Or perhaps Chrome started from something simpler. Android did have an open-source phase. I think ChromeOS never had that, though some still associate it with Android. A tangible button would be preferable, but it would require disassembling and soldering. More costly, or possibly even more so if things go wrong. Edited October 27, 2022 by Bombastinator