Error 0x502 Android Emulator
Asked Answered
W

6

16

I just started in Android Studio to display a map using mapbox, and when I launch the emulator, the map is not displayed but only the mapbox logo. And I have this error:

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniformMatrix4fv:3400 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/

12:22 Emulator: GLESv2Imp.cpp:glUniformMatrix4fv:3400 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform2fv:3303 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform1f:3268 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform1i:3282 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform1f:3268 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform4fv:3359 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform1f:3268 error 0x502

12:22 Emulator: android/android-emugl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUniform1i:3282 error 0x502

Screen error

I helped myself to this: Emulator: glClear:466 GL err 0x502 That is, I reinstall Android Studio totally, and then I manually reinstall HAXM and Android Emulator in the SDK Tool. I also launched in Android Studio administrator mode but without success.

Thanks for your help

Wadley answered 17/2, 2018 at 11:34 Comment(1)
Did you manage to find the solution for that ?Guyon
C
12

I had the same problem as you. If you take a look at the other answer in that thread (https://mcmap.net/q/750705/-emulator-glclear-466-gl-err-0x502) you'll see that one solution is to change the configuration on the virtual devices in the emulator under "Emulated Performance - Graphics".

This seems to fix the problem for me, despite the fact that the app lags as hell in the emulator.

Cestus answered 18/2, 2018 at 13:27 Comment(0)
C
7

I solved the issue with these steps: 1. Open AVD Manager 2. Actions 3 Wipe Data

Chesney answered 15/6, 2020 at 6:19 Comment(1)
Solid workaround, but not a fix given you have to constantly wipe data and restart the deviceGratify
S
1

For Visual Studio Code (might work for Andriod Studio also)

  1. Open Task Manager
  2. End Task qemu-system-x86_64 | may also be found under thread menu of Visual Studio
  3. Run code again
  4. Select Device (>flutter select device)
  5. in terminal run flutter run

Task Manager | qemu-system-x86_64

Softfinned answered 16/6, 2024 at 9:37 Comment(2)
This caused the error to return, for me. Killing qemu (which is under Android Studio if you're using it) killed the emulated device, and otherwise nothing was different in this process than manually stopping the device from Android Studio's Devices list.Gratify
Yes, The error causes it to shut down forcefully. When you restart it, it will reconfigure itself again, within very high chances of eliminating any future incompatibility or Emulator issues.Softfinned
S
0

I solved this problems just looking for SDK Manager where I found some pending updates.

Strangles answered 25/7, 2024 at 15:3 Comment(0)
P
-1

I just faced with this error. I simply changed the API to the higher version ( changed it from 27 to 29 ) and it just worked perfectly

Pediculosis answered 21/8, 2020 at 8:37 Comment(0)
B
-4

Try Creating An AVD With Application Level 25+. & While Creating AVD Select The Graphics Type As - Automatic So that AVD Can Automatically Detect Ur Graphics Hardware.

Blackfellow answered 17/2, 2018 at 13:3 Comment(1)
I still have the same error that appears, here is what I put : i.sstatic.net/xCegx.pngWadley

© 2022 - 2025 — McMap. All rights reserved.