Re-order incoming config params due to previous Android pr by zgiles, which inserted a new Android config param headers

Add ability to customize the notification title and text.

Update README.md

Small text correction

Add missing comma to example code

Adding an abs() around the distance.

I saw negative distances when I was inside the stationary area, but
moving around within it.. perhaps a few houses over etc. Walking etc.
If I moved farther away, it eventually updated but more becaue it had
a significant update, such as driving miles.
This abs around the distance allows the less-than if statement to work.
Been using it for all day across several cities with great and accurate
updates.
Similar routines over the last few days were highly inaccurate and
behind.

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