Recognition Service Stops in the Background

donmiguel commented 3 weeks ago

Your Environment

Plugin version: V4.16.0
Platform: Android
OS version: Android 10.0.0
Device manufacturer / model: Huawai P20
React Native version (react-native -v): 12.1.1

Plugin config

const state: State = await BackgroundGeolocation.ready({
        // Debug
        reset: false,
        debug: true,
        logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
        transistorAuthorizationToken: token,
        // Geolocation
        desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_HIGH,
        distanceFilter: 10,
        stopTimeout: 5,
        // Permissions
        locationAuthorizationRequest: 'Always',
        backgroundPermissionRationale: {
            title: "Allow {applicationName} to access this device's location even when closed or not in use.",
            message: "This app collects location data to enable recording your trips to work and calculate distance-travelled.",
            positiveAction: 'Change to "{backgroundPermissionOptionLabel}"',
            negativeAction: 'Cancel'
        },
        notification: {
            title: "Background tracking engaged",
            text: "Tracking is running"
        },
        // HTTP & Persistence
        autoSync: true,
        maxDaysToPersist: 14,
        // Application
        stopOnTerminate: false,
        stopOnStationary: false,
        startOnBoot: true,
        enableHeadless: true,
        foregroundService: true,
    });

Expected Behavior

The app should run configured as headless in the background to track movements.

Actual Behavior

After a certain time, when the screen is locked, the tracking stops.

Steps to Reproduce

Use the advanced demo app from the GitHub repo.
Paste the provided configuration into the demo app.
Start the app and start moving.
After some time, when the screen is locked, the tracking stops.
After unlocking the screen and switching to the app, the tracking restarts.

Context

Debug logs

Last logs entries

``` 04-18 15:00:01.163 DEBUG [AbstractService a] 🎾 start [ActivityRecognitionService startId: 1, eventCount: 1] 04-18 15:00:01.166 DEBUG [ActivityRecognitionService a] 🚘 ️DetectedActivity [type=IN_VEHICLE, confidence=96] 04-18 15:00:01.176 DEBUG [AbstractService a] ⚙️︎ FINISH [ActivityRecognitionService startId: 1, eventCount: 0, sticky: false] 04-18 15:00:01.303 DEBUG [AbstractService a] 🎾 start [ActivityRecognitionService startId: 2, eventCount: 1] 04-18 15:00:01.305 DEBUG [ActivityRecognitionService a] *** wasMoving: true, nowMoving: true, startedMoving: false, justStopped; false 04-18 15:00:01.306 DEBUG [HeadlessTask onHeadlessEvent] 💀 event: activitychange 04-18 15:00:01.307 DEBUG [HeadlessTask$2 onHeadlessJsTaskStart] taskId: 39 04-18 15:00:01.311 INFO [ActivityRecognitionService a] ╔═════════════════════════════════════════════ ║ Motion Transition Result ╠═════════════════════════════════════════════ ╟─ 🎾 ENTER: in_vehicle ╚═════════════════════════════════════════════ 04-18 15:00:01.311 DEBUG [AbstractService a] ⚙️︎ FINISH [ActivityRecognitionService startId: 2, eventCount: 0, sticky: false] 04-18 15:00:01.327 DEBUG [HeadlessTask$2 onHeadlessJsTaskFinish] taskId: 39 04-18 15:00:01.516 DEBUG [AbstractService f] ⚙️︎ ActivityRecognitionService.stopSelfResult(2): true 04-18 15:00:01.517 DEBUG [AbstractService onDestroy] 🔴 ActivityRecognitionService stopped 04-18 15:00:03.631 DEBUG [AbstractService a] 🎾 start [TrackingService startId: 34, eventCount: 1] 04-18 15:00:03.632 DEBUG [TrackingService c] ╔═════════════════════════════════════════════ ║ TrackingService: LocationResult ╠═════════════════════════════════════════════ ╟─ 📍 Location[fused 47******,10****** hAcc=4 et=+6d0h25m57s351ms alt=544.0 vel=12.029285 bear=317.0 vAcc=5 sAcc=0 bAcc=0 {Bundle[mParcelledData.dataSize=412]}] ╟─ Age: 43ms, time: 1713445203588 04-18 15:00:03.633 DEBUG [TSLocationManager onLocationResult] ╔═════════════════════════════════════════════ ║ Process LocationResult ╠═════════════════════════════════════════════ 04-18 15:00:03.634 DEBUG [TSLocationManager d] Distance from last location: 36.260777, apparent speed: 12.115194 04-18 15:00:03.634 DEBUG [TSLocationManager a] Median accuracy: 4.0 04-18 15:00:03.635 DEBUG [TSLocationManager c] Odometer: 48759.13 04-18 15:00:03.643 INFO [TSScheduleManager cancelOneShot] ⏰ Cancel OneShot: MOTION_ACTIVITY_CHECK 04-18 15:00:03.659 INFO [TSScheduleManager oneShot] ⏰ Scheduled OneShot: MOTION_ACTIVITY_CHECK in 62993ms (jobID: -18513055) 04-18 15:00:03.664 DEBUG [AbstractService a] ⚙️︎ FINISH [TrackingService startId: 34, eventCount: 0, sticky: true] 04-18 15:00:03.676 DEBUG [HeadlessTask onHeadlessEvent] 💀 event: location 04-18 15:00:03.679 DEBUG [HeadlessTask$2 onHeadlessJsTaskStart] taskId: 40 04-18 15:00:03.683 DEBUG [HeadlessTask$2 onHeadlessJsTaskFinish] taskId: 40 04-18 15:00:03.694 INFO [SQLiteLocationDAO persist] ✅ INSERT: 4829b1f4-a021-4637-9531-88962d698607 ```

christocracy commented 3 weeks ago

🔴 ActivityRecognitionService stopped

this is normal and expected. You are merely misunderstanding this log-entry’s meaning. It only means that the Service assigned to handle events has completed its work and stopped, as it’s supposed to. The plug-in has registered a PendingIntent with the ActivityTransitionService (provided by play-services), which will continue to relaunch the plug-in’s ActivityRecognitionService when another event occurs.

After some time, when the screen is locked, the tracking stops.

“After some time” as in stopTimeout: 5.

read the wiki here at this GitHub repo “Philosophy of Operation”. Also read the api docs Config.stopTimeout.

christocracy commented 3 weeks ago

You can confirm that the ActivityRecognitionService remains actively tracking motion events by observing the logs while physically shaking your device vigorously to simulate walking. It sometimes helps to shake for a bit (eg 15s) then place it down flat for a few seconds, pick up and shake again.

donmiguel commented 3 weeks ago

Thanks for clarifying and pointing to the docs. I get that after the stopTimeout expires and I am not moving the plugin enters the stationary state. However, in my case, the app stops tracking while I am moving. Location authorization is set to always.

christocracy commented 3 weeks ago

Huawai P20

This is one of the worst-performing devices on earth. I own one.

see https://dontkillmyapp.com

donmiguel commented 3 weeks ago

I agree. Tests with a Pixel device are looking better.

transistorsoft / react-native-background-geolocation