Related
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 have recently bought a HTC Nexus 9 tablet for the purpose of USB debugging in Android Studio. This process works on other computers at university but I cannot get it to work properly from my home system,which is what I require. I have tried every single suggestion I have came across online but none have actually worked.
Steps Tried:
Downloading the latest google USB Driver
Installing it through Android Studio and Manually in device manager
Tried ADB Interface Driver and ADB Composite Interface Driver
Configuring driver inf file by adding hardware ID's
Ensuring usb debugging is enabled on the device
Using different USB ports,3 different cables
Tried connecting in PTP mode,MTP mode,charging only mode
Rebooted device and computer
Re installed android studio
No matter what I do,the device wont be shown in android studio or ADB.exe(under list all devices in terminal,also tried start and kill server). I am officially out of ideas,if anyone could figure this out I would be forever grateful!
I have attached some images of some of the things I have tried without success. Once driver has been installed it is listed as "Android Composite ADB Interface" or "Android ADB Interface". Operating system is Windows 7 64-bit
Device on first plug in
Picking a driver
Download HTC PC suite from following link ,install and give a try
http://pc2.software112.com/getfreesw/231109-1805719/htc-pc-suite-07.html
I personally have had many issues with setting things up for Android. Things you should ensure you do include;
Ensure you obtain the appropriate packages in the SDK manager - for example, I wasn't able to make logcat work when debugging with my phone until I downloaded the files for my specific version of Android (so the API files for a Nexus 9).
I believe you may also have to download drivers for your actual phone to allow connection - you should be able to download this from the HTC website. This might be what you need, although I haven't checked it out, and I cant find where I downloaded my drivers from;
http://forum.xda-developers.com/showthread.php?t=2217396
In general, you want to download lots of things from the SDK manager as you'll need them anyway, so don't hold back on just downloading them.
For those (like me) who is still concerned with this issue. You need to go to win+pause break ->Device Manager->Find "AdbInterface" with exclamation sign->Update driver->Search manually->Specify USB driver downloaded from SDK and enjoy: C:\Users\username\AppData\Local\Android\Sdk\extras\google\usb_driver
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
Okay so the facts:
I have been developing for Android device (Samsung Galaxy S3 Mini GT-I8190) in my PC for the last half year.
When i installed the developing tools, android SDK, eclipse, etc, all was like "plug and play"
It was easy and worked verry well.
So some days ago i just realised Eclipse shows my device NO MORE, here is how i tried to solve this issue in chronologic sorting:
Tried to replug my device
Tried to restart eclipse
Tried to restart device
Tried to restart PC
Tried to uninstall USB drivers and reinstall via Kies (I have tried
the old Kies, it has installed a driver which was not worked.)
I tried to update my Kies to a newer version and install the usb
driver again, not helped.
I tried with the new Kies 3, and it says that this version does
not recognise my device.
I tried to uninstall Kies, uninstall the the usb driver and download
a simple SAMSUNG driver file, so basicly i tried to install it
without Kies, not helped.
I tried to reinstall Windows 8.1 (yes, i made a whole system reinstall for this, which is not helped)
I tried to download Google usb drivers from SDK manager, not helped
I tried some commands to adb like "kill server" "starts server"
I tried to manually update driver from MyComputer's manage menu, not
helped.
I have made a factory reset on my device.
My computer sees my device so i can trasfer files. Developer mode is on.
Running adb devices output is empty, so i cannot see my device in list.
So here i am at a projects deadline with a mystery and i cant get it work.
Whoever solves this gets 500 reputation from me. Im not kidding, this is all i can offer.
E D I T:
Tried everything mentioned below. Is it possible that my phone or my PC's hardware makes this mess?
Try this :
Right click on My Computer --> Properties --> Device Manager --> Right Click on your device --> Update driver software --> Click on " Browse my computer for driver software --> Give path of your android sdk like "D:\Android_Sdk\sdk\extras\google\usb_driver" and tick "Include subfolders" --> Click next
Now repeat the steps till "Browse my computer for driver software".
Then click on "Let me pick form list of device drivers on my computer -> Click on the first option and click next and then click yes.
Drivers will be installed for your device.
This works for me.Hope this helps.
Try this process :-
1.Uninstall previously installed drivers and close eclipse
2.Connect your device with USB storage & USB debugging in Developers options on
3.Go to find new hardware wizard in you computer
4.Install Drivers including adb from there by selecting your device
5.After that restart eclipse , your device might be detected
These steps worked for me when i faced the same problem but my device was different , hope this works for you
As you hav tried every method now try Universal Naked Driver 0.72 removing previously installed drivers.
Universal Naked Driver works for most of the devices.
another alternative UniversalAdbDriver
Also check your supply USB port too, if u pass on a hub usb disconnect of this and link to pc directly.
follow this:
1 . find in SDK Manager --> Extra --> Google USB Driver -->install.
2 . please install samsung kies3 in your system . and connect your device with it then try ..it will work 100% . also tell me which target version you r using in your project if it 19 API level and your mobile is 17-18 API level then it ADT will not give u permission to run (not show you your device in android device choose dialog )
The answer is mindf. itself.
Today i asked my friend to test this problem with his device, (he's got a very same galaxy s3 mini device) and what i found was really blown my mind.
Eclipse does see his device, but not mine.
**
Yes, two identical, very same product and mine is invisible for Eclipse.
**
I just cant find words...
(It happened to me today after the updating from 22.3 to 22.6)
Verify " AndroidManifest.xml > Manifest Extras > Uses sdk > Min SDK Version " suits your device.
I was using my Samsung Galaxy S3 Mini GT-I8190L and I forgot that the minimum SDK for mine is API 16 (for Android v4.1.2). I fixed the number and now everything it's ok.
Try installing UniversalAdbDriver. It worked perfectly for me (GT-I8190).
I have tried connecting the USB debugger on Samsung Galaxy S2 and Samsung Galaxy Nexus. It still manages to fail on both devices. At the moment I am using Windows XP and I am running out of ideas.
Here is what I tried:
Installed SAMSUNG_USB_DRIVER_FOR_MOBILE_PHONES_1.4.8.0.exe
Searched and tried to install the drivers on Google drives.
Has anyone have this similar problem and could share a solution?
EDIT* Both devices Samsung Galaxy S2 and Samsung Galaxy Nexus are able to connect to the PC but not to the debugger. Drivers installed with different variances even done installing Samsung Kias.
I am adding a bounty tomorrow for 50 reps. I really need to test what I am doing on an actual phone.
You need to download Samsung Kies I know that the software description doesn't mention that it is the correct drivers for developers, but it in fact is.
An old issue used to be:
Use the USB2.0 ports on the back of the PC not the 1.0 front facing port.
I feel you have not installed sdk properly. Reinstall the http://dl.google.com/android/installer_r18-windows.exe, the open the adb and update all the things for the particular sdk you want.
Then verify that you have given the exact location of sdk in eclipse>window>preferences>android
Then restart eclipse.
Even you cant open it then set environment variables. For that add following ;E:\android-sdk-window\platform-tools; in PATH. Then restart windows.
After that try adb devices, adb kill-server command in Command prompt.
You will be able to see your device.
Is there any "ADB interface" devices in your PC's Devices Manager?
If you are using DDMS,Maybe there is a console(cmd.exe) window behind DDMS,you can get some log there.
Did you enable the debug mode on your device? This is not listed in the steps you followed.
Go to Settings -> Applications -> Development -> and set USB debugging.
You can use PdaNet software to connect your device for debugging. I was have the same issue and resolve with using this software. Use the following link to download this software:
http://junefabrics.com/android/download.php
I also have samsung Galaxy SII and i face the Same Problem before some days. But now i am able to get debug the app in My SII.
Please follow the steps and make sure that you follow it completely then only you cna able to get debug in your phone.
First select the Option to Install App from Unknown Sources.
You will find that option in Setting -> Applicatios -> Unknown sources. Select it as yes.
then Select the Option like USB Debugging.
You will find that option in Setting -> Development -> USB debugging. Select it as yes.
Now, Install latest Samsung Kias In your PC. Reboot Your PC, Eclipse and may be Phone also
Now, Try with connecting the Device.
Hope you will get debugging your app in to your phone.
If not then let me know which trouble you get.
Enjoy. :)
My phone has this:
Settings -> SD card & phone storage -> Mass storage only (USB connection mode is mass storage only)
Make sure that this option is NOT checked. If it is u can enable USB debugging and unknown sources and it still wont work.
If you just need to connect to the device for install and debugging you can manually select the driver to use when you plug it in.
Don't let windows search for it, choose I will pick the driver from a list, then select android composite ADB interface. It may warn you that this driver doesn't match, but it works!
I also had many problems to get samsumg galaxy S2 work on my pc. If I remember correctly finally I ended up installing Samsung Kias and installed some drivers through there. Then restarted the computer and never launched kias from then on. My phone is still not visible form command line adb devices, but now I can develop in Eclipse and deploy on the device without any problems.
From time to time I lose connection to the device (E.g. if another device was plugged in). Then I need to restart Eclipse and my device becomes visible again.
Some friends of mine also shared that some other mobile device usb drivers were conflicting with the samsung drivers (it was ZTE if I am not wrong). They uninstalled the ZTE drivers and then got the Samsuung running ok too. Try consider uninstalling all other usb drivers before you try the Galaxy S2.
Have you installed exactly the right SDK version for the phone you're using?
Given that you can access the phone on the PC via KIES, I assume that you have all the correct USB drivers installed.
Ensure that debugging is enabled on your phone. This can be done from the Settings preferences.
Install the Android SDK. Add %ANDROID SDK_INSTALL_PATH%/platform-tools to your path.
If everything is working up to this point, plug in your phone and execute the following from the command line.
adb devices
and you should see your device listed.
Install the Android Developer Tools plugin in Eclipse.
Create/Import your project.
Right click your project and from the context menu, select Debug As --> Android Application
I have had exactly the same problem as you, I even gave up on developing for 2 months because of this. I have just started again and really needed to get this working.
I tried all of the above and pretty much every combination of the above and still failed.
I have just got it working by not doing anything different apart from when I uninstall the old USB driver (add remove progs), the next time I installed AGAIN, I used the SAMSUNG USB Driver for Mobile Phones V1.3.450.0 (an older version than ones suggested on other help forums, I just got it by accident somewhere and thought I'd try it). The next time I plugged the phone in, it did all the usual finding CDC etc. that it always did when it failed...but then.... it asked for the ADB Driver, WOW! I got excited. I just selected Install Automatically and away it went.
I still already had the PDANet thing running and that popped up saying a connection is available. I've not used it though because it wouldn't install on my phone anyway.
FYI, I have these settings on the phone:
USB debugging ON (obviously)
Allow Mock Locations OFF
Unknown Sources ON
I hope this helps.
Dan.
This may not help at all since you have probably tried it already but I had huge issues on two different windows 7 machines getting my s2 to connect for debugging.
I ended up getting one working by plugging in the s2 USB connection, un-installing the drivers for it in the device manager, unplugging the USB connection, un-installing Kies, downloading the most up to date version of Kies, installing that and plugging it back in.
The other one was even more painful, it was a while ago now but I did the same as the above but removed eclipse and the Android SDK as well, installed the latest version of Kies first, the eclipse, then the sdk and made sure all of that was done before I plugged the phone in.
I faced same issue which you faced..
I solved this by this way.
1) Right click on my computer and select Manage
2) Then select Device manager..
3) connect your phone (galaxy s2 in my case)
4) I found one device with named "unknown" in sub option I foung my phone name i9100
5) Then right click on that and select update driver software
6) you will see then this..
Tadaa....Done :)
Hope this will help you also..