Android Studio: Unable to start the daemon process

Question

I\'m facing the below error when I\'m trying to import a gradle project in Android Studio.

Unable to start the daemon process.
This problem might be caused b         


        

Answer 1

I faced this issue in intellij idea and solved by doing this,

try to set "VM options" to -Xmx512m at Settings | Build, Execution, Deployment | Build Tools | Gradle | Gradle VM options

Answer 2

You need to install all necessary packages with Android SDK Manager:

• Android SDK Tools

• Android SDK Platform-tools

• Android SDK Build-tools

• SDK Platform

• ARM\Intel System Image

• Android Support Repository

• Android Support Library

Answer 3

I think it's wrong JAVA_HOME make this error. when i get error i try all the way,but it don't work for me. i try delete c:.gradle and Compiler Android studio but it's still don't work. i Re-install the system it work, when update system i get the error again. I try Compiler JAVA_HOME user environment and system environment:

when i use cmd input java:

when cmd.exe show the masage it mean it's work, try to runing Android Studio, it will fix the error.

Answer 4

Try this... I have tried and work fine for me

This issue is related to low memory...

Close your browsers, visual Studio and other services..

after that run following command

ionic build android 

it will run successfully..

//Solutions is
create "gradle.properties" file in android folder and add following line into file
org.gradle.jvmargs=-Xmx512m -XX:MaxPermSize=512m

<your project>\platforms\android\gradle.properties

You can open browser and others..

ionic build android

Now it will work fine.

Answer 5

Check your project folder. You may have there a file called gradle.properties and in there, check to see if you don't have this line:

org.gradle.jvmargs=-Xmx2048m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8

In my case, I just deleted the file, but check the contents to see if you don't actually want to keep some of the settings.

Answer 6

I was getting this same issue, and none of the other answers here helped my particular case.

It turned out to be because my Android Studio project was defaulting to use JDK 8.

Changing this, in the project settings, to point at a JDK 7 installation fixed this for me.