From: David Henningsson <david.henningsson@canonical.com>
To: "Nathanael D. Noblet" <nathanael@gnat.ca>
Cc: alsa-devel@alsa-project.org
Subject: Re: Internal Mic Boost channel is unused
Date: Mon, 16 Sep 2013 23:57:48 +0200 [thread overview]
Message-ID: <52377EDC.6040105@canonical.com> (raw)
In-Reply-To: <5237204A.7040602@gnat.ca>
On 09/16/2013 05:14 PM, Nathanael D. Noblet wrote:
> On 09/13/2013 06:34 PM, David Henningsson wrote:
>>>> > 2) The internal microphone requires that the mic boost channel be
>>>> something other than 0 to function properly.
>>>>
>>>> You have to find out whether node 0x1a or 0x1b can be used as the
>>>> headset
>>>> jack (headphone with Mic using TRRS connector)
>>>
>>> So basically I need to plug a microphone into each port and figure out
>>> if both of them work as microphone. A couple things.
>>>
>>> 1) What if both can be a microphone?
>>> 2) If only one can be a microphone, I have no idea how to tell you if
>>> its 0x1a or 0x1b.. hda-analyzer/alsa low level stuff is completely new
>>> to me.
>>
>> When you plug something in, you can look at the output of "amixer -D
>> hw:<cardname> contents" to see what, if anything switched to "values=on"
>> instead of "values=off".
>>
>> We would like you to plug a mic into the mic jack and see in what way
>> the output of "amixer -D hw:<cardname> contents" changes.
>> Then we would like you to plug a headset (with both headphone and mic,
>> like most smartphones have), and again see if there's a difference in
>> amixer.
>> You can also try this with a headphone only in the headphone jack, if
>> you like.
>>
>
> So here's what I did. I didn't have a combo headphone/mic thing handy.
>
> 1) nothing.out is the netbook with nothing external plugged in.
> 2) mic.out is when I plugged in a microphone into the mic jack
> 3) head.out is when there were headphones plugged into the headphone jack
> 4) both.out is when something was plugged into both (mic into mic and
> headphone into headphones...
>
> A quick diff shows that amixer is seeing differences.
> --- nothing.out 2013-09-16 09:11:54.678168182 -0600
> +++ mic.out 2013-09-16 09:11:54.675168245 -0600
> @@ -6,7 +6,7 @@
> : values=on
> numid=18,iface=CARD,name='Mic Jack'
> ; type=BOOLEAN,access=r-------,values=1
> - : values=off
> + : values=on
> numid=20,iface=CARD,name='Mic Jack',index=1
> ; type=BOOLEAN,access=r-------,values=1
> : values=off
>
>
> Given this information... what's the next step?
Matching this with your alsa-info, we can see that 'Mic Jack'
corresponds to 0x1b and 'Mic Jack', index=1 corresponds to 0x1a.
Hence you could try turning pin 0x1a to "not connected" in
hda-jack-retask. (I don't know how/if hda-jack-retask is packaged in
Fedora, but it is part of alsa-tools.)
If this resolves your problem, we could then try making that the default
in upcoming kernels, but the question is we really dare to do that,
without clear confirmation that 0x1a is actually useless. In current
state it's a bit buggy, but if the headphone jack is actually a headset
jack turning that off would make the headset mic go from "needs manual
adjustment to work" to "completely unusuable".
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2013-09-16 21:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 15:52 Internal Mic Boost channel is unused Nathanael D. Noblet
2013-09-12 18:43 ` David Henningsson
2013-09-12 19:17 ` Nathanael D. Noblet
2013-09-13 3:23 ` Raymond Yau
2013-09-13 16:04 ` Nathanael D. Noblet
2013-09-14 0:34 ` David Henningsson
2013-09-16 15:14 ` Nathanael D. Noblet
2013-09-16 21:57 ` David Henningsson [this message]
2013-09-18 15:28 ` Nathanael D. Noblet
2013-10-09 19:46 ` Nathanael D. Noblet
2013-10-09 19:58 ` Nathanael D. Noblet
2013-10-10 13:33 ` David Henningsson
2013-09-14 2:23 ` Raymond Yau
2013-09-14 4:14 ` Raymond Yau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52377EDC.6040105@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=nathanael@gnat.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.