Configurable scan job ids

[davidgyoung]

The Job Scheduler ScanJobs used in Android 8 has a hard-coded job id of 1 and 2. Because this job id must be unique per application, this can cause collisions with other app job ids. This changes the default job ids to be a high integer number, and declares them in AndroidManifest.xml:

        <service android:name=".service.ScanJob"
                android:permission="android.permission.BIND_JOB_SERVICE" >
            <meta-data android:name="immmediateScanJobId" android:value="208352939" />
            <meta-data android:name="periodicScanJobId" android:value="208352940" />
        </service>

These may be overridden in the app manifest as needed like this:

        <service android:name="org.altbeacon.beacon.service.ScanJob">
            <meta-data android:name="immediateScanJobId" android:value="1000" tools:replace="android:value"/>
            <meta-data android:name="periodicScanJobId" android:value="1001" tools:replace="android:value"/>
        </service>

The job ids may also be changed programmatically with:

        ScanJob.setOverridePeriodicScanJobId(100);
        ScanJob.setOverrideImmediateScanJobId(101);

However, for third party apps using the library the programmatic syntax should be avoided as it accesses a private API and is not guaranteed to be supported in future releases.

This resolves #582

[dietert]

Hi David

I suppose that "immmediateScanJobId" with 3 'm'-s is a typo in the documentation?

Regards
Dieter

[davidgyoung]

Yes, this is a typo in the documentation which I just fixed here. Thanks for noting it This same typo actually was in the AndroidManifest.xml for the library when it was released in version 2.13, but it was quickly updated in minor release 2.13.1 in #653