MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for example portable video players.

Media Transfer Protocol (commonly referred to as MTP) is part of the 'Windows Media' framework and thus closely related to Windows Media Player. Windows Vista has built-in support for MTP. Support for Media Transfer Protocol in Windows XP requires the installation of Windows Media Player 10 or higher. Apple and Linux systems do not support it natively but have software packages to support it.

To install the driver you will need to go to the device manager. You can do this by hitting Windows + X on the keyboard and then clicking 'Device manager'. Plug in your device. In the device manager you will have to look for a device named simmilar to your hardware. Right click on it and click 'Update Driver Software'. The USB drivers help us to connect our phone to the computer and perform tasks like transferring data, syncing your device with a PC. They help us to connect our Android devices to tools like Odin, Sony Flash tool, and SuperOneClick. The interface behind it, which is the interface between the device drivers and operating system between device and device drivers, there’s no change to that. That has held seamlessly for 20.

The USB Implementers Forum device working group is presently working on standardizing MTP as a fully fledged Universal Serial Bus (USB) device class. When that process is complete, MTP will be a USB device class peer to USB mass storage device class, USB Video Class, and so on.

-->

Drivers Revolution Education USB devices

Summary

How to use the DeviceWatcher object to detect devices
How to open the device for communication
How to close the device when you are finished using it

Important APIs

When you write a UWP app that interacts with a USB device, the app can send control commands, get device information, and read and write data to/from bulk and interrupt endpoints. Before you can do all that, you must find the device and establish connection.

Before you start...

This is the first topic in a series. Before you start this tutorial, you must have created a basic Visual Studio project that you can extend in this tutorial. Read Getting started with UWP apps for more info.
Code examples are based on the CustomUsbDeviceAccess sample. You can download the complete sample from this code gallery page.
The USB device used in tutorial is the SuperMUTT device.
In order to use the Windows.Devices.Usb namespace to write a Windows app that interacts with a USB device, the device must have the Winusb.sys driver loaded as its function driver. Winusb.sys is provided by Microsoft and is included with Windows in the WindowsSystem32drivers folder.

Flowchart: Finding the device

To connect to a USB device, you must first find the device based on various discovery patterns and then connect to it:

Connect to any USB device with a specific device interface GUID.
Connect to a USB device with a particular Vendor ID and Product ID and that has a specific device interface GUID.
Connect to a USB device with a particular Vendor ID and Product ID without knowing the device interface GUID.
Connect to a USB device which has known device class.

Key concepts

What is a device interface GUID?

A kernel-model driver, during its initialization, register and exposes a GUID called the device interface GUID. Typically, the app uses the exposed GUID to find the associated driver and its device, and then open a handle to the device. The retrieved handle is used for subsequent read and write operations.

However, in the case of Winusb.sys, instead of the driver exposing the device interface GUID, it can be provided in one of two ways:

In the device's MS OS descriptors. The device manufacturer sets DeviceInterfaceGUID as a custom property in the extended properties descriptor in the device. For more details, see the 'Extended Properties Descriptors' document in Microsoft OS Descriptors.
If you installed Winusb.sys manually through a custom INF, the INF registered a GUID in the INF. See WinUSB (Winusb.sys) Installation.

Drivers Revolution Education Usb Devices Pc Camera

If a device interface GUID is found for the device, your UWP app can find all devices that match that device interface GUID.

How is USB device identification shown in Windows?

Every USB device must have two pieces of information: vendor ID and product ID.

USB-IF assigns those identifiers and the device manufacturer must expose them in the device. So how can you obtain that information?

Even when the device doesn't have a device driver loaded, that is, Windows detects it as an 'Unknown Device', you can still view the identifiers in the Device Manager in the Hardware Id property value. That value is a combination of those two identifiers. For example, for the SuperMUTT device, the Hardware Id is 'USBVID_045E&PID_F001'; vendor id is '0x045E' and product id is '0xF001'.
If there is an INF for the device, obtain that string from the Models section.
You can inspect various registry settings. The easiest way is to see the
HKEY_LOCAL_MACHINESYSTEMControlSet001EnumUSB<hardware id>
For more information, see USB Device Registry Entries.
Hardware ID is used by the app manifest to identify the device.
<Device>

Your UWP app can find all devices that match a specific vendor and product ids. You can narrow the search results by specifying the device interface GUID.

What are USB device classes?

Most USB devices conform to device class specifications approved by USB-IF. By using those specifications, devices of similar nature can exhibit their functionality in a standard way. The biggest advantage of this approach is that the device can use a Microsoft provided in-box class driver or the generic Winusb.sys driver.

Some devices might not follow a USB-IF specification. Instead they expose vendor-defined functionality. For such devices, either the vendor must provide the device driver or Winusb.sys can be used.

Whether a device is vendor-defined or conforms to a device class, it must describe this device class related information:

Class code: Indicates the device class to which the device belongs.
Subclass code: Within the device class, indicates the subclass of device.
Protocol code: The protocol that the device uses.

For example, the SuperMUTT device is a vendor-defined device and that information is indicated by class code is FF. If your device shows class code as FEh, subclass code as 02h, and protocol code 00h, you can conclude that the device is a class-compliant IrDA bridge device.Your UWP app can communicate with devices that belong to these device classes:

ActiveSync
CdcControl
DeviceFirmwareUpdate
IrDA
Measurement
PalmSync
PersonalHealthcare
Physical
VendorSpecific

Your UWP app can find all devices that match a specific set of class, subclass, and protocol codes.

Get the Advanced Query Syntax (AQS) string for the device

Generate an advanced query string (AQS) that contains identification information about the device that you want to detect. You can generate the string either by specifying the vendor/product IDs, device interface GUID, or by the device class.

Drivers Revolution Education Usb Devices Wireless

If you want to provide the vendor ID/product ID or the device interface GUID, call any overload of GetDeviceSelector.
In the example of the SuperMUTT device, GetDeviceSelector retrieves an AQS string similar to this string:
'System.Devices.InterfaceClas

Drivers Revolution Education USB Devices