[PATCH] Default bluez-gnome UI to a connectable state

[PATCH] Default bluez-gnome UI to a connectable state

[Mario_Limonciello]

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

Looking through the code, it appears that bluetoothd does start up connectable, but the UI doesn't reflect this from the first boot.  This patch should address it.

Mario Limonciello 
Dell | Linux Engineering 
Mario_Limonciello@Dell.com 

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 03_default_connectable.patch --]
[-- Type: text/x-patch; name="03_default_connectable.patch", Size: 687 bytes --]

diff -Nur -x '*.orig' -x '*~' bluez-gnome-1.5/properties/adapter.c bluez-gnome-1.5.new/properties/adapter.c
--- bluez-gnome-1.5/properties/adapter.c	2008-08-24 16:14:24.000000000 -0500
+++ bluez-gnome-1.5.new/properties/adapter.c	2008-09-27 03:52:57.000000000 -0500
@@ -408,9 +408,8 @@
 					_("Other devices can connect"));
 	group = gtk_radio_button_get_group(GTK_RADIO_BUTTON(button));
 	gtk_box_pack_start(GTK_BOX(vbox), button, FALSE, FALSE, 0);
-
-	if (mode && g_ascii_strcasecmp(mode, "connectable") == 0)
-		gtk_toggle_button_set_active(GTK_TOGGLE_BUTTON(button), TRUE);
+	
+	gtk_toggle_button_set_active(GTK_TOGGLE_BUTTON(button), TRUE);
 
 	adapter->button_connect = button;
 

Re: [PATCH] Default bluez-gnome UI to a connectable state

[Marcel Holtmann]

Hi Mario,

> Looking through the code, it appears that bluetoothd does start up connectable, but the UI doesn't reflect this from the first boot.  This patch should address it.

this patch can't be right. It can happen that the device starts up in
off mode. You need to figure out why the mode variable doesn't correctly
point to connectable.

Regards

Marcel