Oct 15, 2010
This month, I am not able to get a AT&T Samsung Galaxy Captivate to be recognized by my Win xp when I connect them with a USB cable. This is the same phone I had trouble connecting a few months back. With much help from this list, I was able to get them connected. (Win device mngr, red check mark, get ID, insert this ID in android_winusb.inf file and reinstall android sdk usb driver.) After the fix, communication was successfull for Aug and Sept (about 10 connections per monthduring a 5 day period). But this month the Win xp will not recognize the phone. The only thing that happens is that the device manager, usb, list is updated to include "unknown device" which has no ID's. I have talked to AT&T and Samsung. One person said that there was "an update Oct 5" and this bit of information got me introduced to Samsung tech suppor level 1 and then, after considerable talking, to level 2. Samsung level 2 said that I must have the specific USB cable that came in the box with the phone, I said that probably was not the problem because I have used this (motorola) cable successfully at least 20 times. Then all of a sudden I get a dial tone. So I drove the 20 miles, went into the owners home (while talking to him on his phone, he has mine to use beta testing) and got the cable. Results are the same with this Samsung cable. I am writting this long note becasue I have lots of time waiting for 50 minutes for level 2 support again. I am loosing hope that Samsung is going to be able to help me or possibly they recognize my phone # and know my problem is unresolvable. Does anybody have any light they can shed on this issue?
View 2 Replies