This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verification-needed-artful' to 'verification-failed-

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-artful

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  can't record sound via front headset port on the Dell Precision 3630

Status in HWE Next:
Status in linux package in Ubuntu:
Status in linux-oem package in Ubuntu:
Status in linux source package in Xenial:
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-oem source package in Artful:

Bug description:
  The Dell Precision 3630 is a desktop computer, it has only one front headset
  jack on it, after we plug a headset in it, we can't record sound via the

  And Realtek told us that "This platform was the fixed type headset only for
  iphone type. Fixed type headset was not run for default headset mode rule.
  It's hardware fixed type solution. Don't need to run software headset mode.
  Hardware layout not support UAJ functions."

  And Realtek submitted this patch to fix this problem.

  With this patch, the driver only set pin 0x19 as the headset-mic and will not
  call alcxxx_headset_mode init function anymore since the circuit is hardware
  fixed to be iphone-type headset-mic.

  [Test Case]
  Boot up the system, and plug a iphone-type headset, record the sound via
  headset-mic, it can record the sound and sound quality is pretty good.

  [Regression Potential]
  Very low, this patch is only specific to precision 3930 (subsystem id:
  0x10280871 and 0x10280872).

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to