Develop Reference

"Starting Gradle daemon" loop creating endless processes

Whenever I open or create a project in Android Studio, and it starts to do its background build or whatever, it gets to "Starting Gradle daemon", but gets in a loop and never stops repeating that step. As a result, the build never finishes and it keeps creating Gradle daemon processes until the system runs out of memory and freezes.
This is in Ubuntu. It did work previously, and I don't know what could have changed to make it start happening. Has anyone else run into this problem and been able to fix it?

TL;DR: Turn off Windows Mobile Hotspot (aka, adHoc Adapter or Wi-Fi Direct Virtual Adapter) before your first build.
For some reason, while the hotspot is on, gradle server cannot accept incoming connections from /127.0.0.1 according to the log file in %userProfile%\.gradle\daemon\<version>\. And so, it keeps spawning new daemons thinking the old ones (sleeping in wait for connections) are dead.
Every time you need a new gradle daemon (eg. open a new project), you have to turn the hotspot off, wait for AS to connect to the daemon (eg. start building, sync gradle files, etc.), then re-enable it.
Notice that if you forget to disable the hotspot and start a build/sync process, your RAM will be filled with waiting gradle daemons. Kill them all before you try again or you will have an "Insufficient Memory" error.
I use this nice command in a shortcut file to kill all deamons with one click:
C:\Windows\System32\taskkill.exe /F /IM java.exe /T. Of course this is assuming you have no java processes other than gradle daemons (which is mostly the case when I'm working on AS), and you don't mind working daemons be restarted (which isn't a big deal imo).
This problem started only after upgrading from AS 4.0 to 4.1 and stayed for the next upgrades too.

I had the same problem on Linux.
I traced it down to a firewall misconfiguration. It prevented Android Studio from communicating with Gradle daemon using IP over loopback interface.

I have same Error on Win 10, I searched a lot but nothing helped me.
I off/on window firewall, defender, edit rules ...etc. no result
Solution is (may be)
restore all firewall settings.
old style Control Panel → System & Safety → Windows Defender → Restore Defaults
Note: options/words may not very similar, because it translated.
Update 1:
Other solution
is run Build before connect PC to internet, then after Daemon started connect to network, and builds will work fine.
or you can try disabling Daemon, or let it work offline.
I hope this could help someone.

for me:
disconnected the real device attached for testing,
which, i use for testing apps as well as for internet connection through tethering.
and hurray.
on more study,
found that the loose usb cable was culprit.

Unable to start the daemon process. error still exists

i have added the imagei got this error while using android studio ,i did try changing org.gradle.jvmargs to 1024m but it didnt work neither did deleting the .gradle file and starting android studio again, i also tried removing all the files n then reinstalling it but it also didnt work can anybody pls help me out
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/4.4/userguide/gradle_daemon.html
Please read the following process output to find out more:

I had the same problem, i also tried many ways. And after i uninstalled Connectify me program, it worked. So i think you can try to uninstall some programs you have just installed. Sorry for my English.

Android Studio Gradle Error - Protocol Family Unavailable

So I am relatively new to Android dev. and have been getting Android Studio set up on my computers. I have it set up just fine on my Mac. When I downloaded and installed it on my Windows 8.1 desktop the gradle build seems to fail every time. With an error message stating that the Protocol Family Unavailable. I've tried several things including uninstalling and reinstalling Android Studio.
NOTE: I did try what was said to work here Gradle project refresh failed - Protocol family unavailable yet it did not solve the problem for me.

When I used Stunnel I faced this problem and my problem was solved when I disconnented it.
Check too see if you have any Stunnel, Vpn or Proxy connection and if so, disconnect it.

I also had this problem and the referenced thread also didn't work for me.
What did work was setting _JAVA_OPTIONS environment variable to make Java use IPv4.
_JAVA_OPTIONS = -Djava.net.preferIPv4Stack=true
Note that Android Studio sets this variable in the vmoptions file. But for some reason, it isn't used by the Java VM started by Android Studio to run Gradle daemon.
After I did that, everything started to work ok and Gradle could build my project.
I hope it helps.

I run into this problem when my firewall blocked studio64.exe from connecting to the internet. I fixed it by granting access.

You could try to fix it temporarily by disabling your anti-virus software while using Android Studio. I'm not entirely sure it will work, but it's worth a try, it worked for me, though I'm aware-, and agree with that this is far from a permanent fix, but it might be good enough while waiting for a fix from the Android Studio team, at least it will let you keep working!
Hope this helps!

"Run command prompt as administrator - type cmd in the 'search programs and files' text box in the Windows Start menu; right-click and select 'Run as administrator'.
At the command prompt, type
netsh winsock reset
Restart your PC
This worked for me."
I found it in
Android studio "Cannot start internal HTTP server"

My problem was using a VPN on an per-app basis connection mode while Android Studio was blocked.

I solved same problem by disabling antivirus.

for me proxifire.exe was running in background and cause to connection problem, after closing problem gone

This answer is same as first answer in this topic, means first answer is true and works well, but my answer is in detail, i did not set that variable, just turn off proxy.
This error arises due to proxifier running that basically tunnels the computer in ipv6 which is not supported by daemon.
So to overcome this and build project either close the proxifier application from system tray or add the environment variable
_JAVA_OPTIONS= -http://Djava.net.preferIPv4Stack=true

Android studio "Cannot start internal HTTP server"

I'am trying to install Android studio, but bad luck..:-(.
Windows 7
Latest Andriod studio
Latest Java
Installed the latest Java and also added it to the system settings according to http://www.youtube.com/watch?v=TTrUX1kUpDo
Also downloaded Gradle and updated the system settings
Stopped all firewall actions
So far so good, Android studio is also starting without any problems. But then I get two messages:
Internal HTTP server disabled: Cannot start internal HTTP server. Git integration, JavaScript debugger and LiveEdit may operate with errors. Please check your firewall settings and restart Android Studio
Gradle 'Nieuwproject' project refresh failed: Connection refused: connect
So after a few days of trying I was hoping that somebody could help me out..:-)

Here's what worked for me - I got the same error:
Internal HTTP server disabled: Cannot start internal HTTP server. Git integration, JavaScript debugger and LiveEdit may operate with errors. Please check your firewall settings and restart Android Studio
Run command prompt as administrator - type cmd in the 'search programs and files' text box in the Windows Start menu; right-click and select 'Run as administrator'.
At the command prompt, type
netsh winsock reset
Restart your PC
This worked for me.
Just to mention: I also added Android Studio and Gradle folders to my virus protection exceptions in case it was being blocked, but that didn't resolve the problem; the problem was only resolved once I followed the steps above.

Turn OFF firewall then turn ON again.
Sometimes firewall blocks it automatically when you start your PC. It also blocks to internet browsing for other reason but restarting firewall may solve this problem.

I encountered this problem after uninstalling Avast from my Computer,few days later i installed Avast again and the problem went away,Dont know what the connection is but thats what solved my problem

if Shell&ServicesEngine is installed on your computer, uninstall it and restart the Android Studio.

Eclipse issue - Launch error: Failed to connect to remote VM. Connection timed out

I get the message
Launch error: Failed to connect to remote VM. Connection timed out.
each time i debug my application on read device. I added to the AndroidManifest the:
<uses-permission android:name="android.permission.SET_DEBUG_APP"/>
and
android:debuggable="true"
But still this is not helping. When i reset the Eclipse ( close it and open it again ) this problem sometimes solved. Its really hard to work in this way - How can i solve this problem?

I sometimes have this problem after I disconnect phone from the computer and reconnect again.
I do CTRL + ALT + DELETE and kill all adb.exe processes and it fixes it for me.
Please try if this also works for you.
Note: I find this faster than restarting adb from command line/eclipse

Just had this bug, tried several things, finally, changing the port worked. I was at port 8600, changed to 8601 and connects instantly! You can find this setting in Windows->Preferences->Android->DDMS. Change default port, apply, and restart Eclipse.

Just uninstall the app from your device and run the debug again.

I don't know why, but this works for me: First Run(or Debug) your application in an emulator and then Debug the application on the device (without closing the emulator).
I know it is not a good solution though, but it's easy.

Another thing to try:
In my case I had 2 instances of eclipse running
To solve:
Close eclipse
Use task manager to kill any additional eclipse processes that are running
Restart eclipse

When running my APP as an Android Application on a Galaxy SII, all worked fine.
When debugging the same app, I got the error:
Launch error: Failed to connect to remote VM. Connection timed out.
On my Windows XP there was installed JRE 1.7. After uninstalling Java 1.7 completely, and installing JDK 1.6u26, I was able to debug my app.

In Eclipse...
Window --> Preferences --> General --> Network connections, choose 'Native' as Acrive Provider.
I had this problem and I became crazy.
Now I've resolved.

I had the AVG 2013 on my system, I uninstalled it and everything is working fine. I guess AVG was not allowing the emulator to open the port for debugger.

Yeah, I've been having this problem a lot these last few weeks.
StackOverflow does not lack in offered solutions, but most involved restarting or killing something.
I noticed the error message included the phrase, 'Connection timed out.', and so I hoped that there was some setting to extend that time and so the attachment wouldn't time out.
There is!
What worked for me was to increase the 'timeout' time.
I'm currently on Eclipse Kepler (Build id: 3.0.3-20140327-1716-Typesafe)
Under the Windows menuu -> Perferences -> Java -> Debug
Near the bottom of the window you will see the following field: Debugger timeout(ms): 3000
I just added another zero, 30000, and my troubles were no more.
You may find that your breakpoints continue to be skipped initially, but wait!
With this long timeout time now, just keep running past those breakpoints until the debugger successfully attaches and boom! You're stopping at breakpoints.
Better still, start up your app in 'debug mode', fold your arms, wait 30 secs or more...then have at her!
It was the following link that lead to this revelation:
getting Launch error: Failed to connect to remote VM. Connection timed out. which trying to debug my app on my device in android