osu
osu copied to clipboard
Graphical Glitches on Android 14
Type
Game Behavior
Bug description
I freshly installed osu!lazer on my new Pixel 8 Pro, and the first thing I noticed were those Graphical Glitches as seen in the video. Seems like Transparency completly isn't working and I'm not entirely sure what's causing the flickering.
Worth noting is that the device was behaving strangely after closing osu!lazer aswell, home background disappeared and stuff took a while longer to respond than usual. Subsequent launches usually crashed very early on, like before getting to the main menu, in the intro sequence. So part of this issue may very well be a graphics driver issue, although I'm not entirely sure, Pokemon Go ran and looked fine, Lazer is the only game I've encountered this on so far
I did see that there are issues with Android 14, but I'm not entirely sure if Realms have much to do with graphical glitches?
Screenshots or videos
https://cdn.discordapp.com/attachments/424921904969941005/1165008084184354917/2l8k2b.mp4?ex=65454954&is=6532d454&hm=a0c33fec089cb84484d85dd5582d8639c82c6078ae38a8fffdaee44078b63c43&
Version
2023.1008.1
Logs
Android/data is completly empty for me...
This happens on my Google Pixel 7a too, and apparently does not happen on other devices that do not use Mali-based GPU (e.g Pixel 4a does not have such issue), or maybe even limited to Google devices with Tensor (it does not happen on MediaTek devices. So maybe Exynos-related...?
In my case, the glitches and artifices get progressively worse, "escaping" the application and going so further to even crash the entire SystemUI components and making the phone unusable. And yes, I am on Android 14 (UP1A.231005.007
) too. And this did not happen on Android 13 and previous.
The Android/data/sh.ppy.osulazer/files/logs
folder is empty, just like @Eeveelution's situation.
I have been experiencing the same issues on my Pixel 7 and I also have crashes when I enter a map
Same thing, but not outside-osu graphical glitches after playing the game The game sometimes crashes too.
I found a workaround to fix the graphical glitches:
- Go to developer options
- Navigate to ANGLE Preferences
- Change osu! to angle
Note that I found this when fiddling the developer options and haven't done much research and investigation on this.
~Edit: this can only be done in the beta version of Android (for some reason)~
Edit2: don't show dialog box or it'll crash
I found a workaround to fix the graphical glitches:
- Go to developer options
- Navigate to ANGLE Preferences
- Change osu! to angle
Note that I found this when fiddling the developer options and haven't done much research and investigation on this.
That works, but some other games are buggy with it.
Maybe find a way to change renderer in osu! to ANGLE?
That works, but some other games are buggy with it.
Maybe find a way to change renderer in osu! to ANGLE?
As per ANGLE's documentation, it should be possible by setting some flags, which are only available on the beta builds, making it useless in production builds. What you've done is enabling the ANGLE driver for every application, hence crashing various games/applications (read more about it here).
Although, what @Joehuu is talking about is different. That's for enabling the ANGLE driver per-application which, as I said before, is only available on beta builds and unusable on production ones. I've tried to get the application (the Android System ANGLE one) working, but setting osu! to ANGLE is just like not setting the value at all.
Adding the Google Camera (application which crashes with ANGLE) through ADB to angle_gl_driver_selection_pkgs
and setting its value (angle_gl_driver_selection_values
) to native
is useless, meaning the only way to temporarily set osu! to use ANGLE is via the beta program.
This happens on my Google Pixel 7a too, and apparently does not happen on other devices that do not use Mali-based GPU (e.g Pixel 4a does not have such issue), or maybe even limited to Google devices with Tensor (it does not happen on MediaTek devices. So maybe Exynos-related...?
In my case, the glitches and artifices get progressively worse, "escaping" the application and going so further to even crash the entire SystemUI components and making the phone unusable. And yes, I am on Android 14 (
UP1A.231005.007
) too. And this did not happen on Android 13 and previous.The
Android/data/sh.ppy.osulazer/files/logs
folder is empty, just like @Eeveelution's situation.
I remember opening OSU Lazer on my pixel 7a on Android 13 and it working fine, when I updated to Android 14 things started breaking. It's not a device issue, it's a OS issue.
Might want to change the name of the issue
Found a fix!
Enable ANGLE in dev settings and it works perfectly
Just realized joehuu found this before me :/
yeah you're not the first to discover this, this is if anything just a workaround not a fix
Found a fix! Enable ANGLE in dev settings and it works perfectly
Just realized joehuu found this before me :/
Enjoy using your Google Camera now, lol
That works, but some other games are buggy with it.
Maybe find a way to change renderer in osu! to ANGLE?
As per ANGLE's documentation, it should be possible by setting some flags, which are only available on the beta builds, making it useless in production builds. What you've done is enabling the ANGLE driver for every application, hence crashing various games/applications (read more about it here).
Although, what @Joehuu is talking about is different. That's for enabling the ANGLE driver per-application which, as I said before, is only available on beta builds and unusable on production ones. I've tried to get the application (the Android System ANGLE one) working, but setting osu! to ANGLE is just like not setting the value at all.
Adding the Google Camera (application which crashes with ANGLE) through ADB to
angle_gl_driver_selection_pkgs
and setting its value (angle_gl_driver_selection_values
) tonative
is useless, meaning the only way to temporarily set osu! to use ANGLE is via the beta program.
December patch now allows angle per-app now (November might had allowed this already(?) didn't test but I remember the "angle as the default driver" was grayed out just like Dec)
Phone (Pixel 6) is rooted though so this may not be correct 💀
Phone (Pixel 6) is rooted though so this may not be correct 💀
Can confirm this works on a non-rooted Pixel 7.
Same issue on Pixel 7 pro, had to restart my phone to make it usable. After enabling Angle for osu the game just doesnt start
Facing the same issue. (Pixel 7a)
Same issue on Pixel 7 pro, had to restart my phone to make it usable. After enabling Angle for osu the game just doesnt start
Ok it works now, you cant have the ANGLE dialog enabled
Still an issue on 2023.1224.0 on Pixel 7 Pro. Leaving my message here to bring more attention to the issue :) Also, I don't know if it's the ANGLE renderer's fault, but I'm getting pretty bad performance on song select, about 40FPS, and it feels pretty bad
That works, but some other games are buggy with it.
Maybe find a way to change renderer in osu! to ANGLE?
As per ANGLE's documentation, it should be possible by setting some flags, which are only available on the beta builds, making it useless in production builds. What you've done is enabling the ANGLE driver for every application, hence crashing various games/applications (read more about it here). Although, what @Joehuu is talking about is different. That's for enabling the ANGLE driver per-application which, as I said before, is only available on beta builds and unusable on production ones. I've tried to get the application (the Android System ANGLE one) working, but setting osu! to ANGLE is just like not setting the value at all. Adding the Google Camera (application which crashes with ANGLE) through ADB to
angle_gl_driver_selection_pkgs
and setting its value (angle_gl_driver_selection_values
) tonative
is useless, meaning the only way to temporarily set osu! to use ANGLE is via the beta program.
December patch now allows angle per-app now (November might had allowed this already(?) didn't test but I remember the "angle as the default driver" was grayed out just like Dec) Phone (Pixel 6) is rooted though so this may not be correct 💀
ANGLE crashing the game for me
ANGLE crashing the game for me
@kilyabin Disable the "show ANGLE dialog box" setting, worked for me
ANGLE crashing the game for me
@kilyabin Disable the "show ANGLE dialog box" setting, worked for me
worked for me too
Seems to be fixed with the recent Android 14 beta (AP11.231215.009) without the workaround. Still can use the workaround until the change makes it to stable.
Also pinning as we have seen in recent reports and we weren't using the pinned system as much anyway.
Sadly not all devices can enable ANGLE
I just got the android 14 update on my device (months late) and it does not exhibit the same graphical artifacts as mentioned here. So it seems like this is firmly in the realm of "gpu / driver issue on google pixels specifically".
I have a update available on my Pixel 8 Pro, I'll try running Lazer after the update and report back
I just got the android 14 update on my device (months late) and it does not exhibit the same graphical artifacts as mentioned here. So it seems like this is firmly in the realm of "gpu / driver issue on google pixels specifically".
Mine is Poco X6 Pro which has Dimensity 8300 Ultra chipset and it still has the artifacts even with latest build or the latest update of HyperOS. It's not limited to Pixel phones only
Reporting back: After the update all the graphical glitches went away, was fully playable
I'm using Realme C67 and the app won't even start. Android 14, ANGLE not supported. Snapdragon 685.
I'm using ios but someone tell me should reply to this issue...
https://github.com/ppy/osu/assets/34775378/e921a4cd-9450-4a4a-b2d0-dc4027288b78
metal render iOS 17.4.1 It only happens when I minimize the game immediately after starting
if this is another issues I will open a new one
I'm using ios but someone tell me should reply to this issue...
metal render iOS 17.4.1 It only happens when I minimize the game immediately after starting
if this is another issues I will open a new one
did you try the new release with the experimental renderer? that is supposed to fix the issue
Should post in https://github.com/ppy/osu/discussions/27659 instead.