The same thing happens if I try to copy files either via mounting or using pull with adb. If I open Eclispe (my development IDE) and try to run a new build of an app, I'll generally lose the connection.

Usually then, I can clear the logcat or run the logcat fairly stable. I can debug in ddms, install through Eclipse, etc, etc.Īt home, if I reboot both the computer and phone and pull up a command prompt without having Eclipse open, I MIGHT be able to see the device by typing adb devices. My work machine is a Core 2 Duo, don't recall the model.Īt work, I can do anything, mount the sdcard on the phone and copy easily, use adb to push, pull, uninstall, install. My home machine (the problem one) is an Athlon 64 2.2 Ghz. The phone is currently rooted running the Serendipity mod, though this issue was exactly the same on the stock firmware. I have the same Samsung drivers installed, same versions of Eclipse, etc.

The machines are both Windows XP, Service Pack 3, 32 bit. I do development for it from 2 different computers, one at home, one at work.

I have a Samsung Captivate (love it minus it's crappy GPS). I'm not 100% sure if this should go here or the main Stack Overflow, but I decided to go with this area in hope I might catch someone with more specific experience with a similar problem.

Ionic samsung android emulator for mac