tree 8f9b9e664a91bde344d9ac97d7f2ce919e5e04d7
parent af7c978216cec465ad038b579ffc2be3ca8c7c66
author Brad Larson <brad.larson@garmin.com> 1262108875 -0600
committer Jean-Baptiste Queru <jbq@google.com> 1273257315 -0700

Use isLocationProviderEnabled to test for enabled providers

LocationManagerService was just checking if the string of (comma-separated)
Location Providers contained the provider we were interested in.  This works
fine in normal cases, but breaks if we add a provider such as test_network.
Enabling test_network causes LocationManagerService to think that the network
provider is also enabled.

The code in Settings.Secure.isLocationProviderEnabled() checks for the commas
in the string as well, to make sure that a provider name which is a substring
of another provider name won't cause problems.  It also centralizes the code
which reads the string.

Signed-off-by: Brad Larson <brad.larson@garmin.com>

Change-Id: I00dfe7c2b09739ed4c8ed07c6167e409b0bf7d13