Windows Drivers for Android Phones

Unlock your device and connect to a PC using a USB cable (you may use the cable attached to your LG charger). Once connected, you may be prompted on your phone to select a USB connection type, select Media sync (MTP) or File Transfer. The driver it should install should be a USB midi driver, instead windows installs a USB audio driver, and also shows a yellow triangle in the device manager. I tried to install the Yamaha USB midi drivers, but the installation instructions say that I need to 'cancel' the device setup wizard which should automatically appear, so that Yamaha.

The App Inventor Setup software includes the Google USB driver, which handles the following devices:

• T-Mobile G1* / ADP1
• T-Mobile myTouch 3G* / Google Ion / ADP2
• Verizon Droid (not Droid X)
• Nexus One
• Nexus S

If your phone is one of these, then the driver should have been installed along with the App Inventor Setup software. All other devices will require you to obtain and install a USB driver from the device manufacturer. In either case it's a good idea to check the driver installation, as described below, before proceeding.

You can find links to drivers for many Android devices at http://developer.android.com/sdk/oem-usb.html . If your device is not listed, we recommend you search the manufacturer's website for information on how to install drivers for your particular phone and/or review these resources:

• Android Developers Google Group and Android Beginners Google Group: Search under terms like 'Android SDK', 'drivers', 'install', and the name of your device.
• Thread on drivers from the App Inventor community forum

Checking the driver installation:

It's been our experience that the Windows drivers do not always correctly install automatically. Here's how to check the driver:

• Open a Command Prompt window and navigate to the directory where the software was installed. For example, if you installed the Setup software as an administrator, and this is a 32-bit system, the directory should be C:Program FilesAppInventorcommands-for-Appinventor, or Program Files (x86) for a 64-bit system.
• Type the 'dir' command and check that one of the files listed is adb.exe. If it's not, then you are in the wrong directory or the software didn't install.
• Plug your phone into one of your computer's USB slots, making sure that the phone shows USB connected and USB debugging connected.
• Type the command 'adb devices'. You should see the messages 'daemon not running' followed by 'daemon stated successfully', followed by 'list of devices attached'. If there is a device in the list, something like HT99TP800054, then the phone is connected and the computer and the phone can communicate and the drivers should be OK.
• On the other hand, if the list of devices is blank, you'll have to get additional drivers, or install the existing drivers manually.

Installing the App Inventor drivers manually

The AppInventor Setup software includes the Google USB driver, as noted above. If your device is one of the ones that the driver handles, the drivers should have been installed automatically, and the driver installation should check out as described above.

If the check fails, you need to install the Google drivers manually. You can find instructions here. In following the instructions, note that you do not need to install the SDK or download the drivers again since they were included with the App Inventor Setup software, and you can find them in the App Inventor software directory in the usb_driver sub-folder of the appinventor-setup folder where the installer placed the software, for example C:Program FilesAppInventorcommands-for-Appinventorusb_driver.

The directions for installing the Google USB drivers may also help if you have trouble with a manufacturer's driver, but in general, you might need to search on the Web for help in the various Android developer forums.

Other issues

If the drivers are installed, and you see the phone listed by 'adb devices', but App Inventor still won't connect, then you should ask in the App Inventor Forum. Some devices may require special extra steps, or there may be some other issue. If you find (or solve) issues with other devices, please post to the Forum so that other App Inventor users can benefit from your experience.

Windows Drivers Installed? Now finish setting up your device.

This topic summarizes the new features and improvements for Universal Serial Bus (USB) client drivers in Windows 8.

For information about new features in USB in general, see New for USB Drivers.

New Driver Stack for USB 3.0 Devices

Windows 8 provides a new USB driver stack to support USB 3.0 devices. The new stack includes drivers that are loaded by Windows when a USB 3.0 device is attached to an xHCI host controller. The new drivers are based on Kernel Mode Driver Framework (KMDF) and implement features defined in the USB 3.0 specification. The new drivers are as follows:

• Usbxhci.sys
• Ucx01000.sys
• Usbhub3.sys

The new driver stack maintains compatibility with the existing client drivers that were built and tested on earlier versions of the Windows operating system.

To see an architectural block diagram of the USB driver stack and a brief description of the new drivers, see USB 3.0 Driver Stack Architecture.

Features Supported by the New Stack

The USB driver stack for USB 3.0 devices supports many new features. Some of features are configurable by the client driver. Those features are as follows:

• Static streams for bulk endpoints.

  Streams provide the client driver with the ability to perform multiple data transfers to a single bulk endpoint. The Windows Driver Kit (WDK) for Windows 8 provides new device driver interfaces (DDIs) that allow a client driver to can open up to 255 streams in a bulk endpoint. After streams have been opened, the client driver can perform data transfers to and from specific streams. For more information, see How to Open and Close Static Streams in a USB Bulk Endpoint.

• Chained MDLs

  A client driver can specify the payload in a chain of MDLs instead of a contiguous buffer. This allows the transfer buffer to be segmented in physical memory hence removing restrictions on the number, size, and alignment of buffers. Using chained MDLs can boost performance during data transfers because it avoids double buffering. For more information, see How to Send Chained MDL.

• Function suspend and remote wake-up for composite devices.

  The feature enables a function of a composite device to enter and exit a low-power state, independently of other functions. The function driver can also request a device-initiated remote wake-up. Such a request must be handled by the parent driver of the composite device. The Microsoft-provided parent driver (Usbccgp.sys) supports function suspend and remote wake-up features. The WDK for Windows 8 provides DDIs that allow replacement parent drivers to implement those features. For more information, see How to Implement Function Suspend in a Composite Driver.

