Baseflow / Baseflow/flutter-geolocator
Android GPS accuracy negatively affected after upgrading to 8.2.0
- Dominant language
- Dart
- Stars
- 1.3k
- Forks
- 803
- Avg merge
- 8h 16m
- Merged PRs (30d)
- 1
Description
## 🔙 Regression
Android GPS accuracy negatively affected after upgrading to 8.2.0
### Old (and correct) behavior
Previously on android devices and emulator, listening to a position stream with with best accuracy provided events a few meters apart. For example, when recording a track while walking, each point returned by the stream would be a few meters apart. (about once per second). Behavior observed on physical devices and emulators.
### Current behavior
After upgrading to version 8.2.0 the position stream is return points 80+ meters apart (10+ seconds apart) during my testing.
### Reproduction steps
Record a track with similar duration/distance before and after upgrading to 8.2.0 on an Android device. If each track has a similar duration and distance, the track recorded on 8.2.0 will have far fewer points (and greater distance between each point) than the track recorded on a previous version. The track recorded on pre 8.2.0 versions will have about 10x more points. IOS seems to retain the same behavior and number of points after upgrading to 8.2.0.
### Configuration
**Version:** 8.2.0
**Platform:**
- [ ] :iphone: iOS
- [X] :robot: Android
Contributor guide
Research direction
Start by reproducing the Android position-stream behavior described, comparing version 8.2.0 with a pre-8.2.0 version on a device or emulator. Use the track point count, spacing, and timing as the acceptance criteria: Android should again produce points only a few meters apart at roughly once per second, while iOS behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart, flutter
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100