Navigation and GPS
Why did navigation stop?
Short answer
Most often Android's battery optimisation has restricted Walkable while the screen was off. It can also simply be that you reached the end of the route, or that a reroute needed data in an area with no offline map and no signal.
Updated · 3 min read
Battery optimisation is the usual culprit
Android aggressively limits apps it thinks are idle. Walkable runs a foreground service with a notification precisely so the system knows a walk is in progress — but some manufacturers apply their own, harsher rules on top.
Excluding Walkable from battery optimisation, and from any manufacturer-specific 'app sleep' list, is what fixes this for good.
The less alarming reasons
You arrived. Guidance stops when the route is complete; recording continues until you finish the walk.
A reroute could not be calculated because there was no map data for the area and no connection. Recording carries on regardless.
Common problems
Directions stop whenever the screen locks
Exclude Walkable from battery optimisation and from any manufacturer app-sleep or 'protected apps' list.
The notification disappeared mid-walk
The system stopped the foreground service — the same battery restriction. The recording up to that point is kept.
Related guides
- My battery is draining quicklyGPS and the screen are the cost. Pocket the phone and let guidance speak.
- Notifications are not appearingCheck the notification permission, and allow exact alarms for timed reminders.
- My walk was not savedUsually the walk was never finished, or the system stopped the app mid-walk.
Was this helpful?
Nothing is sent or recorded — this only changes what you see next.
Feedback about the guide: Why did navigation stop?Still stuck? Contact Walkable Support or ask the Community.