public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: john <john281198@gmx.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problems with InputStream and OutputStream
Date: Mon, 30 Aug 2004 14:34:03 +0200	[thread overview]
Message-ID: <41331EBB.9000606@gmx.de> (raw)
In-Reply-To: <1093867195.5620.16.camel@pegasus>

[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]

Hi,

the relevant parts of the sources are attached (the important parts are 
the BTMidServ.java and the method doConnect() in BTServiceSearchUI.java).
I hope the comments and Info-Messages will be enough declarations.

I use Debian Linux with a 2.6.7 Kernel and KDE version 3.2.3.
The phone is a Siemens SX1 with firmwareversion 10. It uses a Symbian OS 
Serie 60.
The USB-dongle is from Acer and should be supported from BlueZ.

Greeting Johannes

Marcel Holtmann wrote:

>Hi Johannes,
>
>  
>
>>The way, to start a server on the Handy I already tried, but I didn't had in
>>mind, that this has to be so, but to have a completely new connenction
>>between the devices (or has it to be so?).
>>    
>>
>
>forget about that. I was confused and thought that you wanna connect
>from the PC to your phone,
>
>  
>
>>The complete protocol is attached to the mail. The accosted lines exists
>>(see attachment - would it be better to see the java-sources?).
>>    
>>
>
>If you put it into a tar then name it this way ;)
>
>  
>
>>On the pc runs a server, that is listening to a connection. A mobile phone
>>searches for the device and the service, tries to connect an sends a 7byte
>>long string ("String!"). This way works without any problems. Immediately
>>after receiving, the server sends an 6byte long string("Handy!") to the
>>phone, using the same connection. But the phone only receives an empty
>>string.
>>    
>>
>
>The string "Handy!" goes over the connection and right after that the
>Linux side closes the connection. Maybe that is the problem or it is the
>credit based flow control on the phone. I don't see any CFC problem, but
>I also didn't wrote the Bluetooth stack on the phone. I think it is a
>good idea to add a sleep(1) before you close the connection.
>
>Some other information might be handy. What kernel do you use and what
>do you use as server on the Linux side? What kind of phone is this?
>
>Regards
>
>Marcel
>
>
>
>  
>


[-- Attachment #2: src.tar --]
[-- Type: application/x-tar, Size: 20480 bytes --]

  reply	other threads:[~2004-08-30 12:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 11:44 [Bluez-users] Problems with InputStream and OutputStream Johannes Lintner
2004-08-30 11:59 ` Marcel Holtmann
2004-08-30 12:34   ` john [this message]
2004-08-30 12:40     ` Marcel Holtmann
2004-08-31  7:42       ` Johannes
2004-08-31 10:23         ` Marcel Holtmann
2004-08-31 10:55           ` Johannes
2004-08-31 11:05           ` Johannes
  -- strict thread matches above, loose matches on Subject: below --
2004-08-26 10:48 Johannes
2004-08-26 11:24 ` Marcel Holtmann
2004-08-30 10:20   ` Johannes
2004-08-30 10:27     ` Marcel Holtmann
     [not found]       ` <413307E0.6060602@c-lab.de>
2004-08-30 11:09         ` Marcel Holtmann

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=41331EBB.9000606@gmx.de \
    --to=john281198@gmx.de \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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