I am developing an application that is using the dbus api. The application
will setup the wifi for the unit. I am struggling a bit to see the best
practice for making sure we have fully updated list of services. I know I
can configure connman to automatically scan by using BackgroundScanning
which is by default set to true. Is the best practice to let connman manage
the scanning or should my application trigger a scan whenever needed. The
default scan schedule for connman is not enough as I see it but I know you
can setup a scan schedule in wpa_supplicant but it looks like connman is
starting wpa_supplicant so I am not sure how to change this default scan
schedule that connman is setting up. Any comments are appreciated.
From: Vasyl Vavrychuk <vasyl.vavrychuk(a)globallogic.com>
When we start p2p scan we reset Wi-Fi autoscan, i.e. autoscan timer is
stopped but Wi-Fi scanning status is not touched.
This is probably due to we get Wi-Fi scanning during P2P find implicitly.
This fact was veryfied using wpa_cli.
But when p2p scan stops in p2p_find_stop function we did not reverted our
action but did reset Wi-Fi autoscan again for some reason.
plugins/wifi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/plugins/wifi.c b/plugins/wifi.c
index fa8d0bf..6be23a4 100644
@@ -1782,7 +1782,7 @@ static void p2p_find_stop(struct wifi_data *wifi)
connman_device_set_scanning(wifi->device, CONNMAN_SERVICE_TYPE_P2P, false);
static gboolean p2p_find_timeout_trigger(gpointer data)