summaryrefslogtreecommitdiffstats
path: root/location/lib/java
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Disable AR HW when client binder dies." into mnc-dr-devDaniel Estrada Alva2015-08-261-0/+2
|\
| * Disable AR HW when client binder dies.destradaa2015-08-241-0/+2
| | | | | | | | | | | | | | | | | | Ensure that activities are unregistered from AR HW when the client's binder dies. This clean up is required to prevent AR HW to keep active when there are no clients listening for events. Bug: 19894637 Change-Id: Iccd609cf1d2d4a4453c7a96cb8645b61639c3234
* | Cherry-pick: Add callback-based support for HW Activity Recognition.destradaa2015-08-243-14/+88
|/ | | | | | | | | Add a callback-based mechanism for GmsCore to connect to Hardware Activity Recognition. This allows GmsCore to stop polling to identify if the Android platform supports the functionality or not. Bug: 17112184 Change-Id: I8f9459cbd15eecd70f6919c6551e6f7a663c732f
* Add versioning to FLP HAL.David Christie2015-04-142-1/+22
| | | | | | | Retain compatibility with implementations compiled against old headers or left unchanged from LMP. Change-Id: I3f7cfaaf0cba8697c312940a805b053c6040caa6
* Add ability to flush FLP HAL batched locations buffer.David Christie2015-04-131-0/+8
| | | | | | | | | Currently GmsCore has to guess how many locations to retrieve based on requested frequency and then demux the output looking for timestamps (that aren't monotonically increasing). This capability gives GmsCore a more graceful solution. Change-Id: Ie1d71615f699bc0d3c63f8b80aa7b40b9971cf96
* Add a status callback for location batching in FLP HALDavid Christie2015-04-132-4/+48
| | | | | | | -Allows GmsCore to know when location is unsuccessful so it can switch to a SW solution. Change-Id: I3d1df7b828f7fb189446881eea87d9a952310614
* Add capability callback for FLP HAL.David Christie2015-04-122-9/+64
| | | | | | | | | | | | | | | | | | | | Let HAL implementation tell if geofencing/batching is supported and which technologies (GNNS, wifi, etc) can be used. Still todo: Add ability for GmsCore geofencing to tell which technologies are supported (instead of just using it to update monitoring). This requires SystemApi change + approval so will do in separate CL. Note that the classes in the lib are not copied directly into GmsCore. The instance will always be whatever is in the platform. This is why the callback is backwards compatible as long as their is a default implementation (but not if it's abstract). Change-Id: I7d6adeb049b89935bc4443785df5d7ef4c730e5d
* Add smallest displacement field to FLP HALDavid Christie2015-04-081-0/+8
| | | | Change-Id: I4d857256c035c65185be3be8401bec8d45091aaf
* Fix exceptions in ActivityRecognition platform stack.destradaa2014-07-172-0/+39
| | | | | | b/16348349 Change-Id: I1f85283c86130b86389a1be7da49904658b0558c
* Add support in the platform for Activity Recognition Hardware.destradaa2014-07-114-0/+307
| | | | Change-Id: I7c4fff3526583475a5edf1f4ba8fede4e9419ead
* Remove unused imports from frameworks/base.John Spurlock2013-11-202-4/+0
| | | | Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
* Address Robin's code review comments in initial FlpHal submission.destradaa2013-08-093-27/+102
| | | | Change-Id: I50889599fdc5938a19b8bff4f11e64f44bcebdbf
* Add FlpHal layer to support Location Batching.destradaa2013-08-084-0/+398
| | | | Change-Id: Ia3a57d869dfb3f067a1b95fa66d54f311ddcfdc3
* Use FastPrintWriter... everywhere.Dianne Hackborn2013-06-241-1/+2
| | | | | | | | | | | | | One problem this turned up is, because FastPrintWriter does its own buffering, a lot of code that used to use PrintWriter would fail -- if it pointed to a StringWriter, there was no buffering, so it could just immediately get the result. Now you need to first flush the FastPrintWriter. Also added some new constructors to specify the size of buffer that FastPrintWriter should use. Change-Id: If48cd28d7be0b6b3278bbb69a8357e6ce88cf54a
* GPS Hardware geofencing.Jaikumar Ganesh2013-04-101-0/+67
| | | | | | Add support for doing geofencing in hardware. Change-Id: I6d5015190e8d84e1f4beb1010ed977a71c1622d0
* Revert "Move location provider lib to frameworks/ex - 1"Laurent Tu2012-12-115-0/+541
| | | | This reverts commit 578081f9da7ddb056b9b98524c639acd9194ecb6.
* Move location provider lib to frameworks/ex - 1Laurent Tu2012-12-055-541/+0
| | | | | | | | | Move location provider lib to frameworks/ex so it can be re-used in GmsCore. This is the frameworks/base part of the change (1). Change-Id: Ifc31a6809876e9c9afb6ed841b66cf06de7e8964
* Hide new location APIs and undeprecate old onesLaurent Tu2012-11-012-2/+136
| | | | | | | | | Hide all new location APIs related to LocationRequest/Geofence and undeprecate all deprecated APIs consequently to the LocationRequest and Geofence introduction. Also introduce LocationRequestUnbundled for LocationProviders to use. Change-Id: I5b116c7d342041f45b341c88a4b6813571118018
* fix NLP for COARSE applications, build FLP with SDKVictoria Lease2012-11-011-0/+17
| | | | | | | | | | | | | | | In this commit, we provide a means for unbundled location providers to attach an EXTRA_NO_GPS_LOCATION to the Locations that they report. We also build FusedLocation against the SDK rather than the internal tree. Used in conjunction with I394ded497b8de40d1f85618bff282553cdf378cb to fix NLP for applications with only ACCESS_COARSE_LOCATION permission. Bug: 7453355 Change-Id: Ie696f7abff9ef5237740ab87fe9f537a1c812c54
* Add documentation for com.android.location.provider shared library.Nick Pelly2012-08-164-13/+31
| | | | Change-Id: I222d61811c88272e84a85512623210c0238337e5
* Fix a couple of bugs from the location overhaul.Nick Pelly2012-08-101-0/+3
| | | | | | | | | | Marshall LocationRequest array correctly. Observe reportLocation from FusionEngine. Actually deliver the setRequest message to fusion engine. Change-Id: Iff64596fdd42f9fb06e563591dda9fbe0241533a
* Location overhaul, major commit.Nick Pelly2012-08-104-358/+287
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Add location shared library for location provider APIs.Dianne Hackborn2010-09-282-0/+440
First part, adding the existing classes in their new library. The old code will be removed once everything gets switched to using this. Change-Id: I27b6ad8c75c16f35300090e95f12a7db5608e3a3
generated by cgit v1.1 at 2024-05-29 03:05:29 +0000