chromebook-linux-audio icon indicating copy to clipboard operation
chromebook-linux-audio copied to clipboard

Samsung Chromebook Plus V2 (Nautilus) Headphones Jack / Internal Mic not working

Open Lioncat6 opened this issue 1 year ago • 6 comments

Describe the bug When using --force-avs-install to force the use of the built-in speakers, it seems the headphones jack no longer functions and in order to re-enable it, you must run the script again without that argument. The internal mic doesn't seem to work regardless.

Boardname Nautilus

Logs debug-logs.tar.gz

Lioncat6 avatar Jan 20 '24 16:01 Lioncat6

Headphones should show up if you plug them in, nothing in the logs indicates an error with headphones. As for internal mic, it looks like a bug in the stock chromeos firmware so there really isn't anything I can do about it.

WeirdTreeThing avatar Jan 20 '24 19:01 WeirdTreeThing

The device is always there to switch to, and no matter what I try, whenever using --force-avs-install, I cannot get any audio output from the headphones jack. When using sudo evtest, it doesn't even see the unplug/plug events that would usually show... as for why, I have no clue image image

Lioncat6 avatar Jan 21 '24 02:01 Lioncat6

Without using --force-avs-install (Functioning Properly) image image image

Lioncat6 avatar Jan 21 '24 03:01 Lioncat6

Interestingly enough, the headphones will still function until the second reboot after running the script with --force-avs-install, but running the script without it, rebooting, then running the script with it, then rebooting again to get both the speakers and headphones functioning at the same time is not exactly ideal...

Here's the logs when it's in this weird state with everything functioning:

debug-logs.tar.gz

alsamixer is on a different devices as well image

Lioncat6 avatar Jan 21 '24 03:01 Lioncat6

See what happens if you leave your headphones plugged in at boot. It seems like da7219 on kabylake broke with a recent kernel update.

WeirdTreeThing avatar Jan 21 '24 22:01 WeirdTreeThing

After some more fiddling around, I figured out that it seems to work on boot 100% of the time, but if it's suspended at all (doesn't matter if headphones are plugged it), it stops working.

Lioncat6 avatar Jan 21 '24 23:01 Lioncat6