Android device device monitor error "Java started but returned exit code = 13"

Question

When I start the monitor of the Android device in the android studio, "Java started, but returned the exit code = 13", an error appears with the Java path files. I am using "android studio (beta) 0.89"

Answer 1

This happened to me only after installing the latest version of Java (v8), which for some reason only comes with 32-bit support, and my computer is 64-bit.

I fixed the problem by uninstalling version 8 of Java, which automatically dropped to Java 7, and it works fine.

Answer 2

I fixed this problem on my Windows 7 computer by installing the 64-bit version of Java 8. I did not need to remove or downgrade Java.

Be careful when loading a Java installation. According to this FAQ , you will probably end up with 32 bits if you use the default installation.

Manually select the “Offline Offline (64-bit)” version here , rather than letting the Java website choose for you.

Answer 3

I was able to fix this problem by uninstalling the 32-bit version of Java 8 that I had and then installing the latest version of the 64-bit version of Java 8. (I didn’t have to downgrade)

Answer 4

Follow the path shown in the error popup. Add the java path to the eclipse.ini file located in the monitor folder in Android studio.

Add: -vm C: \ Program Files \ Java \ jre7 \ bin \ java.exe (path to your current java file) To: -vmargs

Answer 5

I think that you are trying to open the wrong version of monitor.exe, it may have been changed during the update. The sdk / tools / lib section must have both 32 and 64-bit versions in the "monitor-x86 or _64" folder. try one if it works well. If you want to download a 64-bit version of Java, you must use a 64-bit browser. For example, in IExplorer 11 + you can change it to 32 bits and return to 64 bits when necessary. I tried updating Java to and still getting java error.

Answer 6

Install both 32 and 64 bit Java 8. This fixed this for me.

Answer 7

Found a solution:

• Uninstall Java 8 Update (64-bit)
• Install Java 7 Update 71 (64 bit)

I also downgraded the JDK from 8 to 7, but this may be optional

Answer 8

If you run win8.X, just go to the control panel and uninstall the java 8 version after everything is okay.

Answer 9

I ran into this problem, even though I had the latest x64 for Java 8 JDK installed and the JAVA_HOME environment variable set.

For me, at least the first line of the error popup shows that it uses the Oracle symbolic link in C: \ ProgramData \ Oracle \ Java \ javapath to find the correct javaw.exe location. In my case, this actually pointed to the x86 assembly of the same version of the JRE, which I also installed for some reason.

I finished cleaning and uninstalled all versions of the JRE / JDK, and then reinstalled the latest x64 JDK. This has changed the symbolic links, and now it runs smoothly.

Most of the other answers should help solve the same problem, but for diagnostic purposes, if you already have x64 installed, it will probably help check C: \ ProgramData \ Oracle \ Java \ javapath.

Answer 10

[DECISION]

Go to the next file in your Android SDK. Sdk \ Tools \ Lib \ monitor-x86_64 \ monitor.ini

and add the following line, you may need to change the path to java -vm C: \ Program Files \ Java \ jre7 \ bin \ java.exe before "-vmargs"