Adapter.RemoveDevice() also removes the pair information according to the document doc/adapter-api.txt. However, unplug a virtual cable in HID spec doesn't mean unpair. Anyway, let me check the source once again. Thanks. 2010/7/20 Johan Hedberg <johan.hedberg@xxxxxxxxx>: > Hi, > > On Tue, Jul 20, 2010, Liang Bao wrote: >> I have a question on "Virtual Cable Unplug" in current BlueZ version. >> >> Currently BlueZ doesn't expose a D-Bus method in input/device.c for >> virtually unplug cable which is a mandatory requirement to pass >> TC_HOS_HCR_BV_03_I. Actually the support in kernel is already there. >> Can anyone give some insight to why this is not exposed at the DBUS >> API level like Connect/Disconnect/GetProperties? Can I think the >> reason behind this design is we only need one of "Disconnect" and >> "VirtualUnplug" to allow user to disconnect? > > AFAIK the unplug should be sent when you do Adapter.RemoveDevice() > > Johan > -- 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
