You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The BackgroundGeolocation library has the ability to only report changes in location when the user moves. This saves power in some cases, e.g. if the phone is sitting on a charger and not moving, the accelerometer shows it is stationary. The library saves power by returning a Stationary point.
Verify the behavior around this. I suspect it only generates a callback once, then stops calling until the phone moves again. If this happens, upon the move we should backfill so that we have the same point reported at 5 minute intervals until that next point report.
Example:
@3:01 - I set my phone down on the desk @3:02 - The BackgroundGeolocation callback triggers and we save a coordinate @3:40 - I move my phone @3:40 - The BackgroundGeolocation callback triggers and we save a coordinate
If the above does occur (which we need to verify), we should save the same reported coordinate from 3:02 at 3:07, 3:12, 3:17, 3:22, 3:27, 3:32, 3:37 and then save the new 3:40 coordinate.
The text was updated successfully, but these errors were encountered:
The BackgroundGeolocation library has the ability to only report changes in location when the user moves. This saves power in some cases, e.g. if the phone is sitting on a charger and not moving, the accelerometer shows it is stationary. The library saves power by returning a Stationary point.
Verify the behavior around this. I suspect it only generates a callback once, then stops calling until the phone moves again. If this happens, upon the move we should backfill so that we have the same point reported at 5 minute intervals until that next point report.
Example:
@3:01 - I set my phone down on the desk
@3:02 - The BackgroundGeolocation callback triggers and we save a coordinate
@3:40 - I move my phone
@3:40 - The BackgroundGeolocation callback triggers and we save a coordinate
If the above does occur (which we need to verify), we should save the same reported coordinate from 3:02 at 3:07, 3:12, 3:17, 3:22, 3:27, 3:32, 3:37 and then save the new 3:40 coordinate.
The text was updated successfully, but these errors were encountered: