More carrier bind fixes: direct boot and package changes.

For direct boot, we must listen to ACTION_USER_UNLOCKED and rebind
upon unlock in case the carrier service is not direct boot aware.

Also, previously, we only evaluated bindings on package changes to the
package that was currently bound to, if any. But if no binding is
present, and then a package change leads to a scenario where a binding
should be made, the binding would never be established. This can
happen when a new carrier package is first installed, or if the
component/package goes from disabled to enabled. Thus, when package
changes occur, also reevaluate bindings for any phones which have no
binding information.

Fixes: 28964849
Fixes: 29043701
Change-Id: Ia60c7035d2a3f3f02445f017920f8c4650f464f4
1 file changed
tree: 8c67c05483257683649ed166d0bd1a5df5b5cb93
  1. src/
  2. tests/
  3. tools/
  4. Android.mk
  5. CleanSpec.mk
  6. README.txt