Significant Change Mode - Clarification on expected operation.

[ackleyimproved]

Android Version 2.5.3 and Oppo Finder X5. MQTTS.

As per documentation: "waits for the smart phone to tell it that the device has moved". And specifically for significant change mode: "Location data from other apps is reused and published as soon as it arrives".

Specifically for significant change mode I can get it to track very nicely only if connected via android auto or google maps. This is consistent the documentation.

However, if screen is off and not using any other GPS app (like google maps/android auto) NO data will be sent by own tracks. Is this consistent on how it should work? If so it is possible to have own tracks receive the GPS data directly instead of waiting for another app?

[TimYorke]

I'm seeing similar behaviour. Location updates are only sent either when I have the map view of the OwnTracks app in the foreground, or another app is accessing location data (in my case Magic Earth)

This is with Google Play version, 2.5.3, HTTP comms on Pixel 9a running GrapheneOs. Google Play services is not logged in, and no network access, but it has unrestricted battery and full-time precise location permission. Owntracks also unrestricted battery and full-time precise location permission

[memehammad]

Having the same issue on hyperos. Any fix?

[Korenchkin]

do you guys log with google maps?(timeline),since google should be optimized,so it basically should tell owntracks how to log (if i understand this correctly)...

i would be okay with this,singe timeline basically works the way i like it(but i need owntracks for my server)...and by the way timeline stays on device,so there should be no security/privacy concerns

[growse]

If so it is possible to have own tracks receive the GPS data directly instead of waiting for another app?

Move mode will poll the GPS every seconds and essentially guarantees a regular location update. Heavy on the power usage though.

@ackleyimproved Have you got "battery optimization whitelisted" enabled?

his is with Google Play version, 2.5.3, HTTP comms on Pixel 9a running GrapheneOs. Google Play services is not logged in, and no network access, but it has unrestricted battery and full-time precise location permission. Owntracks also unrestricted battery and full-time precise location permission

We've had other reports similar on GrapheneOS, where one of the ways it behaves differently to the Google flavour is that it won't deliver location updates via the Google Play Services fused provider when the app is in the background. I don't know why this is the case. Recommend you try the OSS verison and see if that makes any difference.

[mfortini]

I also found significant differences if the phone is in power saving mode or not. Background permissions are granted.

[TimYorke]

Recommend you try the OSS verison and see if that makes any difference.

This seems to work much more reliably, thanks.

[github-actions[bot]]

Marking issue with request for more data as stale, due to no updates.