Why PGSharp Teleport Stops Working After an Update

Every time Niantic ships a Pokémon GO client update, PGSharp has to catch up with a new build to match the underlying game code. Location errors can involve the current PGSharp build, Pokémon GO updates, or Android location configuration, and there’s rarely one single cause. If you updated Pokémon GO from the Play Store manually, or your phone auto-updated PGSharp isn’t ready for yet, teleport can silently stop registering even though the app opens fine. The current PGSharp release as of this guide is version 1.270.2, requiring Android 9.0 or above, so if your build is older than that you’re already behind. Check the version number in PGSharp’s settings menu against whatever pgsharp.com lists as current before doing anything else.

First Check: Is Mock Location Actually Set?

This sounds basic but it’s the single most common cause of PGSharp teleport not working, especially right after a system update wipes developer settings. Go to Settings > System > Developer Options > Select Mock Location App, and confirm PGSharp is still selected. Android resets this setting after some OS updates and after certain security patches, so a teleport that worked yesterday can just stop today with zero error message. If Developer Options itself has vanished, tap the build number in About Phone seven times to bring it back, then reselect PGSharp as the mock location provider and restart the app completely, not just minimise it.

Toggle High Accuracy Location Mode

PGSharp’s teleport function depends on Android’s location stack reporting consistently, and GPS-only mode can conflict with a mocked location, causing the joystick or teleport to freeze or jump back to your real coordinates. Switch to Settings > Location > Mode > High Accuracy (sometimes labelled ‘Improve Location Accuracy’ on newer Android skins), which forces the phone to blend GPS, Wi-Fi, and network data rather than relying on raw GPS alone. On some Samsung and Xiaomi builds this setting hides inside a battery optimisation submenu, so search your settings app directly for ‘location mode’ if you can’t find it in the obvious place.

Clear PGSharp’s Cache Before You Reinstall Anything

A corrupted cache is a quieter cause of teleport failure than most people assume, and it’s the fix that gets skipped because reinstalling feels more thorough. Go to Settings > Apps > PGSharp > Storage & Cache, then clear both cache and data. This resets PGSharp’s local session without touching your Pokémon GO account, and it fixes a surprising number of ‘teleport button does nothing’ reports. Only move to a full reinstall if clearing cache and data doesn’t help, since a reinstall means re-entering license keys and re-linking your account.

Update PGSharp From the Official Source Only

If PGSharp is more than one or two point-releases behind, teleport and joystick features are the first things to break because they touch the game’s location handling directly. Open PGSharp, and if an update banner appears, install it immediately rather than dismissing it. If no prompt shows, download the current build straight from PGSharp’s own site rather than a mirror or forum link, since outdated third-party APKs are a common reason people report broken teleport that a five-minute update would have fixed. Never sideload from a random Discord or Reddit link, both for security and because those builds are often several versions stale.

Root-Specific Causes: Magisk Modules and Zygisk

On a rooted phone, PGSharp teleport not working has an extra layer of possible causes that non-rooted users never see. Magisk modules that hide root status from Pokémon GO (commonly via Zygisk or a DenyList configuration) can reset their allow-list after a reboot, which means the game suddenly detects root, throws a location error, or silently blocks the mock location signal. Check Magisk > Settings > Zygisk and confirm PGSharp and Pokémon GO are still correctly listed in the DenyList/hide list after any reboot or Magisk update. This is the exact reason our PGSharp Root vs No Root comparison flags rooted setups as more powerful but higher-maintenance than the standard install.

Using the Rooted PGSharp Launcher? Check This First

The rooted Launcher build of PGSharp handles location spoofing at a lower system level than the standard APK, which is why it’s generally considered more stable against detection, but it also means teleport failures behave differently. If teleport works in the standard app but not through the Launcher, the module itself may need reinstalling after a Magisk core update, since Launcher-based spoofing hooks tie directly into root permissions rather than Android’s mock-location API alone. Walk back through the full install order in our PGSharp Launcher setup guide if teleport stopped working right after a phone-wide root update, since a missed step there is a common cause.

Error 11 and Error 12: What They Actually Mean

