I tried both the OwnTracks server and Dawarich, and had problems using them with my reverse proxy (Caddy), which I didn’t manage to fix. Eventually, I installed the Nextcloud app Phonetrack, and I’ve been using it for months with the OwnTracks client: it works fine, it can also export GPX files, which I can use to tag pictures shot with my camera, using Darktable. I recommend this solution if you are already using Nextcloud!
There is also
But I could never get it to ingest any data from the recc Android apps (this is probably a me problem, though, Linux Unplugged crew are using it).
Misleading as fuck. The Timeline feature never went away - it’s just device-only.
There’s a good chunk of us who used it with the web, and they’re adding that to the vast Google graveyard. That in and of itself makes me excited to see an alternative because Google will kill the app version on a whim too.
The device only was for privacy. When the data was stored in the cloud, the government had unrestricted access. By making it device only they need to get your device to get that data.
Privacy? I’m sure that Google tried so hard to monetize it and after so many years they didn’t found a way, couldn’t use it for ai training too, so they decided to turn it off and save millions in database costs.
They still exfiltrate user movements for improving Google maps, it’s just that they don’t need to keep them indefinitely or for years or maintain a nice interface for that
Yes, that’s correct, Google didn’t do it out of the goodness of their non-existent heart, they made what they think is the best financial decision.
It’s a good one for the consumer though, whether see that or not. It’s good that your every move ever taken is stored in a company’s database.
Don’t worry, they most certainly used it to train a decent model of any typical American demographics movements before scrubbing it.
Lol. The only thing this setting does is hide the information from the user. Google, or a thousand other data brokers (many probably created by Google for this purpose) still retain that data indefinitely.
It never went away. It’s still a feature. It’s just stored locally on your device. Thats it.
Yes, technically it’s still on the tiny screen of your phone with a really bad ux to make it go, sure. But you see how ‘went away’ is both true for web and effectively true for phone app? You do see that, right?
Yeah, super hard to find…
Thanks for clarifying, I was worried for a second.
What does device-only mean in this context? That it’s only stored on your phone?
Because of various privacy legislation, and people not wanting Google to track them as much, they stopped syncing the data to Google servers. As someone who’s worked at big tech companies, my guess would be that storing so many people’s location history was flagged as an issue during a privacy audit.
It’s entirely local now. You can enable encrypted backups and back up the data, however you can really only have the data on one device now, and the web version is gone.
It’s no longer accessible from a desktop, only from the Google Maps app.
What else could that possibly mean?
I tried setting up own tracks like a year ago and it sucked HARD.
Has the computer setup potion become any easier?
How exactly does it work from your phone’s perspective? Does it hook into Google Play Services location data? Do you need to install a different low-level application that replicates that functionality? (If so, what’s the battery life impact like?) Does it need a foregrounded app?
I’m really interested in this, because like the author I’m really upset at Google killing yet another incredibly useful feature. But the article is a little light on details.
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.
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?
The article said there’s a phone companion app
But not exactly how the app works. If it’s a Strava-like app you have to remember to run in the foreground, the value is a lot lower to me than something that either uses or replicates GPS’ automatic background behaviour.
