mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Conan <formyneeds2@tutanota.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux ALSA Development <alsa-devel@alsa-project.org>
Subject: Fwd: Lenovo Thinkpad T490 Microphone Noise
Date: Sun, 30 Jul 2023 10:04:39 +0700	[thread overview]
Message-ID: <9759f20c-cb24-dde4-cca6-f893033b7802@gmail.com> (raw)

Hi,

I notice a bug report on Bugzilla [1]. Quoting from it:

> I have reported this issue to the Arch but they redirected me to here.
> https://bugs.archlinux.org/task/79245
> 
> 
> Description:
> When I use microphone for online meetings, my sound reaches them with a high noise that prevent it from being understood. I tested the microphone on my own and yes the noise is there. I tried pulseaudio and pipewire, but neither has solved the problem. This problem is not stemming from hardware since I do not have this issue with Windows 10.
> 
> Additional info:
> * pulseaudio: 16.1-6, piprewire: 1:0.3.75-2, kernel: 6.4.6-arch1-1
> 
> Steps to reproduce:
> 1 - Open a chat app/website or online meeting tool like, Whatsapp, Signal, Zoom, etc.
> 2 - Speak to the microphone. You can use Whatsapp and Signal to listen your microphone sound.

See Bugzilla for the full thread.

The reporter chose the incorrect component when this bug was being filed
on Bugzilla (only generic `Kernel`), hence missing sound maintainers
and I had to forward it to the mailing list instead.

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217730

-- 
An old man doll... just what I always wanted! - Clara

                 reply	other threads:[~2023-07-30  3:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9759f20c-cb24-dde4-cca6-f893033b7802@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=formyneeds2@tutanota.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®