Client contract version for USB client drivers

A client contract version identifies a set of rules that the client driver when sending requests to the USB driver stack. Failure to do so might result in an unexpected behavior. For information about those rules, see Best Practices: Using URBs.

A client driver that intends to use the capabilities of the USB driver stack for 3.0 devices, must identify itself with the client contract version of USBD_CLIENT_CONTRACT_VERSION_602. Such a client driver is required to register with the USB driver stack. After registration, the client driver must query the underlying USB driver stack to determine whether the stack supports the required capability. To facilitate those operations, the following KMDF-specific methods and WDM routines have been included in the WDK for Windows 8:

T-mobile Usb Devices Driver Updater

New Routines for Allocating and Building URBs

Windows 8 provides new routines for allocating, formatting, and releasing URBs. The URB structure is allocated by the USB driver stack. If the underlying stack is the new USB driver stack, the URB is paired with an opaque URB context. The USB driver stack uses the URB context to improve URB tracking and processing. For more information about the routines, see Allocating and Building URBs.

The new routines are as follows:

• USBD_AssignUrbToIoStackLocation routine to associate an URB with an IRP. This routine only applies to WDM client drivers.

In addition to the routines in the preceding list, there are new KMDF-specific methods for URB allocation. For KMDF-based client drivers, we recommend that you call,

• The WdfUsbTargetDeviceCreateUrb method (instead of USBD_UrbAllocate) to allocate an URB.
• The WdfUsbTargetDeviceCreateIsochUrb method (instead of USBD_IsochUrbAllocate)to allocate an URB for an isochronous transfer. Those calls allocate a variable-sized URB that is based on the number of isochronous packets required for the transfer. For more information about isochronous transfers, see How to Transfer Data to USB Isochronous Endpoints.

New User Mode I/O Control Requests for USB 3.0 Hubs

Windows 8 provides the new IOCTLs that applications can use to retrieve information about USB 3.0 hubs and their ports. The new IOCTLs are as follows:

By sending the preceding I/O requests to the USB driver stack an application retrieve the following set of information:

• Hub descriptors
• Properties of all ports and companion ports
• Operating speed of a device that is attached to a port

New Compatible ID for WinUSB

Device manufacturers can add 'WINUSB' in the firmware (Microsoft OS feature descriptor) so that Windows recognizes the device as a WinUSB device. In Windows 8, Winusb.inf has been modified to include USBMS_COMP_WINUSB as a device identifier string. That modification enables Windows to automatically load Winusb.sys, as the function driver for the device, as soon as the device is detected. For more information, see WinUSB Device.

New Visual Studio templates for USB client drivers (*New for Beta)

Microsoft Visual Studio 2012 includes USB User-Mode Driver and USB Kernel-Mode Driver templates that generate starter code for a UMDF and KMDF USB client driver, respectively. The template code initializes the USB target device object to enable communication with the hardware. For more information, see the following topics:

For more information, see Getting started with USB client driver development. Extend your driver by performing Common tasks for USB client drivers.

For information about how to implement UMDF and KMDF drivers, see the Microsoft Press book Developing Drivers with the Windows Driver Foundation.

UASP driver

Windows 8 includes a new USB storage driver that implements the USB Attached SCSI Protocol (UASP). The new driver uses static streams for bulk endpoints, as per the official USB 3.0 specification.

Boot support

The Windows to Go feature allows Windows to boot from a flash drive or an external drive. You can boot with your copy of Windows from those drives on various machines.

T-mobile Usb Devices Drivers

Enhanced debugging and diagnostic capabilities

Windows 8 provides new USB 3.0 debugging tools to improve diagnosing USB issues faster. There are new USB 3.0 kernel debugger extensions that examine USB 3.0 host controller and device states. You can use USB WPP and event tracing to analyze USB interactions and troubleshoot USB device issues more easily. Windows 8 supports debugging over USB 3.0. For more information, see Setting Up a USB 3.0 Connection Manually.

New USB-specific failure messages in Device Manager

At times, Windows can fail to enumerate an attached USB device. Typically, enumeration failures occur when requests sent to the USB device fail or the device returns incorrect descriptors.

In Windows 8, when such failures occur, the General tab in Device Manager displays a USB-specific error message that indicates the reason for failure.

The error strings are as follows:

• A request for the USB device descriptor failed.
• The USB set address request failed.
• A USB port reset request failed.
• A previous instance of the USB device was not removed.
• The USB device returned an invalid USB configuration descriptor.
• The USB device returned an invalid USB device descriptor.
• Unable to access the registry.
• A request for the USB configuration descriptor failed.
• A request for the USB device's port status failed.
• The USB device returned an invalid serial number string.
• The USB set SEL request failed.
• A request for the USB BOS descriptor failed.
• A request for the USB device qualifier descriptor failed.
• A request for the USB serial number string descriptor failed.
• A request for the USB language ID string descriptor failed.
• A request for the USB product description string descriptor failed.
• A request for the Microsoft OS extended configuration descriptor failed.
• A request for the Microsoft OS container ID descriptor failed.
• The USB device returned an invalid USB BOS descriptor.
• The USB device returned an invalid USB device qualifier descriptor.
• The USB device returned an invalid USB language ID string descriptor.
• The USB device returned an invalid Microsoft OS container ID descriptor.
• The USB device returned an invalid Microsoft OS extended configuration descriptor.
• The USB device returned an invalid product description string descriptor.
• The USB device returned an invalid serial number string descriptor.

T-mobile USB Devices Driver

Related topics

T-mobile Usb Devices Driver Wireless

New for USB Drivers
Universal Serial Bus (USB) Drivers