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
I updated to 3.5.0 (apk from github) for Android. On opening QField, I see a "positioning service" notification. I find this confusing for two reasons:
I haven't opened a project, so I don't expect QFIeld to ask for position. There's no UI that is displaying my position, so I'd say it should not be activated. (Hard for me to follow what's going on; I don't see the green warning dot for location use from CalyxOS, so I'm guessing the issue is just the notification.)
Generally, programs that use location do not display this kind of notification when in the foreground. They display it when they are both 1) in the background and 2) doing background tracking, when configured to do so.
I pushed the "go home (square)" to get back to the home screen. The notification is still there. In this state, not having opened a project, and background, QField should not be asking for location or doing much of anything at all. Android doctrine seems not to distinguish much between back button and home button; the app is not on the screen and is not expected to do much, unless configured explicitly to do so.
My main project does have a tracking layer, as I was experimenting with that. But even if I load the project, I don't really expect background tracking and background battery use. I'd expect that background tracking is something I'd have to opt into from settings or a wizard, and that if this is in the Play store the rules would require that, from having watched e.g. Vespucci struggle with play store approvals: Even when the user had asked for recording position in background, their was angst about specific language.
(I'm not suggesting QField is doing anything devious; I view these as UI issues and also a battery issue of not running the GNSS receiver unless asked for.)
The text was updated successfully, but these errors were encountered:
Just reconfigured for internal GNSS vs bluetooth that's powered off :-) Looks like with opening a project with tracking and hitting home, positioning continues to run. And just on opening QFIeld, no project, it's requesting location.
I updated to 3.5.0 (apk from github) for Android. On opening QField, I see a "positioning service" notification. I find this confusing for two reasons:
I pushed the "go home (square)" to get back to the home screen. The notification is still there. In this state, not having opened a project, and background, QField should not be asking for location or doing much of anything at all. Android doctrine seems not to distinguish much between back button and home button; the app is not on the screen and is not expected to do much, unless configured explicitly to do so.
My main project does have a tracking layer, as I was experimenting with that. But even if I load the project, I don't really expect background tracking and background battery use. I'd expect that background tracking is something I'd have to opt into from settings or a wizard, and that if this is in the Play store the rules would require that, from having watched e.g. Vespucci struggle with play store approvals: Even when the user had asked for recording position in background, their was angst about specific language.
(I'm not suggesting QField is doing anything devious; I view these as UI issues and also a battery issue of not running the GNSS receiver unless asked for.)
The text was updated successfully, but these errors were encountered: