Background location update doesn't work #9

Open
opened 3 months ago by davidskeck · 27 comments

Hello,

I am running NextTracks on a Pixel 4a and have it configured to work in significant changes monitoring mode, but the location never updates. I can manually update it by going into the application and changing the mode or hitting the upload button, but the location never updates otherwise. I know the MQTT broker is configured and working correctly because OwnTracks works with the same server on someone else's iPhone and updates correctly. Any tips for settings to change so NextTracks will work well with my setup? Thank you!

Hello, I am running NextTracks on a Pixel 4a and have it configured to work in significant changes monitoring mode, but the location never updates. I can manually update it by going into the application and changing the mode or hitting the upload button, but the location never updates otherwise. I know the MQTT broker is configured and working correctly because OwnTracks works with the same server on someone else's iPhone and updates correctly. Any tips for settings to change so NextTracks will work well with my setup? Thank you!
Owner

Did you disable battery optimisation for NextTracks in android? If not, that might be a problem.

Did you disable battery optimisation for NextTracks in android? If not, that might be a problem.
Poster

I did indeed. I have all green checkmarks on the status page. Any other ideas?

It seems that location updates are being sent, but they don't have the correct location value. I can see the timestamp updating but not the location.

I did indeed. I have all green checkmarks on the status page. Any other ideas? It seems that location updates are being sent, but they don't have the correct location value. I can see the timestamp updating but not the location.
Owner

Do you see location updates when the App is open?

Do you see location updates when the App is open?
Poster

Not unless I change the monitoring mode or click the update button. It will send updates automatically otherwise, but as I said, will only have an older location (from the last time I manually updated it).

Not unless I change the monitoring mode or click the update button. It will send updates automatically otherwise, but as I said, will only have an older location (from the last time I manually updated it).
Owner

Well, are you moving a bigger distance than the set locatorDisplacement? In significant mode, small changes aren't reported to the server, but when changing the mode to move mode for example, the location will be updated.

Well, are you moving a bigger distance than the set locatorDisplacement? In significant mode, small changes aren't reported to the server, but when changing the mode to move mode for example, the location will be updated.
Poster

Huh. That's a great question. My value is 25. What unit is that in?


Huh. That's a great question. My value is 25. What unit is that in? -----
Owner

It's 25 meters.

It's 25 meters.
Poster

OK. Yeah I'm moving miles without it updating.

OK. Yeah I'm moving miles without it updating.
Owner

Could you send me your NextTracks config? (with credentiala removed)

Could you send me your NextTracks config? (with credentiala removed)
Poster

Sure! It is below. Thanks!

{
  "_type" : "configuration",
  "waypoints" : [ ],
  "_build" : 32100,
  "autostartOnBoot" : true,
  "cleanSession" : false,
  "clientId" : "***",
  "cmd" : true,
  "debugLog" : false,
  "deviceId" : "***",
  "fusedRegionDetection" : true,
  "geocodeEnabled" : true,
  "host" : "***",
  "ignoreInaccurateLocations" : 0,
  "ignoreStaleLocations" : 0.0,
  "info" : true,
  "keepalive" : 3600,
  "locatorDisplacement" : 25,
  "locatorInterval" : 8,
  "locatorPriority" : 2,
  "mode" : 0,
  "monitoring" : 1,
  "moveModeLocatorInterval" : 5,
  "mqttProtocolLevel" : 3,
  "notificationEvents" : true,
  "notificationHigherPriority" : false,
  "notificationLocation" : true,
  "password" : "*******",
  "ping" : 30,
  "port" : 8883,
  "pubExtendedData" : true,
  "pubQos" : 1,
  "pubRetain" : true,
  "pubTopicBase" : "owntracks/%u/%d",
  "sub" : true,
  "subQos" : 2,
  "subTopic" : "owntracks/#",
  "tid" : "DK",
  "tls" : true,
  "username" : "***",
  "ws" : false
}
Sure! It is below. Thanks! ``` { "_type" : "configuration", "waypoints" : [ ], "_build" : 32100, "autostartOnBoot" : true, "cleanSession" : false, "clientId" : "***", "cmd" : true, "debugLog" : false, "deviceId" : "***", "fusedRegionDetection" : true, "geocodeEnabled" : true, "host" : "***", "ignoreInaccurateLocations" : 0, "ignoreStaleLocations" : 0.0, "info" : true, "keepalive" : 3600, "locatorDisplacement" : 25, "locatorInterval" : 8, "locatorPriority" : 2, "mode" : 0, "monitoring" : 1, "moveModeLocatorInterval" : 5, "mqttProtocolLevel" : 3, "notificationEvents" : true, "notificationHigherPriority" : false, "notificationLocation" : true, "password" : "*******", "ping" : 30, "port" : 8883, "pubExtendedData" : true, "pubQos" : 1, "pubRetain" : true, "pubTopicBase" : "owntracks/%u/%d", "sub" : true, "subQos" : 2, "subTopic" : "owntracks/#", "tid" : "DK", "tls" : true, "username" : "***", "ws" : false } ```
Owner

