PS 1 – The easiest way I found to set the environment variable, it’s to modify the script that launch the Android Studio ( studio.sh, in my case it is inside /opt/android-stuido/bin), and add at the begining this: export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1 With this change, when I run the emulator within Android Studio, it will also load the system libraries. The definitive solution is to set the ANDROID_EMULATOR_USE_SYSTEM_LIBS environment variable to 1 for your user/system.
#Android emulator mac doesn't boot full
emulator -avd EMULATOR_NAME -netspeed full -netdelay none -use-system-libs How? Adding “-use-system-libs” at the end of the command. Solution? Very easy: to use the system libraries instead of the packaged in Android Studio. As it is explained here, it seems that Google packaged with Android Studio an old version of one library, and the emulator fails when it tries to use my graphic card.
#Android emulator mac doesn't boot driver
In my case, the application says that there is a problem loading the graphic driver (“ libGL error: unable to load driver: r600_dri.so“). If everything is ok, the program doesn’t start, and it writes in the terminal the concrete error. You can see the name of your (previously created with AVD Manager) emulators with this command. emulator -avd EMULATOR_NAME -netspeed full -netdelay none So:ġ – Open a terminal and go to this folder: ~/Android/Sdk/toolsĢ – Start the emulator with this command. I think the best way to find the concrete error with the emulator is to start it within a terminal.
And what’s the cause of that? As you can see, there could be many causes. It seems that “Waiting for target device to come online …” is a generic message that appears, always, when the emulator can not start properly. For this you could copy and paste your command line from “Run” or “AVD” Android Studio console. You need to discover the reason of this… You could run your emulator from the command line. I had a similar problem… Android Emulator doesn’t open.
0 kommentar(er)
