I am using intelliJ IDEA12.1.3 for Android Development.
I am running hello world app but when emulator is launched there comes message in commandline that device is not ready wait for 20 sec.
Uploading file
local path: C:\Users\Haseeb\IdeaProjects\untitled\out\production\untitled\untitled.apk
remote path: /data/local/tmp/com.example.untitled
Installing com.example.untitled
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.untitled"
Device is not ready. Waiting for 20 sec.
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.untitled"
Device is not ready. Waiting for 20 sec.
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.untitled"
Device is not ready. Waiting for 20 sec.
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.untitled"
Device is not ready. Waiting for 20 sec.
Google emulator uses ARM opcode, a kind of machine language. It must convert from ARM opcode to Intel opcode. That's why it's slow.
If the Android Emulator does not start properly, this problem is often caused by problems with HAXM. HAXM issues are often the result of conflicts with other virtualization technologies, incorrect settings, or an out-of-date HAXM driver. Try reinstalling the HAXM driver, using the steps detailed in Installing HAXM.
Fix 1 – Stop Emulator from AVD Manager From Android Studio, select “Tools” > “Android” > AVD Manager. Right-click the emulator you are using, then choose “Stop“. Try running the emulator again.
In case you get an error like "Intel virtualization technology (vt,vt-x) is not enabled". Go to your BIOS settings and enable Hardware Virtualization. Restart Android Studio and then try to start the AVD again.
If anything goes wrong starting the emulator, you can get the Device not ready message "forever". Even if things go perfectly it can take five minutes or so to start sometimes -- especially after you wipe user data. Kill the run or debug attempt (look for a red square) and start the emulator from the AVD manager, then wait for it to get to the home screen before trying to run or debug your app.
I usually begin my work day with Android by starting the emulator from the AVD Manager (sometimes I start more than one if I'm testing different devices/android versions, etc) then leaving them up all day long. Unless your program does something really awful, running another debug session will kill the old copy and install and run a new one so there's no reason to start and stop the emulator.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With