Develop Reference

Android Studio Emulator: Process finished with exit code 3 [duplicate]

I have been messing around with android studio and I ended up installing cocos2dx and using an arm cpu emulator to work with cocos2dx. I have recently seen a message prompting for an update for the android emulator service so I installed it and now my emulator crashes while trying to boot and gives this error in the logcat - this is the error it gave me
19:36 Emulator: **
19:36 Emulator: ERROR:/buildbot/src/android/emu-3.0-release/external/qemu/fpu/softfloat.c:486:round_canonical: code should not be reached
19:36 Emulator: Warning: QObject::~QObject: Timers cannot be stopped from another thread ((null):0, (null))
19:36 ADB rejected shell command (getprop): closed
19:36 Emulator: Process finished with exit code 3
I have no idea what this means but I know it has something to do with the update I downloaded, is there any way to roll back the update maybe?

I've come across the same issue on Windows 10: the current version of Android Emulator (Nov 14, 2018: 28.0.16) crashes or freezes as soon as a virtual ARM device is started. When I start it from command line, it prints
Emulator:
ERROR:/buildbot/src/android/emu-3.0-release/external/qemu/fpu/softfloat.c:486:round_canonical:
code should not be reached
As a temporary solution, I downgraded the emulator to an older version and the problem disappeared.
Here you can find Android Emulator 27.2.9:
Windows: https://dl.google.com/android/repository/emulator-windows-4773671.zip
Mac: https://dl.google.com/android/repository/emulator-darwin-4773671.zip
Linux: https://dl.google.com/android/repository/emulator-linux-4773671.zip
Steps to downgrade the emulator:
Stop all instances of the emulator and close Android Studio;
Open Android SDK directory. Its location can be found in the settings: Android Studio->File->Settings->Appearance & Behavior->System Settings->Android SDK->Android SDK Location;
Move existing 'emulator' directory somewhere outside of Android SDK (if you just rename and leave it there, AVD Manager will find it and start using again);
Unpack one of emulator-*-4266726.zip into the SDK directory;
Launch Android Studio and don't update Android Emulator until it's fixed.
Related answer: How to downgrade Android Emulator

I've come across the same issue on Windows 10,I upgrade Android Emulator 28.0.16 to 28.0.20 also solve the error.

Android program compiles with no errors,but refuses to install

i've posted this question earlier,but could'nt get any solutions.Please i really do need help.After following a couple of tutorials,i have written a ListFragment application which compiles with no erros,but refuses to install on AVD which has API 17,android 4.2.2
[2014-05-09 20:27:44 - Carrebeanne] Failed to install Carrebeanne.apk on device 'emulator-5554!
[2014-05-09 20:27:44 - Carrebeanne] (null)
[2014-05-09 20:27:44 - Carrebeanne] Launch canceled!
Please What i'm i suppposed to do?I've been stuck here for 2 days now

Need help about android basic things that confused me for a few days

I'm a freshman for the android developing, and I met a question that confuse me for a few days.
I run the simple "hello world" code (I promise there is no error in the code, cause I copy it directly from the homepage of SDK), then the emulator runs but my app is not installed in it. and the console is like this:
[2012-06-12 23:05:50 - HelloPig] ------------------------------
[2012-06-12 23:05:50 - HelloPig] Android Launch!
[2012-06-12 23:05:50 - HelloPig] adb is running normally.
[2012-06-12 23:05:50 - HelloPig] Performing com.example.hellopig.HelloPigActivity activity launch
[2012-06-12 23:05:50 - HelloPig] Automatic Target Mode: launching new emulator with compatible AVD 'aaa'
[2012-06-12 23:05:50 - HelloPig] Launching a new emulator with Virtual Device 'aaa'
[2012-06-12 23:05:55 - Emulator] emulator: emulator window was out of view and was recentered
[2012-06-12 23:05:55 - Emulator]
It just keep holding there, I think there should be something like installing app and success. I firstly thought the problem is eclipse cannot find my emulator, but there is no error. I have checked the build debug keystore path, it is the place where my emulator is.
I also have checked the environment variables, but I think there is no problem with them
(I can run java and adb in cmd)
I really have no idea, so could anyone help me?
following are the versions of the softwares:
jdk 1.6
ADT 18.0.0
SDK platform 1.5
eclipes java EE IDE for developers
Looking forward to hearing from anyone of you :)

I would suggest starting your emulator before trying to install your app. It looks like you are waiting for Android to start your emulator for you.
Otherwise there isn't enough information here. I would suggest running logcat (open a command prompt, and type 'adb logcat') which will give you more verbose logging information.
Post the output from your logcat (if your problem isn't immediately obvious).

Android-Hello World

I'm currently learning how to create android applications so I started with the basic "Hello World" tutorial over at the Android Developers home page. The code is quite simple but when I run it(I'm using Eclipse and a AVD v2.2), it only shows "Android." It does not go to the Home Screen. I updated everything and I still get the same problem. Is there something I did not or
New errors:
[2010-09-29 09:35:04 - DeviceMonitor]Sending jdwp tracking request failed!
[2010-09-29 09:41:50 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2010-09-29 10:16:23 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2010-09-29 10:16:28 - HelloAndroid] Installing HelloAndroid.apk...
[2010-09-29 10:20:27 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2010-09-29 10:20:27 - HelloAndroid] (null)
[2010-09-29 10:20:29 - HelloAndroid] Launch canceled!

