Wifi: Do not enable configured networks on WPS events.

The Android framework enables the configured networks after WPS
SUCCESS, the supplicant shall consider the networks based on the
priority for the WPA2 handshake after the successful WPS handshake.
This might end up in the station connecting to the AP other than
the current one with which the WPS handshake is done. Moreover,
since framework does not disable the networks and the wpa_supplicant
was the entity that disabled the networks before wps handshake, it
could actually be cleaner to re-enable the networks that were
disabled during the WPS operation within wpa_supplicant. This patch
addresses this by not enabling the configured networks on WPS events.

Bug: 10537481
Change-Id: I2fefc85d0e1f0f1fa96a76940f26aea05219c1ed
Check if intent can be resolved before starts

Change-Id: Ib9ef20f9480b1ad2093955fffb34298d493015d6
Signed-off-by: Roger Chen <cxr514033970@gmail.com>
Fix typo in DevicePolicyManager documentation

Typo in DevicePolicyManager documentation
See: http://code.google.com/p/android/issues/detail?id=60235

Change-Id: Ic120297cfdc46ec49f870e0750ec831ba6362399
Fix the bug in replacing a fragment with itself.

Summary:

We are facing a bug that some fragments in our app got removed
randomly. We debugged the app and it seems there is a bug in
the fragment API.

When we we are trying to replace a fragment with itself. We will
try to make the operation a null op, then both `op.fragment` and
`f` will be reset to null.

  op.fragment = f = null;

But since it's inside a loop, if the list `mAdded` still have
items to be visited, the code will continue to the next
iteration. Then it will compare the fragment with null, and
reach the line:

  mManager.removeFragment(old, mTransition, mTransitionStyle);

Eventually it will delete all left fragments in the list `mAdded`.

This diff adds a break to abort the searching after we null
the operation.

Test Plan:

1) Tested with our app. No fragment is randomly removed.

Revert Plan:

Change-Id: I5dc2c07a1bb1d1da1b0fd4e5610d970d55a81e86
Tags:
Signed-off-by: Kang Zhang <kangzhang.cn@gmail.com>