A jumping location can come from an ended FlashGo session, battery policy, route completion or the way the receiving app combines location sources.
Use responsiblyFlashGo includes developer testing among its stated uses. Receiving apps can detect or reject mocked locations; follow applicable laws and third-party terms.
Find the moment it resets
- Does it happen when the screen turns off? Check background limits.
- Does it happen when the route reaches its end? Start a longer route and compare.
- Does only one target app jump? Inspect that app’s cache and mock-location handling.
- Does FlashGo still show an active location session? Restart it if needed.
Stabilize the test
Allow FlashGo to run in the background for the duration of the controlled test, keep the device charged and use a short route. Record the exact time, app state and route position when the reset occurs.
Avoid false conclusions
Wi‑Fi, Bluetooth, IP and account signals can disagree with the mocked GPS position. A map marker that moves does not prove every subsystem accepted the same location.
Common questions
Why does the location return when the screen locks?
The device may be limiting background work. Review the manufacturer battery settings and confirm FlashGo remains active.
Can route settings prevent every reset?
No. Route settings cannot override receiving-app policy or device process limits.