I assume you are using the emulator. You have to be patient; it takes a very long time to start up (several minutes.) You can start the emulator manually by going to the Window menu in Eclipse, selecting "the Android SDK and ADB manager," clicking on the emulator you created and then clicking on the Start button. Wait until you see the home screen. If necessary, unlock it by clicking and dragging the mouse down over the screen until it's unlocked.
If you have access to a physical phone and USB cable, you will have a much better (faster) experience overall.
Good luck!

I had the same problem and was bugged by it for two days. but this is what worked for me. one you get this error. try running your project (APP) again. it did the trick for me.
I had done everything. digged the web, installed and re-installed everything 4-5 times including the JDK as well. m not sure if it will help in the long run, but it seems to have worked for me.

As for me, I had the same problem and it helped to increase SD volume and max VM app heap size. (Android SDK and AVD manager - Virtual device - Edit) What is interesting, the back change of SD and heap to the previous values is OK, too. That means, that any change of emulator parameters and its rebuilding is enough. (Simple restart won't help)
Definitely, it is cheaper, than total reinstalling. :-)

unlock the screen from the emulator. That did the trick for me.

go to the run configurations and select target tab. under this tab you can see your targets. then select automatically radio button and select a check box of AVD. then try to run, most probably your issue will be solved.

I had the same problem and this is how I resolved.
if you run
adb devices
I had nothing on the list. So did.
adb kill-server
and
adb start-server
Now if you run the emulator again, the Activity oncreate event will hook properly.
Not sure if this is intended but on the first run on the emulator does not work.
And someone confirm on this?
Thanks.

I had the same problem I was running Android 3.1 Java 1.6 on Eclipse. Just rerun the build process and it kicks in the second time.

I also encountered error when followed instructions, so i ran "adb logcat" which showed that it is not able to find the class.
In the instructions(tutorial) - : It has been said that (during create new project or class)application name set to Hello World and activity name became HelloWorldActivity.
So if you maintain both CreateActivity name and application name both same, then it might work.
I have increased the AVD RAM size to 1024 and VM application to 36 0r 48 or 24.

If anyone getting following error,
[2010-09-29 09:35:04 - DeviceMonitor]Sending jdwp tracking request failed!
[2010-09-29 09:41:50 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2010-09-29 10:16:23 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2010-09-29 10:16:28 - HelloAndroid] Installing HelloAndroid.apk...
[2010-09-29 10:20:27 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2010-09-29 10:20:27 - HelloAndroid] (null)
[2010-09-29 10:20:29 - HelloAndroid] Launch canceled!
Simply restart your application.
Wait for some time.Bcaz it take some time.
when you will get screen with "Data-time-charging-lock",
click on lock .There will be some animation.Again click on same lock.
AND Your Are DONE.You will get output..........

this kept happening to me ... how i solved it was to use " adb install " in a command prompt ...search for adb.exe if its not in your path. Make sure the emulator is running by going to run configuration and hitting run. This starts the emulator without installing your apk file. After the emulator starts up run the command prompt stuff listed above.

I restarted my virtual device with the option Wipe User Data checked and then reran my app. That finally worked for me.
Note that in response to the other comments, I also tried the following:
Simply restarting the device
Restarting the device after changing the VM heap size
Restarting my computer

You might want to try out using Android Studio's AVD. That AVD seems to work better for me.

Issue with 'Hello Android' tutorial

