Obsolete
Status Update
No update yet.
Comments
ti...@gmail.com
Don't forget to reopen "Android Virtual Device(AVD) Manager" after patching all the libs.
xa...@android.com
ch...@google.com
Thank you for submitting this issue. It was last modified over a year ago and did not generate a high star count. We have made a large number of improvements in the last year which hopefully resolved this issue. In order to correctly prioritize issues in our upcoming release, we are closing this bug. If you continue to experience your issue on the latest stable version of Android Studio, please submit a new bug report. We apologize for any inconvenience this may cause you.
Description
Please put all the libs in attachment to Android "/system/lib64" like this:
“/system/lib64/”:
libOpenglSystemCommon.so
lib_renderControl_enc.so
libGLESv1_enc.so
libGLESv2_enc.so
“/system/lib64/egl”:
libEGL_emulation.so
libGLESv1_CM_emulation.so
libGLESv2_emulation.so
“/system/lib64/hw”:
There may be server ways to do it. But "adb push" is not OK. Because, after reboot, you may find all libs are gone.
If you're using linux, you can do it like this:
1. find the system.img in your SDK package.
It could be in "adt-bundle-linux.../sdk/system-images/android-L/default/x86_64/system.img"
2. mkdir temp
3. sudo mount -o loop system.img temp
4. Open "temp" folder, you may see "lib64". And then copy all the attachment files to the ".../temp/lib64/" folder.
5. Reboot the Android emulator.
6. you can umount temp now
sudo umount temp
If the system still cannot boot, please check the libs are in the right folder using adb shell command, like this:
“/system/lib64/”:
libOpenglSystemCommon.so
lib_renderControl_enc.so
libGLESv1_enc.so
libGLESv2_enc.so
“/system/lib64/egl”:
libEGL_emulation.so
libGLESv1_CM_emulation.so
libGLESv2_emulation.so
“/system/lib64/hw”: