[CHORD MS 530, recording] Microphone problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-driver (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
For 17.10, as requested, here is a Bluetooth test using Audio headphones. In this case I am using the CHORD MS 530. The sound works but the microphone does not. So I can't use it for meeting calls to talk and hear at the same time. I follow the normal steps of pairing and indeed it auto selected the device in the output tab of the sound option in the system settings, but on the input tab, it simply does not show as working. It shows on the input list but there is no recording working in there.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+
ProcVersionSign
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Jul 20 14:40:23 2017
InstallationDate: Installed on 2017-05-18 (63 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitec
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: CHORD MS 530
Symptom_Type: Only some of inputs are working
Title: [CHORD MS 530, recording] Recording problem
UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago)
dmi.bios.date: 01/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3401
dmi.board.
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases: /wiki.ubuntu. com/Releases
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.