No description
Find a file
2023-04-01 17:53:34 -07:00
app Add power management to readme. 2023-04-01 17:53:34 -07:00
assets mark start and end of a track with a pin icon (see #95) 2021-03-09 22:27:42 +01:00
gradle/wrapper Updated gradle to 7.2.1. 2023-03-04 21:43:52 -08:00
metadata font style changes & preparing a new release 2022-01-12 15:23:56 +01:00
.gitignore Kotlin Rewrite - everything is new 2020-01-02 18:00:37 +01:00
AUTHORS.md Remove CONTRIBUTE.md. 2023-03-26 13:30:32 -07:00
build.gradle Updated gradle to 7.2.1. 2023-03-04 21:43:52 -08:00
gradle.properties Kotlin Rewrite - everything is new 2020-01-02 18:00:37 +01:00
gradlew Update gradle wrapper 2020-07-31 19:50:37 -04:00
gradlew.bat Update gradle wrapper 2020-07-31 19:50:37 -04:00
ic_launcher.svg New app icon for this fork. 2023-03-26 19:33:43 -07:00
LICENSE.md updated copyright 2022-01-05 17:20:44 +01:00
README.md Add power management to readme. 2023-04-01 17:53:34 -07:00
settings.gradle initial commit 2016-08-29 14:50:41 +02:00
trkpt_squircle_128x128.png Add app icon to readme. 2023-03-30 22:04:58 -07:00

trkpt

This is a fork of Trackbook by y20k. Thank you y20k for this great project.

The goal of this fork is to make 24/7 recording easier. I want to be able to run trkpt nearly all of the time. I have written more about this at voussoir.net/writing/obsessed_with_gpx. The main differences between trkpt and Trackbook are:

  1. trkpt stores points in an SQLite database instead of json files.

    • You can put the database in a folder that you sync to your PC with Syncthing.

  2. trkpt does not store "tracks" as objects. Instead, tracks are rendered and exported on the fly by querying the database of trackpoints.

  3. trkpt adds the feature of "homepoints". When you are near a homepoint, trackpoints are not recorded. You can put a homepoint at your house or other places where you spend lots of time, so that you don't get large clouds of useless trackpoints at those locations.

    • Although Trackbook has a feature to omit points that are close together, natural GPS inaccuracy and drift is large enough to create points that are far apart, especially while indoors, leading to clouds over time. You can choose the radius of your homepoint to eliminate these clouds.

Power management

When you are near a homepoint, trkpt will slow down the GPS polling frequency to reduce power consumption. When trkpt detects movement from the device's accelerometers, or when the GPS detects you are away from the homepoint, it will wake back up to full power.

If the GPS is completely unable to receive a fix because you are indoors, underground, or trapped in a Faraday cage, trkpt will turn it off after a few minutes. Without any fix, we can't even tell if we're near a homepoint, and the GPS burns a lot of energy trying. Again, the motion sensor will wake it back up to full power.

When you are away from a homepoint, and the GPS is not struggling, trkpt will always run the GPS at full power.

If your device doesn't support the motion sensors used here, then trkpt will always run at full power. It will not sleep or kill the GPS. Maybe we can find another solution to improve battery performance for devices in this scenario.

Mirrors

https://github.com/voussoir/trkpt

https://gitlab.com/voussoir/trkpt

https://codeberg.org/voussoir/trkpt