From: Tanu Kaskinen <tanuk@iki.fi>
To: Oleksij Rempel <bug-track@fisher-privat.net>
Cc: pulseaudio-discuss@lists.freedesktop.org,
linux-bluetooth@vger.kernel.org
Subject: Re: [pulseaudio-discuss] how to troubleshoot bluetooth audio issues?
Date: Sun, 14 Oct 2012 18:59:50 +0300 [thread overview]
Message-ID: <1350230390.30695.22.camel@x230> (raw)
In-Reply-To: <507ADA75.9040204@fisher-privat.net>
On Sun, 2012-10-14 at 17:29 +0200, Oleksij Rempel wrote:
> Hallo all, (Pulseaudio and Bluetooth devs)
>
> i have Samsung HS3000 bluetooth headset. Mostly it works but there are
> different issue with it:
>
> - volume level seems to be set to max (at really uncomfortable level)
> - at the moment i trying to change volume with pavucontrol or after it i
> get bad sound. Some times sort of cracky or trashy sound, some times
> just white noise.
> - play/stop key do not works with linux (not pulse issue)
>
> how to troubleshoot this issues? what tools should i use and where
> should it start?
Regarding the broken audio: I would suspect that the headset is buggy,
because the volume handling code should be pretty well tested in
pulseaudio, and I don't think bluetoothd touches the audio signal at
all. To confirm that, I think it's somehow possible to capture the audio
that is sent to the headset, but I don't know how. Maybe the bluez
people can answer that (I'm a pulseaudio guy myself).
Are you using the headset in the HSP or A2DP mode, btw? If A2DP, then
that would suggest a pulseaudio bug, since I don't think the headset
will get any notification via A2DP when you change the volume in
pavucontrol.
--
Tanu
next prev parent reply other threads:[~2012-10-14 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 15:29 how to troubleshoot bluetooth audio issues? Oleksij Rempel
2012-10-14 15:59 ` Tanu Kaskinen [this message]
2012-10-14 17:24 ` [pulseaudio-discuss] " Oleksij Rempel
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=1350230390.30695.22.camel@x230 \
--to=tanuk@iki.fi \
--cc=bug-track@fisher-privat.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pulseaudio-discuss@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).