views:

1663

answers:

9

I'm using Windows 7 Ultimate 64 bit edition and Eclipse 3.5 with the Android plugin. Every time I create a new project and try to publish it, I get an error like this:

[2010-02-15 22:48:10 - EPG3]Uploading EPG3.apk onto device 'emulator-5554'
[2010-02-15 22:48:15 - EPG3]Failed to upload EPG3.apk on device 'emulator-5554'
[2010-02-15 22:48:15 - EPG3]java.io.IOException: Unable to upload file: timeout
[2010-02-15 22:48:15 - EPG3]Launch canceled!

The emulator is working perfectly, adb can see it, I can even logcat from it, but it can't push or pull anything from it. Nothing appears in logcat to suggest the emulator even received any command. It doesn't matter if I have the Firewall on or off, or if I try invoking adb install to bypass the plugin. Nothing works even with a blank app.

Any ideas?

A: 

um, wierd. Try running adb from an admin shell?

Segfault
Doesn't seem to make a difference. I ran as an admin shell and a command such as "adb install EPG3.apk" just hangs there forever. I can type "adb shell" for example and it connects no problems, but nothing when trying to install.
locka
A: 

Make sure you start Eclipse using "run as administrator".

sadboy
Running as administrator makes no difference. Same issue - IOException. I am able to pull files from the emulator, I am able to run a shell on it. I am able to run logcat. I just can't install anything.
locka
A: 
Christopher
locka
A: 

Did you try to add the path of the tools directory to your system PATH as described here ?

Philipp
Yes, tried that. As best as I can tell the issue is not with adb running, or with the emulator running but in getting adb to upload anything to the emulator. From what I understand the Eclipse plugin is through the IOException I see whereas when I do it through adb it just hangs indefinitely.I'll add that my adb won't upload anything to an attached device either. If I try something such as adb -d install foo.apk, it just hangs there forever. Everything functions correctly through Ubuntu on a second machine (although adb server has to be run with sudo to install to USB devices).
locka
A: 

Hey. Wondering if you fixed the problem. I am running Vista with 64-bit and am having the same trouble. I have tried the suggestions here but nothing seems to help. Let me know if you found anything out. Thanks.

Joshua Sutherland
locka
+1  A: 

Isnt this a problem with resources loading? Tried all the hello examples without problems, now the first with drawables and now I/O problem as you had.

I think its the reason that in the example they speak of a drawable folder, but in my default project structur there are 3 drawable folders.

Keep on debugging ;)

Raphael
A: 

Perhaps increasing the size of sdcard would solve the problem

Waqar Hameed
+7  A: 

Not sure if this helps but I had the same exception when I tried uploading a project to the device and fixed it by increasing the value of "adb connection time out (ms)" (eclipse -> window -> settings -> android -> ddms.

I was pretty pissed at myself that it took me so long to find the setting so I thought I'd share.

DieBagger
A: 

I got this error about every 30-40 compilations. I don't how, but this solution work for me.

Go to bin/ folder and rename your EPG3-debug.apk file to EPG3.apk (if you are using debug mode) or EPG3-release.apk to EPG3.apk (in Run mode), return to Eclipse, now you can Debug/Run your application. This should "unchoke" this whole situation, so you can make changes in your code and next time Debug/Run program normally (until you get this error once again, then you must repeat this tip).

NiegodziwyBeru