I'm developing an android app with Xamarin and Visual Studio 2013. I have connected my android applet to the computer. Sansung Kies recognizes the device. Adb recognizes it also because when I type "adb devices" the device appears in the list. But when I debug the app Visual Studio doesn't let me choose my device, it only proposes to me to use the android virtual emulator. In my device the "USB debug" option is enabled. So what am I doing wrong?
EDIT
Just got a new machine and ran into the same problem.
Following these steps:
http://visualgdb.com/KB/usbdebug-manual/
as suggested by Veverke in the comment below fixed the issue for me.
just had the same issue and fixed it with a combination of these two links. Obviously our issue isn't the exact same issue that's listed in the first link but that's why I had to use both to kind of synthesize a solution.
https://web.archive.org/web/20140410204811/http://krumelur.me/2014/01/30/xamarins-visual-studio-plugin-missing-android-devices-genymotion-and-parallels-desktop-dont-panic/
http://developer.android.com/tools/extras/oem-usb.html
Basically, in Visual Studio 2013 start the Android SDK Manager. Scroll all the way down to the 'Extras' folder, where you will find the 'Google USB Driver'. Mine was already installed, so I deleted the package, confirmed I wanted it deleted, then reinstalled it.
Then, I opened Windows Explorer and right clicked 'Computer', then clicked 'Manage' (need Admin priviledges). In the newly opened Computer Management window I clicked 'Device Manager' under Computer Management > System Tools in the hierarchy on the left.
In the main window, I expanded 'Other Devices' and saw the device I was looking for. I right-clicked it and chose 'Update Driver Software', then 'Browse my computer for driver software'.
Now you need to hit Browse... and find where you installed the packages.. for myself it was under
C:\Users\zumberge\AppData\Local\Android\android-sdk\extras\google\usb_driver.
Click next, the you need to choose to accept Google, Inc. as a trusted source.
Then the process should be finished and you'll be good to go.
Don't know if you need to restart VS2013, but I did for good measure.
Hope this helps and it's not too late.
For VS 2015, LG Nexus 4 and Windows 7, following solution works for me.
Debugging On and Off during the running instance of Visual Studio, your physical device appears in the device list.
Restart of Visual Studio 2013 has resolved the issue for me.
Details:
Visual Studio was open while I was trying to make the device visible to the system.
After installing the device driver, I have restarted the "adb" and saw that the device is added to the list "adb devices".
However the name of the device at the Visual Studio was not changed, some numbers.
After restarting the Visual Studio, real name of the device is shown "NVIDIA Shield Android TV.."
Then I did not get this error anymore.
I just ran adb command prompt and hit 'adb devices' and it showed daemon was not running. It installed itself and now i can able to see android devices there.
C:\...\...\source\repos\ABC\ABC\Ex.Android>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZF22Q3T unauthorized
After enabling debug mode on my android device, I found I had to change the 'USB PC Connection' option. It was set to 'Charge Device'. When I switched it to 'Media Sync (MTP)' and reconnected to my PC it then showed up in Device Manager, but the drivers did not appear to be working with VS. I reinstalled the 'Google USB Driver' in SDK Manager. I removed my device in Device Manager and added it back using the Google USB Driver. When I disconnected/reconnected the device to my PC, Windows asked what I'd like to do with the device. I realized the first time it had asked me, I quickly clicked 'Do Nothing'. This time I noticed the first option was to run an exe on the device to install the driver. After the install completed I disconnected/reconnected the device and the device prompted me to allow my PC to debug. After selecting 'Allow', the device showed up in VS while VS was already open.
Also make sure you have the correct configuration selected for your device. (eg. ARM for most smartphones)
If its set to one that your device doesn't support, then the device won't show up even if adb can see it. Simply switching the configuration solved the problem for me.
Try restarting adb server using:
select "Tools" from top bar then
select "Android". In the list there will be an option to restart adb server as "Restart Adb Server".
After clicking it everything works fine.
It worked for me.
I followed most of the steps mentioned, but still couldn't get it to work. Some things I did were:
download and install google driver from android sdk manager
locate the device in windows device manager and update driver (pointed to the google usb driver)
switch usb connection from mtp to ptp
restarted visual studio
restarted computer
Finally, what worked for me was googling the drivers for my particular android device (lg g4) and landing on this site . Once I installed the drivers I was immediately able to debug in visual studio using my device. it works whether the usb connection is mtp or ptp.
http://www.andromods.com
In case you are using Samsung and have MyKnox installed, you cannot enable USB-Debugging until you uninstall MyKnox as stated in This Link
Related
I am using a brand new xamarin.forms solution generated with the flyout shell template in VS 2022 community edition.
When I open the emulator and follow the first time setup, where it generates a common android device I get this error when trying to launch the emulator. I also get this error when creating a device myself.
Unknown AVD Name Error <- This part has been fixed by setting the ANDROID_SDK_HOME variable to the correct directory in the Environment Variables in system settings. But the emulator can still not be used for debugging.
I have tried looking around for solutions on all sorts of forums to get the emulator to work, but didn't find anything that made a difference.
I have tried running on a local device using USB instead as it was suggested that it was easier to get to work then the emulator, which didn't work either. The device does not show up in the Android Emulator drop-down menu. I then tried different cables and it still did not show up as a detected device.I then tried via wireless connection just in case something was up with the cables. It still doesn't show up. But if I check the devices through the adb command prompt I can see the device is connected and authorized, both when using the cable and when using the wireless connection. And the computer itself detects the device just fine.
The Device is in developer mode.
USB debugging is on.
The computer is approved as a trusted device.
Android project is set as start up project.
SDK's and tools have been downloaded using the Android SDK manager.
USB drivers have been downloaded for the device.
I have already tried
closing and opening VS multiple times.
Unloading and reloading the project.
Setting the device to PTP mode instead.
Reinstalling VS including deleting and regenerating the Java and Android folders.
Uninstalling VS 2022 and trying 2019 instead.
Generating a new VS solution.
downloading and installing the JDK manually.
Seeing that Virtual emulation is on in the BIOS.
Making sure the system is able to run Hyper-V and that it is on.
checking that the folder paths are set correctly in the options menu.
Making sure all nuget packages are up to date.
Any suggestions would be highly appreciated as I cannot debug and test the device properly at the moment.
If you see an error about a failure to install the APK on the emulator or a failure to run the Android Debug Bridge (adb), verify that the Android SDK can connect to your emulator. To verify emulator connectivity, use the following steps:
Launch the emulator from the Android Device Manager (select your virtual device and click Start).
Open a command prompt and go to the folder where adb is installed. If the Android SDK is installed at its default location, adb is located at C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe; if not, modify this path for the location of the Android SDK on your computer.
Type the following command:
adb devices
If the emulator is accessible from the Android SDK, the emulator should appear in the list of attached devices. For example:
List of devices attached
emulator-5554 device
If the emulator does not appear in this list, start the Android SDK Manager, apply all updates, then try launching the emulator again.
Update:
you can open the Android Device Manager first.
Select the device you want to run and click the Start button, so that the virtual machine can be started and detected, and then your virtual machine The device will be added to the Android Emulators menu.
I ended up wiping the hard-drive and starting from scratch. This time all I had to do was install VS and enable Hyper-v and everything worked as it should right away.
I have absolutely zero idea what caused this issue, but a complete wipe fixed it.
I am developing Xamarin forms app. I am not able to deploy app in nexus 6p( phone is not listed in device list ). Tried below steps, still phone is not detected.
I have installed Google USB Driver using Android SDK manager.
I have downloaded usb driver for nexus 6p and done 'Update driver software'
option in device manager under 'Portable devices' section. Device
gets displayed as 'Nexus 6p' within Portable devices section in
device manager and also seen as local drive( next to C: drive ).
Selected droid project as startup project.
But phone is not listed in visual studio device list. Any help?
Make sure the 'USB DEBUGGING' option in DEVELOPER OPTIONS remains checked on your connected Android Device.
I've lost lots of time because this item would uncheck itself for some reason between reboots/restarts and Enabling/Disabling the DEVELOPER OPTIONS.
If anyone else is still struggling with this in 2017, and your USB debugging is definitely on and it's still not appearing - I managed to fix this by turning developer options OFF then ON again from the device's settings. Also ensure that the USB option is set to:
Charging - Just charge this phone
I couldn't get any other method other than this to work. The device was then immediately detected by Visual Studio 2017 for me.
You ABD interface is not installed on your system, so first install the ABD driver from your local machine using (C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver).
And check your device is in developer mode.
If all the setting will be good then your visual studio automatically detect your device and you can start to debug your app on your device.
If you have installed VS2017 in parallel to VS2015, you also may have a look here Android devices not showed anymore in VS2015 after installing VS2017
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 having trouble running an app I am developing in Android Studio on my Nexus 7. I have successfully gotten this to work before using the same tablet and computer (running Windows 8), but since having my laptop repaired and everything wiped I'm convinced something with my dev environment is messed up.
When I go to run the project, there are no available devices, so it is not recognizing my Nexus 7 anymore.
Things I have tried
making sure my computer recognizes the device and that I have the Nexus 7 driver installed from ASUS
going to the SDK manager and ensuring I have the Google USB driver installed
closing Android Studio and re opening it, restarting my computer, restarting my Nexus 7
killing adb.exe from the task manager
ensuring I have USB debugging enabled and toggling that on and off
switching from MTP to PTP and back again (currently connected as MTP, not sure if that is correct)
Any help would be greatly appreciated. This is very frustrating and I would like to just get back to developing again.
Update- I just noticed that when I go to developer options, "Wait for debugger" (near where you toggle USB Debugging) is grayed out. I think this has something to do with it but I'm not sure how to enable it.
I got it!
This was at least the issue in my case, I hope maybe this will help someone someday, apparently I had not installed the adb driver properly:
Search for Device Manager from the search bar on the start screen
Open Device manager, click on your Android device
Select"Update Driver Software"
BOOM. Now Android Studio recognizes the device.
I know this may not be the solution for everyone, but its worth a shot if you are having trouble testing apps on your device.
Between upgrading my second-gen Nexus 7 to Android 5.0.x and Android Studio leaving beta I lost the ability to debug on my tablet.
To get this working again I used a combination of the above advice.
I grabbed a copy of the USB Driver from Asus, but updating the Device in Device Manager and pointing to the unzipped files wasn't enough.
The next step was to point Device Manager to the Android Studio sdk directory (on a 64-bit Windows 8 install that was C:\Program Files (x86)\Android\sdk - beta versions of Android Studio - or %localappdata%\Android\sdk - switched to in 1.x) and then things worked just fine again.
Another possible reason that you may not be able to connect is:
Don't forget to enable debugging mode in Android setting.
I have had the same problem, although just getting started with my Nexus 5 and windows 7. I installed google usb driver package using SDK manager first, computer recognized phone but studio could not find it. Went in to manually update driver for phone but update driver couldnt find it, downloaded driver separately and pointed it to directory path, driver installed then studio found it and ran fine.
Here is the problem. I want to run my Android Studio apps on my device (Samsung Galaxy Ace 2). But nothing works for me. Tell me what I've missed:
1) USB debugging is on
2) ADB driver is installed (in device manager i can see Android Composite ADB Interface)
3) ADB device list is still clear, even if i reset server(adb kill-server, adb start-server, adb devices - list of devices is clear)
4) in google usb driver directory, in android_winusb.inf file I added my device identificators
5) Android device manager still cannot connect to my device, showing this error when I reset it: "adb connection error an existing connection was forcibly closed by the remote host"
So I will be glad to hear any advices. Hope you'll help me
Did you try to configure the "Media Mode" in "Camera (PTP)" instead of "Media device (MTP)"? This is sometimes solving the issue. Its in the USB Computer Connection options of your Android device, you should see an "authorize" dialog then.
Update 04/2017: looks like it has been fixed in Android 7.1.2
I have done numerous ways of handling that issue. Finally it has worked! I am using LG Optimus II, but I believe the following steps are generic to other Android devices as well.
Step 1:
Make sure your device is enabled for development. If yes, go to Step 2, otherwise go to Settings > About phone and tap Build number seven times which is magic number :-).
Now Developer Options is available in the Settings.
Step 2:
Before you plug your device to PC, Go to Settings > Developer Options and select USB Connection method.
Step 3:
Plug the phone to the PC, you are given options for the USB Connection method, and please select Internet connection. Make sure you have connected to the Internet. By the way, I have changed MTP to PTP, it did not work for me. Therefore, I tried Internet connection mode, then it worked.
Step 4:
Run the app in the Android Studio, it will ask you to authorize the device for development, and select YES!.
Step 5:
Run the application via Android Studio and choose the device, not emulator, and BINGO! Welcome to Android development board.
Try swapping the USB port the cable is plugged into.
Sounds crazy but after 20 minutes of debugging this worked for me.
I also tried above solutions but got no luck. So here's what I did:
Download and install PdaNet+ to fix connection issues between my computer and android device
Enable USB debugging on my android device
Unplug the phone and plug it again after it's installed
Run my app and voila! My android device is now recognized by Android Studio
Although my computer could recognise my phone, I had to install the official drivers from the Samsung developer site to get adb/Android Studio to recognise it:
Samsung Android USB Driver for Windows
Click Revoke USB debugging authorization in Developer option and try it again.
Solution for those working with Huawei phones - You will get this error when ADB interface is not installed. Check if you have installed Huawei HiSuite. USB driver gets installed when you install HiSuite (I suppose this is true for most of the new phones that come with a Sync Software). If the ADB interface is installed on your computer you should see 'Android Composite ADB Interface' under Android Phone in your Device Manager as shown in this picture.
If you have Mi Device than you need to enable this two option after enabling Developer Mode.
USB Debugging (Enable = True)
Install via USB (Enable = True)
See this screenshot.
LG Optimus Zone 2 pp415 d\n connect in mtp, but does work in internet connection mode. Lost lots of time messing with it. There's no doc for this, but I'd suggest trying all 4 of the connection options. Only 1 that works for me is Internet Connection->Ethernet, then win 8 auto-detects a driver and installs it. In MTP mode despite all drivers being registered with device manager, adb doesn't pick it up.
I had the same problem. So here is what i did
reinstalled the device driver
changed the USB computer connection from MTP to Mass storage(UMS)
And it worked.
For me, I tried the above. Turns out my USB cable was bad. I changed the cable and then it worked.
I am sorry that i bothered you all. The problem was my device is cloned in different places in device manager. It was gone when I tried to update driver for my phone in "Other devices" list, and before i have been updating it in wrong sections. Thank you all.
In my case it was due to already running and hanged adb.exe on another user under my PC. I had two users on my PC, the second user had the adb.exe process hanged even when I tried to end the process. It worked with me after (End Process Tree) from the Task Manager.
Hope this will help someone with multiple users :)
Ahmad
In addition to the above configurations, I had to set deployment target to "Open Select Deployment Target Dialog", run once (choosing my device from the options listed), and from then on Android Studio was able to see my device even after changing the deployment setting back to "USB Device". My SWAG is that since Android Studio uses its own internal cache to find your device, it has to be initialized first.
I was on Samsung S8 and had same problem too. After I installed Samsung Kies, issues was resolved for me, as I believe it had updated the correct driver required for my Samsung S8.
On Windows 7 , the only thing that worked for me is this. Go to Device Manager -> Under Android Phone -> Right Click and select 'enable'
i had to install android studio in 2 machines and ive solved this problem intalling samnsung kies, i use 3 diferents samnsung devices (plus some other of my family and friends) and i dont have to strugle with the drivers, it works for me and i recomend it. hope it helps
For me, this ended up being because I had the wrong SDK level installed (new version of Android Studio installed the SDK for Android 10, whereas I have a device that runs only Android 8.1). While Android Studio would "recognize" the device and display a string in the "devices" menu instead of just saying that no device was connected, installing the right SDK level for my device ended up changing the string to something recognizable (my device's model name) and allowed me to actually run my app over ADB.
I had a big problem with my Samsung S10 Plus as it was not detecded by Android Studio on my Macbook even if I did all what is required to be detected, that is to say:
Enable developer mode (7 taps on Build version in Android settings)
Enable USB debugging
What I did is to start "Android File Transfer" on my Macbook and the magic happened. A popup appeared on my device asking if I want to authorize an USB access to it. I clicked "Yes, always" and now Android Studio can detect my device on my Mac :)
Change the connection method Build-In CD ROM it works for me
On HTC mini one 2, besides enabling the Developer Options, the following worked for me:
Go to More in Wireless & Networks
Mobile Network Sharing
In USB network setting
Select Internet pass-through