On Tue, 2015-10-13 at 14:42 -0700, Naveen Singh wrote:

> There is nothing that application knows that connman does not know.
> In fact application gets to know through connman that connection did
> not go through. The way application gets connected back is to initiate
> a scan and hoping that one of these scan would find the AP (or
> services) and then run autoconnect would trigger and get device
> connected. But in this case run autoconnect would not attempt
> connection because service state was left to failure.

This approach won't work at all. When ConnMan receives a Scan() over
D-Bus, it will scan immediately and reset its own autoscan timer. Which
means that if the application issues a scan after less than ~6 minutes,
it causes ConnMan to scan so often that wpa_s never times out its WiFi
networks. So if the service has failed, it has failed for all eternity.

The solution here is very simple. Get rid of the application assisted
scan and let ConnMan handle it instead.



connman mailing list

Reply via email to