Friday, Jun 04, 2021 at 14:38
Hi Michelle,
Apologies for the length of this reply.
Thanks for the clarification. I am definitely talking about the tracking feature. Not the snail trails, which I don’t use. I have been using the tracking successfully since I subscribed as a member. Apart from the startup issue, the tracking has been working perfectly and has recorded our recent trip around Australia, 12,000km over 30 days. Once the tracking app was running, all positions were synced to the server each day. There was usually a bit of a catch up in the sync process once we got back into reception range. It was rare that we had reception all day to allow real time syncing. The tracking was running for about 30 days with no issues, apart from the fact that I had to remember to start the app each morning before we set off for the day.
To clarify, ‘Stop on close’ is set to off and start on boot is set to on. The iPhone 7 I am using for the tracking is mounted permanently in my vehicle and plugged into power. At the end of each day, I turned off the power to the phone and shut it down. The Tracker app was running in the background when I turned off the phone, as was the Traveller app and the Tomtom Go app that I use.
The tracking in the Tracker app was set to ‘On’ on the ‘
Home’ screen, and tracking on the Traveller app was set to ‘Off’. Both apps were running all the time, but only the Tracker app had tracking enabled and was running in the background. Depending on where we were, either the Tomtom Go app or the Traveller app was running in the foreground.
While we were away, I noticed on day one, that no positions would be saved to the phone or synced to the server, unless I physically opened the app when I turned on the phone. If I turned on the phone and forgot to click on the Tracker app, like I did the first couple of days, I would end up with a straight line between where we stopped over night, and where I remembered to click on the app. Once I did click on the app, a message would be displayed telling me ‘Track logging started’. This message was only displayed the first time I clicked on the app after turning on the phone.
Once I discovered this, I use to
check if tracking had started and that my positions were being saved/recorded correctly each morning after driving a short distance from our overnight stop. This was checked on the server tracking map. This was also checked several times during the day with no issues. The tracking was always up to date and continuous. No straight lines between stops.
Once I realised there were issues if I turned off the phone, if we stopped moving during the day, I alway left the phone turned on, with the app running in the background, plugged into our second battery. (Screen locked). Once I started moving again, tracking would recommence and positions would be recorded correctly, no straight lines. I did not need to click on the app to restart tracking if the phone had been left turned on.
I didn’t want to play around too much with the settings while we were away, as I didn’t want to jeopardize the tracking not working. I just made it a point to click on the app each morning, (Sometimes I forgot).
Since returning from the trip, I have tried closing the Tracker app to see if the problem only related to the app restarting when the phone was powered on, when it was left running in the background. This made no difference. Once the app is closed, or the phone is turned off, no positions are recorded / saved to the phone and none are synced to the server, once the app is opened again.
I have tried driving around for several days with the app running in the background, ie, not clicking on it when I turn on the phone. No positions are saved to the phone and none are synced to the server. If I attempt to create a track log for the period, it tells me there are no positions in the date range.
I have also tried closing the Tracker app, with the same settings, and driving around for 2 days. When I opened the app at the end of two days, there were no positions saved to the phone and none were synced to the server. If I attempt to create a track log for the period, it tells me there are no positions in the date range.
If I click on the Tracker app after turning on the phone, positions are saved to the phone and synced to the server. If I am in reception range, this occurs correctly in real time, if I am not, the positions are synced correctly once I am in reception range. I am able to create a track log for this period.
It was my understanding that if the Tracker app had the following settings, ‘Stop on close’ is set to ‘Off’ and ‘Start on boot’ is set to ‘On’, once the phone was powered on, positions would be saved to the phone, without further intervention, irrespective of whether the app was closed or running in the background, and they would be synced to the server once the app was running and in mobile service range.
The only time positions would not be saved/recorded, is during the period the phone was actually powered off, hence the importance of turning the phone on at the same location where you turned it off, to ensure a continuous timeline/track with out straight lines between stop and start positions.
Currently, the only way to have positions saved and synced is to physically open the tracker app, after the phone has been turned on. Once you do this, it works correctly until you turn off the phone, irrespective of whether you are moving continuously or if you stop and start moving again. (To me, this indicates that the motion sensors are working correctly and the app is using them correctly, once you physically open the app.)
As I have only been using the apps on the iPhone since iOS 14.5, I can not tell you if it worked differently with earlier versions. I am currently running iOS 14.6
I have also tested this on my iPhone 12, same iOS version, and it behaves exactly the same. Happy to give you a phone call if it would make it easier to discuss, rather than a long discussion that may or may not be of interest to other members.
It would be interesting to know if anyone has the tracker app running on an iPhone using the latest iOS version and is not having this issue.
Appreciate your help Michelle.
FollowupID:
914646