If teleport throws a specific error code rather than just failing silently, it narrows things down fast. Error 11 (location not found) almost always traces back to mock location being disabled or set to the wrong app, so recheck Developer Options first. Error 12 (unable to locate/failed to detect location) usually points to a weak GPS lock or a genuine location error involving Android’s location configuration rather than PGSharp itself. Moving near a window, toggling airplane mode on and off to force a GPS refresh, or switching from GPS-only to High Accuracy mode clears most Error 12 cases without needing to touch PGSharp’s settings at all.

Teleport Works But Pokémon Run Away: That’s Not a Bug

This gets reported as ‘PGSharp teleport not working’ constantly but it’s a completely different issue: a cooldown soft ban. After a long-distance teleport, Pokémon GO enforces a real-world travel speed check, and if you jump too far too fast the game penalises catch rates for a period. Your auto-catch will still throw the ball, but Auto Catch might throw a ball, but every Pokémon will flee instantly, and this is a soft ban due to cooldown, requiring you to wait up to two hours before the auto-catcher will successfully catch Pokémon again. PGSharp’s built-in cooldown timer tells you exactly how long is left, use it instead of guessing.

Conflicting Apps: The Silent Teleport Killer

Running any other fake-GPS app, VPN with a location-masking feature, or a second spoofing tool alongside PGSharp is one of the most overlooked causes of teleport failure. Android only allows one active mock location provider at a time, so if a leftover fake GPS app is still installed and was previously selected, PGSharp’s teleport can silently fail even with the correct app now selected in Developer Options. Uninstall any old location spoofer completely rather than just disabling it, and close background VPN apps before opening PGSharp, since some VPNs intercept location-adjacent permissions in ways that conflict with mock location.

When to Just Reset the Whole Setup

If you’ve worked through mock location, cache, version, and root module checks and PGSharp teleport is still not working, a clean reset saves more time than continued troubleshooting. Uninstall PGSharp completely, reboot the phone, reinstall the latest version fresh from the official source, reselect it as the mock location app, and log back in. On rooted phones, also reboot into Magisk and re-verify your DenyList settings after the reinstall, since a fresh app install sometimes needs re-adding to the hide list manually. This fixes the handful of teleport failures that don’t trace back to any single setting.

Why This Keeps Happening on the Same Phone

If teleport breaks every single time Pokémon GO or your phone’s OS updates, that’s usually a sign the device itself is fighting the setup rather than PGSharp being unreliable. Budget phones with aggressive battery management kill background location services, cheap Android skins reset Developer Options more readily, and non-rooted devices can’t hide root status at all, meaning any future detection improvement from Niantic hits harder. A phone properly rooted and configured for Pokémon GO botting from the start avoids most of this churn because the mock location, root hiding, and PGSharp Launcher setup are already locked in correctly rather than patched together after the fact.

The ToS Reality Behind Every Fix in This Guide

None of these fixes change the underlying risk of using PGSharp at all. Niantic defines cheating as falsifying location through GPS spoofing and accessing the game client through unauthorized third-party software, and enforces a three-strike policy that can end in a permanent ban. Every troubleshooting step above gets your teleport function working again, but it doesn’t reduce detection risk on its own, that comes down to sensible cooldown habits and not chaining multiple spoofing tools together on one account.

PGSharp teleport not working: key takeaways

Most PGSharp teleport not working cases trace back to mock location getting deselected, an outdated PGSharp build, or a stale cache. On rooted phones, add Magisk/Zygisk DenyList resets to the checklist since root-hiding modules commonly lose their configuration after reboots or updates.

If teleport works but catches fail, that’s a cooldown soft ban, not a bug, and the fix is patience rather than more troubleshooting. Revisit this checklist after major Pokémon GO or Android updates, since compatibility between them can shift without warning.

Buying recommendation

If you’re resetting mock location and re-checking Magisk DenyLists every other week, the setup is working against you, not for you. A phone that arrives already rooted, hidden, and configured specifically for PGSharp’s Launcher build removes most of the recurring breakage covered in this guide.

Frequently asked questions