Develop Reference

Failed to install itcuties-data-usage-app.apk on device '0123456789ABCDEF': Connection refused: connect

I have developed an application . I have also connected a device with my laptop . But when I am trying to run application , I have got the following error .
[2015-05-07 16:38:52 - itcuties-data-usage-app] WARNING: Unknown device API version!
[2015-05-07 16:38:52 - itcuties-data-usage-app] Uploading itcuties-data-usage-app.apk onto device '0123456789ABCDEF'
[2015-05-07 16:17:01 - itcuties-data-usage-app] Failed to install itcuties-data-usage-app.apk on device '0123456789ABCDEF': Connection refused: connect
[2015-05-07 16:17:01 - itcuties-data-usage-app] java.net.ConnectException: Connection refused: connect
[2015-05-07 16:17:01 - itcuties-data-usage-app] Launch canceled!
I have tried for solution . I have set the ADB connection Time Out to 10000ms. But still the problem is not solved . Please help me .

By following 3 points , I have solved this problem .
Restart adb
Restart phone
Restart PC

Genymotion android 5 network error

I have downloaded a new genymotion android 5 ova file, and imported it to virtual box successfully. When I start the new device, it takes a long time and shows this error:
Unable to connect to the virtual device. Genymotion will now close.
Please check VirtualBox network configuration.
for more information please refer to :
https://cloud.genymotion.com/page/faq/#collapse-nostart
I read the troubleshot followed the error message. My network configuration is correct as the instruction. (The address is 192.168.56.100/24, and DHCP is the same rang. Also other virtual devices correctly start.)
I ran the vm with the VirtualBox and got this error:
init : cannot find '/system/bin/install-recovery.sh' , disabling 'flash_recovery'
IP Management : 192.168.56.101
failed to execute /sbin/v86d make sure that the v86d helper is
installed and executable Getting VBE info block failed (eax=0x4f00,err=-2)
vbe_init() failed with -22
What should I do ?

I get an error ddms Can't bind to local 8602 for debugger - no debugging for Android

I am just starting develop a simple hello world application and I got this error and I cannot debug any application on AVD nor any device.
I am using Eclipse Juno and Windows 8.
[2012-11-11 10:57:37 - ddms] Can't bind to local 8610 for debugger
[2012-11-11 10:57:37 - ddmlib] An established connection was aborted by the software in your host machine
java.io.IOException: An established connection was aborted by the software in your host machine
at sun.nio.ch.SocketDispatcher.write0(Native Method)
at sun.nio.ch.SocketDispatcher.write(Unknown Source)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.write(Unknown Source)
at sun.nio.ch.SocketChannelImpl.write(Unknown Source)
at com.android.ddmlib.JdwpPacket.writeAndConsume(JdwpPacket.java:213)
at com.android.ddmlib.Client.sendAndConsume(Client.java:575)
at com.android.ddmlib.HandleHeap.sendREAQ(HandleHeap.java:348)
at com.android.ddmlib.Client.requestAllocationStatus(Client.java:421)
at com.android.ddmlib.DeviceMonitor.createClient(DeviceMonitor.java:837)
at com.android.ddmlib.DeviceMonitor.openClient(DeviceMonitor.java:805)
at com.android.ddmlib.DeviceMonitor.processIncomingJdwpData(DeviceMonitor.java:765)
at com.android.ddmlib.DeviceMonitor.deviceClientMonitorLoop(DeviceMonitor.java:652)
at com.android.ddmlib.DeviceMonitor.access$100(DeviceMonitor.java:44)
at com.android.ddmlib.DeviceMonitor$3.run(DeviceMonitor.java:580)
[2012-11-11 10:58:41 - ddms] Can't bind to local 8602 for debugger
[2012-11-11 10:58:41 - ddms] Can't bind to local 8610 for debugger
[2012-11-11 10:58:41 - ddms] Can't bind to local 8602 for debugger
I checked many available solutions including:
disabling windows firewall / antivirus
adding a line " 127.0.0.1 localhost" into host file
checking if there was not another eclipse instance running in background (I have only one instance running)
restarting adb
recreating avd
restarting eclipse and my computer also didn't help
changing in Window -> Preferences -> Android -> DDMS "base local debugger port" and checking "use ADBHOST" with "127.0.0.1" also didn't help me.
checking with netstat -a that the ports are not in use
Please, maybe somebody can solve the madness so that the debugger will connect.

I had the same problem since installing Windows 8.
Installing JRE 6 did solve the issue however it did work once without the need to to this..
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jre-6u34-oth-JPR

OK I spent some hours to figure it out:
It turned out that the cause was Java 7. I uninstalled Java 7 and installed Java 6 and debugging works now!

Failed to install myapp.apk on device 'emulator-5554'

I'm trying to run an android app but it's throwing these three lines in red.
[2012-07-08 20:39:23 - myapp] Failed to install myapp.apk on device 'emulator-5554': An attempt was made to access a socket in a way forbidden by its access permissions
[2012-07-08 20:39:23 - myapp] java.io.IOException: An attempt was made to access a socket in a way forbidden by its access permissions
[2012-07-08 20:39:23 - myapp] Launch canceled!
I've put the tools and plateform folder into enviormental variable and also tried every possible thing which can be done but nothing change.
I've tried it installing manually and its says by "adb install myapp.apk"
and I get
protocol error
rm failed for /data/local/tmp/myapp.apk, No such file or directory
Edited:
I can't install anything using SDK Manager I m getting
Fetching URL: http://developer.sonymobile.com/edk/android/repository.xml
Permission denied: recv failed
Done. Nothing was installed.
kindly help me to resolve it
thanks

Try window->show view->devices->view menu->Reset adb and again run application.

Two primary reasons for ADB's protocol error are:
Zombie ADB process (e.g. adb.exe in Windows's task-manager or just adb in Linux ps -aux)
Default ADB port (e.g. 5037, 5554, 5555 etc) being occupied by some other process(es).
For both of these issues, the easiest solution is to kill the zombie or the port-blocking process. I explained the steps for both Windows and Linux here: adb kill-server not responding?
You may also try launching ADB with a non-default port. The steps are explained here: Changing default port (i.e. 5037) on which adb server runs
On Windows, I started getting this issue out of nowhere and was driving me nuts. I am happy that I could find the root of the issue. Hope this helps you too. Cheers!

Was having the same issue, turns out was simply because I was using a USB extension cable.
Removing that fixed it.

android Eclipse logcat error: device() request rejected - device not found

I am having trouble getting my somewhat new Thunderbolt to print to logcat in eclipse...when I plug it in, I get the following error in the console:
[2011-08-04 11:23:10 - DeviceMonitor]Failed to start monitoring
[2011-08-04 11:23:11 - Logcat]device () request rejected: device not found
java.io.IOException: device () request rejected: device not found
at com.android.ddmlib.AdbHelper.setDevice(Unknown Source)
at com.android.ddmlib.AdbHelper.executeRemoteCommand(Unknown Source)
at com.android.ddmlib.Device.executeShellCommand(Unknown Source)
at com.android.ddmuilib.logcat.LogPanel$3.run(Unknown Source)
I can run adb just fine, and sometimes when I totally restart my computer logcat will work for a while, but it usually doesn't. Makes it hard to debug!
Anyone have any ideas?

Try typing the following using adb (either from the adb.exe directory or after adding adb to your environment variables):
adb kill-server
adb start-server
See if this works.
EDIT:
It looks like the device is not installed on your system.
This means you need to install the manufacturer's device drivers.
The entire list can be found here.
The driver for your Thunderbolt can be found here.
Install these and restart your computer if needed, and give it a try again.