What you need to know
- Pokémon Go version 0.153.0 has broken high refresh rates.
- One of the most popular phones affected is the OnePlus 7 Pro that has a 90Hz display.
- There is still no word from Niantic on whether is this a new bug or an intentional change.
One of the recent trends we're seeing in the smartphone market is high refresh displays. It started out with gaming phones, but it has now made its way to the OnePlus 7 Pro, and if the rumors hold true, it will also be on the new Pixel 4.
One of the main draws to high refresh rate displays is how buttery smooth they can make games look. However, it's up to the developers to implement that high refresh rate in their games. Pokémon Go was one title that did this, until recently that is.
Many users have gone online to complain that the most recent update has broken the high refresh rate support and is capping performance at 30FPS. Most of the complaints are from users of the OnePlus 7 Pro with a 90Hz display, seeing how that's currently the most popular phone with a high refresh rate. However, there have also been a few complaints from Razer Phone users who have an even higher refresh rate at 120Hz.
Can you please Fix your latest update on the one plus 7 pro phone 0.153.0 has destroyed the 90hz refresh rate through this game. It's a serious problemCan you please Fix your latest update on the one plus 7 pro phone 0.153.0 has destroyed the 90hz refresh rate through this game. It's a serious problem— M Spadezz (@mspadezz1127) August 27, 2019August 27, 2019
The frame rate issue was introduced with version 0.153.0 of Pokémon Go app, but the high refresh rates are still working with the older 0.151.0 version. You can grab the older version from APK Mirror, but that is only a temporary solution and it will eventually stop working.
There is still no word from Niantic, the developer of Pokémon Go, on whether or not this is a bug or an intentional change. Hopefully, it's just a bug which can be squashed quickly and we can all get back to our silky smooth Pokémon hunting.
There's oftentime engine reasons to lock to 30 fps, so that's probably what happened here. Titling is a bit fear mongering.
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.