[pulseaudio-discuss] [BUG] Using bluez 5.5 & pulseaudio a bluetooth headset cannot be used as a recording device.

Tanu Kaskinen tanu.kaskinen at linux.intel.com
Mon Jun 3 02:14:14 PDT 2013


On Fri, 2013-05-31 at 19:43 +0200, Alexander Winnig wrote:
> >> /usr/local/bin/start-pulseaudio-x11 actually didn't exist. Should I
> >> create it or copy /usr/bin/start-pulseaudio-x11 to
> >> /usr/local/bin/start-pulseaudio-x11? I copied it over, rebooted but
> >> pactl list sources short still does not list sources.
> > If you didn't modify /usr/local/bin/start-pulseaudio-x11 so that it
> > runs /usr/local/bin/pulseaudio instead of /usr/bin/pulseaudio, then the
> > copying alone didn't change anything.
> >
> >> BTW: I did not use any flags when building bluez and pulseaudio...
> > Good.
> >
> I re-copied a new wheezy-image on my sd-card. Now pactl list sources 
> short shows the bluez-device. But still, an empty file is the output.

How exactly did you record the file? Did you ensure that you're
recording from the right source? If you use parecord, you can give the
source name with --device=sourcenamehere

> I have the impression that you need to make the headset believe that a 
> phone call is coming in for it's mike to become active.

I've never heard of such headsets. At least my headset allows PulseAudio
to use the microphone at any time.

-- 
Tanu



More information about the pulseaudio-discuss mailing list