Please bear with me, I know there are a lot of threads about the same problem but I've tried everything suggested in them to fix it and nothing has worked so far.
I used to use an S7 (Android 7) on my private Win 7 PC and set up a Win 10 workstation a couple of weeks ago that I've been using since. Since then, every time I connected the phone to the PC, it displayed a message on the phone about giving permission to use the MTP connection (Which it only did once on my Win 7 PC) and then debugging was working just fine.
Yesterday the phone didn't show that message and Eclipse also didn't detect it (it didn't show up in the "Devices" tab), I had to restart the PC to get it to work again (restarting ADB,.. didn't work). Today even restarting the PC didn't help.
What I've tried so far:
Restart the S7
Restart the PC
Kill and restart ADB (through Eclipse and command line - said "daemon not running; starting now at tcp:xxxx", then "daemon started successfully" every time)
Disable and re-enable Developer Mode
Disable and re-enable USB-Debugging
Change connection mode to PTP and back to MTP
Set to "always prompt to pick device" instead of "automatic" in Eclipse (Run - Run Configurations - Target) - it's now back on "automatic"
Different USB port
Different USB cable
I installed the Google USB driver through the SDK Manager when I started using Win 10 but Eclipse stopped detecting the S7 after restarting the PC, so I uninstalled it again and have been using the driver Win 10 found since then (and, like I said, everything has been working fine until yesterday)
Install Kies (it told me to connect a phone, even though the S7 was connected)
I found out what the problem is: It's Windows 10 downloading updates in the background!
Why I think it's the updates:
Yesterday, when the PC had stopped detecting the phone, I restarted it, which took longer than usual because it had to install a couple of updates.
Today, after writing the first post and installing Kies, I did another restart and it installed updates again - afterwards it worked fine again.
I just came back from my lunch break (I disconnected the phone before I left) and the "MTP permission" message didn't pop up again and Eclipse also didn't find the S7 again, so I restarted the PC: This time it didn't say "updating" but again it did take longer than a normal restart and it displayed a spinning circle, which it usually does when it's still reconfiguring stuff after installing updates.
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!
I need to know how to make Windows 7 forget it ever connected to my LG G Stylo phone. I have three devices that I use in Android Studio development. For some reason, this one is no longer being detected by the ADB. Something has happened to make it no longer show up, because it did a couple of weeks ago.
AS's ADB will detect my other two devices, and this device shows up in the in the ADB on another computer. I have tediously gone through the registry and removed everything referencing the Stylo, but it still will not show up in AS's ADB.
Thanks for the help!
John
To start, I have just purchased the LG Stylo 3 plus and ran right into this situation. TO repeat the basics you need
With Android Studio shut down...
Turn on Developer options (tap 7 times on build number in settings
(Settings>System>About Phone>Build Number
Turn on USB Debugging in Developer Options
(optionally) check on the type of USB connection, MTP or PTP should
work
(Optionally) Because I did it, also do a revoke USB tap.
Here was the key for me. I needed to install the LG USB Windows Drivers for my Windows 7 (I'll try 10 tonight and update). Go to this page
LG Drivers and firmware
and either type in model number or browse to find device. LG has a nice interface to install the Windows Drivers. I recommend the Support tool to verify the device as the up to date drivers as well. Start Android Studio and to test I just started the app in debug mode and went through the process of setting up ADB for using the new;y connected device.
Developer options" has to be ON in order to make AS see the device
If even though device manager you can't saw the device, Windows couldn't find drivers.Maybe the drivers are hidden on the device otherwise download it and install it.
If that doesn't work:
Shut down
Hit F8 (or whatever gets to startup options screen on your computer)
Disable Driver Signature Enforcement.
Run driver
After 10 hours spent, it seems that I need to remove /data/misc/adb/adb_key file and restart the phone. But how can I do it if phone is unrooted and adb has no access?
It's unrooted HTC One M7 Att. I've tried reinstalling drivers many times and reinstalling sdk. I plugged and unplugged usb, changed ports, turned on and off debugging. Nothing helps and rsa dialog doesn't come up. I've also deleted adbkey files in .Android folder on Windows.
I've connected another HTC One and it worked smoothly. So, problem in the phone.
Help?
If your device appears in adb devices output (even as "unauthorized") - your drivers are fine. Also there's no need to reinstall the whole SDK - just make sure you have updated platform-tools package to the latest version.
unplug your device
kill adb (or just reboot your PC)
start adb
make sure your device is unlocked at the idle (launcher) screen
plug your device back in
you should see the authorization dialog now.
that means that you need to confirm the connection on the device (in your case the htc m7).
A Dialog should be displayed on the device (e.g Image below) when you connect to your device.
There is an alternative.....
You can connect it using adb wireless app and debug your apps wirelessly...:)
following is app link.....
https://play.google.com/store/apps/details?id=za.co.henry.hsu.adbwirelessbyhenry&hl=en
Unable to install the drivers for the usb debugging mode on android-system.
The device — Sony Xperia V with Android 4.3, on the PC — Windows 7 Home Premium.
Phone Information in Device Manager. There he defined as "portable device". Sorry for language. It is russian :(
I downloaded the latest ADB drivers from the sit Google, set them manually, and the picture is as follows:
ADB does not see the phone.
Update the Windows driver does not, on the grounds that the best of everything is already.
If remove them when you reconnect a Windows device starts again instantly put all the same his driver.
Disable automatic driver installation failed. In the Home version of Widnows is only possible to disable autostart them with auto-update service, which I did. Set gpedit.msc, where he was to be an item on the prohibition of automatic installation of the device, but it was not there.
You can connect your phone is turned off debug mode and then turn it on. In the Device Manager list is updated, but nothing new in it does not appear.
I faced with this problem for a long time ago when I try to install a custom recovery . Then the phone just was not detected, probably due to lack of drivers. Tried in vain to fix anything, but it was easier to use someone else's car, where the driver got up at once as it should. Now, the problem still want to overcome, for debugging applications on android-emulator inconvenient, it would be nice to do it several times on a real device.
Now I don't know what to do :( Help me please.
You have to install the PC Companion from Sony.
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.