-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failing to start emulator #138
Comments
Have you run with the |
Additional useful logs that I see when using the --debug flag...
but the emulator is not booting up and the instrumented test fails with no connected device error. |
I also see this Not sure why it would use 5681 as the port because the command it is using to start the emulator specifies 5680 as port |
Hmm, so there's a couple of things but nothing too helpful.
I hope this helps! |
Hello,
I am trying to start the emulator by following the Readme but I see an error where the emulator exits with code 137, I am not sure what might be causing this, I know 137 is memory issue, but what would I need to do to fix this because without the task manually I am able to boot up the emulator.
Do you wish to create a custom hardware profile? [no] 09:13:48 V/EmulatorConsole: Creating emulator console for 5680
09:13:48 V/EmulatorConsole: Removing emulator console for 5680
09:13:48 V/ddms: execute: running getprop
09:13:48 V/ddms: execute 'getprop' on 'emulator-5680' : EOF hit. Read: -1
09:13:48 V/ddms: execute: returning
Emulator exited abnormally with return code 137
The text was updated successfully, but these errors were encountered: