Hi, On Fri, May 1, 2009 at 3:14 PM, Ilya Rubtsov <lusyaru@xxxxxxxxx> wrote: > I just would add that with hardware scheduler DeviceDisappeared signal works > fine if there two remote devices in the field, and doesn't work if there is > only one remote device: > > --- > # Now there only 00:16:B8:53:5F:17 is turned on > Fri May 1 20:36:48 2009 Signal: DeviceFound 00:16:B8:53:5F:17 > # Now I turn off 00:16:B8:53:5F:17 and wait, but no signal being emitted... > # So, I turn on 00:02:76:16:F6:8F > Fri May 1 20:38:52 2009 Signal: DeviceFound 00:02:76:16:F6:8F > Fri May 1 20:39:01 2009 Signal: DeviceDisappeared 00:16:B8:53:5F:17 You may just have to wait longer to get the DeviceDisappeared signal the fact the you turned off the device doesn't mean it will instantly disappear it may happen that bluetoothd is idle waiting for scheduler to start another discovery round (use Discovering property to check that.). I will double check if there is some logic problem while emitting DeviceDisappeared but I remember fixing it myself last time and have no complaining since then. -- Luiz Augusto von Dentz Engenheiro de Computação -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
