From: Niv <nivv@cs.bgu.ac.il>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] headset wont work <sdp?>
Date: Fri, 13 Jan 2006 00:43:44 +0200 [thread overview]
Message-ID: <43C6DBA0.9050002@cs.bgu.ac.il> (raw)
In-Reply-To: <43C69CA3.1060606@cs.bgu.ac.il>
sorry for postting so much, its just that I am putting an effort to
resolve it by myself.
I am at the point of suspecting the headset aint pairing right:
> HCI Event: PIN Code Request (0x16) plen 6
bdaddr 00:02:72:E1:03:6A
> ACL data: handle 41 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 3 status 0
Connection refused - security block
> HCI Event: Disconn Complete (0x05) plen 4
status 0x00 handle 41 reason 0x13
Reason: Remote User Terminated Connection
I deleted all content of /var/lib/bluetooth/<dongle addr
>/ and I also turned auth and encrypt off in hcid.conf
when I reset /etc/init.d/bluetooth I see:
* Starting Bluetooth ...
* Starting hcid
... [ !! ]
* Starting sdpd
... [ ok ]
* Starting rfcomm
... [ ok ]
I have already uninstall and reinstall all bluez as well as
bluetooth-alsa to the latest version
:-(
Niv
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-01-12 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:08 [Bluez-users] headset wont work <sdp?> Niv
2006-01-12 18:14 ` Niv
2006-01-12 22:43 ` Niv [this message]
2006-01-13 1:47 ` Niv
2006-01-13 3:20 ` Niv
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=43C6DBA0.9050002@cs.bgu.ac.il \
--to=nivv@cs.bgu.ac.il \
--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;
as well as URLs for NNTP newsgroup(s).