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 11:38:33 +0200	[thread overview]
Message-ID: <1154079513.2298.20.camel@localhost> (raw)
In-Reply-To: <200607281128.09414.fexpop@onlinehome.de>

Hi Felix,

> > First of all the setting iscan on and pscan off somehow works, but is
> > totally stupid. It means you set your device visible, but not
> > connectable. This also means that the remote side can find you, but
> > can't resolve your name. Think about it.
> 
> Sure it's stupid. I did it only for testing purposes. I've mentioned it here 
> just to illustrate that nothing in hcid.conf related to pscan/iscan seems to 
> have any effect at all. (I've "iscan enable; pscan enable;" in my hcid.conf). 
> 
> > > How do I set the discoverable timeout? How am I supposed to set myself
> > > discoverable? Are there new options in hcid.conf? Where is it documented?
> >
> > Check utils/hcid/dbus-api.txt in the CVS. It also contains a dbus-test
> > script that can be used to modify these settings.
> 
> So, there's no way to make my system visible directly after plugging the 
> dongle in without switching to CVS versions???? 

the dbus-test is a Python script. Simple checkout the CVS and use this
one. You need to modify DiscoverableTimeout and Mode. No need to update
the whole BlueZ packages.

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  9:38 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
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 [this message]
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=1154079513.2298.20.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