ExplorInk
GitHub

the phone side · android and ios

The phone app: Android today, iOS planned

The Xteink readers have no GPS receiver, so the phone supplies the fix. That is the first job. The phone goes in a pocket, a tank bag or a pack, screen off, and the reader is the screen instead: on a handlebar, a pack strap, a dashboard, wherever it rides. The app does five things over one Bluetooth LE link: send the position, bring the map squares the reader is missing, record the ride, manage the reader's saved pins, and put a trip shared from Google Maps on the reader's card.

Your phone stops being the display

This is the point of the app, and it is worth saying plainly. A phone mounted where you can see it, a handlebar, a pack strap, a dashboard, is a screen that washes out in overhead sun, heats up in a dark mount, and drains the one battery you also need for photos and a phone call; on a motorcycle it also takes engine vibration all day. None of that changes because the map got better.

ExplorInk does not remove the phone. On the Xteink readers it needs it, for the GPS fix and for map data. It moves the phone off the mount. Screen off, in a pocket or a pack, one Bluetooth link open. What you look at is a reflective e-ink panel, readable in daylight.

Five jobs, one link

JobWhat the app does
Position writes 21 bytes (latitude, longitude, UTC, time-zone offset, heading, sequence, flags, accuracy, speed, altitude) to the reader when the fix has actually moved
Map squares answers the reader when it lists the tiles it does not have, and pushes them over the same link. How map sync works
Ride record writes every raw fix, every packet (failures included) and every link event to one JSON Lines file per recording
Pins reads, saves and deletes the reader's pins, from a coordinate pair, a DMS string, a geo: link or a share from a maps app
Trips takes a route shared out of Google Maps, works out the line along real roads, and puts it on the reader’s card as a trip it can draw

The reader can only pin where the rider is standing: no keyboard, no typed coordinates, no map picker. The phone adds the two things it cannot produce for itself, a place chosen from text and a real clock reading (the readers keep no reliable clock of their own today, so their own pins carry no time). Verified on real hardware, 2026-08-19: list, save, delete and distance all match the reader over the same command channel it already exposes over USB serial. Still unverified: a pin command arriving while a tile transfer is running, and the battery cost of the screen's once-a-second redraw.

A route you planned in Google Maps, drawn on the reader

Plan a trip in Google Maps with as many stops as you like, share it, and pick ExplorInk. The trip is on the reader’s card and drawn across the map, so you can see where it runs next to where you are. It stays a line on a paper map: no turn instructions, no recalculating, no voice. The reader still answers where you are and what is around you.

Two things the app says out loud rather than hiding. A shared link carries the stops and not the line, so the route drawn on the reader is worked out by a router and will not match Google Maps turn for turn. And every stop is listed with its coordinates before anything is sent, because a stop read wrong bends the whole trip and nothing further along can notice: the file is valid, its checksums match, the reader draws it. That list is the only check there is.

A share while the reader is asleep is the normal case, not an error. The trip waits on the phone and goes over the next time the map or the sync screen is open. On the reader it sits under Trips, where it can also be deleted. Verified end to end on 27 October 2026: a six-stop route shared from a phone, 346 points, on the card and ridden from the picker.

The send policy is deliberately lazy, because a packet the reader cannot use costs the phone's battery for nothing: at least 7 s between packets, a 50 m movement threshold, a slower 30 s cadence at walking speed, and one keep-alive an hour when nothing moves at all. The reader redraws in seconds, so sending at 1 Hz would only buy heat.

How the link is put together, and what it took to stop it wasting the phone’s battery.

It starts itself when you open the map

Once per phone you pair with one reader through Android’s own companion-device dialog. After that the operating system watches for that reader. Open the map screen on the reader, wherever it is mounted, and the OS wakes the app: app swiped away, phone locked, nothing tapped, and the bridge starts.

Verified end to end on real hardware, and again after a phone restart, which is the case that usually breaks this kind of thing. One thing it cannot survive: a force-stop from Android’s app settings. Nothing can.

Pairing pins one address, too. Every reader of the same model advertises the same name and the same service, so an unpaired app talks to whichever answers first, and in a car park with two of them, the loser gets a stranger’s position on the map.

What it spends, and when

One switch decides everything: is the reader connected, or is a recording running? If yes, GPS updates, the wake lock and the send timer go up together. If no, all three go down together, and the service stops itself after five minutes with no link. Scanning drops to low power after the first 20 s.

Those rules are read off the code, not off a battery bench. A measured drain figure for a full ride is still missing, and it is written down as missing rather than estimated.

No account, no cloud, and the data stays yours

  • No login, no account, no sync service. The app talks to one reader and to the tile server.
  • A tile transfer is always started on the reader, never by the phone. It is your mobile data, so you say when.
  • The check for out-of-date map squares is off by default for the same reason.
  • Recordings are files on your phone. Nothing is uploaded.

iOS

iOS is planned. It is not started, and there is no date on this page because an invented one would be worth less than the honesty.

What is already settled is the part that usually blocks a second platform: the reader side is not Android-specific. The link is one plain Bluetooth LE GATT service with published UUIDs and a fixed 21-byte position packet, with no pairing, no bonding and no vendor SDK. An iOS client is app work. It needs no firmware change, and the protocol it has to speak is documented on this site.

One part does not port: the auto-start. Waking the app when the reader appears uses Android’s companion-device association, and iOS has no equivalent of that mechanism, so the “open the map and it just starts” behaviour has to be designed again rather than translated. Expect the first iOS build to be a manual start.

Installing it today

The Android app is on Google Play since 13 November 2026: Android 12 or newer, free, and the source is public. It installs and updates like any other app. The firmware side installs from the browser, through the flasher.

Get it on Google Play
QR code opening the ExplorInk GPS page on Google Play
Scan with the phone

One break worth knowing. Every build before this one was signed with the shared Android debug key, and Android refuses an update across a different signing key, so a phone carrying an older sideloaded APK has to uninstall it before the Play version will install. Install ExplorInk on your own reader has the detail, together with the firmware images, the flashing commands and the list of what is still untested.

The Android app source is the app's own repository, and its releases carry the APK. The firmware lives in the ExplorInk repository.

What works today, dated, with the measurement behind each line.