ADB Timeout on Samsung Galaxy S

Posted: April 6th, 2011 | Author: | Filed under: Misc | 2 Comments »

I was going crazy this morning trying to get a build of Key Ring running on a Samsung Galaxy S (Vibrant). Phone showed up under ‘adb devices’, I could push the .apk manually using ‘adb install’, but every time I would deploy from Eclipse I’d get a “Failed to install app.apk on device ‘phone’: timeout”

I kept searching for issues related to the actual phone, Samsung USB drivers,  etc – but as these things sometimes turn out it was a simple setting I finally stumbled upon in this post. I just needed to increase the ADB timeout to 10000 and everything worked fine. Side note… these Galaxy S phones are painfully slow to work with, in the end I wasn’t suprised by the solution.

Anyway, here’s hoping that anyone else running into this issue comes upon this post quickly and can get back to productive work. Happy hacking!

 

  • http://uniquereplica.myopenid.com/ Steve

    Thanks Ross, I had hit this too and had found it only affected the one handset – this would explain why!

    It’s a shame really, the more I use the Galaxy S the more problems it seems to have.

  • http://rossbates.com Ross Bates

    You bet, glad you found it helpful. I think they just loaded so much extraneous eye candy and apps of questionable value onto these phones that it really degrades the overall experience. Would have been nice to see all those phones shipped like the Nexus S – just a straight up Android build.