owntracks doesn't have location permission "allow all the time" about android HOT 3 CLOSED

There's been a few issues raised about this.

In short:

• Current version doesn't need it (it uses a Foreground Service, which doesn't need background location)
• Actually becomes an issue at reboot, where user interaction is required to get full location resolution
• Will become an option to enable in the next version, which should mean interaction-free location tracking continues across reboots, and may (?) better locations on certain devices.

just doesn't track me unless I have it open and am staring at the map live. One thing I noticed is that other apps on my phone have the location permission "all the time"

Does it publish locations when the activity is closed in move mode? I've not tested on CalyxOS so don't know how their location provider behaves.

from android.

I have the app in move mode and it's been sitting on my desk and mostly clocking in the updates. Except between 6:27 UTC and 8:35 UTC it only reported two times. The HTTP POSTs also have that gap. The phone must have been laying here untouched, weird.
The reboot issue has caught me a couple of times...

from android.

When you select move mode, OT requests the highest priority, most energy-hungry type of location updates, which should kick in an active GPS search. Should be the same as opening a maps application in the foreground and getting an instant location that way.

If you're not seeing that, then your device isn't delivering locations to OT in response to its request.

If you get a chance, there's one other thing you can try: if you put the device in move mode and don't observe a location arriving every moveModeLocatorInterval seconds, leave it a bit, and then open up a different mapping application (e.g. Google maps, or Organic maps). Does that now trigger OT to send a location update?

from android.