From: "Murat D. Kadirov" <banderols@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Does not work BT headset
Date: Tue, 2 Sep 2008 22:51:53 +0600 [thread overview]
Message-ID: <20080902165153.GA5135@darkstar> (raw)
In-Reply-To: <alpine.LNX.1.10.0808290815350.26779@nge2.ngu.pk>
[-- Attachment #1.1: Type: text/plain, Size: 2017 bytes --]
08:22 Fri 29 Aug, jayjwa wrote:
>
>
> On Thu, 28 Aug 2008, pramod gurav wrote:
>
> -> Send the output of
> -> $ hcitool conn
> -> It should show both SCO and ACL connections.
root@darkstar:/etc/bluetooth# hcitool conn
Connections:
:/
For the first time, when I was pair my devices, all was normal.
> ->
> -> and have you run
> -> $ passkey-agent --default 0000 &
> -> try running this. This is way to set the PIN for authentication.
> -> And how do you connect before running mplayer?
> -> When you run mplayer it will automatically establish connection. So no need to do it manually if you are doing so.
>
> The audio player should make the connection itself, I think. Also, he seems to
> have the passkey-agent:
>
> -> Aug 27 19:08:10 darkstar hcid[5728]: Default passkey agent (:1.43,
> -> /org/bluez/passkey_agent_5737) registered
>
>
> I've always used it like so:
>
> passkey-agent --default 0000 <bt address of remote device> &
It had a crashing after power on headset:
# ps
..
/usr/lib/bluetooth/add-passkey 00:16:8F:DA:83:75
..
after power on headset proccess 'add-passkey' is down and in
/var/log/syslog appears:
Sep 2 22:42:53 darkstar audio[6044]: Access denied: Authorization agent
does not exist
Sep 2 22:42:54 darkstar hcid[6031]: Got NameOwnerChanged signal for
:1.29 which has no listeners
> Does it work with no remote address specified (could be)?
>
>
> I think it's the auth-agent that is not running. It may be needed. I always
> start this too.
>
> auth-agent &
Is it the same 'register-passkeys'? Yes, it running.
>
> Here:
>
> -> Aug 27 19:12:13 darkstar audio[5741]: Access denied: Authorization agent
> -> does not exist
>
>
> Is the headset an older Bluetooth 1.* device, or the newer 2.*? If it's 1.*,
> then it won't work without patching the kernel.
>
From documentation to headset: "Bluetooth 2.0 supporting headset and
hands-free profile", dongle support BT 2.0 too.
--
Murat D. Kadirov
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-09-02 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 4:11 [Bluez-users] Does not work BT headset pramod gurav
2008-08-29 12:22 ` jayjwa
2008-09-02 16:51 ` Murat D. Kadirov [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-27 13:27 Murat D. Kadirov
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=20080902165153.GA5135@darkstar \
--to=banderols@gmail.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