gpslogger VS OwnTracks Recorder

For location history I use https://gpslogger.app. It's open-source, can be found on F-Droid and has many settings.

I realize tracking takes some battery life. But I already run two GPS trackers on my phone (Google Maps tracks location, also I have GPSLogger. They both use a very small amount of battery. Eufy is using a lot more.

Or you could use a more efficient GPS logging app. eg GPS Logger. https://gpslogger.app/ It has settings you can adjust to save power, eg reduce the frequency of recording points. Then you can export a GPX file afterwards to upload to Strava.

GPSLogger (version 127): A lightweight GPS logger, battery efficient, GPX/KML, add notes, share, upload.

Haven't used strava or komoot and my answer probably is too late, sorry. But I personally used "GPSLogger for Android" on longer trips. Works pretty well, you have several options to tweak the performance and therefore your battery life.

I like GPSLogger for Android to log the trip to GPX https://gpslogger.app/ but haven't found anything I like to save it visually

My method, FWIW, is to attach a small Bluetooth device to the bike (I have a speaker, but anything you can power on or off works). I have an Android phone with Tasker and GPSLogger, and I have a Tasker profile which starts logging when it connects to the specific Bluetooth device, and stops logging when it disconnect. It's a bit of a janky setup but it does record my rides pretty consistently without having to actually handle my phone.

Some people have issues installing Own Track's Recorder - This one is very minimal and saves your locations to an sqlite file.

I also use OwnTracks on my phone and installed OwnTracks Recorder on my server. I skimmed over my blog post for that but I don't think there's much useful for you there.

I've looked at OwnTracks, Orion, and Hauk.

As far as I know, owntracks doesn't actually store location history, it only defines a protocol for exchanging current location info between programs. If you're using their "official" recording server, writing a script to import history looks super easy [1].

[0] https://github.com/owntracks/recorder/blob/master/doc/STORE....

After setting up the client side, a server-side component to receive the OwnTracks app's requests is still missing. OwnTracks ships with its Recorder, which is a small and simple web application written in C. However, I did not like it a lot, as it does not look particularly beautiful and is very limited regarding its functionality. I rather wanted to visualize my data in Grafana. But to get it there, it first needs to be persisted to a database.