I am brand new to Eclipse and Android, but somewhat familiar with Java. That having been said, I tried to follow the 'Hello Android' tutorial from the developer site using the latest Eclipse (Galieo) and the 2.1 Android SDK, I am on a Macintosh running Snow Leopard (OS X 10.6). I have a default virtual device (though my target is actually for phones like my own HTC Incredible which has the snapdragon processor and of course all the latest accoutrement in smart phones).
Everything seemed to go okay until I went to RUN>RUN and then selected 'Android Application'. My computer spins its wheels for a while and then I see two errors. I have pasted the output from Eclipse below:
[2010-05-04 01:53:46 - HelloAndroid] ------------------------------
[2010-05-04 01:53:46 - HelloAndroid] Android Launch!
[2010-05-04 01:53:46 - HelloAndroid] adb is running normally.
[2010-05-04 01:53:46 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2010-05-04 01:53:46 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAVD'
[2010-05-04 01:53:46 - HelloAndroid] Launching a new emulator with Virtual Device 'myAVD'
[2010-05-04 01:53:58 - HelloAndroid] New emulator found: emulator-5554
[2010-05-04 01:53:58 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2010-05-04 01:53:59 - Emulator] 2010-05-04 01:53:59.501 emulator[10398:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2010-05-04 01:54:23 - HelloAndroid] emulator-5554 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'!
I never do see the text in the emulator and the emulator crashes with a message about it quitting unexpectedly.
The crash report states:
Process: emulator [10472]
Path: /Applications/android-sdk-mac_86/tools/emulator
Identifier: emulator
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: eclipse [10468]
Date/Time: 2010-05-04 02:25:41.153 -0500
OS Version: Mac OS X 10.6.3 (10D573)
Report Version: 6
Interval Since Last Report: 2558914 sec
Crashes Since Last Report: 4
Per-App Crashes Since Last Report: 2
Anonymous UUID: C5F178C1-5290-4CA9-AD6E-E9C4F5582754
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000001fd2f000
Crashed Thread: 3
NOTE: Running the emulator from the command line with:
iainnitro-Mac:tools iainnitro$ ./emulator -avd myAVD
2010-05-04 02:49:23.011 emulator[10556:903] Warning once: This application, or a library it
uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw
and move to Quartz.
Segmentation fault
iainnitro-Mac:tools iainnitro$
yields a segmentation fault(as noted above from the terminal output). So the emulator is dying on its own before anything can be shown.
I have tried restarting the ADB processes.
The actual code is line by line from the tutorial and I have never been able to get to the XML part yet.
I am not sure what is wrong with my environment setup or if it is just an incompatibility with Snow Leopard? I would REALLY appreciate any help in resolving this as I am very interested in developing on this platform.
Thank-you,
Mike N Lawrence, Kansas

No direct experience, but this seems to be a recurrent issue:
This thread suggests:
You haven't let the emulator boot all the way up. Start it then wait until you see a desktop, just like on a real phone.
This one mentions (I suspect point 1. is not a concern for you):
Get more RAM. I was running on 256 MB (which I believe is below minimum requirements), just upgraded today to 1024 MB (long time coming), application now starts fine. Although I still do see some error messages in the emulator, they don't seem to actually do anything.
Install from command line. This is a bit laborius, but you can launch an emulator from the command line (assuming <android sdk path>\tools is added to your PATH variable) just type emulator, then browse to the location of your_app_here.apk, and execute
adb install your_app_here.apk
If you launch the emulator from Eclipse, execute adb kill-service and then adb start-service first (or kill-server / start-server. not sure the exact commands). Then your app will be installed on the emulator.
Also (a bit old but might still be relevant)
Maybe the emulator is running so slow, and the adb server, or another component like "DDMS" is a little "desperate" because seems it's waiting to the emulator to iniatialize the some HOME aplication.
But the emulator is running slow, the console in Eclipse send a message: emulator-5554
disconnected! Cancelling 'com.android.hello.HelloAndroid' launch!; and the emulator continues running normally and boot it's system, but don't run application that I build.
So for that problem I run program, and when the emulator is opened, I go back to eclipse in DDMS Perspective and in the Device tab y press a button "restart adb server" before the console shows me the message of "emulator-5554 disconnected!".
I do it several times until the emulator finally boot the OS.
After booted the OS on the emulator, eclipse don't send that disconnect error, and "sends" the app that I've built, also the console shows messages about this.
Then finally appears on the mobile "Hello, Android".

There has been a discussion on this with two proposed solutions
http://code.google.com/p/android/issues/detail?id=724
Comment 17 by zachrcrowe, Jan 06, 2010
FYI - I had to change a line in the Hello Android example to read
this.setContentView(tv); in order for it to work. As mentioned above, the deprecation
warning shouldn't affect the functionality of the emulator.
Comment 18 by mfrony, Jan 14, 2010
I had the same problem when I ran the Hello Android example. The way I solved it and
could run my first Android code was by changing the Project Build Target from 1.1 to 1.5.

This seems to be a timing issue. For some reason Eclipse attempts to load the application on to the emulator before it is "ready". I'm not sure why this occurs but I did find a work around: just start the emulator from the command line before you run the application.
Start clean by closing Eclipse (maybe the OP didn't exit Eclipse before he tried to run via the command line?)
Start the emulator via Terminal by navigating to the android-sdk-mac_86/tools directory and typing:
./emulator -avd my_avd
Open Eclipse and attempt to run the tutorial again using the same steps as before
A dialog box should open asking whether you would like to start a new AVD or use the one that is already running--choose to use the one that is already running.

what i did was to move the circle that appears when the AVD launches to the unlock position, and there it was 'Hello, Android'!

I had this same problem when I tried to run the emulator using a 4.0 AVD. It used to crash at the bootup screen and show 'Segmentation fault' in the console. I was able to fix it by increasing the SD card size of the AVD to 1GB from 32MB.

For whatever reason, I stopped getting the segmentation fault when I added:
this.setContentView(tv);
the 'this' seemingly solved the issue. The seg fault happens if you try to run the emulator without any .apk file I assume. (I was getting that from the command line as well). I hope the tutorial will be updated.

See Related post
Another related post
This worked on Linux for me:
Run Emulator (Wait for the home screen of the Emulator to load)
Click Window > Open Perspective > DDMS
In Devices Panel, click on drop down menu > Reset adb
Run project