From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Browsing Anycom GP-600 GPS Receiver fails
Date: Thu, 21 Sep 2006 18:07:49 +0200 [thread overview]
Message-ID: <1158854869.11194.48.camel@localhost> (raw)
In-Reply-To: <een2ub$f0l$1@sea.gmane.org>
Hi Michael,
> I own an Anycom GP-600 GPS Receiver. This receiver might have a broken
> SDP stack. I use SuSE Linux 9.3.
>
> When browsing the device using the sdptool browse command, it fails.
> However when using Konqueror to browse the SDP-record on the same
> distribution it works fine.
>
> The difference between kde and sdptool browse seems to be, that kde uses
> a 32 bit UUID, while the sdptool uses a 16 bit UUID.
>
> Is there any chance that bluez could handle such trouble more gracefully
> and issue a waring? I remember prior Bluez versions had been working
> slightly better.
it simply means that this device has no public browse group. That is not
a bug. Try "sdptool browse --l2cap <bdaddr>" and see if this works.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-09-21 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 21:28 [Bluez-devel] Browsing Anycom GP-600 GPS Receiver fails M Josenhans
2006-09-21 16:07 ` 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=1158854869.11194.48.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.