From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth serial vs. audio connection
Date: Sun, 27 Mar 2005 18:06:08 +0200 [thread overview]
Message-ID: <1111939568.9195.236.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.62.0503271751420.3135@ybpnyubfg.ybpnyqbznva>
Hi Andreas,
> >MH: > root@notebook:/home/andreas > sdptool search --bdaddr 00:xx dun
> >MH: > Searching for dun on 00:xx ...
> >MH: > Service Name: Dial-up networking
> >MH: > Service RecHandle: 0x10002
> >MH: > Service Class ID List:
> >MH: > "Dialup Networking" (0x00001103)
> >MH: > Protocol Descriptor List:
> >MH: > "L2CAP" (0x00000100)
> >MH: > "RFCOMM" (0x00000003)
> >MH: > Channel: 4
> >MH: > Segmentation fault
> >MH: > root@notebook:/home/andreas >
> >MH: >
> >MH: > (note the last 'Segmentation fault', this might be the reason, the
> >MH: > browse command does not work as expected)
> >MH:
> >MH: what kind of phone is this?
>
> If I just run sdptool browse 00:xx, I don't get any output, I'm not
> sure, this is the normal behavior. I see this as a problem, as there
> are some supported services. But then, I didn't check the code of this
> tool.
this does not answer my question. What kind of phone is this? Does
adding "--tree" before the "--bdaddr" parameter helps?
> >MH: > Thanks so far, but how to proceed? (I've still the same problem,
> >MH: > connecting with bluez 'only' gives an 'audio' connection, not the
> >MH: > expected 'serial' as I got from Windows).
> >MH:
> >MH: What happens if you connect to channel 3 or channel 4?
>
> Duh.... well... thanks for the hint... of course, if I use channel 3 (as
> given in the output of "sdptool search .. sp" it does work, I get a
> 'serial' connection. I'll test this with minicom, whether I can use all
> the commands I need, but I'm confident.
>
> Now, I wonder, whether there is some information on service <=> channel
> pairs that I should have read?
This phone have the serial port profile service on channel 3 and the
dialup networking profile service on channel 4. You can see everything
in the sdptool output.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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:[~2005-03-27 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 11:27 [Bluez-users] bluetooth serial vs. audio connection Andreas Fehr
2005-03-27 11:37 ` Marcel Holtmann
2005-03-27 12:01 ` Andreas Fehr
2005-03-27 12:35 ` Marcel Holtmann
2005-03-27 15:40 ` Andreas Fehr
2005-03-27 15:45 ` Marcel Holtmann
2005-03-27 15:56 ` Andreas Fehr
2005-03-27 16:06 ` Marcel Holtmann [this message]
2005-03-27 16:21 ` Andreas Fehr
2005-03-27 16:58 ` Marcel Holtmann
2005-03-28 7:11 ` Andreas Fehr
2005-03-28 9:15 ` Andreas Fehr
2005-03-28 10:43 ` Marcel Holtmann
2005-03-28 11:13 ` Andreas Fehr
2005-03-27 16:12 ` Andreas Fehr
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=1111939568.9195.236.camel@pegasus \
--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