gpslogger VS fdroiddata

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.

Fork this repository.

For reference my app: project: https://github.com/balzack/databag merge request: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12183

You should add a new entry in "Builds". Have a look at how Newpipe does it for each new version here for example.

To me it's not very clear whether those terms practically apply only to their app, since clearly they can't grab logs from Aurora if Aurora doesn't dump those logs for example... but if this is something the F-Droid team should look into, open an issue on https://gitlab.com/fdroid/fdroiddata/-/issues or inquire in one of their official channels on OFTC (#fdroid) or Matrix (#fdroid:f-droid.org).

OsmAnd~ from F-Droid not having Android Auto is a known bug: see the discussions at https://gitlab.com/fdroid/fdroiddata/-/issues/2567 , https://github.com/osmandapp/OsmAnd/issues/13514, https://github.com/osmandapp/OsmAnd/issues/3391 and https://github.com/osmandapp/OsmAnd/issues/15400

You can also get F-Droid Build Status which I believe will let you see apps that are being attempted to be built even if their build isn't succeeding yet, again for the "catching things early experience". Or, just keep an eye on the issues, merge requests and commits at fdroiddata which is where people actually add new metadata for new apps to be built by F-Droid, and it often takes a while between an app being first mentioned, and it being able to be included, for many possible reasons.