summaryrefslogtreecommitdiffstats
path: root/services/java/com/android/server/location
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Listen for CONNECTIVITY_ACTION in GPS ProviderBrian Muramatsu2012-08-211-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug: 7020678 The broadcast receiver in GpsLocationProvider now listens for CONNECTIVITY_ACTION changes. Set the intent filter so that it catches those actions and updates the network state. Change-Id: I7efd393dfe2aa8b172dd6701d42ff9ed687648a2
* | | Port location blacklist code to MR1.Nick Pelly2012-08-172-1/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I had to re-do this change for MR1 because LocationManagerService changed so much. Here is the original change description: Add package-name-prefix blacklist for location updates. The Settings.Secure value locationPackagePrefixBlacklist and locationPackagePrefixWhitelist contains comma seperated package-name prefixes. Location & geo-fence updates are silently dropped if the receiving package name has a prefix on the blacklist. Status updates are not affected. All other API's work as before. A content observer is used so run-time updates to the blacklist apply immediately. There is both a blacklist and a whitelist. The blacklist applies first, and then exemptions are allowed from the whitelist. In other words, if your package name prefix matches both the black AND white list, then it is allowed. Bug: 6986553 Change-Id: I1e151e08bd7143e47db005bc3fe9795076398df7
* | | Fix regression from location changes: GPS battery tracking.Nick Pelly2012-08-171-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | The client UID list wasn't being saved, so we never removed client UID's. As a result apps get blamed for GPS even when they are no longer using it. Bug: 7007314 Change-Id: Idff3b7c8c0ee87b99c9bdd7bd20d8391d0b1ac0f
* | | Improve coarse locations.Nick Pelly2012-08-161-0/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix a couple of bugs, and modify the behavior of the random offset. The random offset now slowly changes over time, to mitigate against applications averaging out the offset over time while at a grid boundary. Change-Id: Iecffff29145b8c2b30d1eca1662cf9d3e8cff756
* | | Location overhaul, major commit.Nick Pelly2012-08-108-1080/+662
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Themes: Fused Location, Geofencing, LocationRequest. API changes o Fused location is always returned when asking for location by Criteria. o Fused location is never returned as a LocationProvider object, nor returned as a provider String. This wouldn't make sense because the current API design assumes that LocationProvider's have fixed properties (accuracy, power etc). o The fused location engine will tune itself based on the criteria passed by applications. o Deprecate LocationProvider. Apps should use fused location (via Criteria class), instead of enumerating through LocationProvider objects. It is also over-engineered: designed for a world with a plethora of location providers that never materialized. o The Criteria class is also over-engineered, with many methods that aren't currently used, but for now we won't deprecate them since they may have value in the future. It is now used to tune the fused location engine. o Deprecate getBestProvider() and getProvider(). o Add getLastKnownLocation(Criteria), so we can return last known fused locations. o Apps with only ACCESS_COARSE_LOCATION _can_ now use the GPS, but the location they receive will be fudged to a 1km radius. They can also use NETWORK and fused locatoins, which are fudged in the same way if necessary. o Totally deprecate Criteria, in favor of LocationRequest. Criteria was designed to map QOS to a location provider. What we really need is to map QOS to _locations_. The death knell was the conflicting ACCURACY_ constants on Criteria, with values 1, 2, 3, 1, 2. Yes not a typo. o Totally deprecate LocationProvider. o Deprecate test/mock provider support. They require a named provider, which is a concept we are moving away from. We do not yet have a replacement, but I think its ok to deprecate since you also need to have 'allow mock locations' checked in developer settings. They will continue to work. o Deprecate event codes associated with provider status. The fused provider is _always_ available. o Introduce Geofence data object to provide an easier path fowards for polygons etc. Implementation changes o Fused implementation: incoming (GPS and NLP) location fixes are given a weight, that exponentially decays with respect to age and accuracy. The half-life of age is ~60 seconds, and the half-life of accuracy is ~20 meters. The fixes are weighted and combined to output a fused location. o Move Fused Location impl into frameworks/base/packages/FusedLocation o Refactor Fused Location behind the IProvider AIDL interface. This allow us to distribute newer versions of Fused Location in a new APK, at run-time. o Introduce ServiceWatcher.java, to refactor code used for run-time upgrades of Fused Location, and the NLP. o Fused Location is by default run in the system server (but can be moved to any process or pacakge, even at run-time). o Plumb the Criteria requirements through to the Fused Location provider via ILocation.sendExtraCommand(). I re-used this interface to avoid modifying the ILocation interface, which would have broken run-time upgradability of the NLP. o Switch the geofence manager to using fused location. o Clean up 'adb shell dumpsys location' output. o Introduce config_locationProviderPackageNames and config_overlay_locationProviderPackageNames to configure the default and overlay package names for Geocoder, NLP and FLP. o Lots of misc cleanup. o Improve location fudging. Apply random vector then quantize. o Hide internal POJO's from clients of com.android.location.provider.jar (NLP and FLP). Introduce wrappers ProviderRequestUnbundled and ProviderPropertiesUnbundled. o Introduce ProviderProperties to collapse all the provider accuracy/ bearing/altitude/power plumbing (that is deprecated anyway). o DELETE lots of code: DummyLocationProvider, o Rename the (internal) LocationProvider to LocationProviderBase. o Plumb pid, uid and packageName throughout LocationManagerService#Receiver to support future features. TODO: The FLP and Geofencer have a lot of room to be more intelligent TODO: Documentation TODO: test test test Change-Id: Iacefd2f176ed40ce1e23b090a164792aa8819c55
* | | Control GPS logging with propertyBrian Muramatsu2012-08-091-2/+2
| | | | | | | | | | | | | | | | | | This allows users of the PDK to debug GPS issues. Change-Id: I4aff12e124f4264abd1a0be012df4c431044189c
* | | Improve Location object.Nick Pelly2012-07-202-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add getElapsedRealtimeNano(): Currently Location just has getTime() and setTime() based on UTC time. This is entirely unreliable since it is not guaranteed monotonic. There is a lot of code that compares fix age based on deltas - and it is all broken in the case of a system clock change. System clock can change when switching cellular networks (and in some cases when switching towers). Document the meaning of getAccuracy(): It is the horizontal, 95% confidence radius. Make some fields mandatory if they are reported by a LocationProvider: All Locations returned by a LocationProvider must include at the minimum a lat, long, timestamps, and accuracy. This is necessary to perform fused location. There are no public API's for applications to feed locations into a location provider so this should not cause any breakage. If a LocationProvider does not fill in enough fields on a Location object then it is dropped, and logged. Bug: 4305998 Change-Id: I7df77125d8a64e174d7bc8c2708661b4f33461ea
* | | Merge "Improve geofencing: throttle location updates with distance to fence."Nick Pelly2012-07-162-0/+342
|\ \ \ | |/ / |/| |
| * | Improve geofencing: throttle location updates with distance to fence.Nick Pelly2012-07-162-0/+342
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously any geofence (proximity alert) would turn the GPS on at full rate. Now, we modify the GPS interval with the distance to the nearest geofence. A speed of 100m/s is assumed to calculate the next GPS update. Also o Major refactor of geofencing code, to make it easier to continue to improve. o Discard proximity alerts when an app is removed. o Misc cleanup of nearby code. There are other upcoming changes that make this a good time for some house-keeping. TODO: The new geofencing heuristics are much better than before, but still relatively naive. The next steps could be: - Improve boundary detection - Improve update thottling for large geofences - Consider velocity when throttling Change-Id: Ie6e23d2cb2b931eba5d2a2fc759543bb96e2f7d0
* | Create telephony-common and mms-commonWink Saville2012-07-111-5/+6
|/ | | | | | | | | | | | | | | | | These have been created to reduce the size and complexity of frameworks/base. mms-common was created by moving all of frameworks/base/core/java/com/google/android/mms to: frameworks/opt/mms telephony-common was created by moving some of frameworks/base/telephony to: frameworks/opt/telephony Change-Id: If6cb3c6ff952767fc10210f923dc0e4b343cd4ad
* Make location providers upgradeable.Nick Pelly2012-05-292-26/+28
| | | | | | | | | | | | | | Use config_netowrkLocationProviderPackageName and config_geocodeProviderPackageName as intial packages. If another package exists (or is later installed) that also implements a provider, and has the same signatures as the original providers, and has a hgiher version number, then use that instead. The old code used a funky fix of package name substring checks and service checks that was broken and not upgradeable. Bug: 6499445 Change-Id: Ic58f09cf85d31d9abf47707093e22f31dda25cf0
* Increase interval threshold below which we just leave the GPS on.Nick Pelly2012-05-071-2/+19
| | | | | | | | | | Hot TTTF is about 5 seconds, so don't cycle the GPS hardware until the interval is 10 seconds. Also add some more dumpsys logging. Bug: 6367964 Change-Id: I39402fc61f34458a1639c8814610a02606a8eb79
* am 8f30d219: am f0533f94: am 0e873700: Remove the country detector loggingDaniel Lehmann2012-03-121-2/+2
|\ | | | | | | | | * commit '8f30d2191eb88d577d6d2ba9874053cfea0091c8': Remove the country detector logging
| * am 0e873700: Remove the country detector loggingDaniel Lehmann2012-03-121-2/+2
| |\ | | | | | | | | | | | | * commit '0e87370077b322b3a88c345a44c6bf3d56617071': Remove the country detector logging
| | * Remove the country detector loggingDaniel Lehmann2012-03-121-2/+2
| | | | | | | | | | | | | | | Bug:6156714 Change-Id: Id0ff60b0530142e2bce055ee8cf8dde94e974aa5
* | | am ccd08b8d: am e939edb5: am f418738c: am d7fa7dee: Merge "Fixes update of ↵Jean-Baptiste Queru2012-02-281-0/+1
|\ \ \ | |/ / | | | | | | | | | | | | | | | extras Bundle in new Locations for GPS Provider" * commit 'ccd08b8de9dc4c9cfaee93cbbcc7053cc9e8d96f': Fixes update of extras Bundle in new Locations for GPS Provider
| * | am d7fa7dee: Merge "Fixes update of extras Bundle in new Locations for GPS ↵Jean-Baptiste Queru2012-02-281-0/+1
| |\ \ | | |/ | |/| | | | | | | | | | | | | Provider" * commit 'd7fa7deef9bc0cf22bf450fdb062327697c087c4': Fixes update of extras Bundle in new Locations for GPS Provider
| | * Fixes update of extras Bundle in new Locations for GPS ProviderSean Barbeau2012-01-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes the update of the extras Bundle in the Location object each time the platform derives a new GPS location and passes it to listening applications via LocationListener.onLocationChanged(). Sometime between Android 1.6 and 2.1 a bug was introduced that stopped any extras calculated by the platform from being added into the Location object, which means they were never passed up to any LocationListeners for the GPS Provider. This manifested as an issue where the number of satellites used to derive a fix always reported “0” when retrieved from Location.getExtras() (Issue 4810 on the Android Issues page - http://code.google.com/p/android/issues/detail?id=4810). Sample code to be used within LocationListener.onLocationChanged(Location location) which demonstrates this problem: Bundle extras = location.getExtras(); Int numSats = extras.getInt("satellites"); //This always reports “0” //post 1.5, although in 1.5 //it properly reported the //number of satellites used //to derive this location The “satellites” extra key/value pair for Locations is defined in http://developer.android.com/reference/android/location/Location.html#getExtras() This patch modifies GPSLocationProvider.java to properly update the Location object with the extras Bundle before the Location object is passed to any listening applications, and therefore the number of satellites used to derive a fix can now be retrieved properly through location.getExtras() (as shown in sample code above). Therefore, this patch fixes Issue 4810. Change-Id: Ief21056a3623269bb3149ec78ab92738a234f57f Signed-off-by: Sean Barbeau <sjbarbeau@gmail.com>
| * | Cherry-picking Id45abeba and Ia065dec6 for MR1Makoto Onuki2011-12-131-34/+137
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ------------------------------------------------------- MCC detection fixes for CountryDetector - Don't get and cache phone tpe at the initialization time. At this point TelephonyManager is probably not ready yet. - Refresh MCC whenever we get the service state changed callback, even when the state hasn't actually changed, in order to make sure we get refresh country properly when MCC changes. - Also remove the initialization of mPhoneStateListener, which prevented us from registering phone state listener properly. - Also fix tests which were already failing. Bug 5670680 ------------------------------------------------------- Add logging to country detector logic This is for debugging purposes to verify the effects of change Id45abeba1b1e843053ac2c946861b439ca568de4. Bug: 5670680 Change-Id: I238d953484e2c8135f7dac70fce8662c8300a286
| * Always use fresh NTP time for GPSMike Lockwood2011-10-251-7/+2
| | | | | | | | | | | | | | | | | | This is especially important when AGPS is disabled Bug: 5355661 Change-Id: I072dbe1ddf43aa24c8fc39b750040504a1633c53 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | Add logging to country detector logicKatherine Kuan2011-12-121-4/+119
| | | | | | | | | | | | | | | | This is for debugging purposes to verify the effects of change Id45abeba1b1e843053ac2c946861b439ca568de4. Bug: 5670680 Change-Id: Ia065dec6ba651e7e77205f812b7606b15eebdc17
* | MCC detection fixes for CountryDetectorMakoto Onuki2011-12-091-30/+18
|/ | | | | | | | | | | | | | | | | | - Don't get and cache phone tpe at the initialization time. At this point TelephonyManager is probably not ready yet. - Refresh MCC whenever we get the service state changed callback, even when the state hasn't actually changed, in order to make sure we get refresh country properly when MCC changes. - Also remove the initialization of mPhoneStateListener, which prevented us from registering phone state listener properly. - Also fix tests which were already failing. Bug 5670680 Change-Id: Id45abeba1b1e843053ac2c946861b439ca568de4
* Resolve merge conflict for '75f1fdec':Mike Lockwood2011-08-041-2/+33
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GPS Provider Service changes GPS engine needs to receive network state changes from Android fw. Added db query for the current APN, also added a new parameter between JNI / HAL to the new method in AGpsRilInterface struct for gps engine to receive APN from GPSLocationService Conflicts: services/java/com/android/server/location/GpsLocationProvider.java Change-Id: I33c45027f1571493d3525324f62d199517c4960c Signed-off-by: Mike Lockwood <lockwood@android.com>
| * am 0b3af353: am a82ee49a: am 8f5dd9ad: Merge "GPS Provider Service changes"Mike Lockwood2011-08-041-2/+33
| |\ | | | | | | | | | | | | * commit '0b3af353dcf61177158934a11404cf2914038696': GPS Provider Service changes
| | * GPS Provider Service changesKevin Tang2011-08-041-2/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GPS engine needs to receive network state changes from Android fw. Added db query for the current APN, also added a new parameter between JNI / HAL to the new method in AGpsRilInterface struct for gps engine to receive APN from GPSLocationService Change-Id: I62e35c948d2ac1961771d1a10581a3b8e695c05a Signed-off-by: Mike Lockwood <lockwood@android.com>
* | | am 21700fed: am 5f7203eb: am 5a27a754: am bd1dee94: Merge "gps: Adding ip ↵Mike Lockwood2011-07-281-1/+20
|\ \ \ | |/ / | | | | | | | | | | | | | | | address for AGps" * commit '21700fedfe29f6a0a752d2bea46142038e69136c': gps: Adding ip address for AGps
| * | am 5f7203eb: am 5a27a754: am bd1dee94: Merge "gps: Adding ip address for AGps"Mike Lockwood2011-07-281-1/+20
| |\ \ | | |/ | | | | | | | | | * commit '5f7203eb258503bc5d2ba29176bdf483a68a93b8': gps: Adding ip address for AGps
| | * gps: Adding ip address for AGpsStephen Li2011-07-281-1/+20
| | | | | | | | | | | | Change-Id: Ic590187d159853de2f1bd2912e159f0a00d8fb10
* | | am f8d13e53: am bf676d46: am 7083ed44: am 0ff79e88: Merge "GPS: Changes to ↵Mike Lockwood2011-07-281-1/+6
|\ \ \ | |/ / | | | | | | | | | | | | | | | enable on-demand data call flow for CDMA connections" * commit 'f8d13e535c3e6166c2386adac3b3a2f115d2b79d': GPS: Changes to enable on-demand data call flow for CDMA connections
| * | am bf676d46: am 7083ed44: am 0ff79e88: Merge "GPS: Changes to enable ↵Mike Lockwood2011-07-281-1/+6
| |\ \ | | |/ | | | | | | | | | | | | | | | on-demand data call flow for CDMA connections" * commit 'bf676d460d1d1fc8923982006c38d0f6785daea8': GPS: Changes to enable on-demand data call flow for CDMA connections
| | * GPS: Changes to enable on-demand data call flow for CDMA connectionsStephen Li2011-06-051-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | In the CDMA case we do not get a valid APN on a data connection request to the connectivity manager. A fix is put in so that even if we get a null APN we populate this field before we call native_agps_data_conn_open() method to avoid a run time exception. Change-Id: I134ead5d8b177fced9b14756c6bd8199a2b9c35d
* | | Fix issue #4466531: onServiceConnected() not called after...Dianne Hackborn2011-07-262-9/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ...apk reinstall; affects user privacy Disconnecting a ServiceConnection after an app is torn down could impact the bookkeeping of the same service if it has been started for the app. Also address issue #5073927: GSF process can't be killed A new flag allows the systems location manager service to tell the activity manager to not pull bound services up forever into the visible adj level. Change-Id: I2557eca0e4bd48f3b10007c40ec878e769fd96a8
* | | Cached NTP time for system services.Jeff Sharkey2011-07-101-15/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | Uses NTP server and timeout from secure settings, or fallback to defaults in resources. Update various system services to use cached NTP time when fresh enough, or force updates as needed. Bug: 4517273 Change-Id: Ie1c4c4883836013d02ca0bbd850cf8949f93b34b
* | | GPS: Support for on-demand NTP time injectionMike Lockwood2011-06-291-5/+23
| | | | | | | | | | | | | | | Change-Id: I83db0249c13598070ed70b9f90207305b60b468f Signed-off-by: Mike Lockwood <lockwood@android.com>
* | | am 859443f2: am c0d9834a: am 5d78e0b8: Merge "GPS: Change NTP polling ↵Mike Lockwood2011-05-241-2/+2
|\ \ \ | |/ / | | | | | | | | | | | | | | | interval from 4 to 24 hours" into honeycomb-mr2 * commit '859443f2a4d6a2b72c3e9c75720d32d4e4c09489': GPS: Change NTP polling interval from 4 to 24 hours
| * | am c0d9834a: am 5d78e0b8: Merge "GPS: Change NTP polling interval from 4 to ↵Mike Lockwood2011-05-231-2/+2
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | 24 hours" into honeycomb-mr2 * commit 'c0d9834a1c6dd8d9cd0b7fe9b50495578c104405': GPS: Change NTP polling interval from 4 to 24 hours
| | * | GPS: Change NTP polling interval from 4 to 24 hoursMike Lockwood2011-05-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 4 hours is excessive, and we want to save bandwidth on the NTP servers Change-Id: Ic5ac4f4a8e62167206f3f620ea51635a2ea771d6 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | | | am ee60f3fb: resolved conflicts for merge of 18cc814c to honeycomb-plus-aospJake Hamby2011-05-111-8/+3
|\ \ \ \ | |/ / / | | | | | | | | | | | | * commit 'ee60f3fb1b4e61ac8027293a658ba710e36d36b6': Enable support for SMS national language shift tables.
| * | | resolved conflicts for merge of 18cc814c to honeycomb-plus-aospJake Hamby2011-05-101-8/+3
| |\ \ \ | | | |/ | | |/| | | | | Change-Id: I2b569ada3baec2dc486296623063bc2b504c5e96
| | * | Enable support for SMS national language shift tables.Jake Hamby2011-04-061-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for encoding and decoding SMS 7 bit user data using the national language shift tables defined in 3GPP TS 23.038 (GSM/UMTS only), including the new tables added in Release 9 for Indic languages. Decoding is always supported, but encoding is only enabled for the specific language tables added to the new integer array resources "config_sms_enabled_single_shift_tables" and "config_sms_enabled_locking_shift_tables" defined in frameworks/base/core/res/res/values/config.xml. The default empty arrays should be overridden in an OEM overlay for the specific nationalities where SMS national language shift table encoding is allowed/mandated (e.g. Turkey). GsmAlphabet.countGsmSeptets() will try to find the most efficient encoding among all combinations of enabled locking shift and single shift tables. If no 7 bit encoding is possible, 16 bit UCS-2 encoding will be used. This change also fixes a bug in the decoder: when an escape septet is followed by a septet with no entry in the extension (single shift) table, TS 23.038 Table 6.2.1.1 states that the MS shall display the character in the main GSM 7 bit default alphabet table, or the active national language locking shift table. Previously, we were decoding this sequence as a space character. Two consecutive escape septets will continue to decode as a space character, according to Note 1 of table 6.2.1.1. Change-Id: I4dab3f0ffe39f3df2064ed93c9c05f26e274d18b
* | | | Use passive provider for location based country detectionDaisuke Miyakawa2011-04-282-40/+78
| | | | | | | | | | | | | | | | | | | | Bug: 4345419 Change-Id: Ia3e071b97c6971538ea994fdee6029db928201d6
* | | | Remove the deprecated things from Config.java. These haven't been working ↵Joe Onorato2011-04-071-1/+0
|/ / / | | | | | | | | | | | | | | | since before 1.0. Change-Id: Ic2e8fa68797ea9d486f4117f3d82c98233cdab1e
* | | am a5b68f39: am 5982bf66: GPS: Restore XTRA downloading at boot.Mike Lockwood2011-03-171-1/+1
|\ \ \ | |/ / | | / | |/ |/| * commit 'a5b68f39e2936a83eac0b995992724cd5de6905d': GPS: Restore XTRA downloading at boot.
| * GPS: Restore XTRA downloading at boot.Mike Lockwood2011-03-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Between Froyo and Gingerbread we disabled scheduling an XTRA data download at boot because the Qualcomm engineers thought it should not be necessary. However, some users noticed a GPS performance degradation after receiving their Gingerbread update, and some reported forcing an XTRA download cleared up the problem. This change restores the Froyo behavior of downloading XTRA data after boot. Bug: 3509901 Change-Id: I5a52201a2b24ce4a5d3ddb1f86340e3d5387f603 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | am 6c8d8d89: am 8c32bddf: Merge "GPS: Disable verbose logging" into gingerbreadMike Lockwood2010-10-251-4/+3
|\ \ | |/ | | | | | | | | | | Merge commit '6c8d8d8927373fdb9ad1c853396b5dbc8295f996' * commit '6c8d8d8927373fdb9ad1c853396b5dbc8295f996': GPS: Disable verbose logging
| * GPS: Disable verbose loggingMike Lockwood2010-10-251-4/+3
| | | | | | | | | | | | | | BUG: 3127049 Change-Id: I9efd9eb7ff69724b133f3b70c52e173f49ddfbc5 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | am d78c8d8b: am f6572e7e: Merge "GPS: Fix network type logic in ↵Mike Lockwood2010-10-221-7/+14
|\ \ | |/ | | | | | | | | | | | | | | requestRefLocation" into gingerbread Merge commit 'd78c8d8bb9516878eb5042a28d76bd6bcf4c6780' * commit 'd78c8d8bb9516878eb5042a28d76bd6bcf4c6780': GPS: Fix network type logic in requestRefLocation
| * GPS: Fix network type logic in requestRefLocationMike Lockwood2010-10-221-7/+14
| | | | | | | | | | Change-Id: I20ef81bcf029b289389dba57e6cf457fda5acbf4 Signed-off-by: Mike Lockwood <lockwood@android.com>
* | resolved conflicts for merge of 368fdba4 to masterBrad Fitzpatrick2010-10-211-3/+4
|\ \ | |/ | | | | Change-Id: I42b7b433c86a71a5da5db67109f056a280077c9d
| * Reduce logging.Joe Onorato2010-10-191-3/+4
| | | | | | | | | | | | | | | | | | | | Remember, the system and main logs are - Shared resources - Primarily for recording problems - To be used only for large grained events during normal operation Bug: 3104855 Change-Id: I136fbd101917dcbc8ebc3f96f276426b48bde7b7
generated by cgit v1.1 at 2025-08-18 05:48:57 +0000