christocracy
commented
1 year ago What you are likely experiencing here is a user walking around a home / office, where the Android MotionActivity API keeps triggering into the "moving" state. The plugin will not return to the "stationary" state until the MotionaActivity API reports the device is still, when the plugin initiates the stopTimeout timer (which you've configured to 10 minutes.).
Once the stopTimeout timer is engaged, it will be cancelled if the MotionActivity api reports any movement (eg: on_foot). Only after the stopTimeout timer expires will the plugin return to the "stationary" state and turn off location-services.
You can add a Config.motionTriggerDelay (eg: 30000ms) to help decrease spurious motion-triggers while walking around a house.
tushaagit
No, infact we don't want to calculate the distance travelled, while user is in the premises, thats why we have applied distance filter of 50 meters, as user will be majorly working on maintenance of lifts where movement is minimal, we want to keep the location updates as minimum as possible while user is in any premises, and whenever user starts moving again .i.e leaving the premises, then again we want to track his travel. 2 major issues we are facing right now are: 1] Eventhough user is not moving much i.e beyond 25/50 meter still lot of locations gets uploaded, 2] while user is stationary, the locations captured are inaccurate in premises, i.e locations differ by nearly 1 km or so, and because of this, system considers that the user has travelled that much of distance e.g: 1km for each inaccurate location, so if 25 inaccurate locations are captured then odometer increases by 25 km, which is another major issue which we are facing currently. If user has actually travelled by vehicle suppose a distance of 10 km from his home to premise and returns back to his home 10km, so total odometer km should be something around 20, but as it considers inaccurate locations (whose odometer calculation has gone upto 25km, it sums up that with the to-and fro commuting km value (i.e 20km). So total distance travelled comes as 45. Hopefully you got my point.
BG Geolocation keeps on tracking/sending locations continuously even when user/device is still
Your Environment
Plugin version: 4.8
Platform: Android
OS version: 11
Device manufacturer / model: samsung SM-A307FN
Cordova version (
cordova -v): 11.0.0Cordova platform version (
cordova platform ls): Installed platforms: android 11.0.0 ios 6.2.0 Available platforms: browser ^6.0.0 electron ^3.0.0 windows ^7.0.0Plugin config provided to
#ready:bgGeo.setConfig({ url: window.app.config.serviceServicePath + 'RecordUserGeoLocation', params: { "EmployeeID": empID, "UserID": userID, "UserName": userName, "Remarks": "Transistorsoft Recording", "AttendanceID": localStorage.getItem("AttendanceID"), } }