Background Location Stop Detecting Very Late After Stopped about react-native-background-geolocation HOT 6 CLOSED

!!! Edit your issue and provide all the info !!!

Plugin version:
Platform: Android
OS version:
Device manufacturer / model:

from react-native-background-geolocation.

!!! Edit your issue and provide all the info !!!

Plugin version: Platform: Android OS version: Device manufacturer / model:

I have updated the issue with all required info

from react-native-background-geolocation.

@christocracy i have done a few more trips and recorded the logs for it.

At this point i'm inside the car and its parked (for more than 5 minutes), i have included some logs below. If you notice it still says thats the Activity is "in_vehicle". How is it possible ? Shouldn’t it trigger a STILL activity ?

6-26 00:09:22.831 16320 21643 I TSLocationManager: ║ Motion Transition Result
06-26 00:09:22.831 16320 21643 I TSLocationManager: ╠═════════════════════════════════════════════
06-26 00:09:22.831 16320 21643 I TSLocationManager: ╟─ 🎾 ENTER: in_vehicle
06-26 00:09:22.831 16320 21643 I TSLocationManager: ╚═════════════════════════════════════════════
06-26 00:09:22.832 16320 16409 I ReactNativeJS: 'BackgroundLocationUpdate', '06-26-2024 12:09', [ 'onActivityChange:LISTENER:185++++++',
06-26 00:09:22.832 16320 16409 I ReactNativeJS: { confidence: 100, activity: 'in_vehicle' } ]
06-26 00:09:22.832 16320 21643 D TSLocationManager: [c.t.l.service.AbstractService a]
06-26 00:09:22.832 16320 21643 D TSLocationManager: ⚙️︎ FINISH [ActivityRecognitionService startId: 2, eventCount: 0, sticky: false]
06-26 00:09:22.834 16320 16409 I ReactNativeJS: 'BackgroundLocationUpdate', '06-26-2024 12:09', [ 'onActivityChange:LISTENER:185++++++',
06-26 00:09:22.834 16320 16409 I ReactNativeJS: { confidence: 100, activity: 'in_vehicle' } ]
06-26 00:09:22.838 16320 16409 I ReactNativeJS: 'BackgroundLocationUpdate', '06-26-2024 12:09', [ 'onActivityChange:LISTENER:185++++++',
06-26 00:09:22.838 16320 16409 I ReactNativeJS: { confidence: 100, activity: 'in_vehicle' } ]
06-26 00:09:23.041 16320 16320 D TSLocationManager: [c.t.l.service.AbstractService f]
06-26 00:09:23.041 16320 16320 D TSLocationManager: ⚙️︎ ActivityRecognitionService.stopSelfResult(2): true
06-26 00:09:23.046 16320 16320 D TSLocationManager: [c.t.l.service.AbstractService onDestroy]
06-26 00:09:23.046 16320 16320 D TSLocationManager: 🔴 ActivityRecognitionService stopped
06-26 00:09:24.269 16320 16320 D TSLocationManager: [c.t.l.service.AbstractService a]
06-26 00:09:24.269 16320 16320 D TSLocationManager: 🎾 start [TrackingService startId: 155, eventCount: 1]
06-26 00:09:24.271 16320 16320 I TSLocationManager: [c.t.l.service.TrackingService b]
06-26 00:09:24.271 16320 16320 I TSLocationManager: ℹ️ Location availability: true

from react-native-background-geolocation.

How is it possible ? Shouldn’t it trigger a STILL activity ?

The Motion api is provided by Google’s closed-source Play Services api. It is a black box with nothing more than an ON/OFF switch. The plug-in has no control over the accuracy or frequency of the results delivered by that API. There is no guarantee of the quality of results, which will vary from device to device.

from react-native-background-geolocation.

This issue is stale because it has been open for 30 days with no activity.

from react-native-background-geolocation.

This issue was closed because it has been inactive for 14 days since being marked as stale.

from react-native-background-geolocation.