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

Found the removeProximityAlert causes error if none are added already.  must be careful about removing these

Bug in comparing Integer when calculating distanceFilter changes.  always evaluated to a change in distanceFilter on each location change

Keep a single stationaryRegion PendingIntent instance rather than re-creating it each time we need to addProximityAlert.  This seems to have improved lock-ups coming out of a stationary-region.  Minor cleanup, re-arrange some lines, add docs

Import speedAcquisition phase from ios, being more aggressive with geolocation after a pace-change to moving

Debugging Android bugs, onDestroy remove intentReceivers, improperly resetting stationaryAlarm, incorrectly ignoring location in onLocationChanged

Implement stationaryAlarm to detect user stopped rather than passively calculating in onLocationChanged, since onLocationChanged won't fire until distanceFilter is surpassed