Develop Reference

My app won't run on LG G5. USB debugging & OEM driver are OK

I'm struggling to get my stock standard Android application ("hello world") running on my LG G5. My device is just not picked up by Android studio's deployment target window ("No USB devices or running emulators detected").
Can not understand why though because I do not pick up any usb driver issues in computer manager (G5 SE identified under portable devices without shown driver problem), and my phone's development option with USB debugging is enabled as shown by Android instructions.
Some additional guidance would help please.

First of all run adb devices (located in android sdk>platform-tools>) from command line / terminal and check if your phone is listed.
If not restart adb :
adb kill-server
adb start-server
If it doesn't work try changing USB Configuration on your phone: select MTP or PTP. You can change this from top panel when your phone is connected.
If this will show confirmation dialog with MAC address confirm it.
Your phone has to be visible by ADB before it can be visible by Android Studio.

adb devices - No device attached

I need to see my Nexus 7 on the adb devices list.
Although I enable the "" USB debugging "" on the device, but when I try to see the "" adb devices "", then no device is attached?

First you have to download Google USB Driver
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer,
and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name and select Update
Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB
Driver is located in \extras\google\usb_driver.)
Click Next to install the driver.

I know that you've already received right answer. But for those who meet the same error I advice to look for "Revoke USB debugging authorizations" in Developers options on your device. Sometimes it really helps! Especially if everything worked fine before in another OS.

