Menu
Enable USB Debugging on Android 5.0 to 7.0 Enabling USB Debugging on Android such as Samsung Galaxy S8/S7/S7 Edge, LG G6, etc with the system of Android Lollipop/Marshmallow/Nougat is almost the same as that of Android 4.2.x. Jul 11, 2018 Debugging Tools for Windows supports kernel debugging over a USB 2.0 cable. This topic describes how to set up USB 2.0 debugging manually. The computer that runs the debugger is called the host computer, and the computer being debugged is called the target computer. Publisher's Description. Debugging Tools for Windows is a set of extensible tools for debugging device drivers for the Microsoft Windows family of operating systems. Debugging Tools for Windows supports debugging of applications, services, drivers, and the Windows kernel. User-mode programs and kernel-mode programs. Live targets and dump files. Local and remote targets.
If your workstation is running Linux* or Apple* OS X* you already have the necessary USB drivers installed and can safely skip the instructions on this page. In that case, please see Configure USB Debug for Android* for help confirming that your Android USB debug connection is configured and working properly.
If you are using a Microsoft* Windows* development system and are having trouble making your Android* USB debug connection work, you may need to install the Android Debug Bridge USB driver onto your Windows machine, and then connect that driver to your Android device.
For each new Android device that you attach to your Windows machine you will need to repeat the steps described on this page, starting with the section titled Verify that USB debugging is enabled on your Android device to connect the Android USB debug driver to your new Android test device.
A video tutorial is also available below (or at Windows ADB Driver Install for the Intel XDK). The video walks you through the steps necessary to install and configure the Windows Android ADB debug driver so you can debug your app on a USB-connected Android device using your Windows development machine.
The following video shows how to install the Android adb debug driver for use with the now retired Debug tab. These instructions also apply to using remote Chrome DevTools to debug your USB-connected Android device. Watch from ~1:30 thru the 10 minute mark of the video to see the driver installation process.
https://software.intel.com/en-us/videos/windows-adb-driver-install-for-the-intel-xdkGetting started:
To determine if you have the ADB debug driver already installed and configured for use with your Android device, try performing the Chrome browser test described on this page. If that test passes your device is ready to use for USB debug; if not, follow the instructions below to install the Android ADB debug driver and configure your Android device for use as a debug and test device.
The official instructions regarding how to install the Android USB debug driver are available on the Install OEM USB Drivers page of the Android Studio site. However, you may find that those official instructions leave you no better off than when you started..
..instead of using the official Android developer instructions, we recommend that you read on…
If you saw a dialog box similar to the following (after you attached your Android device to your Windows workstation) indicating that USB drivers have been successfully installed for your Android device, you do not yet have the ADB USB debug driver installed for your Android device! This message was simply telling you that the Android MTP and/or PTP drivers were installed.
The driver installation that generated the dialog shown above was a Media (MTP) or Camera (PTP) device driver that provides access to your Android device’s files and photos. It does not provide debug services. See this Android USB Connections Explained for more information regarding MTP and PTP connection modes.
Install the 'Intel USB Driver for Android Devices' on Windows:
If you previously performed this step for another Android device, and you can debug over USB with that Android device, you do not need to install this USB driver a second time. You can go directly to the next section and verify that USB debugging is enabled on your Android device.
You must be a member of the Administrator group or be logged in as Administrator on your Windows development system to perform the operations described below.
- Disconnect your Android device from your Windows workstation (remove the USB cable)!
- Go to the Intel USB Driver for Android Devices page.
- Click the Download Now link.
- Accept the terms and conditions of the download license agreement.
- Click the Download Now link that appears after accepting the license agreement.
- Unzip the contents of the ZIP file you downloaded (e.g.,
IntelAndroidDrvSetup*.zip
), which should contain a single installer named something like IntelAndroidDrvSetup*.exe (the precise name of the file is version dependent). - Run the installer you extracted from the ZIP file on your Windows development system.
- Be sure to click Yes if you are presented with a “User Account Control” dialog asking for permission to “allow this app to make changes to your PC?”
- Follow the install prompts and accept the license agreement.
- Insure that the Intel Android device USB driver is checked and select Next.
- Accept the default install location and select Install.
- If you are asked “Would you like to install this device software?” click the Install button.
- Select OK when the install is finished.
- Select Finish to exit the installer.
See this Detailed Step-by-Step Instructions to Install the Intel USB Driver for Android Devices on Windows for an illustrated set of the above instructions.
Verify that USB debugging is enabled on your Android device:
- Disconnect your Android device from your Windows workstation (remove the USB cable)!
- Find the Settings > Developer options configuration screen on your Android device.
- If Developer options is not visible, select Settings > About device and tap the Build number item seven times. Return to the Settings screen and Developer options should now be visible.
- Enable the USB Debugging option from within Settings > Developer options. Enabling this function automatically launches remote debug mode on your Android device when a USB connection is made with your development system.
Detailed instructions for enabling USB debugging on your Android device can be found in the Enabling On-device Developer Options section of the Run Apps on a Hardware Device page on the Android Studio site.
Sep 03, 2017 Download Data Matrix Excel Barcode Generator 2019 offline setup installer 64 bit and 32 bitlatest version free for windows 10, Windows 7 & Windows 8.1. The Native Data Matrix Barcode Generator for Microsoft Excel provides barcoding capability to Microsoft Excel Spreadsheets with an embedded VBA macro making it easy to share sheets without needing to distribute additional fonts. Generate Free Barcodes Online. Linear Barcodes, 2D Codes, GS1 DataBar, Postal Barcodes and many more! This online barcode generator demonstrates the capabilities of the TBarCode SDK barcode components. TBarCode simplifies bar code creation in your application - e.g. In C#.NET, VB.NET, Microsoft ® ASP.NET, ASP, PHP, Delphi and other programming languages. Data Matrix Data Matrix. 2D barcodes such as Data Matrix are capable of encoding a great amount of data in a small space, and require only one scan to capture all data elements. Linear barcodes require separate scans for each symbol on a label and take up much more space. Apr 23, 2018 Apr 23, 2018 Peninsula produce professional Datamatrix creation software for use in other applications as artwork or in Filemaker databases. Barcode produces not only all the Datamatrix barcode types but also over a hundered other barcode types including all the GS1 barcodes, and specialist codes such as Databar and LAETUS. Datamatrix barcode software.
Enable the Intel USB Driver for Android Devices:
There is, in fact, only one Android USB debug driver (written by Google). The only difference between the various USB debug drivers provided by Android device manufacturers is the device ID in the driver INF file that indicates to Windows that “this driver belongs to that device.” As part of this install procedure we are going to override device ID mismatches and force the Intel ADB driver you downloaded and installed on your Windows workstation to be used with an Android device that has a different device ID.
- Connect your Android device to a USB port on your Windows workstation.
- Right-click Computer on your desktop, or in Windows Explorer, and select Properties.
- Select Device Manager on the left side of the Properties pane. (Alternatively, you can start the Device Manager by typing
mmc devmgmt.msc
at a Windows command prompt.) - Locate and expand Other devices in the Device Manager.
If you don’t see Other devices in the Device Manager your Android device and USB debug driver may already be configured and ready to use, or your USB cable is bad. You can try the Chrome desktop browser test described on this page to see if your device is being recognized for debug.
- Right-click the device name (e.g., Nexus 5 or Android Tablet or ADB Interface, etc.) and select Update Driver Software… This will launch the Update Driver Software wizard.
- Select Browse my computer for driver softwareat the bottom of the dialog box.
- Click Let me pick from a list of device drivers on my computerat the bottom of the dialog box:
- Search for and select Intel Android Device from the 'Common hardware types' list. If you have only installed the Intel USB driver (above) you will only find the Intel Android Device; however, if you have previously installed another manufacturer’s ADB driver you may also see ADB Interface, Android Phone, Android or other names in this list. These other options can also be used, because they use the same USB driver files; for simplicity, select the Intel Android Device.
If you see none of the above options you may have to select Show All Devices (at the top of the list) and then click the Next button to get a complete list of device drivers installed on your system. Please be patient when selecting Show All Devices, it can take a few minutes to populate the list.
- Select a Model from the list of available drivers (see below). If you selected the Intel Android Device, in the prior step, the driver Model you need will be at the bottom of the list: the Intel Android Composite ADB Interface. If you selected some other manufacturer's Android device you should find a variant of Android Composite ADB Interface as a choice.
- When you select one of these “non-matching” ADB drivers you will get a warning message, because the ID of the driver does not match that of your connected Android device. Click Yes to ignore the warning and confirm that you wish to use this driver with your Android device.
- Click Next to install the driver.
- Close the 'successfully updated' driver installation dialog.
If the procedure above was successful, you should now see something similar to the following when you inspect the Device Manager with your Android test device attached via USB (the precise name of this 'interface' under the Android Device may vary as a function of the ADB debug driver you used, but it should say something about 'ADB'):
NOTE: If you change your Android device's USB connection mode from MTP to PTP (or vice-versa) you may have to follow the process above again (starting with the section titled Enable the Intel USB Driver for Android Devices) to reconnect the USB driver with your Android device. There is nothing wrong with your Android device or your system, if this happens; it simply is required with some Android devices.
Now, try the Chrome desktop browser test described on this page to confirm that your Windows workstation can communicate with your Android device. You may have to confirm an “Allow USB debugging?” message on your Android device after it is recognized by your workstation.
Still not working?
If none of this worked, see the first two instructions of this article titled Android Won’t Connect To Windows Over ADB? Fix It In Three Easy Steps for instructions on how to remove problem Android USB drivers from your system so you can start over. Do not follow the third step in that article, use the process outlined above to finish the process!
Usb Debugging Windows 7 64
You may need to go through this process again each time you connect a new Android device (especially devices from a different manufacturer). In that case, if you have previously installed the Intel or Google or Samsung or some other Android USB debug driver, you can select that driver from the available list of drivers and it will work with your new device.
If none of the above worked, and you have Android Studio installed on your system, you can try these instructions.
For more complete information about compiler optimizations, see our Optimization Notice.
-->Debugging Tools for Windows supports kernel debugging over a USB 2.0 cable. This topic describes how to set up USB 2.0 debugging manually.
The computer that runs the debugger is called the host computer, and the computer being debugged is called the target computer.
Debugging over a USB 2.0 cable requires the following hardware:
- A USB 2.0 debug cable. This cable is not a standard USB 2.0 cable because it has an extra hardware component that makes it compatible with the USB2 Debug Device Functional Specification. You can find these cables with an Internet search for the term USB 2.0 debug cable.
- On the host computer, an EHCI (USB 2.0) host controller
- Automatic shutdown timer windows 10. On the target computer, an EHCI (USB 2.0) host controller that supports debugging
Setting Up the Target Computer
- On the target computer, launch the UsbView tool. The UsbView tool is included in Debugging Tools for Windows.
- In UsbView, locate all of the host controllers that are compatible with the EHCI specification. For example, you could look for controllers that are listed as Enhanced.
- In UsbView, expand the nodes of the EHCI host controllers. Look for an indication that a host controller supports debugging, and look for the number of the debug port. For example, UsbView displays this output for an EHCI host controller that supports debugging on port 1.Note Many EHCI host controllers support debugging on port 1, but some EHCI host controllers support debugging on port 2.
- Make a note of the bus, device, and function numbers for the EHCI controller that you intend to use for debugging. UsbView displays these number. In the preceding example, the bus number is 0, the device number is 29, and the function number is 7.
- After you have identified the EHCI controller and the port number that supports debugging, the next step is to locate the physical USB connector that is associated with the correct port number. To find the physical connector, plug any USB 2.0 device into any USB connector on the target computer. Refresh UsbView to see where your device is located. If UsbView shows your device connected to the EHCI host controller and port that you identified as the debug port, then you have found a physical USB connector that you can use for debugging. It could be that there is no external physical USB connector that is associated with a debug port on an EHCI controller. In that case, you can look for a physical USB connector inside the computer. Perform the same steps to determine whether the internal USB connector is suitable for kernel debugging. If you cannot find a physical USB connector (either external or internal) that is associated with a debug port, then you cannot use the computer as a target for debugging over a USB 2.0 cable.Note See this remark for an exception.
Important
Before using bcdedit to change boot information you may need to temporarily suspend Windows security features such as BitLocker and Secure Boot on the test PC.You can re-enable Secure Boot once you’re done debugging and you’ve disabled kernel debugging.
- On the target computer, open a Command Prompt window as Administrator, and enter these commands:
- bcdedit /debug on
- bcdedit /dbgsettings usb targetname:TargetName
where TargetName is a name that you create for the target computer. Note that TargetName does not have to be the official name of the target computer; it can be any string that you create as long as it meets these restrictions: Audio editor studio free download.- The string must not contain “debug” anywhere in the TargetName in any combination of upper or lower case. For example if you use “DeBuG” or 'DEBUG' anywhere in your targetname, debugging will not work correctly.
- The only characters in the string are the hyphen (-), the underscore(_), the digits 0 through 9, and the letters A through Z (upper or lower case).
- The maximum length of the string is 24 characters.
- If there is more than one USB host controller on the target computer, enter this command:Windows 7 or later
bcdedit /set '{dbgsettings}' busparamsb.d.fwhere b, d, and f are the bus, device, and function numbers for the host controller. The bus, device, and function numbers must be in decimal format (for example, busparams 0.29.7).Windows Vista
bcdedit /set '{current}' loadoptions busparams=f.d.fwhere b, d, and f are the bus, device, and function numbers for the host controller. The bus, device, and function numbers must be in hexadecimal format (for example, busparams=0.1D.7). - Reboot the target computer.
Setting Up the Host Computer
- Verify that the host computer is not configured to be the target of USB debugging. (If necessary, open a Command Prompt window as Administrator, enter bcdedit /debug off, and reboot.)
- On the host computer, use UsbView to find the EHCI host controllers and ports that support debugging. If possible, plug one end of the USB 2.0 debug cable into an EHCI port (on the host computer) that does not support debugging. Otherwise, plug the cable into any EHCI port on the host computer.
- Plug the other end of the USB 2.0 debug cable into the connector that you identified previously on the target computer.
Starting a Debugging Session for the First Time
- Determine the bitness (32-bit or 64-bit) of Windows running on the host computer.
- On the host computer, open a version of WinDbg (as Administrator) that matches the bitness of Windows running on the host computer. For example, if the host computer is running a 64-bit version of Windows, open the 64-bit version of WinDbg as Administrator.
- On the File menu, choose Kernel Debug. In the Kernel Debugging dialog box, open the USB tab. Enter the target name that you created when you set up the target computer. Click OK.
At this point, the USB debug driver gets installed on the host computer. This is why it is important to match the bitness of WinDbg to the bitness of Windows. After the USB debug driver is installed, you can use either the 32-bit or 64-bit version of WinDbg for subsequent debugging sessions.
Note The USB 2.0 debug cable is actually two cables with a dongle in the middle. The direction of the dongle is important; one side powers the device, and the other side does not. If USB debugging doesn’t work, try swapping the direction of the dongle. That is, unplug both cables from the dongle, and swap the sides that the cables are connected to.
Starting a Debugging Session
Using WinDbg
On the host computer, open WinDbg. On the File menu, choose Kernel Debug. In the Kernel Debugging dialog box, open the USB tab. Enter the target name that you created when you set up the target computer. Click OK.
You can also start a session with WinDbg by entering the following command in a Command Prompt window, where TargetName is the target name you created when you set up the target computer:
windbg /k usb:targetname=TargetName
Using KD
On the host computer, open a Command Prompt window and enter the following command, where TargetName is the target name you created when you set up the target computer:
kd /k usb:targetname=TargetName
What if USBView shows a debug-capable port, but does not show the port mapped to any physical connector?
On some computers, USBView shows a debug-capable port, but does not show the port mapped to any physical USB connector. For example, USBView might show port 2 as the debug port number for an eHCI controller.
Also, when you use USBView to look at the individual port, it is listed as debug-capable.
But when you plug in a USB 2.0 device (like a flash drive) to all the USB connectors on the computer, USBView never show your device connected to the debug-capable port (port 2 in this example). USBView might show the external connector mapped to a port of an xHCI controller when in fact the external connector is mapped to the debug-capable port of the eHCI controller.
In a case like this, you might still be able to establish kernel-mode debugging over a USB 2.0 cable. In the example given here, you would plug your USB 2.0 debug cable into the connector that shows as being mapped to Port 2 of the xHCI controller. Then you would set your bus parameters to the bus, device, and function numbers of the eHCI controller (in this example, 0.29.0).
bcdedit /set '{dbgsettings}' busparams 0.29.0
Additional Support
For troubleshooting tips and detailed instructions on setting up kernel debugging over USB, see Setting Up Kernel Debugging with USB 2.0.