ckrey
commented
4 months ago You are right, if you swipe out the iOS app it does not report anything anymore. On the other hand, there is no memory or performance penalty if you don't swipe out apps in iOS. Just start the app and then return to the menu screen. OwnTracks will then e.g. report your movements in "Significant Mode". If you want to have more timely enter/exit events, we recommend setting Regions for home, gym, school, etc. Region monitoring works very well in iOS Background ... as long as you don't kill the app by swiping it out
rbrinson
jpmens
This is more of a question. Sorry for the length, but I wanted to ensure that the use case was properly understood.
What I'm Trying to Achieve: In my family, there are 3 devices, 2 run Android (Google Pixel 7 Pro and One Plus 8T) and 1 runs the latest iOS on an iPhone 15. We have used Life360, which does provide the family tracking functionality that I am hoping to replicate. The problem that I have with Life360 is that I am handing my location data over to a third party and trusting them not to sell it or otherwise give it out to others. I consider it a matter of privacy. However, Life360 have done precisely that.
Steps Followed: So, I setup the OwnTracks Recorder in a Docker container with Nginx Proxy Manger in front of it to provide basic auth to the HTTP front-end. I used this tutorial as a guide for setting things up. After installing the Android and iOS apps on the devices and configuring them to point to my recorder instance with their basic auth credentials, I was able to map each device as a friend in the friends table, and we can all see each other in the client apps map.
The Problem: The problem that I am having is getting tracking data equivalent to Life360. I have read the Location section of the OwnTracks booklet, and from that I have gleaned that on Android, I just need to play with the "Minimal location displacement" and "Location interval" under Preferences | Advanced to fine tune the "Significant Changes" mode such that enough movement reports are generated to make the data relevant for my wife to see that I am at the gym or for me to see that she is still at the store. I also tried "Move" mode, which did produce a lot of data points, but I could see how that would have a negative impact on the battery.
My daughter has the iPhone 15, and iOS just doesn't want to actively report in to the OwnTracks recorder. I have tried both "Significant Changes" and "Move" modes. Yesterday, she traveled about 22 miles away. While she was away, I checked the recorder to see if any data points were being logged, and I noticed that there weren't any. When she got home, I opened the iOS OwnTracks app. When I then checked for data points, I found that about 5 dots appeared on the map showing the route taken. However, these only appeared after opening the app. I tried changing the mode to "Move" and updated the locatorDisplacement and locatorInterval to lower values. On Android, this caused many data points to be generated. However, on iOS, I haven't seen even one data point since that change.
I did note some mentions of having the app running in the background and "swiping" of the app discouraged. Does this mean that the iOS OwnTracks app must always be in the foreground to report properly? Does it mean that the iOS app can be an app in the background, but you cannot "swipe" it out? Either of these scenarios is not the way Life360 operated, and it's not even how the Android OwnTracks app operates. On Android, the OwnTracks app seems to have a background service running in the selected Location Mode even if the app is not in the foreground or even in the background carousel. Does anyone know of settings for Android and iOS OwnTracks that replicates Life360's movement tracking? Thanks for any insight!