Bug in comparing Integer when calculating distanceFilter changes.  always evaluated to a change in distanceFilter on each location change
Found the removeProximityAlert causes error if none are added already.  must be careful about removing these
Add logging to onProvider methods
Move initial call to setPace in onStartCommand out if if(intent) {} block.  This may have been causing major issues where tracking fails to start after OS kills service due to lack of memory.  Also return START_REDELIVER_INTENT, which also may have been causing problems
Implement stationary-heartbeat location monitor in order to keep proximity-detection alive.  Android 4.4 proximity detectors are supposed to fire after 4min while suspended but I don'tt see that happening.  This Alarm of fixed time to ping the GPS at regular interval seems to make stationary-exit work well.  Also turned on CellLocationChange event-listener but that only works in foreground unfortunately.  IF that actually worked, we could have something similar to ios Significant Changes system.  This is why we have to poll the GPS regularly while in stationary-mode
Take care with creating foreground Notification for pre API level 16
remove config param authToken in favour of entire http params object, more flexible for others
Update docs with new API
clean up
Only reset stationary alarm when we have an accurate location and speed
Move stationary-monitor block into BraodcastReceiver.  Increase stationary-monitor rate to 3min
Cleanup
Remove some clauses from getLastBestLocation, remove requiremement that location have speed > 0.75 when exiting stationary region, this could be what's causing inability to exit stationary region on some devices
it's possible for location-poller to still fire its last alarm if EXIT was determined via proximity-detector, if isMoving here, just bail out
Merge pull request #8 from christocracy/android

Android