domingo, 2 de agosto de 2026

Long Walk, Active Sensors, and a Lost GPX

I went on my usual walk—one of those I always do to keep up my pace—but this time my main app failed me: Samsung Health. It’s the platform I’ve been using for a long time; in fact, it was the first one I started with to record my routes. Over time, and so as not to depend on a single tool, I added three more apps as a backup and for testing purposes. These other three are free, just like Samsung Health, though they come with one detail: they load you up with ads. When you have mobile data enabled, that constant advertising gets a bit cumbersome, but setting that inconvenience aside, they work perfectly well and without charging a single penny, so I got used to running them in parallel.

On this particular outing, I activated all four—or at least I thought I had. For some reason I don’t know, Samsung Health didn't take the command. It could have been an internal system glitch or perhaps my own rush: maybe I closed the screen or exited the app before the first three seconds of the countdown needed to start tracking the GPS route finished. Be that as it may, for that app's log, it was a loss, because it wasn't a short lap: it was 8.80 km of steady-pace training within a total activity of nearly 14 km.

When the map of an outing like that gets lost, it's pretty annoying. In this particular case, it wasn't a big deal because I was able to make up for it with the other three apps; as long as just one of them saves your track, your geographic record is already safe. The real problem appears when you rely on a single app and this glitch happens to you, or when you trust passive tracking.

This is where the paradox of automatic mode comes in: Samsung Health detects your walk without you pressing any buttons. It records absolutely everything with impeccable precision: elapsed time, calories burned, step count, final duration, average pace, elevation gain, and it even builds a detailed intensity chart for you. It gives you the complete report, but it leaves out what is fundamental for anyone who analyzes or shares their routes: the drawing of the route on the map.

Starting from that deliberate omission—why does it map everything yet not draw the map?—I started reflecting on what the underlying reasons might be.

The first hypothesis that crosses anyone's mind is a matter of privacy. But as soon as you scratch the surface, that excuse falls apart under its own weight. Nobody in their right mind can seriously believe they retain any kind of privacy by carrying a smartphone in their pocket. We are heavily monitored. In the event of any investigation or illicit act, the first thing that gets seized and examined is the cell phone, from which a meticulous history of movements and communications is extracted. Privacy immediately takes a back seat to the tracking capabilities of modern technology.

Furthermore, the very data the app gives you automatically proves that tracking existed. To calculate speed, pace, and elevation, the phone's internal sensors were working continuously. Cell towers know exactly where a person is moving through the process of signal triangulation, detecting location in real time.

When you buy a phone and accept the terms of use, data surrender is already implicit. The smartphone is not an isolated device, but an extension of the person themselves. There is a whole chain of actors accessing that information: telephone companies, hardware manufacturers, operating system developers, and third-party apps that demand we sign privacy permissions in order to be installed. We all know data is collected and processed.

So the central question imposes itself: if the route is recorded internally on some server or in the phone's memory—somewhere we can't see—why doesn't the app give you the open option to access it? It would be as simple as offering a selector: "We detected your automatic walk and saved the map; if you want it, download it; if not, discard it."

The argument that automatic tracking captures unwanted movements inside the house doesn't hold up either. The phone's algorithm knows how to perfectly distinguish when there is continuous walking on the street and when it's two or three household steps that immediately stop. There is no risk of mapping the intimacy of the home.


For those of us who like to document our routes, analyze topography, or upload tracks to community platforms like Wikiloc, having the file in GPX format is indispensable. I know there is a theoretical and quite convoluted way to try to recover that data: it consists of linking Samsung Health with Google Fit, resorting to tools like Google Takeout to extract location history or root folders, filtering the data, building a text file (.txt) with the coordinates, and manually rearranging them to finally convert it into a .gpx file.

However, that level of homemade engineering and digital literacy goes beyond what a user looks for in their daily routine. It requires disproportionate effort for what should be a native app feature. It's an exhausting and technical hassle that few people feel like subjecting themselves to, when the logical thing would be to press an "export GPX" button.

Even if the automatic mode trace included the exact initial stretch where you walk out your front door, it wouldn't be an insurmountable problem either. Any user can trim or edit the ends of a GPX file using simple editors before publishing it. Obviously there will be people who don't know how to do it or who don't need the map at all, but for those of us who do make use of that data to record our workouts, the option should be available.

Ultimately, this walk remained cut short in Samsung Health's history. I was left with the screenshots, performance charts, and numerical exercise data, but not that app's .gpx file to upload the route. Even so, it wasn't a lost trip: the system glitch ended up serving as a good trigger to put these reflections on paper about the control of our own data and the design of the tools we use every day.


No hay comentarios.:

Publicar un comentario