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.
I am new to android studio and have been having trouble connecting my tablet to android studio so i can test my apps. My tablet is an filemate x2 that runs on android 4.4.2 and i've changed android studio to 4.4.2 from 6.0 . My computer im using is too old so i cant run a virtual machine because of multiple issues(intel HAXM, etc) but i run on windows 7. Its an off brand tablet and i tried to find the OEM driver and thought i found something like it on Wintec(filemate's company) website but it didnt work. anyone have any ideas?
Many times it will not recognize the device and because of driver issues, the device won't show up.
go to settings -> control panel -> hardware and sound -> device manager
check for any devices showing an error. Many androids will show as an unknown USB device.
try to update the drivers for it.
Hope this helps.
Hello Android Enthusiasts,
I am in a funny situation which, it seems, I am stuck in. I have been developing simple Android apps on Eclipse and running on the emulator just fine. But recently my attempt to install and run them on a real device (Samsung Galaxy Y) failed again and again.
I stopped the emulator and plugged my real device to the computer with a USB cable. As soon as I did that, I would see the "Installing device driver software" notification and it would complain that the driver for the Abstract Control Model, ACM, was missing.
A few times I ignored the notification and tried to launch an app on my phone. But Eclipse would simply ignore my read device, start the emulator, and run the app on it instead.
I know it is not an Eclipse issue. But how do I get around this USB issue which seems a common problem on Samsung devices based on comments left by many on various sites?
Thanks.
you need to install the appropriate USB driver for your android device Go through this link first Setting up a Device for Development and Installing a USB Driver
I am having trouble debugging my android app on my phone. My Phone is an LG Optimus G running on android version 4.0.4. Everywhere says to update the driver, but when I do that, my computer doesn't recognize it. I have android ADT installed with SDK versions 4.2, 4.0.3, 2.3.3, and 2.2. I think it might be the fact that my phone is a 4.0.4 and not 4.0.3. And I have USB debugging enabled on my phone. The emulator is just to choppy and laggy to debug on. And one more thing, I have tried debugging already and it has not found the device, although i can find all of the files and pictures on File Explorer. Please help.
If you are on Windows I suggest you try downloading PdaNet http://pdanet.co/, this app is used to share Internet from your android phone to your PC, BUT ALSO helps you install the correct drivers for your Android.
I've found that using this program is the most simple way to get most Android phones working on Windows, plus if you don't want the software you can just uninstall it and the drivers will be kept.
I have a Samsung Galaxy S Advanced that I want to use to test my Android applications on. Just recently, I switched to Windows 8. Everything appeared to be working fine, Windows 8 detected my device fine however, the device was not list when I ran adb devices. I know I set-up the phone correctly, enabling USB debugging in the developer settings.
This problem can be fixed by installing the official Samsung USB Mobile Phone driver. You can find this driver at the official Samsung site: http://www.samsung.com/nl/support/model/GT-I9100LKATNL-downloads After installing this driver, your device will show up in adb devices