Case study (on my WXP SP3... yes I still use it..), phone AllView V2ViperE, Android version 5.1:
If you continue to have no devices attached (although Android Composite ADB Interface is OK in Device Manager.. I mean without the yellow "!"), the root cause could be the adb server.. Workaround: download a new adb release (e.g: http://www.androidro.ro/descarca-si-instaleaza-driveri-adb-pentru-telefoanele-allview/).. I choose V1 Viper S.. unrar and run adb-setup-1.4.2.exe which will create the C:\adb\ directory:
C:\adb>dir
Directory of C:\adb
12/11/2016 03:23 PM <DIR> .
12/11/2016 03:23 PM <DIR> ..
10/19/2014 02:18 AM 1,009,664 adb.exe
10/19/2014 02:18 AM 96,256 AdbWinApi.dll
10/19/2014 02:18 AM 60,928 AdbWinUsbApi.dll
10/19/2014 02:18 AM 196,608 fastboot.exe
4 File(s) 1,363,456 bytes
2 Dir(s) 6,116,716,544 bytes free
C:\adb>
Now just run:
C:\adb>.\adb devices -l
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
DQBMWGSC9HT8CQ7D unauthorized
//V. in this stage allow USB debugging on the phone, then just run again:
C:\adb>.\adb devices -l
List of devices attached
DQBMWGSC9HT8CQ7D device product:V2_Viper_E model:V2_Viper_E device:V2_Viper_E
C:\adb>.\adb -d shell
shell#V2_Viper_E:/ $
Eclipse/LogCat also come alive.. Voila.. Vive la Roumanie.. Now I'm struggling with ndk debugging..

Android adb is unable to find Teclast G18 tpad for on mac os

Android adb can't detect Telcast G18 tpad for mac os. I've run
adb kill-server
to stop the adb daemon and run
adb start-server
to restart the adb daemon. But still failed to make adb recognize it?

According to this discussion on the google group, I am trying to modify the adb_usb.ini file by appending the correspondance device usb vendor id.
But how can I know which usb vendor id should I use? Fortunately, I managed to google a list of vendors for usb drivers here, in which case here, the usb device vendor id is:
vendor TECLAST 0x071b Teclast

I faced the similar problem with Teclast P79HD tablet PC built on Intel CPU. My Windows7 desktop detected the tablet which was connect via USB as an unknown USB device and I could not update its driver. The only program that helped me to revive the tablet was Adb_Run_v.3.78.65 by Vitaly Shipilov. You can download this program anywhere in the Internet. It's free.
You should act in the following way:
Install Adb_Run_v.3.78.65 on your Windows desktop.
Restart your PC.
Click Adb Run icon to start the program, then exit from the program. You should start it to start adb server. After that you will see adb.exe process via the Task Manager.
Go to Setting of your tablet, then Storage -> USB computer connection (additional settings) and check 'Media device (MTP)' in 'Connect as' section. Then connect your tablet to PC via USB cable.
After that your PC will detect the tablet as Media device (MTP). You will see the unit in the Device Manager as Android Phone. Now you can transfer files but you cannot use the tablet in debug mode when USB is connected. To resolve this problem you should act as it is described on the page:
Configuring Your Android* USB Debug Connection
See the second half of this article 'To install the Android USB debug driver on Windows 7, 8 or 10'. The driver which helped in my case was 'Android Composite ADB Interface v.4.0.0.0 [23.05.2014]' by Google, Inc. And I checked 'Camera (PTP)' in 'USB computer connection' instead of 'Media device (MTP)'. After this procedure Android Studio began detecting my tablet right and I was able to use it in debug mode.

ADB not recognising Nexus 4 - more advice

Following on from ADB not recognising Nexus 4 under Windows 7 I am having problems getting the Eclipse android development environment to recognise my new Nexus 4. My privious Nexus S had no problems.
I believe I have followed all the advice in this previous post but am still stuck.
Can anybody who has succeeded getting the nexus 4 available for android development on windows 7, tell me what their driver detail are for the "Android Composite ABD Interface"? Mine say:
* Driver Provider: "Google Inc"
* Driver Date: 27/08/12
* Driver Version: 7.0.0.1
When my phone storage is set to either PTP or MTP, I still can't see it through the eclipse "android virtual device manager".
When set to PTP, if I run the "adb devices" command described in the linked article, I do get an entry appearing in the dos box, but nothing in the "android virtual device manager" in eclipse.

The solution is to connect your device with PTP instead of MTP and, it works.
Connected devices are not visible in AVD manager. AVD manager is for emulators.
To show connected devices, you use only ADB with this command :
adb devices

This is great step by step tutor for it:
http://androidsecurity.wordpress.com/2013/06/05/install-google-nexus-4-adb-usb-drivers-on-windows-android-studio/

Uninstall the device driver completely from Windows and re-install it.

If you dont see the device in the Devices lists:
First, you need to make sure USB debugging is enabled on your device. Settings->DeveloperOptions: Turn on debugging and enable USB debugging. Ideally, you will install the USB drivers from google, and it will work fine: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver. There are some cases that new installation may mess up the device connection. You may want to try these:
It may lost the connection, so you can try:
adb kill-server
adb start-server
adb devices
Updating to new tools may mess up the settings:
Go to Storage Options and try to set as Media(MTP) or Camera(PTP) connection. Swtiching to one of them will help
Revoke authorizations, disable usb debugging and then enable

Your Nexus 4 isn't a virtual device, so won't show in Virtual Devices Manager.
If you open the Devices view, then you should see your Nexus 4 listed, and when you run your app it should prompt for running it on as physical or virtual device.

Android ADB doesn't see device

I'm trying to run my applications on OMEGA T107 tablet. But adb doesn't see my device. I tried almost everything.

Some of these answers are pretty old, so maybe it's changed in recent times, but I had similar issues and I solved it by:
Loading the USB drivers for the device - Samsung S6
Enable Developer tools on the phone.
On the device, go to Settings - Applications - Development - Check USB Debugging
Reboot O/S (Windows 7 - 64bit)
Open Visual Studio
I think it was step 3 that had me stumped for a while. I'd enabled developer tools, but I didn't specifically enable the "USB Debugging" but.

I tried all the ways listed on the web for a whole day, but I didn't get any solutions. Then, I followed a link and in just two minutes my problem was solved!
By the way, it's for Windows users!
Find out the vendor id of the device from device manager.
To do this, connect the OTG port to the USB port of your computer.
Go to Start Menu and right-click on “My Computer” and chose “Properties”.
Select the “Devices” option which will open “Device Manager”.
Select your device (mostly in USB devices or Other devices) and right-click and choose “Properties”.
Choose the “Details” tab and select “Hardware Ids” from the property dropdown, you can see the hardware id, in my case it was x2207 .
Open android_winusb.inf and add these lines:
;<Device name> in our case I gave MK808
%SingleAdbInterface% = USB_INSTALL, USB\VID_2207&PID_0010&MI_01
%CompositeAdbInterface% = USB_INSTALL, USB\VID_2207&PID_0010&REV_0222&MI_01
Open C:\Users\.android\adb_usb.ini and add the following entry
0x<device id> .. in our case it is 0x2207
Restart ADB by
adb kill-server
adb start-server
Now ADB should recognize the device.

I had same issue, none of the solutions worked for me.
Open Settings Menu -> Developer Options -> USB Debugging should be on
Android 11
Settings -> System -> Developer options -> USB debugging

The normal way to fix this is indeed to restart the adb server :
adb kill-server
adb start-server
then
adb devices -l
should list connected devices
But it possible that it doesnt fix the problem. It appends to me.
I had to disable/enable the debug mode on the device, and then restart adb server.

On Windows it is most probably that the device drivers are not installed properly.
First, install Google USB Driver from Android SDK Manager.
Then, go to Start, right-click on My Computer, select Properties and go to Device Manager on the left. Locate you device under Other Devices (Unknown devices, USB Devices). Right-click on it and select Properties. Navigate to Driver tab. Select Update Driver and then Browse my computer for driver software. Choose %ANDROID_SDK_HOME%\extras\google\usb_driver directory. Windows should find and install drivers there. Then run adb kill-server. Next time you do adb devices the device should be in the list.

Not all USB cables can transfer data. Try using a different USB cable if your device is charging, but doesn't establish a connection to your machine.
Read more: How to tell a USB charge-only cable from a USB data cable - Dignited

What operating system are you on? If you running Windows you will want to make sure you have the drivers. You should also make sure that your Android SDK Manager is not only installed, but it also contains some additional things for different devices. Not sure if yours is in there or not.
Make sure that your phone has debugging enabled. I found myself having to run
adb kill-server
adb devices
often.

On windows, you will need to install drivers for the device for adb to recognize it. To see if the drivers are installed, check the device manager. If there is any "unrecognized device" in the device manager, the drivers are not installed. You can usually get the adb drivers from the manufacturers.

For Windows 8 64 bit with a Nexus 10 device, this worked for me:
https://github.com/koush/UniversalAdbDriver
It has a link at the bottom to this:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi

It worked for me in my Astro Tab A737
Download and install PdaNet+ from http://pdanet.co/a/ in your computer.
follow all steps in the wizard while installing .Once the drivers are installed Android studio should recognize the tablet.
Also, make sure the device is in PTP mode.

Uninstalling all old "Android ADB Interface" drivers that were installed previously and then installing the new one worked for me.

Debugging needs to be enabled on the target device in order for adb to see it.

Intel has a peach of an article on this. It's all the same driver. It's just a Device ID mismatch in the Inf file which can be edited, or Windows forced to Install the driver we point it to. Intel's article is very thorough and takes care of every hurdle you come across. The link - https://software.intel.com/en-us/xdk/docs/installing-android-debug-bridge-adb-usb-driver-on-windows

Keep in mind while you connecting device Android propose to select one of possible connection options.
In my case:
File transfer
Power charging
Media
Not all types of connection will work with ADB. In my case need to select Power charging to be able to connect to ADB

Go to Device Manager
Right-click Android Composite ADB Interface
Uninstall devices
Right-click your LocalPC then select Scan for hardware changes
Your device should be enabled
Open Command Prompt
adb kill-server
adb start-server
adb devices