Linux bluetooth development
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] "Can't connect RFCOMM socket"
Date: Fri, 24 Mar 2006 11:17:56 +0000	[thread overview]
Message-ID: <1143199077.6863.4.camel@bnocera.surrey.redhat.com> (raw)
In-Reply-To: <31511.1143197715@www019.gmx.net>

On Fri, 2006-03-24 at 11:55 +0100, Daniel Hertrich wrote:
> Dear bluez developers,
<snip>
> * rfcomm bind /dev/rfcomm0 00:02:EE:0D:71:96 1

Did you check that the device you're connecting to has RFCOMM on channel
1?

> --> The phone asks "connect to ?" I confirm and enter the pin which is
> stored in /etc/bluetooth/pin. After a few seconds:
> --> Can't connecto to RFCOMM socket: Resource temporarily unavailable

Double-check the pin setup in /etc/bluetooth/hcid.conf, the pin_helper
is the important thing.

> Some of the hci* tools complained about a missing libsdp library.

The tools will complain, but libsdp is included in libbluetooth nowadays
and isn't required anymore.

-- 
Bastien Nocera <hadess@hadess.net> 
It's beautiful, it's like a monkey.            -- Jean-Claude Van Damme



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-03-24 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24 10:55 [Bluez-devel] "Can't connect RFCOMM socket" Daniel Hertrich
2006-03-24 11:17 ` Bastien Nocera [this message]
2006-03-24 14:03   ` Daniel Hertrich
2006-03-24 14:55   ` Daniel Hertrich

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=1143199077.6863.4.camel@bnocera.surrey.redhat.com \
    --to=hadess@hadess.net \
    --cc=bluez-devel@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