Does it work in move mode though? And btw, what Android version are you running?

Does it work in move mode though? And btw, what Android version are you running?
Poster

It does not work in move mode either.

GrapheneOS Android 11

It does not work in move mode either. GrapheneOS Android 11
Owner

Do you have another Android device that has stock android where you could try NextTracks? I suppose it's possible that GrapheneOS could cause problems here.

Do you have another Android device that has stock android where you could try NextTracks? I suppose it's possible that GrapheneOS could cause problems here.
Poster

I do not. I understand if that's the case. Thank you for looking into this with me.

I do not. I understand if that's the case. Thank you for looking into this with me.
Owner

Well, I think it's the most likely scenario since I have nearly the exact same setup but I can't reproduce the problem.

Well, I think it's the most likely scenario since I have nearly the exact same setup but I can't reproduce the problem.

Hello, I followed the discussion and would like to add that I use NextTracks on CalyxOS and have no problems with it. I decided against Graphene mainly because of the strange views on security the Graphene maintainers expressed...

https://calyxos.org/

Hello, I followed the discussion and would like to add that I use NextTracks on CalyxOS and have no problems with it. I decided against Graphene mainly because of the strange views on security the Graphene maintainers expressed... https://calyxos.org/
Poster

Interesting. I wonder what could be causing it in Graphene. I considered Calyx but everything I have read points to Graphene being the most secure. I think there are going to be plenty of disagreements between OSes so the arguments between the developers doesn't really bother me.

Are you running microG on Calyx? I only ask because there is no Google play service layer in Graphene and I wonder if that could cause my issue.

Interesting. I wonder what could be causing it in Graphene. I considered Calyx but everything I have read points to Graphene being the most secure. I think there are going to be plenty of disagreements between OSes so the arguments between the developers doesn't really bother me. Are you running microG on Calyx? I only ask because there is no Google play service layer in Graphene and I wonder if that could cause my issue.

microG is a "native" part of CalyxOS. I can confirm it works in some cases I checked.
Nevertheless Google play services - or their absence - have nothing to do with your problem. It is the whole idea behind NextTracks to omit Google at all in the code. NextTracks is completely Google-free.

microG is a "native" part of CalyxOS. I can confirm it works in some cases I checked. Nevertheless Google play services - or their absence - have nothing to do with your problem. It is the whole idea behind NextTracks to omit Google at all in the code. NextTracks is completely Google-free.
Poster

Gotcha. yeah I just read you can disable microG in calyx so I wasn't sure if you had it enabled or not.

I know that is the whole point of NextTracks but I thought perhaps there could be a bug in it somewhere that microG was covering.

Gotcha. yeah I just read you can disable microG in calyx so I wasn't sure if you had it enabled or not. I know that is the whole point of NextTracks but I thought perhaps there could be a bug in it somewhere that microG was covering.

