transistorsoft / react-native-background-geolocation

Sophisticated, battery-conscious background-geolocation with motion-detection
http://shop.transistorsoft.com/pages/react-native-background-geolocation
MIT License
2.66k stars 425 forks source link

I have a problem in your library, because it is giving some straight lines and crossing guards and taking too long to start the transmission with the server! #1202

Closed otonielloliveira closed 3 years ago

otonielloliveira commented 3 years ago

Your Environment

Expected Behavior

Actual Behavior

image

Steps to Reproduce

image

Context

Debug logs

Logs ``` PASTE_YOUR_LOGS_HERE ```
christocracy commented 3 years ago

Do not ignore the issue template:

Platform: iOS or Android OS version: Device manufacturer / model:

christocracy commented 3 years ago

I see nothing wrong with your maps. Those locations are extremely close. Go for a long field-test of several kilometers.

otonielloliveira commented 3 years ago

Platform: Android OS version: Device manufacturer / model: J7 - Prime - Android : > 10

image image

christocracy commented 3 years ago

Your top image is meaningless to me without showing individual points. I suggest you test against the dev server at http://tracker.transistorsoft.com (See API docs Config.transistorAuthorizationToken

Your second image was likely from using mocked location, where the location constantly flips back and forth between mock location and real GPS.

christocracy commented 3 years ago

If by model J7, you mean Samsung J7, these budget device are missing important sensors Gyroscope and Magnetometer (they only have an accelerometer). These device are not ideal for location-tracking. The Samsung J7 is not a good device for development.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You may also mark this issue as a "discussion" and I will leave this open.

stale[bot] commented 3 years ago

Closing this issue after a prolonged period of inactivity. Fell free to reopen this issue, if this still affecting you.