Nothing changes anywhere
Start with the boring checks, because they cause most failures. Open LSPosed and confirm GPS Setter is switched on, not merely installed on the phone.
Confirm System Framework is ticked in the module scope. Without that entry there is no system hook, and the map inside GPS Setter is the only thing that ever moves.
Reboot after any scope change. Hooks load when processes start, and a running system will keep using its old, unhooked behaviour until it restarts properly.
One app still shows the real location
That app is probably asking Google Play services for its location, not Android directly. On the Full build, add Play services to the scope, then force-stop and reopen the target app.
On the FOSS build the same logic applies to microG. Add the microG package to scope when the target depends on it, and retest with a fresh app start.
Also confirm the app itself is in scope for per-app mode. Selecting it inside GPS Setter's own settings is not enough on its own; the manager scope is the authority.
Tip: Work through this guide in order the first time. Most GPS Setter problems come from one skipped step early on, not from the step where the problem appears.
The real location flashes before the fake one
Older builds spoofed live fixes but left the cached last location alone. An app opening a map could briefly show the real position before the set one arrived.
Current releases fix this by spoofing the cached location and the fix handed over when a listener registers. Update your fork from its LSPosed listing and the flash should disappear.
If it persists, restart the target app after applying the location. A listener registered before you applied the change can hold stale data until the app restarts.
Spoofing stops by itself, or an app crashes
Stops that happen overnight usually trace to battery optimisation. Exclude GPS Setter from battery saving so its foreground service survives the night and the screen-off hours.
Crashes after scoping one app point the other way. Strong anti-tamper protection can reject hooked processes, so remove that app from scope and use the system-wide hook for it instead.
Never run two location modules together while diagnosing. Disable every other spoofer, reboot once, and test GPS Setter alone. Conflicting hooks produce symptoms that look like bugs but are not.
Download: GPS Setter itself is free from its LSPosed listing. Go to the download section for the file information and the external download button.
Related guides
How to Install GPS Setter with LSPosed: Step-by-Step
From APK to a working set location: enabling the module, choosing scope, and the reboot most people skip.
GPS Setter Full vs FOSS: Which Build Should You Download?
Same module, different foundations. A clear comparison of maps, location providers, and which phones each build suits.