-
-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessing location info while background #958
Comments
If possible at all, only asking for foreground should be the way to go. I assum complete background tracking will be hard to implement. Something to improve UX by "pseudo background" (i.e. to use other apps while tracking, but cannot be used to save battery) https://developer.android.com/guide/topics/ui/picture-in-picture |
The problem is that it appears like QField would do something in the background what it doesn't... |
QField can work in background, for example to track a path, but many Android devices stop the GPS/GNSS receiver when the app using geolocation is in background or the display is off. So even if the app is working in background it doesn’t receive geolocation data because the GPS/GNSS receiver is off. To solve this problem there are many apps to hold the GPS/GNSS active. |
I cannot reproduce this. I use "GPS Connected", too, to keep GPS running in the background as it helps keeping the fix in difficult terrain. I would like to use tracking lines to see the area I have covered in my surveys. Tracking with QField works just fine until I turn off the display. QField then no longer creates new vertices at the given time intervals until I turn the display back on. Then it simply connects the last point with the current position. |
Closing this in favor of an enhancement filed in another issue. |
I need more investigations but I wonder if we can improve that. QField needs only location info while in use. Still it requests the user for access during running in background...
QField Master and Android 10
The text was updated successfully, but these errors were encountered: