From: tmp@nitwit.de
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Error connecting transport
Date: Sun, 27 Mar 2005 18:59:06 +0200 [thread overview]
Message-ID: <200503271859.06756.tmp@nitwit.de> (raw)
In-Reply-To: <200503271845.15263.tmp@nitwit.de>
KbluetoothD:
"Possible evice/Service class mismatch
To use the kbtobexsrv service, some other devices might require a modified
class number for your bluetooth adapter in /etc/bluetooth/hcid.conf.
current the class is set to 0x0. We suggest you change this to somethign like
0x10000000 instead of restart BlueZ's hcid. The service will be activated
anyway."
Well, can somebody translate?
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-27 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 16:45 [Bluez-users] Error connecting transport tmp
2005-03-27 16:59 ` tmp [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=200503271859.06756.tmp@nitwit.de \
--to=tmp@nitwit.de \
--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