From: "Aveek Audhya" <aveek@rebaca.com>
To: <Bluez-devel@lists.sourceforge.net>
Cc: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] connect fail : Operation now in progress
Date: Thu, 31 May 2007 16:44:19 +0530 [thread overview]
Message-ID: <E1HticC-00011g-SL@mail.sourceforge.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]
Hi,
I am trying to communicate with a J2ME application running on my
mobile phone(Nokia 6600) using a client program running on a Linux machine
(FC6). The 'sdptool browse' reports that the J2ME application is listening
on channel 4. The J2ME application is using btspp protocol whereas my client
side application is using RFCOMM. But when I run the client application, the
'connect' system-call fails (returns -1) with error value "Operation now in
progress". I am using BlueZ protocol stack.
What can be the probable reason for this kind of behavior? Any suggestion is
appreciated.
Thanks,
Aveek
[-- Attachment #1.2: Type: text/html, Size: 4685 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- 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 reply other threads:[~2007-05-31 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 11:14 Aveek Audhya [this message]
2007-05-31 15:07 ` [Bluez-devel] connect fail : Operation now in progress Bastien Nocera
2007-06-01 13:48 ` Aveek Audhya
2007-06-01 13:56 ` Bastien Nocera
2007-06-06 13:16 ` Aveek Adhya
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=E1HticC-00011g-SL@mail.sourceforge.net \
--to=aveek@rebaca.com \
--cc=Bluez-devel@lists.sourceforge.net \
--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).