public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ing. Gabriele Oberhammer" <gabriele@naustech.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Headset half working using Bluez's ALSA plugin
Date: Thu, 24 Jan 2008 23:30:58 +0100	[thread overview]
Message-ID: <479911A2.6040704@naustech.com> (raw)
In-Reply-To: <d89ddf300801240717g61e06642v28d6f0cf1b3cf2da@mail.gmail.com>

Ok, I eventually managed to compile and install bluez-utils!
The problem was that the audio module was not built, even if I used 
--enable-all switch in configure. To have the audio module built I had 
to add --enable-audio  (so it seems that --enable-all does not.... 
enable all  ;-)
Note that to have network/serial/input services built you have to add 
--enable-{network,serial,input} too.

Here's the correct configure  line:

sudo ./configure --prefix=/usr --mandir=/usr/share/man \ 
--sysconfdir=/etc  --localstatedir=/var --libexecdir=/lib \
--enable-all --enable-audio

Unfortunately I'm stuck with the same situation of the first post, i.e. 
playback works well but capture is not working.


$ arecord -D bluetooth -f S16_LE  /tmp/test.wav

produces always files 44 bytes long without any audio  ;(

So, before giving up, is there in the list someone with a fully working 
bluetooth headset who could give me some hints?

Thanks in advance,
bye.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-01-24 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 11:43 [Bluez-users] Headset half working using Bluez's ALSA plugin Ing. Gabriele Oberhammer
2008-01-22 16:14 ` Guillaume Bedot
2008-01-24 10:07   ` Ing. Gabriele Oberhammer
2008-01-24 15:17     ` Brad Midgley
2008-01-24 22:30       ` Ing. Gabriele Oberhammer [this message]
2008-01-24 23:20         ` Brad Midgley
2008-01-25  8:33           ` Ing. Gabriele Oberhammer
2008-01-25  9:01           ` Ing. Gabriele Oberhammer
2008-01-27 11:04     ` jayjwa
2008-01-27 11:26       ` Gabriele Oberhammer
  -- strict thread matches above, loose matches on Subject: below --
2008-01-24 13:42 pramod gurav
2008-01-24 13:54 ` Ing. Gabriele Oberhammer

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=479911A2.6040704@naustech.com \
    --to=gabriele@naustech.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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