PC cannot trnasfer files to Nexus

**laua** · 02-04-2012, 03:23 AM

Own my galaxy nexus for a few day , loaded a few apps, and transfer pictures and vedio files to it from PC. Then next day when I drag and drop a files or files to it PC open the copy widget but not action. I can see the folders on the nexus. call Samsung, they advice me to reset my nexus to factory state. I work that way. but I have to restore everything. any idea why, and any fix without a total reset.
Edit/Delete Message

**GIkari** · 02-04-2012, 05:53 AM

A few questions...

1) are you using the included USB cable?

2) what version of windows are you using?

3) have you tried using both MTP and PTP("camera") connection modes?

**rdmodlin** · 02-04-2012, 08:50 AM

I am having the same problem. It worked perfect before. Windows 7. Could it be the update from Windows a week ago?

**ellisz** · 02-04-2012, 09:23 AM

I had mixed results when I first got the phone as well. I ended up using a wifi file transfer app and have not looked back. Kind of a pain at first but is easy now.

I use Wifi File Explorer Pro. There are free ones I believe but I got this on the Amazon Free app of the day a while back.

**Eggshen** · 02-04-2012, 10:43 AM

I've never had a problem where it stopped working but I do notice that sometimes when transferring files, it's extremely fast, other times it's extremely slow. No idea why, nothing changes.

**yosteve** · 02-04-2012, 01:03 PM

I use ex file explorer, find the file copy and paste it. Haven't done it in while. I don't know if the app actually handles the copy and pasting it just allows me to see the folders and files.

**sicario666** · 02-04-2012, 01:31 PM

Download airdroid from the market. It works great and gets the job done quickly. There are some other cool features you can check out as well

**clicq0** · 02-04-2012, 01:50 PM

I had the same problem -- I was able to copy files to the device the first time, but once I put a couple hundred files on the device, I can't consistently get files to transfer.

This has been reported to Google's bug tracker already:

Supposedly it's fixed in 4.03.