commit | 1582bddf620625f9e6f6c407a707d6a916387df1 | [log] [tgz] |
---|---|---|
author | Christopher Wiley <wiley@chromium.org> | Thu Nov 15 11:31:14 2012 -0800 |
committer | Gerrit <chrome-bot@google.com> | Tue Nov 20 16:57:18 2012 -0800 |
tree | dd2b22348a09f1a44a9f2475e9d5fcd809a865f1 | |
parent | 6e5639f9ef54db278c5f2265d5364e5994966f4a [diff] |
shill: Disable autoconnect on activating cellular services Don't allow services undergoing activation to be connected by the manager. Implement this by asking the capability (through the device) whether it is currently in the process of activation. This works around a huge mess where Chrome forces autoconnect off, and then has retrying reconnect logic after activation. BUG=chromium-os:36301 TEST=Activations work as before. The real magic will happen when we stop toggling the autoconnect bit from the mobile activator in Chrome. Change-Id: I92cb6780712d341605f51e4a98041bb3642ab6fe Reviewed-on: https://gerrit.chromium.org/gerrit/38314 Reviewed-by: Christopher Wiley <wiley@chromium.org> Tested-by: Christopher Wiley <wiley@chromium.org> Commit-Ready: Christopher Wiley <wiley@chromium.org>