@skraw

Hello, I followed the discussion and would like to add that I use NextTracks on CalyxOS and have no problems with it. I decided against Graphene mainly because of the strange views on security the Graphene maintainers expressed...

https://calyxos.org/

It's unfortunate that the CalyxOS project and community take every opportunity to spread misinformation about GrapheneOS to attack it across every possible platform. This is a nice example of how you folks spread misinformation about us everywhere.

What are these supposedly 'strange views' on security expressed by GrapheneOS developers? Why are you jumping into this issue and spreading misinformation about GrapheneOS in order to promote a project which has behaved incredibly maliciously towards us? I know the answer already, and all I can do is suggest that you avoid attacking us with misinformation. You aren't really helping the project you're trying to promote, because each of these incidents is archived and our eventual response to these attacks will be proportional to what has been done.

Nevertheless Google play services - or their absence - have nothing to do with your problem. It is the whole idea behind NextTracks to omit Google at all in the code. NextTracks is completely Google-free.

CalyxOS sends the real-time location of users to proprietary location services via microG. How is it not related to be using network locations services through it?

GrapheneOS works the same way as AOSP in regards to location, at least by default. It has GNSS with A-GPS support in the base OS. There are no differences in this for AOSP and out-of-the-box GrapheneOS. It's possible that this app is relying on network-based location features that aren't currently provided. We plan to provide alternatives to those network services via a more privacy-respecting approach, but for now we don't provide more than the AOSP functionality.

@davidskeck

Are you running microG on Calyx? I only ask because there is no Google play service layer in Graphene and I wonder if that could cause my issue.

GrapheneOS doesn't include any form of Google services or other proprietary services like CalyxOS but it does have https://grapheneos.org/usage#sandboxed-play-services. It won't help in this case because this app is presumably using the OS location APIs rather than the Play services location APIs. The key thing is that the OS location APIs on the stock OS will use Play services as a backend, so the app is using Play services on the stock OS. Similarly, an OS using microG and their network-based location providers is using those as backends.

GrapheneOS and AOSP provide GNSS + A-GPS by default so the app needs to make sure to use it in a way that it has time to get a lock, etc. and certain things like geocoding aren't available with only the AOSP implementation. GrapheneOS does plan to fill in these gaps in AOSP, but with a privacy-respecting approach and it certainly won't be sending off real-time location, addresses, etc. to proprietary services by default, especially without informing the user.

@skraw > Hello, I followed the discussion and would like to add that I use NextTracks on CalyxOS and have no problems with it. I decided against Graphene mainly because of the strange views on security the Graphene maintainers expressed... > > https://calyxos.org/ It's unfortunate that the CalyxOS project and community take every opportunity to spread misinformation about GrapheneOS to attack it across every possible platform. This is a nice example of how you folks spread misinformation about us everywhere. What are these supposedly 'strange views' on security expressed by GrapheneOS developers? Why are you jumping into this issue and spreading misinformation about GrapheneOS in order to promote a project which has behaved incredibly maliciously towards us? I know the answer already, and all I can do is suggest that you avoid attacking us with misinformation. You aren't really helping the project you're trying to promote, because each of these incidents is archived and our eventual response to these attacks will be proportional to what has been done. > Nevertheless Google play services - or their absence - have nothing to do with your problem. It is the whole idea behind NextTracks to omit Google at all in the code. NextTracks is completely Google-free. CalyxOS sends the real-time location of users to proprietary location services via microG. How is it not related to be using network locations services through it? GrapheneOS works the same way as AOSP in regards to location, at least by default. It has GNSS with A-GPS support in the base OS. There are no differences in this for AOSP and out-of-the-box GrapheneOS. It's possible that this app is relying on network-based location features that aren't currently provided. We plan to provide alternatives to those network services via a more privacy-respecting approach, but for now we don't provide more than the AOSP functionality. @davidskeck > Are you running microG on Calyx? I only ask because there is no Google play service layer in Graphene and I wonder if that could cause my issue. GrapheneOS doesn't include any form of Google services or other proprietary services like CalyxOS but it does have https://grapheneos.org/usage#sandboxed-play-services. It won't help in this case because this app is presumably using the OS location APIs rather than the Play services location APIs. The key thing is that the OS location APIs on the stock OS will use Play services as a backend, so the app is using Play services on the stock OS. Similarly, an OS using microG and their network-based location providers is using those as backends. GrapheneOS and AOSP provide GNSS + A-GPS by default so the app needs to make sure to use it in a way that it has time to get a lock, etc. and certain things like geocoding aren't available with only the AOSP implementation. GrapheneOS does plan to fill in these gaps in AOSP, but with a privacy-respecting approach and it certainly won't be sending off real-time location, addresses, etc. to proprietary services by default, especially without informing the user.

