I've just installed VS2015 Community with Xamarin to develop some mobile apps. The problem is, I can't achieve debugging Android apps on any device. Android Device Monitor shows empty list. I tried connecting different phones, which I know are detected on my friend's PC. I can explore their files from windows explorer, from there computer sees them.
USB Debugging on the phone is turned on.
USB connection mode is set to camera, no change at all.
I have Google USB driver installed in Android SDK manager.
I tried adb kill-server, adb start-server. Nothing changed. adb devices
shows empty list.
This is device manager while Developers options are disabled on the phone.
And here with enabled Developers options
I also tried updateing driver to google usb driver, but windows said it's up to date.
You most likely did not grant access to the device. Try to go into the developer settings on the smartphone and revoke the USB debugging authorisation. Then connect the phone to the pc and and wait for a popup on the phone which you should accept. After accepting you should see your device with adb devices.
You can also try to set the connection mode to MTP (instead of the camera PTP).
Hope it helps!
Enable the device for development
Goto: Device > Settings > Developer Options > tick USB debugging
Sometimes just restarting Visual Studio might help
Try the this:
1 - Close Visual Studio
2 - connect your device
3 - Restart visual studio with the device already connected by usb (with the device options checked)
This just happened to me. And it seems setting the startup project to your Android project fixed it.
My understanding is that the Google USB Drivers from the Android SDK Manager only work for Google Nexus devices (at least according to https://developer.android.com/studio/run/win-usb.html); annoyingly enough, to use other kinds of devices you'll probably need to download vendor-specific drivers. For example, I definitely had to download Motorola's drivers to use my Droid for debugging purposes. Unfortunately, for whatever reason Windows wasn't able to automatically detect that that's what it needed to download, so I had to download them manually.
I had the same problem, using a Samsung Galaxy A5
Google Drivers Installed
Samsung Drivers Installed
Phone shows up in file explorer
Plugging the phone in while Visual Studio was opened resulted in a pop up asking for permission. After authorising, everything worked perfectly. I didn't have to go into the developer settings on the smartphone and revoke the USB debugging authorisation.
To preface, I had connected my phone (a blackberry which had Android and full Google Play Store access) via Android Studio before so I KNOW it's possible, but when I was trying to do it with Xamarin I was having issues, Visual Studio just wouldn't recognize my device.
Found the problem appears to be the USB cable I was using. When I standardly plug in the USB, blackberry gives me the option to just charge the phone, or to enable File Transferring. But the first cable I was using always just charged the phone and didn't give me options. I tried switching the usb cable and voila, I got the prompt, and I can see the device now in the Start Debugging dropdown. So it looks like there's charge-only usb cables as well as Data cables. Be sure you're using a Data cable else it won't be able to see your Device
I had the same issue after updating Visual Studio found that in recent versions is better if you open VS in administrator mode to properly work, this should fix the problem.
I had previously revoked debug auth on my phone, but my phone didn't prompt me to allow debugging on my PC when I connected it again. Ended-up restarting my LG V30 while connected to my PC and I was prompted to allow debugging.
After that, Visual Studio 2019 version 16.10.0 adds my phone to the device list.
Running on Windows 11. Visual Studio 2022. But, I don't think the versions are really relevant here - included for completeness.
Followed all instructions re enabling USB debugging from the device. Also, the USB Drivers for my Samsung device were successfully installed on the Windows machine.
I was running the Duet Display application as I had previously installed it for use with my iOS devices. This appears to have created a conflict when connecting the Android device, as the prompt related to Duet would appear but not the prompt to allow USB debugging from the computer along with the RSA thumbprint. Once I exited the Duet app from my system tray and reconnected the Android device I got the prompt and it immediately appeared in Visual Studio 2022.
Here's some things I check when having an issue with Android device not appearing:
Enable developer mode on the device from settings
Install (e.g. to windows) the manufacturer's* developer USB drivers for the device
Ensure the Minimum Android Version in the AndroidManifest.xml is lower or equal to your device
And as always, try a different lead and restart both PC and Device!!
*Manufacturer Android USB Development driver links I know of:
Sony | Samsung | Google/Nexus | Blackberry
I have just updated from VS2015 (14.0.25402.00 Update 3) to VS2017 (15.7.5).
Amongst other things, I had to migrate a .forms app from 2.3.x to 3.1.x...
As it (according to MS) now should be possible to install also the Xamarin integration software in parallel to older versions of VS, I first (for security reasons) wanted to leave my “old” .forms app under VS2015 and .forms 2.3x and start to update to .forms 3.x with VS2017.
First, everything looked good - I was able to open my “old” .forms 2.3.x project in VS2015 (what was not possible in the earlier migration from VS2013 to VS2015).
But, I was not able to bring my two dev mobiles (both Samsung Galaxy S7) to work under VS2015 again, although, they were showed to my dev-machine (windows explorer) correct.
After wasting about a full day (doing every suggested workaround, I found on the web), I gave up und started to migrate the .forms project under VS2017.
Under VS2017 both mobiles were showed immediately without any problems and I was able to debug to the device.
So.. it seems, as the installation of VS2017 (with Xamarin integration SW) has “destroyed” something in the VS2015 installation regarding the access to the mobile devices...
I wasn't getting the USB debugging prompt on the device to trust the PC it was connected to and it wasn't appearing in the drop down list of devices in Visual Studio or ADB. Tried many things but installing the USB driver for the device (in my case Sony Xperia XA1 from: https://developer.sony.com/develop/drivers/
After installing this device driver by right-clicking the ADB Interface device in Device Manager and choosing the downloaded driver it showed the prompt to allow the PC and now works fine. This was on Windows 8.1 . I don't remember having to do the same for my Windows 10 PC.
I tried all the options but the only way I got it working is to unplug the USB cable and connect it on a different USB port.
After downloading phone specific drivers and restarting computer / restarting visual studio etc etc. What fixed it for me was from developer options
Disable USB Debugging
Enable USB Debugging
This was on a Samsung Galaxy, looks like although it was saying USB debugging was enabled it was in fact not enabled until I retriggered it using the above method.
Simply put, my Samsung Galaxy Core LTE is plugged in via USB, but is not listed by Android Studio as a running device.
I've done some Googling to try to find a driver or something to fix my problem, but nothing. I also can't emulate the Galaxy Core LTE device in Android Studio. Anything I can do?
According to your comments, you did this to solve your problem
Enable USB Debugging via Settings -> Developer Options -> Set USB Debugging checkbox to true
Authorize PC to access your device
Have you enabled your USB Debugging?
If not then go to Setting>>Developer Option and enable it.
Download the adb driver from here for samsung.
Install it. If you are using windows 8.1 and still having the issue then just follow this steps.
It should work.
I was able to debug my Android application on two different computers, but have not done so for some time. Yesday, I attempted to debug my Android application on both of these computers but was not able to.
My device is listed when I use the command "adb devices".
My device is a Samsung S II LTE, but the o/s version has changed. When everything was working it was Android 4.0.3, now it is 4.0.4.
My device does appear in the Eclipse "Android Device Chooser" > "Choose a running Android device", but the "Debug" column is blank, and if I try to debug using that entry, my application is installed into the device and excuted, but not debugged.
Yes, I have explicitly specified "Debuggable" in the application manifest, although it should not actually be required.
I tried installing the latest version of Kies (and the USB drives that come with it).
I tried installing the USB drivers directly from Samsung.
Yes, "Settings" > "Developer options" > "USB debugging" is checked.
However, all of these efforts did not make Eclipse / Samsung Android S II LTE (4.0.4) debugging possible. I also noticed that there is an SDK for Android 4.0.3, but not for Android 4.0.4.
Is my inability to debug my application due to the Android 4.0.4. SDK not being available?
Better yet... is it possible for me to debug my application on my device again and if so, how do I go about it?
Many thanks to anyone that can help me!
Your problem doesn't sound too bad. Make sure you've updated Eclipse and your SDKs/tools. Make sure you've turned your phone off and on.
You should first try debugging a new empty Android project. Does that work?
Can you access logcat through DDMS? If not, can you run and access logcat through the command-line (without going through Eclipse)?
Did you set some breakpoints? From your project, did you right-click on it, and select Debug as Android Application?
Your problem is that windows doesn't recognise your device.
I recommend you to install the right driver for you samsung galaxy SII Or you can install Samsung Kies wich comes with a set of driver that should work for your Android developments.
i tried everything. Checked USB debugging and allowed unknown sources. (Android 4.0.1)
When i connect galaxy nexus with the PC without USB debugging, it works.
When i connect galaxy nexus with the PC with USB debugging, it doesn't work.
I can start my app on windows.
I have Windows 7.
Thnx
in order to debug apps on the device, you need to install a USB driver first. although you may connect the device to PC as mass storage, you still need the driver for development. you can download it from the manufacturer Sumsung.
also,make sure you have installed the latest ADT plugin.
the samsung drivers have moved. this one fixed the issue for me
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
You need to download the USB Driver from Samsung: http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#content2
If you want to install something that will avoid any future problem with every Samsung device, install Samsung Kies:
http://www.samsung.com/ca/support/mobilesoftwaremanual/mobilesoftwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
One confusion is that the Android docs mention the Galaxy Nexus One and Nexus S as needing the Google USB Driver. The Galaxy Nexus does not, it needs the Samsung one.
Instal OEM USB Drivers:
http://developer.android.com/tools/extras/oem-usb.html
For Google devices install Google USB driver:
http://developer.android.com/sdk/win-usb.html
Here is where you get the drivers now: samsung
Generally speaking you have to search in the manufacturer's website as stated here
I am just starting to learn Android development using the Android SDK and Eclipse. I can get my HelloWorld starting app to run in the device emulator, but not on my Verizon Droid handset. I have downloaded the drivers for Windows 7 and I can see the files on the handset in Windows Explorer, so I'm assuming I have the drivers working. I have enabled the USB Debugging on the handset.
The problem is that when I set the Debug mode to Manual in Eclipse, I do not see my device in the "Choose device" list. What am I missing?
Before you connect the handset, do you have the handset drivers installed on the PC? If so, without running the Eclipse if you connect the handset to PC, does a pop up show up on bottom right saying "your drivers are installed and your device is ready to use"? (assuming windows development environment)
Before developing/testing on handset you should be able to seamlessly establish handset and PC connectivity. Only then will you be able to use handset for Android development.
Try Installing Samsung Kies. When installing Kies, it utomatically install the drivers for your device.I faced the similar issue before insatalling kies, after installing it.my problem is slved, i am able to see the device in eclipse in DDMS perspective.