[aasasd]

Just so you know, if you're using regular Google-infused Android, then depending on how you ‘kill’ Maps it may still be running in the background. And it may start in the background without you running the app.

I'd also bet that Google's other apps transmit your location anyway―if only because other apps use it too―and that it's not necessarily reflected in the timeline in the web profile.

[behnamoh]

> And it may start in the background without you running the app.

Are you sure about this? If an app is terminated, can it still run itself without you running it?

[dannyw]

Google Play Services is the underlying app the records and uploads your location to Google Timeline, and that restarts itself if it is force quit.

[aasasd]

I have a different maps app (Yandex) that keeps popping up in the process list despite me killing it off with ‘force stop.’ Probably not the only one, for that matter.

Flicking an app in the recent apps list doesn't close its background processes. And you won't see it there when such a process runs again. See e.g. the ‘OS Monitor’ app for the actual list of processes (for Android ≤6).

Google's apps are likely even more privileged. Play Store hogs the processor and network every time I enable wifi. On a past phone, Google Maps also ran conspicuously on boot and, iirc, when wifi was turned on.

Something might've changed in newer versions of Android, dunno. But I doubt it that Google would limit its own abilities.

[sbuk]

No.