Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error logged in API 33 and 34 #319

Open
craftedcodes opened this issue Mar 9, 2024 · 1 comment
Open

Error logged in API 33 and 34 #319

craftedcodes opened this issue Mar 9, 2024 · 1 comment

Comments

@craftedcodes
Copy link

craftedcodes commented Mar 9, 2024

I get this error:
2024-03-09 13:24:15.448 8756-8780 EGL_emulation com.example.abschlussaufgabe E tid 8780: eglGetConfigAttrib(1268): error 0x3005 (EGL_BAD_CONFIG)
2024-03-09 13:24:15.448 8756-8780 EGL_emulation com.example.abschlussaufgabe E tid 8780: eglGetConfigAttrib(1268): error 0x3005 (EGL_BAD_CONFIG)
2024-03-09 13:24:15.448 8756-8780 libEGL com.example.abschlussaufgabe E call to OpenGL ES API with no current context (logged once per thread)
2024-03-09 13:24:15.448 8756-8780 libEGL com.example.abschlussaufgabe E call to OpenGL ES API with no current context (logged once per thread)
2024-03-09 13:24:15.462 8756-8776 OpenGLRenderer com.example.abschlussaufgabe W Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
2024-03-09 13:24:15.462 8756-8776 OpenGLRenderer com.example.abschlussaufgabe W Failed to initialize 101010-2 format, error = EGL_SUCCESS
2024-03-09 13:24:15.469 8756-8776 Gralloc4 com.example.abschlussaufgabe I mapper 4.x is not supported
2024-03-09 13:24:15.476 8756-8776 OpenGLRenderer com.example.abschlussaufgabe E Unable to match the desired swap behavior.

It doesn't break down the app. The app works absolutely fine. Just the error is being logged which is problematic for me.

I used Pixel 7 Pro with API 33 and 34.

Does anyone know a solution for this bug? It's a graduation project where I had to use Kotlin and XML (yes, I would have also preferred Jetpack Compose).

@umberto-sonnino
Copy link
Contributor

Hi @craftedcodes! Those are just debug prints for when the app is starting up and trying to find a good EGL configuration that matches your device. Since it's iterating all of them, it stops logging once it finds the rendering backend finds one it needs. These should only be appearing when running the app in debug mode. Are you also seeing them in release mode?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants