v1.1

Fixed two text messages being sent instead of one when sharing starts.
Messages now report what really happened: sent, waiting or failed, with the reason.
A message held back for lack of signal is retried on its own.
New update check, optional and off by default.
With no destination set, messages no longer leave a gap.

First public release

First public release

Works without Google Play Services: location comes from the AOSP LocationManager, maps from MapLibre, retries from WorkManager. It installs on any device, including ones with no Google apps at all.

Installing

The APK is on the Releases page. Download it and open it:
Android will walk you through three things worth explaining, because none of
them means anything is wrong.

"Unknown developer"

Play Protect shows a warning for any app that did not come from the Play
Store. Tap More details and then Install anyway. Before that, the
browser or file manager may ask you to allow installation from this source:
that is the app you downloaded with, not this one.

The warning is not about the app being unsafe. It only means Google has not
scanned it, which is true of everything distributed outside its store. If you
want to check the APK really came from the person who published it, compare
its certificate fingerprint with the one in the release notes.

The SMS permission cannot be turned on

If you use the SMS channel, Android may refuse the permission and show a
shield saying access was denied. This is a protection applied to apps
installed straight from an APK file, and it blocks exactly the permissions
malware abuses most.

To unblock it:

1. Settings → Apps → I am here
2. The ⋮ menu at the top right
3. The entry about restricted settings, and confirm with PIN or fingerprint

The permission can then be granted normally, from the app's Diagnostics screen
or from Permissions.

This depends on how the app was installed, not on who signed it: installing
from F-Droid, Obtainium or adb install never triggers it.

Battery

Settings → Apps → I am here → Battery must have Allow background usage
switched on. That is the setting that matters: with it off, the system treats
the app as restricted and can kill the service mid-journey.

Seeing the app listed as Optimised is normal and not a problem. A foreground
service with a persistent notification keeps running regardless. Turning
optimisation fully off is an improvement rather than a requirement: it helps
on long stops with the screen off and when resuming after a reboot. Tap the
row itself, not the switch, to reach the Unrestricted option.

The Diagnostics screen inside the app shows all of this at a glance. Red
rows stop sharing from working; amber rows only make it sturdier.