Migration from Google Maps: All-time tracking (Google Timeline)

[Massimo-B]

Derived from the main discussion Migration from Google Maps #21747...

How to track device all the time

I started evaluating the Trip Recording plugin. It has far more options compared to Google Timeline concerning the count and accuracy of taken positions. Good. On Google Timeline it was unclear how often the measurements were taken. Sometimes the track was incomplete when the device was idle.

One question is, how energy-intensive that is compared to Google Timeline which was running all the time in the background. Does the Osmand version from F-Droid use a different location service than the Google Play version? If Osmand from Play is using the same Google Location service, does it take more energy? At least it's possible to reduce the count of measurements to adapt it.

I enabled the automatic trip recording when navigating. But anywway having the recording running all the time it could get canceled and needs to be restartet. If all-time recording is a feature it should be implemented as system service or might get some way to get restarted when killed. I already disabled all powersaving and enabled Autostart on the Osmand App.

The all-time recording into files and segments is not optimal. I enabled automatic splitting into segments after 2hours break. But actually it should better split files after 1 day. I also enabled to storage into monthly subdirectories.
I found the GPX files in /storage/emulated/0/Android/data/net.osmand.plus/files/tracks/rec
Distributing these files into a private cloud can be easily done by FolderSync. I don't see any advantage on using the Online-tracking to some URL, especially when navigating in areas with bad network.