Add new Cordova CSP meta tag.  Modify schema of returned geolocation, placing location params into 'coords' key in order to make room for extra meta-data, such as detected-activity from Android

Remove Cordova references from BackgroundGeolocation lib.  All cordova references and callbacks will be handled in CDVBackgroundGeolocation

Edge

Update CDVBackgroundGeoLocation.m

Implement new ios config param disableElasticity

Implement new ios config param disableElasticity to disable speed-based distance-filter auto-scaling.  Also disabled ios log-messages when debug: false

Edge

Keep track of 'enabled' state in Settings -- when using autoStart, only start when plugin is enabled

Implement Android SharedPreferences for configuration.  

Implement Android SharedPreferences for configuration.  This allows much simpler configuration of auto-starting the device at device BOOT, since the BootReceiver can now read its configuration from SharedPreferences.  This also allows the plugin to always add the android permission BOOT_COMPLETED and teh state of @config startOnBoot will determine whether to start the service.  Better error-handling on params/headers config.  Tip-of-the-hat to Nicholas Felmlee for all this

Edge

Transmit isMoving state from plugin->service in case setConfig is executed, which must stop/start the service to apply the new config -- we don't want to put the service in stationary-mode if it's already in moving mode

Don't recreate a new backgroundService Intent each time we configure -- merely setExtra new config values

Oops, typo.  meant startService.

Configurable location request

Allow LocationRequest to be more configurable for calculating fastestInterval, locationUpdateInterval

Http service

spacing

Implement BOOT_COMPLETED receiver.  NOTE:  You must manually add the android permission android.permission.RECEIVE_BOOT_COMPLETED to your AndroidManifest -- the plugin has this element in its plugin.xml purposely commented-out.  Also, when the BackgroundGeolocationService is run due to a BOOT_COMPLETED, there's no way to fetch any kind of user info, such as an authentication_token for your server to authenticate an HTTP request (if you've enabled the HTTP feature).  However, the HTTP request will insert the Android UUID which you *can* use to authenticate the request.  It's up to the developer to map the Android UUID to some particular user on your server.  You may fetch the Android UUID using the standard cordova plugin org.apache.cordova.device (see the documentation there on that API)

Http service