Up until recently I had no problems debugging with my Nexus 5 connected via USB cable to my PC (Windows 10).
Suddenly I cant see my device in the "Connected Devices" list. can anyone help?
Can't see nexus 5
Driver is OK
And I can edit my files through the explorer.
Help?
try to use original nexus cable when connect from device to computer , i have this case and solve it when use this cable
Today I noticed the same behavior on my LG Nexus 5 with Android M.
I also remember two icons that are in status bar when you were connected through USB. One for charging and one for debugging. None of these is showing anymore.
My only guess is that some hardware is damaged. Probably the USB connection port. Yesterday I remember that my cable was causing unstable connection and the 2 icons I mentioned were appearing/disappearing repeatedly in one second(flickering). It looks like it was bad connected due to broken cable until finally it burned some internals.
I've seen other people complaining for the same reason. Nobody has discovered or posted any reasonable answer yet.
After years of programming apps and using n5 for debugging, this is for sure not driver (I'm on Mac OS X), adb, or other typical problem.
The only thing is left to try is restoring to factory.
UPDATE:
Before posting this answer I tried everything, changed a lot of cables, even tried booting into safe mode. And just after posting this answer here, I tried one more time to reconnect all cables from my MacBook and the charging icon appeared again!
My new guess is: there might be some bug probably related to battery.
When started noticing the problem first my phone battery was about 11%. Now that it works again it's on 50%+.
And I say it's a bug because I know for sure that I ran a lot of apps from Android Studio with phone being below 50%.
Related
I am trying to create a React-Native app and I need to connect my device to troubleshoot some issues that only occur on the physical device and not the simulator. For some reason I have never been able to connect my Pixel 2 XL to my PC. I am running Windows 10 and I have tried all of the following.
Enabling developer mode and USB Debugging on my device.
Uplugging and replugging my device 20+ times in a row.
Changing the USB port I am using.
Changing the USB connectivity settings in Developer Options > Default USB Configuration. (Options are: File Transfer, USB tethering, MIDI, PTP, No data transfer) I've tried them all.
Restarting my device while it's plugged in
Downloading the Google USB Driver (in Android Studio).
Restarting my PC when the device is plugged in.
Updating my PC, and updating my device.
Checking Device Manager and trying to update the driver. (So the device used to show up with the yellow warning triangle next to it and trying to update the driver never worked. But now, the device doesn't even show up in Device Manager anymore)
Factory Reset my phone.
Downloaded Media Feature Pack for N and KN versions of Windows 10 (Suggested by the google tech support)(I called them)
I feel like I've tried everything previously addressed in every Stack Overflow question on this issue.
Finally solved the issue. The data cable was the problem. If you have tried all the steps above, and nothing is working, buy a new cable. This one works great and seems very durable for my Pixel 2 X: https://www.amazon.com/gp/product/B01N4OKUB8/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
I had this issue too - my Google Pixel 2 XL is about 9 months old. Was developing an app, so using USB debugging to debug the app as I built it. One day it mysteriously stopped working, though no issues with charging. I tried everything, including using all the different USB ports on my laptop, with no luck.
I eventually gave up and started using the emulator on Android Studio, and since I didn't need data transfer for anything else, I didn't send my phone for repair or anything.
A few weeks later it just started working again, all by itself...
I don't think I did anything to fix it - the moral of the story is, if you don't need it urgently, there's a chance it might just decide to work again!
When I run adb devices there are no devices showing as connected. My device is a LG Optimus Exceed 2 running 4.4.2
There are many of these posts around, so here's what I've done:
I'm using the cord that came with the phone. It charges and tries to sync photos, so it isn't an issue here. Switching usb ports and trying a powered usb hub doesn't affect it either.
I've added the vendor id (0x1004) to ~/.android/adb_usb.ini
Restarted and unplugged any combination of things you can think of
USB Debugging is on. And has been restarted. Same with Unknown sources.
I have never used EasyTether, nor is it installed anywhere on my computer.
Updated adb, updated my sdk.
Restarted adb server
Tried installing LG's drivers: http://www.lg.com/us/support-mobile/lg-VS450PP (They say they don't support Mac S/W upgrade, yet they have a package to install. No help there)
I have a Nexus S running 4.1 that works, and an old LG phone running Gingerbread that connect.
Any wizards out there who've already struggled with this who have advice?
I tried all of the connection types (charge, MTP, PTP) but perhaps not "Internet Connnection, modem"? You can change it by pulling down the system-wide drop down menu and touching "USB connection".
This is how I fixed it, but I thought I'd tried this already, so I can't guarantee it wasn't this in conjunction with one of the things done above.
PTP seemed to do the trick. Never had to do that on any other device...
I had the exact same problem. Selectin Internet Connection and then Ethernet as the USB connection type fixed it and everything is working as expected now.
I know this sounds like a stupid answer, but the same thing happened to me. It turns out the micro USB cord was just bad - which is weird, because it still charged the phone perfectly fine. After testing the bad cable unsuccessfully on a phone that had been recognized on my mac before, I switched to a different micro USB cable, and that made all the difference.
This is late in the game but I had an additional step to all the other suggestions. The phone was showing up in the System Profiler after I switched the usb mode to 'MTP' mode, but I didn't see any usb tethering options. After adding the phone's vendor ID to the usb ini file, enabling the developer and usb debugging, killing and restarting adb, I still didn't see my device in adb devices.
I finally had to download the Mac driver for the phone directly from LG.com. After installing and rebooting on the computer, the device showed up in adb devices.
So I've read nearly every stack overflow answer about this issue, but still no solution. My device keeps getting disconnected. I've switched through 12 wires, I've tried every USB port; nothing. Eclipse keeps dropping the connection. It happens most often when I enter debug mode. Has anyone found a solution to this? Is this a bug in the new update? Seriously, this makes debugging and testing so painful. It slows down my testing by at least 3 times. There has to be a better solution.
First thing I tend to try is the following commands in cmd/terminal
adb kill-server
adb start-server
And lastly,
adb devices
To check the device is connected.
Following that I'd try restarting the device, and perhaps as a last resort uninstall/reinstall it's drivers.
Edit: also, do you have access to another device? In the past I've had issues with specific devices constantly dropping out.
I experience that when my nexus7 2012 kept disconnecting; root cause was the USB3 connection.
Changing to a USB2 port fixed my issues; can you try switching to a lower speed port?
I was having a very similar problem but using Android Studio on OS X. By default Android Studio points to an SDK inside it's application bundle so I changed the SDK location setting to point to another version of the Android SDK I had downloaded manually and this seems to have fixed the disconnection issues I was having.
Instructions for changing the SDK location setting can be found in this answer.
My connected device (an Acer) was working a treat until I rebooted my mac. After the reboot, Eclipse dropped the connection every single time I ran the app. I tried two cables and every port in my iMac but nothing worked. I had to disconnect and reconnect the device for every run (a real pain when debugging!).
What worked for me was to run the app. When the window appeared to choose the device to run on (which was empty), I disconnected then reconnected the device, but before clicking to run, I checked the box (bottom left) to use this device for each run. It now runs every time directly on the device.
a unpowered usb hub did fix the problem for me. it was happening on both my samsung s6 and my sony z5 premium.and both on my pc and my mac. (using android studio).
Use short usb cable. The shorter the length of cable, the more stable the adb connection. I had the same problem for long time. I changed the cable to shorter one and I haven't got that problem anymore.
Has anyone found a good solution to debug a galaxy nexus as it gets power?
I can only debug and use the nexus 10 while its plugged into my computer. I can only charge the nexus 10 when its plugged into a wall.
It charges from USB so what am I suppose to do short of rooting the device and using ADB connect to its IP address?
Do they make cables? Are there ways to send more amps through a USB slot? would a USB hub work?
Something, anything? This is truly a nightmare
I see you're leaning towards a hardware solution, but my answer is more of a workaround I am using:
I assume that most of your debugging you do on emulators, but if you just need to know what's crashing your app on nexus 10, maybe you can try ACRA to get the stack trace. I found it very useful as I cannot test all devices and all versions, plus my IDE is on a VM without USB support... I call it "poor man's debugging".
More on this post: android - how to send crash reports
If it was me, I would get two USB cables (1 Nexus 10 cable and another USB-USB cable) and splice the power leads from one into the Nexus 10 cable. That way you could then plug the Nexus 10 cable from computer to Nexus 10, and the other cable from your wall charger.
Of course, you have to be comfortable doing this, and sure of your soldering.
EDIT 1: I should also note, that you might wish to look into the POGO pins on the side of your Nexus 10. I believe that these can be used to charge the device (I'm sure a little bit of googling will confirm this). You could see if there are any docks out yet (There weren't when I last checked a couple months back) that could be used to charge it, leaving the USB connection free.
If you don't mind to root your device, or already have done this. ADB over WIFI could be an option. You can find the directions for ADB over TCP in this post:
How can I connect to Android with ADB over TCP?
I followed the steps for USB Debugging showed here under paragraph 8 and my HTC Desire is recognized once:./adb devices
List of devices attached
SH0BJPL02419 device
Then I run the exact same command once more and the connection is lost. Sometimes I can also see the devices three times but after a couple of secs the connection is gone.
USB Debugging is still displayed as 'on' on the phone, though.
I use Debian Squeeze 64bit.
Thanks in advance for any help!
Selecting 'harddrive' on the phone did the trick in case anyone is interested.