Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Cant´t connect RFCOMM socket: Device or resource busy
Date: Fri, 14 Oct 2005 13:22:39 +0200	[thread overview]
Message-ID: <1129288960.5057.44.camel@localhost.localdomain> (raw)
In-Reply-To: <45bf5ff80510140328me0ad427k4c1a8269cc97dccb@mail.gmail.com>

Hi Artur,

> Im having this problem of getting this error message when i try to run
> the following command: 
> 
>         rfcomm -i hci1 connect 1 00:13:FD:BB:22:3F 9
>         
> 
> Can't connect RFCOMM socket: Device or resource busy
> 
> This happens everytime im downloading a file, i stop the bluetooth on
> my cell phone then i reconnect and try to send the same file. Is there
> a solution to handle this problem without reseting the hci1 ?
> 
> Even if i try to restart the bluetooth daemon the error persists, only
> reseting my machine im able to connect again using the rfcomm command.
> Im using debian sarge with the bluez packages. 
> 
>  
> 
> The output from from hcidump when i try to perform this operation is:

install the latest hcidump and use the -X and -V parameters.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-10-14 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 10:28 [Bluez-devel] Cant´t connect RFCOMM socket: Device or resource busy Artur Almeida
2005-10-14 11:22 ` Marcel Holtmann [this message]
2005-10-15 10:19   ` [Bluez-devel] " Artur Almeida

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=1129288960.5057.44.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --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