Re: [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian

[Marcel Holtmann <marcel@holtmann.org>]

Hi Felix,

> > > No, unfortunately the settings I've changed via dbus-test are lost after
> > > unplugging the dongle.
> >
> > they must stay, because otherwise it is a bug. You did set the
> > discoverable timeout to zero, do you?
> 
> sure, I have. It's probably a bug then. But keep in mind I'm using dbus-test 
> with the Debian distributed bluez-utils (3.1-3), maybe it's already fixed in 
> 3.2..
> 
> Here's what I did:
> 
> # dbus-test -i hci0 SetDiscoverableTimeout 0
> # dbus-test -i hci0 SetMode discoverable
> # dbus-test -i hci0 GetMode
> discoverable
> # dbus-test -i hci0 GetDiscoverableTimeout
> 0
> 
> Unplug the dongle, then immediately after plugging it in again:
> 
> # dbus-test -i hci0 GetDiscoverableTimeout
> 180
> # dbus-test -i hci0 GetMode
> discoverable
> 
> Wait some (~3) minutes:
> 
> # dbus-test -i hci0 GetMode
> connectable

that is a bug and it is still present in bluez-utils-3.2. I have no idea
how, but somehow the unplug and replug sets the default discoverable
timeout of 3 minutes. If you look at the stored value it is still 0, but
this doesn't help.

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