From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sdptool fails with ppc6700
Date: Fri, 24 Feb 2006 16:06:23 +0100 [thread overview]
Message-ID: <1140793583.4260.19.camel@localhost> (raw)
In-Reply-To: <43FF1F65.3010708@xmission.com>
Hi Brad,
> > Try usimg sdptool browse XX:XX:XX:XX:XX:XX --l2cap (some phones do not
> > implement Public Browse Group which is used for discovery by default)
> > and if this does not help for some phones you have to ask for specific
> > profiles to get an answer (new Motorola's): sdptool search --bdaddr
> > XX:XX:XX:XX:XX:XX DUN for an example.
>
> thanks... the l2cap scan didn't help, but searching specifically for DUN
> did.
>
> The phone still locks up whenever I try to max out the connection so
> it's going back unless there's an easy fix. Maybe it's some kind of bad
> interaction between bluez and pocketpc. :(
show me the "hcidump -X -V" for that problem. I think that I know what
it is and I titled it ByeByeMoto. I've seen similar things on my new
RAZR V3x.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-24 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 8:40 [Bluez-devel] sdptool fails with ppc6700 Victor Shcherbatyuk
2006-02-24 14:59 ` Brad Midgley
2006-02-24 15:06 ` Marcel Holtmann [this message]
2006-02-25 4:38 ` Brad Midgley
2006-02-25 15:31 ` Brad Midgley
-- strict thread matches above, loose matches on Subject: below --
2006-02-24 15:19 Joshua Wright
2006-02-24 15:04 Victor Shcherbatyuk
2006-02-24 3:54 Brad Midgley
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=1140793583.4260.19.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).