From: Johannes <lintner@c-lab.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] general question on the procedure of BlueZ
Date: Tue, 07 Sep 2004 09:56:38 +0200 [thread overview]
Message-ID: <413D69B6.3070107@c-lab.de> (raw)
In-Reply-To: <413C4835.2010203@c-lab.de>
Hi,
can you give me a short checklist, which modules I have to start, that
the communication will have success? Perhaps I have forgotten something.
when I do lsmod, I see the following (relevant) entries:
l2cap 28416 2
hci_usb 16000 2
bluetooth 52100 6 l2cap,hci_usb
ehci_hcd 32644 0
uhci_hcd 33680 0
usbcore 115040 5 hci_usb,ehci_hcd,uhci_hcd
Do I need more to use the BT Serial Port Profile on serverside with no
problems?
Thanks Johannes
Johannes wrote:
> Hi again,
>
> I forgot to say, that the sdp-deamon says "Segmentation fault", when I
> cancel it, to start an new version of my proxy.
> Hopefully it helps.
>
> Greets Johannes
>
>
> Johannes wrote:
>
>> Hi all,
>>
>> I would have a question on the general procedure, how BlueZ works.
>>
>> My problem is, that the video-file, I will send from Server to mobile
>> phone, is corrupt. At most, there were transmitted only 9216byte
>> instead the origin 12913byte. When I let the server sleep for (e.g.)
>> 60sec. after the video-file (over an OutputStream and
>> OutputStream.close()) is sent and before the connection is closed to
>> the phone, it works. But this is not really a good implementation.
>>
>> So, how does the BlueZ-Stack works. Does it has an puffer, smaller
>> than 13kbyte or how is the connecton-closing realized? Will be the
>> connection closed, if such an methode will be called, no matter,
>> whether there are data in the puffer?
>>
>> Greets Johannes
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by BEA Weblogic Workshop
>> FREE Java Enterprise J2EE developer tools!
>> Get your free copy of BEA WebLogic Workshop 8.1 today.
>> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
>> _______________________________________________
>> Bluez-users mailing list
>> Bluez-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-users
>>
>>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-09-07 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 13:47 [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-05 17:53 ` Collin R. Mulliner
2004-09-06 8:30 ` Marcel Holtmann
2004-09-06 8:50 ` Michael Schmidt
2004-09-06 9:17 ` Marcel Holtmann
2004-09-06 10:38 ` [Bluez-users] general question on the procedure of BlueZ Johannes
2004-09-06 11:21 ` Johannes
2004-09-07 7:56 ` Johannes [this message]
2004-09-06 11:43 ` [Bluez-users] no concurrent inquiry / inquiry scan and L2CAP connection as slave Michael Schmidt
2004-09-06 8:37 ` Xavier Garreau
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=413D69B6.3070107@c-lab.de \
--to=lintner@c-lab.de \
--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