I'm very tired of these attacks across many platforms orchestrated by CalyxOS and it's beyond ridiculous seeing it here. We'd greatly prefer not having to respond to misinformation spread about GrapheneOS but if it continues we'll refute it. My intention was to come here and provide useful help and information. It's unfortunate that even in a place like this, the malicious people harassing us, raiding our community and spreading misinformation are active.

I'm very tired of these attacks across many platforms orchestrated by CalyxOS and it's beyond ridiculous seeing it here. We'd greatly prefer not having to respond to misinformation spread about GrapheneOS but if it continues we'll refute it. My intention was to come here and provide useful help and information. It's unfortunate that even in a place like this, the malicious people harassing us, raiding our community and spreading misinformation are active.

@davidskeck You're 100% correct about what's happening. It's unfortunate someone malicious decided to detail things with misinformation in an opportunistic attack on us.

@davidskeck You're 100% correct about what's happening. It's unfortunate someone malicious decided to detail things with misinformation in an opportunistic attack on us.

@strcat: really, I have no idea why you hijack this thread only to tell the readers your bad feelings about Calyx, which I don't share. I use it for some months now and never had any problems with it, and there is no point in criticising MicroG, because if you don't want it, then just disable it.
I am in the linux community for decades now, and I don't believe anyone anything denying me root rights on my very own devices - explaining this by openly considering the owner of a device as too dumb to handle its security. And that's basically my critics on Graphene. In this respect, it is built in the same thinking as Apple IOS, and that is not compatible with me. Case closed.

Now, do you have any ideas how to help davidskeck ?

@strcat: really, I have no idea why _you_ hijack this thread only to tell the readers your bad feelings about Calyx, which I don't share. I use it for some months now and never had any problems with it, and there is no point in criticising MicroG, because if you don't want it, then just disable it. I am in the linux community for decades now, and I don't believe anyone anything denying me root rights on my very own devices - explaining this by openly considering the owner of a device as too dumb to handle its security. And that's basically my critics on Graphene. In this respect, it is built in the same thinking as Apple IOS, and that is not compatible with me. Case closed. Now, do you have any ideas how to help davidskeck ?

It was you who hijacked this thread as part of ongoing attacks by your community on GrapheneOS across a bunch of platforms. It's plainly visible that you showed up here to attack the project and try to promote something else.

I am in the linux community for decades now, and I don't believe anyone anything denying me root rights on my very own devices - explaining this by openly considering the owner of a device as too dumb to handle its security. And that's basically my critics on Graphene. In this respect, it is built in the same thinking as Apple IOS, and that is not compatible with me. Case closed.

You're promoting CalyxOS which doesn't give you root access either. You're also completely misrepresenting why the security model on AOSP / GrapheneOS works the way it does. It's not us derailing this thread. You showed up here to attack us, spread misinformation and misrepresent the views of the project. It's not clear why you're doing that. Now you're accusing us of doing what you showed up here to do.

