From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] 2 Successive OBEX Connect Request
Date: Wed, 30 Nov 2005 07:43:08 +0100 [thread overview]
Message-ID: <1133332988.18079.1.camel@blade> (raw)
In-Reply-To: <20051130064037.90802.qmail@web32412.mail.mud.yahoo.com>
Hi Arch,
> I would like to ask the implications on BlueZ whenever a Bluetooth
> device issues 2 Successive OBEX Connect Requests. This was done
> without any OBEX Disconnect Request after the first Connect Request.
> This is how the new Samsung D600 phone is doing a Bluetooth
> transaction when you're doing a Bluetooth printing.
include "hcidump -X -V" to show what's going on there.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-11-30 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 6:40 [Bluez-users] 2 Successive OBEX Connect Request Arch Sayo
2005-11-30 6:43 ` Marcel Holtmann [this message]
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=1133332988.18079.1.camel@blade \
--to=marcel@holtmann.org \
--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).