public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vlad Skarzhevskyy" <skarzhevskyy@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Unable to read data via RFCOMM socket from a JSR82 program running on phone
Date: Mon, 14 Apr 2008 22:54:15 -0400	[thread overview]
Message-ID: <cc1649d10804141954h1be91b0an8b7e5bc6bfe8660b@mail.gmail.com> (raw)
In-Reply-To: <FFED2D1514034841A6270D98984E7D0C020C7159@pdsmsx415.ccr.corp.intel.com>

Hi Peter
  We at bluecove.org constantly testing connections from JSR-82 on top
of BlueZ on Linux to client on Mobile phone L2CAP or RFCOMM and back.
No problems detected in BlueZ.
  Make sure you are connecting to right service!

  Look at this application as test
http://snapshot.bluecove.org/bluecove-examples/bluecove-tester/  it
runs on Linux and the MIDLet version can be installed on the phone.

--
Vlad

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-04-15  2:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15  1:59 [Bluez-users] Unable to read data via RFCOMM socket from a JSR82 program running on phone Zhu, Peter J
2008-04-15  2:54 ` Vlad Skarzhevskyy [this message]
2008-04-17  6:56   ` Zhu, Peter J
2008-04-17  7:24     ` David Rehle
2008-04-17 13:37       ` Zhu, Peter J

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=cc1649d10804141954h1be91b0an8b7e5bc6bfe8660b@mail.gmail.com \
    --to=skarzhevskyy@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