Example in the JS code is:
        bgGeo.configure(callbackFn, failureFn, {
                        url: ‘somewhere + UUID, // <-- only required
for Android; ios allows javascript callbacks for your http
                        params: {
        // HTTP POST params sent to your server when persisting
locations.
                        },
                        headers: {
                                "Content-type":
"application/x-www-form-urlencoded",
                                "auth_uuid": UUID,
                                "auth_token": TOKEN,
                        },
                        desiredAccuracy: 10,
                        stationaryRadius: 20,
                        distanceFilter: 30,
                        debug: true // <-- enable this hear sounds for
background-geolocation life-cycle.
                        });

Updates to be less verbose in non debug mode

Android

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

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

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

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