***EDIT*** Disregard. It was the type of Port - USB (2.0?) on both machines even though I was using different cables.
Can't copy off the photos with Win7, green bar scrolling and just hangs.
Tried two workstations.
We used this phone in October at a wedding to take photos without it being on a carrier. OS 8.x
Was able to connect and transfer files then.
Wife's phone crapped out while we were there so I just activated the Pixel then.
And of course it updated to Pie.
Now however after update to 9.0 when it is connected to Win7 it just goes braindead when trying to transfer pictures.
Now if I connect it to my laptop running Mint 18 I can copy off photos just fine.
I deleted the entire DCIM sub-directory structure under Linux and took a handfull of photos and then tried again on Win 7 and again it just hangs.
Anyone by chance have a solution?
Thanks, _Dan
Related
My Samsung Intercept wont connect to my computer, everytime I plug it in, I get USB device not recognized, how can I get it to be recognized? Im running android 2.2.1, and my computer is running Windows 7 Ultimate 64-Bit
I tried posting a link but the spam prevention police apparently wont let me post links until I have 8 posts. So I'll just quote:
First I tried to use Win 7′s XP mode, which was a total failure. The Windows stock Virtual PC cannot control any devices, it just reads them as belonging to the real computer. After a lot of searching I found the open source Oracle Virtual Box, which is Windows Virtual PC on crack. With Virtual Box, you can mount any number of operating systems to play around with. As a bonus it has the capability to see external devices as its own. All you need is an install disk for your operating system of choice. I had gotten the Intercept to work with both XP and 7 32 bit, so I chose to install a Win 7 32 virtual machine.
For all the specifics on how to install a virtual operating system in Virtual Box, read the user manual. Its large and technical, but skimming the first two chapters should tell you all you need to know to get started. The short version, you set up a partition for your virtual machine, you then “boot” the virtual machine with the install disk of your operating system of choice. You then go through all the normal installation steps, and bingo-bango you now have a virtual copy of XP/7/whatever.
Here is where things get hazy. I was under the impression that the virtual machine would be where I would see the phone. However for mysterious reasons, suddenly the phone now gives me the option to mount and my main Windows 7 64 has no problem letting me into the phones drive!
I don’t know why. I can close the virtual machine and still have access when I plug in. I wish I knew what the heck was going on and how a virtual 32 bit 7 convinced a real 64 bit 7 that the Intercept is OK, but I do not. All I know is that Virtual Box somehow worked for me, perhaps it can work for you. Other than that Virtual Box is a nifty tool I should have had long ago. Good luck!
UPDATE: I wrote this a couple months ago and while it did work, I have a funny feeling that its all just pure luck as to if Windows will bother to recognize the phone. I have computers it works fine on and some that refuse to see the phone no matter what I do. The whole key is to just keep trying, something will work eventually. If all else fails get an app like SwiFTP and move on with your life.
Click to expand...
Click to collapse
Retrieved from wordpress.
Thank you very much for this information, I will get to trying the Virtual Box and the SwiFTP, thank you again.
The above information you gave still didnt work :/, do you or anyone else know what I could do to fix?
Hello, I wanted to say that the whole process for the computer to see the Samsung Intercept is buggy to say the least. I have a good knowledge base of computers as I work as a Desktop Support technician for the past 10 years. I read many posts and replies. None seem to be concrete on a resolution. I tried the usual methods. I downloaded the Samsung SWUpdate+Patch. I downloaded the Sprint USB Modem drivers from Samsung's Web site. I also downloaded the custom files for the Kernel and custom recovery. The first thing I tried on all four of my computers was to install the Samsung USB Modem drivers. The second thing I did was to install the SWUpate+Patch software. My first test computer was a Compaq D500 desktop. Windows XP-SP3 with USB 1.0 ports and a USB 2.0. I placed my phone in USB Debugguing Mode. I then powered off my Phone. I held down the three magic keys to get the phone in "Download" mode. I checked Add/Remove Programs both programs were installed- Samsung USB Modem Driver and the SWUpdate. I first opened the Samsung SWUpdate program. I followed the onscreen instructions of the Samsung program. The program could not communicate with the phone. Bottom right corner of the program said disconneted. I tried chaning the Port Settings in the program to COM1, COM2, etc. All said disconnected. I tried opening the Samsung program several times. Restarting the phone, unplugging the battery etc. I also tried using a different USB cable besides the one that came with the phone. No communication. I tried the same process on another PC which had Win7Pro 32Bit SP1. Almost same results, but I had the computer install these three devices when I opened the Samsung program and connected my phone:Android UMS, S3C6410 Android ADB, CDC Abstract Control Model (ACM) I thought I was good. Status still Disconnected. I restarted the computer tried the whole process again. This time the computer gave me three messages of "Device not Recognized." So I tried a few more different was to get the drivers into Device Manager nothing worked. I even tried that PDA2net app that app wouldn't see the phone wither. Then I looked into the PDA2net directory and saw some drivers .INFs that I thought might work.. I would get a little farther, but then the driver seemed to install and partially recognize the devices, but then a message said that it could start "Error 10" So I tried another computer. Windows 7-64bit. I knew this was going to be a long shot..and it was.. Samsung USB Modem Driver not supported on this version of Windows. So I tried my work computer Win7Enterprise 32Bit. Same issues Device not recognized three or four times. I tried the two USB cables for my phone the OEM one and Aftermarket. No luck. So I had my old trusty Dell D600 laptop. WinXP-SP3 32bit USB 1.0. I installed the Samsung USB Modem driver then the Samsung SWUpate app. I got my Recover.tar file dropped into the Bin dir. I opened the Samsung SWUpdate app and holy **** the damn program was able to connect to my phone I couldn't believe it.. I wanted to take a screen shot of it working just so I could make sure it wasn't B.S. I used my laptop with an Aftermarket USB Cable. I'm not sure if it's a Data USB cable or just a charging cable. I don't think there is two different cables as I've read many times on different fourms. I'm not sure why my laptop works with the phone. When my phone did finally connect it connected on COM3. So maybe it's a port setting/IRQ. I also turned off my Firewall each time just incase it was blocking communication.
If anyone has any questions please feel free to reply. I will try to help in any way possible. I wanted to say thanks to XDA Forum and to Super-6-1 on YouTube..you guys Helped Me more than you know.!!!!!
Hello I just got the Infuse from AT&T and while I am liking the phone there are 2 major issues I am having and 1 minor one that I can not seem to find a fix for.
First when I try to use GPS the phone can see 11 satilites but it refuses to use any of them and will not allow me to use the navigator or any other GPS tools. I have installed GPS Test and GPS Status and both apps show the same thing 11 satilites visible, 0 in use.
Next when I connect the Infuse to my PC (Windows 7 64 bit) and start up the Mass Storage thing but my computer never sees the device. I do not have the pop up to view files and when when I go into my computer no new drives or devices are listed.
Lastly I keep setting a live wallpaper as my wallpaper but every few hours it resets back to the factory original background. How can I get the wallpaper to stop resetting?
I like this phone but these are pretty major issues that will force me to return this device if they can not be resolved...
GPS - How long did you wait? Are you on stock Froyo or one of the Gingerbread builds? GB provides major GPS lock time improvements, but has its own issues.
Win7 USB mounting - no clue. Works fine for me in Linux. (Except when running Cyanogenmod 7, but that's a known issue with our CM7 builds. I just used ADB for file transfers there.)
Live wallpapers resetting - No clue, I hate live wallpapers. My static wallpaper has always been fine. Sometimes if the launcher takes too long to init it will flake out though - if you're on a bone stock ROM (e.g. you haven't flashed an alternate kernel or an alternate full ROM), this might be another symptom of RFS being a horrible filesystem. ext4 conversion is called Voodoo Lagfix for a reason...
I have waited upwards of 10-15 minutes for the GPS to fix. I just had it fix when I was driving but it was all over the place, showed me driving down the middle of a river 100 feet away from where I really was for most of the time...
I have a stock ROM. I just picked the phone up on Monday night so I haven't had it long enough to do too much with it yet and I can't root it since I only bought it because I needed a new phone for my vacation this weekend and the GS2 isn't out yet. I will be returning this as soon as the GS2 hits shelves this month since it will be before my 30 day return window is up but I would like a phone with working GPS and the ablity to copy my files and put movies on it for that month... sigh I might just have to swap it at the store tonight.
As far as the Mass Storage problem some people are saying I need the drivers some people say I don't need them. I do not have them so I will download them and give that a try. Do I get them from Samsung or AT&T?
Typically live walpapers only revert when the battery is low.. its either 15 or 20%
The drivers seem to fix the not detected issue. They can be found in a number of places including here on xda. Search your model # drivers
Keep in mind that can also be a cable issue...or a usb port issue.
Are you using the samsung cable? Did you try other ports?
For gps...open gps test and hot menu.tools.manage and clear agps state
Then memu.toold.manage and download and see if that helps
There are some other tips here on xda that help as well, i dont have the links handy
Sent from my GT-I9000 using XDA App
Drivers shouldn't affect basic USB storage, only Kies and ADB connections.
If USB Mass Storage doesn't work it might be a problem with the PC. I know one port on my laptop HATES my Infuse. Constant USB disconnects.
Entropy512 said:
Drivers shouldn't affect basic USB storage, only Kies and ADB connections.
If USB Mass Storage doesn't work it might be a problem with the PC. I know one port on my laptop HATES my Infuse. Constant USB disconnects.
Click to expand...
Click to collapse
Same here...
Drivers shouldnt affect it...but I could swear I have read two posts that after installing them the issue was mysteriously resolved
Sent from my GT-I9000 using XDA App
Ok so the problem with the USB Mass storage is definitely a driver issue. I connected the USB cable to 3 PC's 2 of which were nearly identical Dell laptops all 3 had Windows 7 64bit OS. On the desktop and one laptop the device was not discovered and nothing happened. On the second laptop windows installed some drivers automatically upon connecting and the device was discovered without any issue. I then downloaded and installed Kies on the other laptop to get the Samsung drivers and after doing that windows immediately saw the device and again installed some drivers and I have had no problems connecting since. So it looks like the confusion over whether or not the divers are required is due to some builds of windows 7 64bit come with the required drivers pre-installed and some do not.
I have tried clearing/downloading new agps data 3 times but it still does not connect to the satilites it sees. I am at a loss there... it may just be a faulty device, I have read some early builds have GPS issues.
efarley said:
Ok so the problem with the USB Mass storage is definitely a driver issue. I connected the USB cable to 3 PC's 2 of which were nearly identical Dell laptops all 3 had Windows 7 64bit OS. On the desktop and one laptop the device was not discovered and nothing happened. On the second laptop windows installed some drivers automatically upon connecting and the device was discovered without any issue. I then downloaded and installed Kies on the other laptop to get the Samsung drivers and after doing that windows immediately saw the device and again installed some drivers and I have had no problems connecting since. So it looks like the confusion over whether or not the divers are required is due to some builds of windows 7 64bit come with the required drivers pre-installed and some do not.
I have tried clearing/downloading new agps data 3 times but it still does not connect to the satilites it sees. I am at a loss there... it may just be a faulty device, I have read some early builds have GPS issues.
Click to expand...
Click to collapse
If you needed to install drivers, for some reason the device never properly entered USB Mass Storage mode (Maybe it went into MTP mode instead?), or Windows decided not to enable the Mass Storage component because it couldn't find drivers for something else.
Proper USB Mass Storage never requires a driver under any OS since Windows 98SE.
efarley said:
Hello I just got the Infuse from AT&T and while I am liking the phone there are 2 major issues I am having and 1 minor one that I can not seem to find a fix for.
First when I try to use GPS the phone can see 11 satilites but it refuses to use any of them and will not allow me to use the navigator or any other GPS tools. I have installed GPS Test and GPS Status and both apps show the same thing 11 satilites visible, 0 in use.
Next when I connect the Infuse to my PC (Windows 7 64 bit) and start up the Mass Storage thing but my computer never sees the device. I do not have the pop up to view files and when when I go into my computer no new drives or devices are listed.
Lastly I keep setting a live wallpaper as my wallpaper but every few hours it resets back to the factory original background. How can I get the wallpaper to stop resetting?
I like this phone but these are pretty major issues that will force me to return this device if they can not be resolved...
Click to expand...
Click to collapse
GPS: Root your phone and use fasterfix. My GPS locks on in seconds.
Mass Storage: I have no idea, mine works fine. I have W7 64bit too.
Maybe you got a lemon...because I would definitely say this is not representative of how nice a phone this one is.
I had the live wallpaper issue when I first got my phone. Turns out you have to move the live wallpapers from the sdcard to the phone to get them to stick.
From XDA App on Infused v2.1.0 OCed to 1.6 GHz
So here is a very interesting question. Or problem perhaps more so. I have the VZ GS3 with the newest PA build 9-17-12 and when I connect my phone to the computer to use it as a mass storage device, I can see the directories, but there are no files shown inside. Also there are many many unnamed directories that show up as well on the SD card portion of the Device. It also seems to show it as a "Portable Media Device" perhaps anyone has some ideas about this one?
Just an FYI, I had this problem on several computers I've tested Windows 7 and Windows XP. Also I had this issue when it was on Previous Roms, ir does not seem to be specific to the PA build I'm on now.
Are you using the original USB cable that came with the phone? I had similar issues using a different cable that I had laying around but as soon as I used the cable that came with the phone all issues were fixed.
Honestly, I didn't even think about that. I'll try that as soon as I get home. (At work now). Thanks very much for the advice.
I have not been able to connect the phone since the windows 10 upgrade.It never finds the devise?
Has anyone else seen this and if so is there a fix ?
Thanks
I actually did have some issues initially. I believe i went in and disabled, then reenabled MTP mode on the N5 while it was plugged into the computer, at which point it was able to see the phone and files correctly. This was while the phone was running the latest official stock. As a side note, I've since put the 3rd developer preview of 6.0 on, and had no troubles at all with Windows seeing the files. I have heard that 10 is still having issues with certain portable memory systems (for example, Nikon camera's aren't functioning correctly; they show up, but have no files listed at all when plugged in via a usb cable). I've only heard of microsoft saying that they are "aware of the problem" thus far.
Hi,
My girlfriend has some issues with her W10 PC. She's on the normal builds (not Insider), latest updates.
The PC is able to read other USB sticks, so the ports are not broken. The phone is identified by the PC, but it only works as a charger. When the state is changed to MTP, nothing appears in My Computer.
I tried to hook it to my W7 work laptop and everything was fine. I have to add that no drivers for the phone were installed on my part.
Any idea if this is a known glitch with W10? I'm on the Skip Ahead builds, so I don't think it's relevant if I check it on my personal laptop.
Thing is, the phone was seen by the PC just fine until a while ago (I don't know what ago means, girls have weird time perception when it comes to technology).
Any hints on what can I do to fix this?
Thanks!
I use Windows 10 Pro with latest updates and Windows and Odin see the phone but not adb for some reason.