Linux bluetooth development
 help / color / mirror / Atom feed
From: jayjwa <jayjwa@atr2.ath.cx>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BT Headset connected but no sound
Date: Tue, 5 Feb 2008 20:57:46 -0500	[thread overview]
Message-ID: <alpine.LNX.1.00.0802052048490.20192@nge2.ngu.pk> (raw)
In-Reply-To: <47A8669E.4080308@gmx.de>


On Tue, 5 Feb 2008, Daniel Stumpner wrote:

-> I got it working!

Lucky ;)

I think I have some hardware incompatibility problems, because my 
logs are looking OK now, and the system device appears to transmit sound while 
the headset acts like it's receiving sound (yet no sound).


-> I patched my 2.6.23 kernel with the bluez-patch and attached the
-> force_scofix=1 option (to kernel boot line and to modrobe.conf just to
-> make sure)
-> That didn't change anything for me.
-> Then I installed the bluez-gnome agent and started the applet. That
-> helped me getting rid of the warning that no authorization agent is
-> available.
-> Should't be one in bluez-utils/daemon/auth-agent.c  ???

Yes, there should be a binary auth-agent.

-rwxr-xr-x 1 root bin 8552 2008-02-05 02:13 /usr/bin/auth-agent


-> How can I get this one working?

I've been starting both passkey-agent and auth-agent. I've not seen auth 
failures in my logs now. Start them before you try to use remote device.

passkey-agent --default (pin) (addr of remote device) &
auth-agent &

Both should background. That's from trial and error, I've not seen that 
documented anyplace. But it seems to work. YMMV.





-------------------------------------------------------------------------
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

  parent reply	other threads:[~2008-02-06  1:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:24 [Bluez-users] BT Headset connected but no sound Daniel Stumpner
2008-02-02  9:32 ` Daniel Stumpner
2008-02-02 10:40   ` Guillaume Bedot
2008-02-03  3:45     ` jayjwa
2008-02-03  4:25       ` Daniel Stumpner
2008-02-02 14:29   ` Guillaume Bedot
2008-02-03  8:05 ` Guillaume Bedot
2008-02-05 13:37   ` Daniel Stumpner
2008-02-05 15:25     ` Brad Midgley
2008-02-06  1:57     ` jayjwa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-05 11:40 pramod gurav

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=alpine.LNX.1.00.0802052048490.20192@nge2.ngu.pk \
    --to=jayjwa@atr2.ath.cx \
    --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