From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Nasty bug with sdp on /etc/default/bluetooth ?
Date: Mon, 04 Sep 2006 19:37:49 +0200 [thread overview]
Message-ID: <1157391469.32195.83.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <7f52ac20609040638i2c34568fu7d7820350d714d36@mail.gmail.com>
Hi Hentai,
> A couple of lines on my /etc/default/bluetooth file
>
> SDPD_ENABLE=true
> SDPTOOL_OPTIONS="add --channel=10 OPUSH"
>
>
> The problem is that i can't send files from the mobile to the
> computer, when obexserver is listening, unless i explicitly do this:
> sdptool add --channel=10 OPUSH
>
> However, i could send files from the mobile if i had kbluetooth
> running, and it seemed to used channel 3. I suspect kbluetooth created
> that channel automatically.
>
> Can someone confirm if this is a bug or not?
> Is there any way to list registered channels? I played with sdptool
> but couldn't get anything from it (most of the times it says no route
> to host).
that is a bug of obexserver. It should register the appropriate SDP
service record by itself. The "sdptool add ..." is only for debugging
and development purpose.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-09-04 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 13:38 [Bluez-devel] Nasty bug with sdp on /etc/default/bluetooth ? Hentai Pantsu
2006-09-04 17:37 ` 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=1157391469.32195.83.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@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