summaryrefslogtreecommitdiffstats
path: root/src/device.c
diff options
context:
space:
mode:
authorJohan Hedberg <johan.hedberg@nokia.com>2008-10-09 09:21:51 +0200
committerJohan Hedberg <johan.hedberg@nokia.com>2008-10-09 09:21:51 +0200
commit7e1d898e394865ea31ae3f79f087ee726e55c01b (patch)
tree5b42810ed7374a61801ae4671c857bbc830b3721 /src/device.c
parenta6fab78087f057d977af6cdc6fff9dfd43b67bb2 (diff)
Don't remove service discovery timer even if device disconnects
Since it's important for us to find out what profiles a device has in order to populate the device object with the correct D-Bus interfaces insist on doing SDP even if got disconnected from the device. Since the timer is only 2 seconds the chances are that device will still be around and the connection will be successfull. This situation can happen if the remote device acts as an initiator for dedicated bonding and brings down the ACL before our timer goes off.
Diffstat (limited to 'src/device.c')
-rw-r--r--src/device.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/src/device.c b/src/device.c
index 778fc6f2..1e7747d6 100644
--- a/src/device.c
+++ b/src/device.c
@@ -533,11 +533,6 @@ void device_set_connected(DBusConnection *conn, struct btd_device *device,
{
device->connected = connected;
- if (!connected && device->discov_timer) {
- g_source_remove(device->discov_timer);
- device->discov_timer = 0;
- }
-
dbus_connection_emit_property_changed(conn, device->path,
DEVICE_INTERFACE,
"Connected", DBUS_TYPE_BOOLEAN,