282
Google killed Maps Timeline, so I self-hosted a better one [OwnTracks]
(www.androidauthority.com)
this post was submitted on 22 Jun 2025
282 points (100.0% liked)
Selfhosted
46677 readers
442 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It (theoretically) works without PlayServices. I'm on CalyxOS with MicroG enabled and while I was testing OwnTracks I think MicroG was using the Gplay Location services or something? I've since turned something off in MicroG location settings that was phoning home to Google and GPS is pretty bad now, not sure if OwnTracks would still be usable.
I think the official app tries to not be killed by Android woth the usual tricks (permanent notification, disabling battery optimisation):
https://f-droid.org/packages/org.owntracks.android
You can (theoretically) control how often locations are tracked and sent but for me was using the location service constantly and draining battery quite a bit.
…
Ah. Those are exactly what I was worried about. It's not able to just happen entirely in the background the same way Google's feature does, then? Kind of automagically?
Mmmh, I don't think the app ever got disabled by Android during my days of testing (I actually reinstalled yesterday and having a look again, battery drain seems a bit better now so far ... ). But obviously a system service is always gonna be prioritised higher than a user app. But as I said I didn't have this problem with this app (actually the only one I can think of is Syncthing and with that I'm not sure if it's not the app going to a sleep mode or something by itself).