nsacaptain.blogg.se - Galaxy s6 enable usb debugging windows 10

The server instance from commandline works for some phones but not all. It messes with the server instance run by Android Studio.

Delete adbkey and adbkey.pub from ~/.android while Android Studio is open.

Once that is done, and if you open up the AVD menu, Android Studio initializes its own ADB and the phone shows up on the AVD menu. AVD menu only showed the emulator that was still running on my computer. $ adb devicesĪt this point, reconnecting the phone does not help. adb command line utility only showed an emulator that was running, but not the phone connected in debugging mode, one that was seen on the AVD menu, up until the command was run. I still don't see the phone (but that does not bother me as I am able to see the phone from the AVD menu).

I am able to see the phone on the Android-Studio's AVD menu and start running the applications.Īdb version 1.0.31, BUT, if I try to run 'adb devices' on the command line, Android-Studio stops showing this phone on the AVD menu. As soon as this occurs, the new phone threw the dialog open and started working.

Apparently android-studio detects this and creates the keys immediately. I removed two files adbkey and adbkey.pub from ~/.android. The old phone, when connected on the USB plug, threw a dialog asking me to confirm the fingerprint of the RSA key, but the new phone didn't show the same dialog when connected.

When I have Android Studio open, the AVD manager didn't show the new phone, but showed the old one. A new phone didn't work with the exact same configuration. A phone bought in 2015 worked without a problem. I am not sure if you ever solved this problem, but I ran into this problem, and tried out many many different procedures, each of which might have helped others, but this is 2016 and a summary might help.Ī brand new phone bought in 2016 didn't work when I installed Android Studio on Linux.