tree 0c53c146388a59d4cbd0efa6b844956fd741256a
parent 508e86e7577fabf528afe06ecc098f8e677ff48c
author Irfan Sheriff <isheriff@google.com> 1311542895 -0700
committer Irfan Sheriff <isheriff@google.com> 1311543303 -0700

Fix interface notification race

In one use case, I see that if we go straight from
wifi client mode to tethering operation, the interface change notifications
are reported in an order that causes to enter tethered state
without actually tethering through connectivity service.

It is because an interface down notification (from wifi going down) comes after
we have started soft ap and we think we have tethered after calling startTethering
and switch to Tethered state

Instead, we should make sure tethering has started before going to Tethered state.

Change-Id: Iba7e8fab0feeb5637d40938862a8638871df8b02