Time for another Pokemon GO bug news update! The freshest one that popped up is the avatar freezing glitch. It’s fairly common knowledge that your in-game avatar moves as you move. That’s the whole point of the game. However, it seems that trainers have recently begun to encounter a glitch where the Pokemon GO “you” refuses to budge.
Nobody is sure what triggers this bug, though lack of RAM might be the culprit. Either way, it’s truly a pain. And the most common workaround is the good old restarting your phone. The other alternative is exiting the app and killing off processes running in the background.
According to the reports of trainers (and my own experience), here’s what happens. You’ll be walking along looking for Pokemon, when suddenly, your avatar will stop. Nothing you do in the game can “unstick” it. Worst of all, there’s no error screen that pops up. No “GPS signal not found” or anything like that. There’s no apparent reason for this bug. Trainers have tried to get to the bottom of this, and they tried to chart locations where this happens. This, however, has yielded no results. The glitch appears seemingly at random.
The most likely reason for this issue is your phone’s RAM memory. Pokemon GO pulls a lot of RAM, so this might be the case. In most cases, once the trainer’s phone is out of RAM, the app will just crash. However, the game will sometimes just stop responding.
If you encounter this bug and it’s making your Pokemon GO experience miserable, there are some things that you can do, and you’ll hate every one of them. The most obvious move is to restart your phone. However, if you want to avoid this, there are more options. You can exit the app buy tapping the Home button on your phone. Then, kill off the apps running in the background. This will release some of the RAM memory and allow you to play again. The extreme version would be to flat out uninstall some of those bothersome apps, such as the social media ones. Your choice.
Hope this helps you, fellow trainers. Let us know in the comments if this works. If you’ve found another way to fix this problem, share it with us!