public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian
Date: Fri, 28 Jul 2006 03:20:00 +0200	[thread overview]
Message-ID: <1154049600.7650.6.camel@localhost> (raw)
In-Reply-To: <200607272208.06047.fexpop@onlinehome.de>

Hi Felix,

> > kbluetoothd finds other devices after that command! (It doesn't make my PC
> > visible to other devices though). 
> 
> Part of the visibility issue seems to be that only PSCAN will be enabled 
> regardless of what I specify in hcid.conf. If I manually do a 'hciconfig hci0 
> piscan' everything is fine again. 

now you are mixing things. The inquiry mode has nothing to do with the
scan mode.

The inquiry mode defines what inquiry result events you will see.
Basically you wanna use Inquiry with RSSI from the Bluetooth 1.2
specification to additionally get the RSSI value.

The scan mode defines is you are visible and connectable. The D-Bus API
sets you to connectable only unless you disable the discoverable timeout
and set your yourself to discoverable. This is a feature of the new 3.x
generation that will make you automatically unvisible after a certain
amount of time.

These two things are not related. And start sending in "hcidump -X -V"
outputs instead of speculating.

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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-07-28  1:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 10:40 [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian Felix Homann
2006-07-27 10:43 ` Marcel Holtmann
2006-07-27 10:58   ` Felix Homann
2006-07-27 11:04     ` Marcel Holtmann
2006-07-29 12:26       ` Felix Homann
2006-07-29 12:42         ` Marcel Holtmann
2006-07-27 17:16     ` [Bluez-users] Several problems with bluez-utils 3.2, kbluetoothd Paulo Wollny
2006-07-27 20:08     ` [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian Felix Homann
2006-07-28  1:20       ` Marcel Holtmann [this message]
2006-07-28  9:00         ` Felix Homann
2006-07-28  9:09           ` Marcel Holtmann
2006-07-28  9:28             ` Felix Homann
2006-07-28  9:38               ` Marcel Holtmann
2006-07-28 10:03                 ` Felix Homann
2006-07-28 10:06                   ` Marcel Holtmann
2006-07-28 10:14                     ` Felix Homann
2006-07-28 10:33                       ` Marcel Holtmann
2006-07-28 10:46                         ` Felix Homann
2006-07-28 10:51                           ` Marcel Holtmann
2006-07-28 10:40                     ` hugues
2006-07-28 11:07                       ` Felix Homann
2006-07-28 15:00                     ` Felix Homann
2006-07-28 15:07                       ` Marcel Holtmann
2006-07-29 12:11                         ` Felix Homann
2006-07-29 12:33                           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27 23:18 Alastair Tse
2006-07-28  1:32 ` Marcel Holtmann
2006-07-28  9:43   ` Alastair Tse
2006-07-29 12:58     ` Marcel Holtmann

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=1154049600.7650.6.camel@localhost \
    --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