I'm trying to use my new Epic to test an application I made a while ago but I can't seem to get Eclipse or the Android Eclipse plugin to recognize my phone.
The android documentation says that I need to install the USB driver package from the list of available packages in the SDK and AVD manager, but there is no USB driver package. In addition, I am unable to even mount my EPic to my computer to do simple file transfers, regardless of whether I use the drivers that Windows downloads from Windows Update or if I use the official driver package from Samsung.com. Although I will get a drive to show up when I plug my phone in, it will be a light grey and attempting to access it leads to it timing out after a few minutes.
I've attempted this on 32-bit and 64-bit editions of Windows 7, and I do have USB debugging enabled. I'm probably missing something since this is my first Android phone, but I sure can't figure it out and I consider myself pretty proficient with this type of stuff
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Aridon said:
Try one of the USB ports on the back of the CPU that are directly connected to the MB. Stupid? I thought so too until it worked for me.
Also make sure you are using the compatible version of Eclipse IDE and that you went through the steps in there to install the SDK plugin properly.
The plugin doesn't work with the newest versions of Eclipse properly. That said if you cant' mount your SD then your computer isn't recognizing it. The EPIC specific drivers were posted yesterday if you aren't using them do so and try the different USB port.
Click to expand...
Click to collapse
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Roisen said:
I originally tried the front USB ports, and then tried the rear ports and got the same results. I am confident that Eclipse and the SDK plugin are playing nice together because I used them extensively in developing the application a couple of months ago, including using a virtual android device for testing.
The Drivers that I downloaded from Samsung were specific to the Epic and were last revised today, so they are the most recent.
Click to expand...
Click to collapse
I downloaded the drivers from Samsung website but am still unsuccessful in mounting my sd card to my Windows 7 64bit pc. Anybody has found a solution??
i had to edit 70-android.rules to include the samsung drivers code 04e8
I fiddled for a couple of hours and it just started working. No idea what I did, so sorry I can't be of more help to other people with this problem.
i'm not sure what this eclipse thing is, but i was having problems connecting my phone to my computer.
but after doing a battery pull, it all started working again. sounds noobish, but hey, it worked!
Related
I have the SDK for windows installed and have the drivers downloaded but they can not install. Even with my phone plugged in, i have tried all 3 different usb settings and currently have debugging turned on.
NOTE: The driver im trying to install is the adb driver.
Also this may be my first android phone but i do know my way inside and out on a computer
farquep,
I'm an Android newbie myself, but I don't think you need those SDK drivers. I tried installing them, and they weren't working for me, either.
I'm not sure if you're trying to root/enable sideloading on your phone, but I found that the drivers included with HTC Sync seemed to get me where I needed to be as far as THAT effort goes.
If you're just trying to hook up your phone to your PC, and expecting to be able to access it like a removable drive, I'm pretty sure you'll be unable to do that until you go through the rooting/sideload enabling process. I never had any luck with it UNTIL I rooted my phone, and I'm pretty sure that's by AT&T's design.
Regards,
Corporate Dog
You need to modify the .inf file for the driver to include your device/vendor code manually or just do what I did which is easier and install HTC sync won't hurt anything you don't have to use it. It will modify the file for you. Or you could have someone upload there modified file. At any rate the problem is the USB plug and play system that does not recognize your device. It only recognizes a handful of devices and the ARIA is not one of them. Good Luck.
Team,
For those of you having trouble finding drivers here are some links.
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
For Linux and Mac the Android SDK drivers should work fine.
I don't know if it is a conflict with my AV or something else, but when I use the x86 drivers linked, my phone will shut off completely when attaching with "PC Internet" option in the USB settings.
http://forum.xda-developers.com/showthread.php?t=731989
they have been on there for some time now
designgears said:
http://forum.xda-developers.com/showthread.php?t=731989
they have been on there for some time now
Click to expand...
Click to collapse
yes they have... This feels redundant. also add in that if you're a nub just install kies and it will auto dl the correct drivers you need.
systoxity said:
yes they have... This feels redundant. also add in that if you're a nub just install kies and it will auto dl the correct drivers you need.
Click to expand...
Click to collapse
Also on a mac you do not need the sdk. You do need to be in debugging mode though.
Also, you could just go to the Captivate webpage on Samsung's site and get the Captivate drivers, not the generic Galaxy S drivers linked in the OP.
thanks was looking for these!
In Windows 7 I'm not having an easy time getting the phone to be recognized. If I click Start > Devices and Printers it shows up as Samsung_Android but even Kies won't recognize the phone so something is wrong. I also can no longer mount my external SD card and have it show up in Windows. I tried to uninstall all the drivers and reinstall but it keeps telling me there are already drivers installed...soo..... *shrugs*
iamcombat said:
In Windows 7 I'm not having an easy time getting the phone to be recognized. If I click Start > Devices and Printers it shows up as Samsung_Android but even Kies won't recognize the phone so something is wrong. I also can no longer mount my external SD card and have it show up in Windows. I tried to uninstall all the drivers and reinstall but it keeps telling me there are already drivers installed...soo..... *shrugs*
Click to expand...
Click to collapse
I had this problem on my desktop as well. I was using a front USB port on my computer and when I plugged it into one of the back ports, it worked. I also found the USB cable that came with the phone to work better than a cable I had lying around. Try different ports and if all else fails, try a different cable.
So here's something bizarre. I've been using my PC (Win 7 64bit) for weeks now with my Captivate and no issues. Had originally had woes when I got it, but it started working. Anyway, today I plug it in and ... it doesn't recognize it. Have installed / changed NOTHING -- only M$ patches have been applied. Tried to roll back prior and get the lovely BSOD probably because I have 4 SATA Raptors RAID-0'd and M$ doesn't know how to use that, but has anyone else seen this behavior before?
And to add to this. I rebooted my phone and now it works again. Very odd but problem solved.
Sent from my SAMSUNG-SGH-I897 using XDA App
ive been trying for weeks and trying all three, generic Galaxy S, AT&T captivate drivers and Kies and can't get anything working in USB Mass storage mode or Kies mode...
This is on Windows 7 64bit. Driving me crazy. USB mode wont install the Mass storage drivers and Kies wont recognize
My issue is that when I connect the phone on Windows 7 32bit the phone and the internal SD card will connect but one I try to click on anything inside the phone or card the phone will immediately disconnect and then reconnect. When I try to click again it will repeat the disconnection. After that, I don't even have to click on the phone or card directories, it will disconnect then reconnect about 6 more times. Eventually it will be stable and not disconnect. This is extremely annoying. Anyone else with this issue.
. .
drivers from softpedia are OLD
drivers are updated!
v1.3.2250.0 (dated 8 march 2011)
download here
I just got my Gtab today and can already find things I just cant live with so im trying to prep for a new ROM when there are some stable ones out there.
I have downloaded everything from the CWM recovery and root threads but i cant seem to get a driver to work... I have tried section #2 multiple times over on both XP pro x86 & Win7 pro x64 but i end up with the same 3 unknown devices on both *neither have SDK*. When i try to install the unknown USB device with the drivers supplied in nvflash it cant find anything suitable *even pointing to sub-directories*. I downloaded the drivers mentioned in the rooting thread and installed those, I went back to the DM and tried every single directory in the newly unpacked location "C:\Program Files\Samsung\etc.." which had quite a few different ones but i havent gotten anywhere.
I remember this being almost identical to the problems i had trying to root my phone so I finally found linux directions and worked from my mac. Does anyone have a clue whats going on and how to get MS FAIL OS to work?
I guess im the only person having this problem... ohh joy another android that is going to be a pain in the as to root
on your computer, uninstall ALL the samsung drivers (for any previous samsung device/phone). Then connect the tab to your computer and let it search on its own. on your tab the usb debugging should be turned off.
I think the tab is designed to let windows recognize it as usb, but if you have any previous drivers they get into the way.
I have no idea in which section to write this, so General seams like the best choice.
I have a Galaxy Y testing device with a broken boot.img. I am trying to get Odin working in Windows 7 in order to flash a new boot.img to this device, but I can't get the Samsung USB drivers to work and my Windows knowledge is now that great as I mostly work on Linux computers, but no fastboot on Samsung devices.
There are two drivers listed in the Device Manager. The Regular Samsung USB drivers, and something called Samsung USB CDC. It's the CDC I seam to have issues with. It just shows an error message that states "The device could not start (Code: 10)". I have already talked to Samsungs online support, but there is not much support to find there. They know nothing about Windows or how to get anything working on it. And google's search engine, which usually is the best friend for something like this, did not come up with much either.
I should mention that I run Windows in VirtualBox. However, I already have HTC Sync Manager fully working with an older HTC device, so this is not a VBox issue. Also, Windows do find the device just fine, it just can't start one of the drivers.
I have tried installing Kies. I have also tried installing other separate driver versions. Nothing is working.
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
WooHooGuy said:
Search the forums for Naked Drivers, its a complete driver package for a lot of android devices.
Give em a try.
I would post a link but my post count is as such that I cannot at this time.
Click to expand...
Click to collapse
I love the idea of a multi driver for all devices, much like on my linux boxes, so thanks for that. However, I get the same issue and same error message. I will try to reinstall windows and see if that will work. It has been many many years since I ran windows as my daily OS, but I do remember that formatting was the best way of fixing issues with it. If this is still no go, I will try to put windows directly on my netbook to see if this could be a Virtual problem anyways, but I don't think so. USB stuff is working fine on the Virtual OSX.
Will report back later
EDIT:
Nothing is working. All I have installed, is the naked driver. When I plug-in my HTC Desire or HTC Wildfire S, the driver is working fine. But when I plug-in the Galaxy S3 or the Galaxy Y, I get the "The device cannot start (Code: 10)".
So HTC devices are working, but Samsung is not. The same problem I had with separate HTC and Samsung drivers.
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
-CALIBAN666- said:
try the one from my link,its latest usb driver exe from kies,worx on win8 64bit too.
http://forum.xda-developers.com/showthread.php?t=1927769
Click to expand...
Click to collapse
Thanks, but I have tried that version, and the one newer (1.5.23). I did manage, efter some reinstalls, to get 1.5.18 (I think is was) to work on the real installation. So maybe my issue is with virtualbox, I just can't see what. I have disabled everything in linux that could block something, I have disabled firewall and such on the virtual windows, I have tried checking and changing perms on the linux device nodes, and tried running VB as root.
At least I got the Galaxy Y running again, but I don't like having unresolved issues so VB is going down
Hello!
I have a Nexus 4 (currently running the latest CM12 nightly) and I have been struggling with this issue for a long time. I needed to transfer some photos on my PC and when I connected my phone I found out that the PC doesn't recognize it at all - it doesn't appear in the Device manager and I don't even have Other devices and/or Android devices as categories in there too. This was about a few months ago when my PC was running Windows 8.1. Before this issue occured I had no problems connecting my phone to the same PC, running the same OS and even in the same port. And also I was running CM nightly builds back at that time too. I started using AirDroid, but it's a pain the butt to transfer masses of files such as photos from there, because it takes a huge amount of time. So basically I have tried the following with no result:
Turned on USB debugging
Tried all of the PC ports and even a USB hub
Tried a different USB cable
Installed Android SDK
Deleted every single USB driver and reinstalled it seperately
Now I am running Windows 10 64x on my PC and it might come as a surprise, but the phone still is not being recognized at all. Yesterday I tried to connect it to a friend's PC and it was actually recognized and I could access i, but I need it to work on my own PC. I will be truly grateful if you could help me resolve this issue and I apologize if there has ever been such a thread in here, but I just made my account Thanks in advance and have a nice day.
heyitsbiscuit said:
Hello!
I have a Nexus 4 (currently running the latest CM12 nightly) and I have been struggling with this issue for a long time. I needed to transfer some photos on my PC and when I connected my phone I found out that the PC doesn't recognize it at all - it doesn't appear in the Device manager and I don't even have Other devices and/or Android devices as categories in there too. This was about a few months ago when my PC was running Windows 8.1. Before this issue occured I had no problems connecting my phone to the same PC, running the same OS and even in the same port. And also I was running CM nightly builds back at that time too. I started using AirDroid, but it's a pain the butt to transfer masses of files such as photos from there, because it takes a huge amount of time. So basically I have tried the following with no result:
Turned on USB debugging
Tried all of the PC ports and even a USB hub
Tried a different USB cable
Installed Android SDK
Deleted every single USB driver and reinstalled it seperately
Now I am running Windows 10 64x on my PC and it might come as a surprise, but the phone still is not being recognized at all. Yesterday I tried to connect it to a friend's PC and it was actually recognized and I could access i, but I need it to work on my own PC. I will be truly grateful if you could help me resolve this issue and I apologize if there has ever been such a thread in here, but I just made my account Thanks in advance and have a nice day.
Click to expand...
Click to collapse
So, with Win 8.1, at one point, Microsoft via their Win updates pushed out an Acer ADB Device Driver which was complete sheet, and you had to roll it back to get it to work. I only vaguely recall the details, but sounds like you uninstalled them. Here is a thread on the issue: http://www.eightforums.com/drivers-...usb-issue-since-last-windows-8-1-updates.html
You might try downloading Wug's NRT, and going through the driver clean up and install steps and see if that fixes it. You may have some USB device which needs to be removed or failed. The Toolkit will walk you through the process. Also, remember on W10, you do not get an obvious pop-up (to the point I have questioned whether my device was detected), but if you click the Messages bubble in the bottom right of the screen and expand it, if it detects, it will tell you a device was detected.