jlow comments on Google killed Maps Timeline, so I self-hosted a better one [OwnTracks]

Selfhosted

63,680 readers

5,234 active

545 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

moderators

[–] jlow@discuss.tchncs.de 13 points 1 year ago (2 children)

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.

permalink

fedilink

source

parent

hideshow 2 child comments

[–] Zagorath@aussie.zone 1 point 1 year ago (1 child)

the official app tries to not be killed by Android woth the usual tricks (permanent notification, disabling battery optimisation)

…

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?

permalink

fedilink

source

parent

hideshow 1 child comment

[–] jlow@discuss.tchncs.de 2 points 1 year ago

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).

permalink

fedilink

source

parent