I don't know why, but all my drivers are up to date and my HTC one won't connect.
Recently my HTC one updated and now when i connect it to my mac, i see it start charging. I even see the USB connection icon show up but DDMS and ADB both don't see the device.. I can't build to it from eclipse.
I checked the obvious, developer options usb debugging is on.. I HATE this phone by the way.. should have got the nexus 5.
anyone experience the same problem? have a fix?
I had the same problem I restarted the adb and my phone and it was able to pick it up
you could also try doing this: Why can't won't ecilpse connect to my Android device?
Related
I have an android tablet "Galaxy Tab 10.1" and need to connect to my pc to debug but it even doesnt show up on Device Manager when I plug the cable. I saw many solutions and tried it, like:
Downloaded samsung usb driver from here:
http://www.samsung.com/us/support/owners/product/GT-P7510MAYXAB
Also in settings USB debugging is enabled.
But there is still no change! Is there any suggestion?? Thanks in advance!
Go to Settings->Select Storage->Click on the three dots->Usb Computer Connection->Experiment with either MTP or Camera. For my phone it works only with Camera mode.
Well, I changed the cable, reinstalled the drivers and worked :)
After you plugged in try to shutdown and then power on the tablet whilst connected. It solved my issue. Hope this helps!!
You could try turning USB debugging off. Also, is there maybe a setting to change the USB mode in settings? Most Android devices have one somewhere.
I've seen this quite a bit, and it seems that happens when the Samsung connector on the bottom of the device is not properly seated. Remove and firmly re-connect has solved the issue a few times for me.
Disconnecting & rebooting the device, run "adb kill-server", reconnect device, run "adb devices" - seems to solve a good few issues also.
Hi There i got a Simple Solution to share.
1st step: Dont connect your android tablet or phone on the computer in this time. :)
2nd step: if your android tablet or phone is on then TURN IT OFF!!
3rd step: NOW after you turn it OFF turn it ON again then connect to the computer Via USB cable..... SEE IF IT WORKS
download Kies and it will automatically download all required drivers - samsung file sync app
read more: http://www.samsung.com/latin_en/support/usefulsoftware/KIES/JSP
download: http://www.samsung.com/us/kies/
Okay Android made this much harder than it needs to be (as usual).
I fought this for two days and finally found a way to turn USB sharing on on the tablet. I loaded the drivers to the computer and it recognized the device but would not read it. The solution was to go to settings, storage and then ignore everything in the storage box. In the top left corner a USB symbol will appear very small next to the sd card logo (if one is mounted) Long Press and drag that down to open a message box. There will be an option to turn on USB sharing.
I think I have done everything right but I cannot get Eclipse to recognize my plugged in running Samsung Tab-2. Below is what I have done. What have I done wrong?
1) I have instelled USB drivers and can move files from the tablet to the Windows XP computer.
2) I have enabled USB debugging on the phone
3) I have been debugging on a virtual device then sending the apd files over email to my tablet and phone. That works fine. Obviously, I have enabled that on the phone.
4) I set up Eclipse to always ask what device to debug on.
5) I plugged the tablet into the USB slot and it is recognized by Windows.
6) I read the instructions Here
7) I click debug and am faced with a blank list of devices under "Choosing a running Android Device". My tablet does not show up.
8) I find myself at wit's end (adventure reference).
9) I ask for help on Stackoverflow.
I think you should take a look at this answer. An identical issue was accepted at that post.
Hope it works to you!
Try a different MicroUSB cable, I have seen this affect the device showing up in Eclipse, even if the cable is working fine for everything else (even transferring files to/from that specific device).
If nothing works you can use adb over wifi by calling : adb connect "your ip adress". I am assuming the Tab runns Android ICS. You can enable Adb over wifi right under the USB debugging- menu point.
How many times have I called tech support and had them tell me to reboot windows? Well, the solution was to reboot windows. Nowhere in any of the installation instructions did I skip a step of rebooting but just thought I should try that.
While debugging, my device frequently disconnects from my PC, usually after every debug session. The device still appears in the DDMS list but the status is "offline". The only way to fix it is to reconnect the USB cord, which becomes a pain after doing it 10 times every hour. There are no visible error messages when it happens.
I thought it was a physical connectivity problem with my USB cord or my device, but I recently upgraded to a brand-new Galaxy Nexus with a brand-new USB cord and it still happens. Now I'm convinced it's a software issue.
Is there any reason why my devices goes offline frequently? Are there any programs that are known to interfere with the Android/ADB connection?
Yup, you are right. It seems to be a software issue.I have faced this annoying thing many times, it happens now and then. I think what happens is that the adb's connection with the device/emulator breaks or becomes faulty, so android starts showing the device as offline. To correct this problem. Go to DDMS-->Devices Tab-->Click the option "Reset adb" (which is the last option, on clicking the dropdown arrow) . You will then see some error report in the console, but after a minute your emulator would be ready to be used without problems. I do it all the time and it works. Try this instead of manually plugging/unplugging the device.
Please check this answer https://stackoverflow.com/a/26425489/1200583 that is for mac but maybe is the same for other OSs
I find it faster to just plug/unplug, but doing the following in command-line should do the same thing:
adb kill-server
adb start-server
We feel your pain. In case you're using the command-line, you can do the same thing by typing "adb kill-server".
I was able to fix this problem for good by updating Samsung Kies, which installed an updated driver for my phone. I suggest you try reinstalling any device drivers.
Patiently, try fixing the USB cord by massaging it and reconnect it to the USB hub securly but not to tight. Also, do not connect with too many USB extended cables or hub or the connection between the device and Eclipse IDE will interfere the duration.
And one thing, do tried putting your device and the USB cord to any flat surface (e.g. table) to support the long cable?
I had the same problem with Galaxy Nexus running CM 10.1.
Updating KIES with latest version seems to have fixed the issue.
Connect your device through a powered USB hub. Some machines, including new apple macbooks, do not have enough power in the USB ports causing ADB to constantly disconnect.
If your device is rooted, you can connect it to adb via wifi. This is very comfortable, much more than wired USB. Of course you don't always have a rooted device.
I also faced this issue. Adb disconnect my Android device each time just after installing the app in android device from eclipse. The issue was with my USB Cable. I was using the USB cable of Blackberry Phone. To resolve this issue i just changed the USB Cable with Android's USB cable(The cable that comes with new Android Phone) and every thing started working fine.
If you are running on Mac OS Sierra and Android Studio 2.1.2 or 2.2.0 then just upgrade your SDK-Platform Tools to 24.0.4 and Restart Android Studio. This will fix it.
The following two solutions worked for me.
You can try either of the two or both of them.
Restart device.
Free some internal storage space (Works in most of the cases).
As title, I can't able to find my phone device into Eclipse.
I activated on the my phone, either Application/Unknown Source and Application/Development/Debug USB.
But into Eclipse not appear any device phone, why?
Thanks'
Go to the cmd prompt, and then take it to the platform-tools.
Then type the commands
adb kill-server
and then
adb start-server
Then to list the connected devices,
adb devices
you will see the list of active devices including the emulator. If the device is not present, continue the steps for some time..
After you get the device listed among the active ones, you can run it in debug mode.
Think, this will help you..! :)
I just had the same problem on 2 of my phones (Nexus 1 and Amaze 4G). After some research I found that people try to overcome this by restarting Eclipse and ADB (only Eclipse won't do) but it took me rebooting the system and phone to make it work again. If you can go to Eclipse->Window->Open Perspective->DDMS and see if your phone shows there with red bug icon next to your app. If so then try what I described above. If you don't see your device in DDMS perspective then it's your USB driver that is not working and needs to be reinstalled
Had a similar problem with my LG P520. In my case, the problem was as a result of me setting the minimum Android level to Android 2.3(9) while the phone was a Froyo/Android 2.2(8) phone. Hence, it was not a compatible device and would hence not be shown in list of compatible devices.
connect your PC with internet may be it will install some software to connect it with the phone debugger and make sure you enable the usb debugging on your phone.
I'm having an issue with my Galaxy S2. I typically leave it in Debug mode, up until a few days ago it has worked great. I've successfully loaded APK's for testing through eclipse previously.
I tried to load a prototype of a new app im working on and when I plugged in the S2 nothing happened, Windows didn't beep like usual and when I tried to view running devices it did not show up.
When I look at the device manager under universal serial bus controllers, it doesn't show any 'unknown devices'
I've tried reinstalling drivers through kies, and third party sources (as well as removing all drivers and letting windows install them again for me.
I've tried connecting as Mass Storage Device, with debug mode on and off.
I've restarted both my computer and phone many times.
When my phone is off and plugged in Windows will beep and say that a device was connected but not recognized (which is more then what I get when the phone is on)
And sometimes when I "troubleshoot connection issues" in Kies it will reinstall the drivers and after the process is complete windows will report "Drivers were not successfully installed"
I've tried plugging it into my Windows XP laptop and it will show up as "Unrecognized device" even after I installed Kies on the laptop, and tried the driver installation it with the same results.
Posting here is my last resort as I've spent close to 5 hours troubleshooting this issue, and searching for answers. My biggest concern is that when I do plug my phone in it will beep to say that it is charging, but windows 7 doesnt even see it!
I appreciate all suggestions & help!
EDIT: Also I installed the Samsung Android USB Driver for Windows and windows reports that the drivers were not successfully installed
Thanks
Jon
Try to key in dialer:
*#7284#
It has 4 options:
UART
MODEM
PDA
USB
MODEM
PDA
In USB section, select the PDA. If it already selected to PDA then reselect it by selecting MODEM and then PDA again.
Only change the USB setting and then press back and try reconnect to kies again.
Hope it helps..
I had the same problem and JUST as i was about to give up, i realized that I had replaced my usb cord with a generic one from the store. I happened to still have the old one around still and that ended up being my issue -.-; Hope this helps someone else!
This really sucks, I know I've had this happen a few times and it's really annoying to have to deal with. I had luck with this post where they suggest:
... they suggested removing battery from hero with usb pluged in and
then putting battery back in, so i did this thinking it wouldn't work
and hey presto, mounting option became available. I was then able to
follow your first set of intructions to install the drivers through
devices and sync is now working!
If that doesn't work there are a few suggestions and helpful driver websites on there for you to follow :-D
I know I would:
Uninstall all drivers related to your device
Restart Computer without connected
Pull battery on device, plug it in, and once detected put battery back in.
If driver doesn't install correctly, or "unknown device", go to the website on that forum to get the CORRECT driver for your device and Windows OS
Go to Control Panel->Device Manager->(unknown device)->Update Driver
Locate downloaded driver, install
Make sure that when connected, the device says "USB Connected" in it's notification area
Click "Turn on USB storage", or "USB Debugging -> USB debugging"
.. this will at least show you that you have the right drivers.
IF you did all of this and you still can't get it to debug through eclipse, you either have conflicting drivers somehow, or your eclipse IDE isn't setup properly. Maybe update Eclipse, and Android SDK and try again?
Sorry can't give you exact details but this problem could be ANYTHING lol
I had the same problem while using a generic cord.
Don't use for usb transfert
I think they are made only for charging.
Solve by using a stock cord not a generic one.
Okay, so after talking to Samsung they informed me that there is a small defect with the female usb connection, and that it can sometimes be loose.
Only solution, mail it to them...
This fix works on all my computers that "don't recognize" my rooted Samsung Android. Plug the phone into the computer and restart phone. When it comes up again, the computer recognizes it.
My method is KIES AIR.
Open Kies Air
Go to settings > Bluetooth off set.
More settings > Tethering and portable hot spot > Bluetooth tethering check true and portable Wi-Fi hotspot check true.
Now KIES air open on your device and start button click. copy IP address to browser
Your s2 is connected your computer.
Open browser, and copied ip then click paste.
I have two Win XP SP3 workstations that would not connect to my Galaxy. Finally fixed it by installing this particular Intel driver and installing Windows Media Player 11.
if you are running a custom kernel on your phone, you may want to check too if you have "force fast charge" turned on or not. I thought my phone and computer would never talk to each other again but it turned out I had fast charge enabled. Turning that off solved the problem for me.
It might be an issue with USB 3.0 ports. I was tormented by this issue too and I was at the point where I was so ready to burn this device to kingdom come. Before I did that, I decided to use my never-used 2.0 port and guess what, IT WORKED! If your PC doesn't have a 2.0, good luck with that.
punch in code *#7284#, (UART set to PDA) and (USB set to PDA)
solved my problem