Android ports unplayable after Android 15 / One UI 7 update on Samsung Galaxy A55
lootenantdan
Member Posts: 6
As per title, the game became recently unplayable after the update to Android 15 based One UI 7 on Samsung Galaxy A55. Things look exactly as you can see on the screenshot:
The sound is on, the screen underneath all that mess seems to be fully interactable (with a bit of luck I can even load a save and run it, despite not being able to see anything). It seems like the graphics are just not rendering.
Every single Infinity Engine game is affected except for the Planescape: Torment recently brought back to the store. Tried clearing the game data / cache and reinstalling - no results.
If anyone got some ideas I'd be very thankful.
The sound is on, the screen underneath all that mess seems to be fully interactable (with a bit of luck I can even load a save and run it, despite not being able to see anything). It seems like the graphics are just not rendering.
Every single Infinity Engine game is affected except for the Planescape: Torment recently brought back to the store. Tried clearing the game data / cache and reinstalling - no results.
If anyone got some ideas I'd be very thankful.
0
Comments
Hi there, is there any update on this?
I've bought BG1 EE also a few days ago and have the same error, it's completely unplayable and it's frustrating.
Please advise.
A lot of us have been supporting you since the beginning and own all your games on different platforms
https://play.google.com/store/apps/details?id=com.beamdog.baldursgateenhancededition
Ok, thanks. What OS do you use? What OneUI version?
Thank you. Do you by chance own PST:EE on Android? Does that one work?
Also, what is your Model name (e.g. SM-S921B).
EDIT:
Installed and tried other games I own, joined Beta where applicable:
PST:EE - working
SoD(beta) - not working
NWN:EE(beta) - working
Some of our Samsung Android customers are experiencing a rendering issue that makes the BG1, SoD, BG2, and IWD games unplayable.
We have been investigating this issue for some time and have not been able to reproduce it on our own test devices. We have not heard of this issue affecting non-Samsung devices at this time. We have recently expanded our testing to family and friends with Samsung devices, and unfortunately, none of their devices are experiencing this issue. Here is the list of Samsung devices that we have tested in the past 3 weeks. The vast majority of these devices are running Android 15 and One UI 7, although we did have one device each on Android 11, 13, and 14.
Samsung tablets: Samsung Galaxy Tab A 10.1, Tab S6 Lite, Tab S8+, Tab S9 Ultra
A Series Phones: Samsung Galaxy A35
Z Series Phones: Samsung Galaxy Z Flip 6
S Series Phones: Samsung Galaxy S20 FE, S22 Ultra, S23, S23 Ultra, S24 Ultra, S25
PST:EE on Android seems to work fine for all users.
If you want to help solve the issue quicker, please provide the following information:
Product name - Galaxy A56 5G
Model name - SM-A566B/DS
Android version - 15
One UI version - 7.0
Country - Czech Republic
Games are completely unplayable, pst:ee runs fine
Product name - Samsung Galaxy S22 Ultra
Model name - SM-S908B/DS
Android VERSION - 15
One UI version - 7.0
Country - United Kingdom
Like above the games are unplayable. I don't have Planescape or NWN so cannot comment on those.
Is it possible these are only issues with European models?
Product name-Samsung galaxy A55 5G
Model name-SM-A556E/DS
Android Vesion-15
One UI Version-7.0
Country-Brazil
"The error persists"
Product name Galaxy S24
Model name SM-S921B/DS
Android version 15
One UI version 7.0 (I installed august's upgrade)
Country France
Thanks for your work! I can't wait to enjoy your game again.
reporting another affected device for the Android 15 / One UI 7 performance issue.
Games: Baldur’s Gate: Enhanced Edition (BG1EE) and Baldur’s Gate II: Enhanced Edition (BG2EE)
Product name: Samsung Galaxy S22 Ultra
Model name: SM-S908B/DS
Android version: 15
One UI version: 7.0
Country: Germany
Issue: After updating to Android 15 / One UI 7, both BG1EE and BG2EE become effectively unplayable due to very poor performance.
Tried so far: Common workarounds suggested in the forum, e.g. forcing 60 Hz (Motion smoothness “Standard”). No improvement.
If you need additional details (build/baseband info, logs, test cases), I’m happy to provide them and help test any fixes. Thanks!
Evidence points to ANGLE/Vulkan on One UI 7 as the root cause
What my screenshot shows:
AIDA64 → GPU Renderer: ANGLE (Samsung Xclipse 920) on Vulkan 1.3.279.
So BG:EE/BG2EE are not using “native” OpenGL ES on One UI 7; they run through ANGLE → Vulkan.
Why this matters:
Older OpenGL ES titles can break when forced through ANGLE/Vulkan on Samsung’s One UI 7 path. That fits the visual corruption we see.
Suggested path for the team:
1. Offer a way to bypass ANGLE (force native OpenGL ES) or ship a test build that does so, to confirm the hypothesis.
2. If staying on ANGLE, investigate GL/EGL state that commonly trips ANGLE (framebuffer formats, sRGB, buffer age/present mode, etc.).
Tester toggle (ADB):
Developer options only shows “Standard/System Graphics Driver” here, so the API path must be toggled via ADB. To force native OpenGL for BG1EE & BG2EE:
adb shell settings put global angle_gl_driver_selection_pkgs com.beamdog.baldursgateenhancededition,com.beamdog.baldursgateiienhancededition
adb shell settings put global angle_gl_driver_selection_values native,native
Revert to default:
adb shell settings delete global angle_gl_driver_selection_pkgs
adb shell settings delete global angle_gl_driver_selection_values
And lastly: huge thanks to the Beamdog team for keeping these classics alive on mobile — your work is awesome!
I just read the story of Yahiko
https://forums.beamdog.com/discussion/30553/the-tale-of-the-totemic-druid/p3
And it inspired me to try this class, and I have no other consistent way of playing than my phone.
Good luck!