Tools AVD manager and chose which emulator you want to use. If you want to run using android sdk, you can do so. I would recommend to download 1st option and refer here to get detailed steps.So:1 – Open a terminal and go to this folder: ~/Android/Sdk/tools2 – Start the emulator with this command. And what’s the cause of that? As you can see, there could be many causes.I think the best way to find the concrete error with the emulator is to start it within a terminal. The Run menu, or press Control+Option+D on a Mac or Alt+Shift+F9 on Windows.“’It seems that “Waiting for target device to come online …” is a generic message that appears, always, when the emulator can not start properly. FIguRE 7-18: Android TV image selection Next, select the recently created.
Android Studio Launch Emulator Mac OS X 10My graphic card is an ATI Radeon HD 6850 by Sapphire.I had the same issue in Android Studio 2.3.3 on Mac OS X 10.12.6 and the issue was caused by Android Studio using an old version of HAXM (6.0.3 when it should have been 6.2.1): $ kextstat | grep intel148 0 0xffffff7f8342c000 0x14000 0x14000 com.intel.kext.intelhaxm (6.0.3) 50449AFC-F7C6-38A0-B820-233E8A050FD6 Removing and reintalling HAXM from within Android Studio according to the instructions didn’t work: Instead, download the HAXM installer manually or if that link expires, find it under under Intel® Hardware Accelerated Execution Manager (Intel® HAXM).After running the installer, it now shows that the current version of HAXM is installed: $ kextstat | grep intel169 0 0xffffff7f83472000 0x1d000 0x1d000 com.intel.kext.intelhaxm (6.2.1) 7B6ABC56-699C-3449-A0EC-BEB36C154E3C After upgrading HAXM manually, I’m able to launch x86_64 emulators.Old answer, which might work instead (note that this didn’t work for me for x86_64 images):The Recommended tab should be highlighted.Even though I had the API Level 25 SDK installed, it showed:Nougat Download 25 x86 Android 7.1.1 (Google APIs)So I clicked Download link which seems to have repaired the API Level 25 SDK. With this change, when I run the emulator within Android Studio, it will also load the system libraries.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=1PS 2 – I work with Debian Jessie. /emulator -avd EMULATOR_NAME -netspeed full -netdelay none -use-system-libsThe definitive solution is to set the ANDROID_EMULATOR_USE_SYSTEM_LIBS environment variable to 1 for your user/system. How? Adding “-use-system-libs” at the end of the command. 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.Solution? Very easy: to use the system libraries instead of the packaged in Android Studio. /emulator -list-avdsIf everything is ok, the program doesn’t start, and it writes in the terminal the concrete error.In my case, the application says that there is a problem loading the graphic driver (“ libGL error: unable to load driver: r600_dri.so“).
0 Comments
Leave a Reply. |
Details
AuthorJulie ArchivesCategories |