Now, do you have any ideas how to help davidskeck ?

I responded above after countering the misinformation you're spreading here about our project.

It was you who hijacked this thread as part of ongoing attacks by your community on GrapheneOS across a bunch of platforms. It's plainly visible that you showed up here to attack the project and try to promote something else. > I am in the linux community for decades now, and I don't believe anyone anything denying me root rights on my very own devices - explaining this by openly considering the owner of a device as too dumb to handle its security. And that's basically my critics on Graphene. In this respect, it is built in the same thinking as Apple IOS, and that is not compatible with me. Case closed. You're promoting CalyxOS which doesn't give you root access either. You're also completely misrepresenting why the security model on AOSP / GrapheneOS works the way it does. It's not us derailing this thread. You showed up here to attack us, spread misinformation and misrepresent the views of the project. It's not clear why you're doing that. Now you're accusing us of doing what you showed up here to do. > Now, do you have any ideas how to help davidskeck ? I responded above after countering the misinformation you're spreading here about our project.

You created an account on this platform just to take the opportunity to attack GrapheneOS on an issue with a GrapheneOS user trying to get something resolved.

#9

Really no point of accusing me of hijacking the thread when it's plainly visible why you showed up here and what you were doing. I was directed here by a user with this problem and saw you taking the opportunity to attack us with misinformation. It's unfortunate that this isn't an isolated case but rather part of ongoing, escalating attacks from your community on GrapheneOS. At every opportunity, you folks are making dishonest claims about us, raiding our rooms, harassing our developers and trying to disrupt development and processes like this one. You showed up on an issue tracker to attack a project and misinform people. That's a problem, and there's going to be a substantial response to it. It's disgusting behavior. Can you please just stop spreading lies about GrapheneOS and leave us be?

You created an account on this platform just to take the opportunity to attack GrapheneOS on an issue with a GrapheneOS user trying to get something resolved. https://codeberg.org/nexttracks/android/issues/9#issuecomment-238935 Really no point of accusing me of hijacking the thread when it's plainly visible why you showed up here and what you were doing. I was directed here by a user with this problem and saw you taking the opportunity to attack us with misinformation. It's unfortunate that this isn't an isolated case but rather part of ongoing, escalating attacks from your community on GrapheneOS. At every opportunity, you folks are making dishonest claims about us, raiding our rooms, harassing our developers and trying to disrupt development and processes like this one. You showed up on an issue tracker to attack a project and misinform people. That's a problem, and there's going to be a substantial response to it. It's disgusting behavior. Can you please just stop spreading lies about GrapheneOS and leave us be?

PLEASE STOP AND GET BACK TO THE TOPIC!

I have the same issue as the thread opener:

  • LineageOS without Gapps

  • Running 16.0 (Android 9) on Tablets it works

  • Running 17.1 (Android 10) on Phone it works

  • Updated Phones to 18.1 (Android 11) and iI run into the same problems.

Even Easer starts Nextracks when I leave home (leaving home wifi) and stops (kill app) Nexttracks when coming home, it does not update also on App start.

The only way to get updates is changing the moving mode in forground.

It would be really helpful to find a workaround or fix here. Thank you very much for this cool peace of Software.

PLEASE STOP AND GET BACK TO THE TOPIC! I have the same issue as the thread opener: - LineageOS without Gapps - Running 16.0 (Android 9) on Tablets it works - Running 17.1 (Android 10) on Phone it works - Updated Phones to 18.1 (Android 11) and iI run into the same problems. Even Easer starts Nextracks when I leave home (leaving home wifi) and stops (kill app) Nexttracks when coming home, it does not update also on App start. The only way to get updates is changing the moving mode in forground. It would be really helpful to find a workaround or fix here. Thank you very much for this cool peace of Software.
Add: Maybe this is a follow up to this one? https://developer.android.com/about/versions/oreo/background-location-limits
Sign in to join this conversation.
No Label
No Milestone
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.