On 08/08/2017 05:22 PM, Sam Nazarko wrote:
From: connman <connman-bounces(a)lists.01.org> on behalf of Jonah Petri
Sent: 08 August 2017 16:10
Subject: When BackgroundScanning = false, connman's Scan() dbus method is broken
I want to report an issue with connman. We set BackgroundScanning = false in main.conf.
However, I have found that this also causes connman to give an erroneous empty response to
the Scan() dbus call, potentially permanently disabling the device.
connman mailing list
I can reproduce this issue. We wanted to disable BackgroundScanning as we support
a few wireless drivers that experience disruption to the connection when scanning
occurs. After disabling BackgroundScanning in ConnMan 1.34, we had numerous
reports of users unable to find any WiFi networks.
This worked in an older version of ConnMan? 1.33? This information would
help to identify the commit which broke the feature.