After update 1.16.100 is visible the loss of performance on Snapdragon SoCs.
For example, I have two devices, with almost the same performance, but one has a Snapdragon SoC, and the other has an Exynos SoC, and this one with Exynos has a exceptional performance, but the one with snapdragon doesn't even reach 30 fps.
Comments 5
Can you write more about the experiences that made you write that issue? What devices exactly did you use, and what OS versions?
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
For any account or purchasing related issues, please contact Minecraft Customer Support directly, as we cannot assist with those here at the bug tracker.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I may not be the original reporter of the issue, but I can attest to the poor performance on devices using Snapdragon 8 Gen 1. The devices I'm experiencing this on are the Samsung Galaxy S22 Ultra and the Samsung Galaxy tab S8 Plus.Â
On both devices I am consistently experiencing frame drops on even the lowest settings.Â
I never experienced this on an older device I owned. That was the Samsung Galaxy S21 Ultra that ran the Snapdragon 888, the predecessor of the Snapdragon 8 Gen 1.
I may open a separate ticket about this problem.
Sorry for the late reply.
Replying to confirm that, as of Minecraft version 1.20.31, the performance issues still occur on Galaxy devices equipped with Snapdragon 8 Gen 1.
Affected devices include...
Device | OS | Processor |
---|---|---|
Galaxy S22 Ultra | Android 13 | Snapdragon 8 Gen 1 |
Galaxy Tab S8 Plus | Android 13 | Snapdragon a Gen 1 |
I do have access to a Galaxy s21 Plus. Will do some testing to see if the performance issues are present on that model too.
Is this still an issue in the latest version (1.17.10)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.