Open Wilker-uwu opened 4 years ago
This will be specific to the device itself as it seems some opengl calls are failing. Unsure whether that's a fundamental incompatibility of the device with what we're doing or some other issue. Google tells me this particular device should support GL ES 3.0/3.1.
the device info is showing me that i currently have 2.0 installed, so if this is an issue of the firmware version of my device and i don't find means to upgrade it because of DRMs or something, then i'm kinda screwed, because all of the updates after the version of when this phone was manufactured are broken (several programs including Contacts Storage were breaking specially after the update in October of 2018), and i even had to reset the image of it to a prior version because a factory reset woudn't do it.
i was suspecting that something like that would be the problem, but i've had the same behavior before the reset. perhaps the Open(?)GL software was broken in my device too?
I totally glossed over the fact the GL ES version was right there in the dump you posted. On looking at it some more it seems the issue actually originates from EGL (which is also a graphics API but a slightly different one). There are traces on the web of similar issues but none that seem very relevant here. Also some hints that Samsung might be doing weird things on some devices, but I can't confirm or deny without actually debugging myself.
Seeing that this is device-specific I wouldn't hold my breath that we will have a fix for you anytime soon, unfortunately. This might get better eventually as we're looking to add alternatives to OpenGL across the board (by leveraging DirectX/Vulkan) but that is a long way ahead.
it's okay then. \^\^ because tbh i would rather wait until i get a new desktop pc and play there for me to personally avoid using DirectX, \^\^' and (going a bit off-topic here) i wonder if i'll be able to run the game in an FSDG-compliant OS (because i've had some bad experiences with my older pc, and i want to avoid some of the stuff in the new one...)
by the way thank you for the attention, i appreciate it ^-^
I think we'll eventually get to a point where we can support GLES 2.0, but this is dependent on further abstraction in o!f and is quite a long while off. Marking as low priority for now.
I know this is low priority for now.... just mentioning my issue https://github.com/ppy/osu-framework/issues/2862 because it's same and also happens on oppo neo 5, same specs on my old phone MyPhone Rio 2 issue but OS and storage size and screen size is only difference. (ColorOS 2.1.0i based on Android 5.1)
As a heads up, we can not support android versions that are 6 years old.
Describe the crash:
the game is unable to launch for me because of this error. this crash is quite old for me, but it took me a while to find out how to get the logs for it to not end up finding that it could be a mistake in my part.
reproduction is as easy as
install›launch›stuck in a (black|splash) screen›crash
osu!lazer version:
2020.717.0
downloaded on 21 of July, if that is relevant. (the application reports 0.1)
Logs:
Matlog report:
no log files were generated by the application itself.
Computer Specifications: