Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 72
Considerations for MTP
To control devices that use MTP an application must get a handle to the device and control the
device through the MTP service. The service handles are found through the following APIs:
• MediaGetDeviceHandle
• MediaBrowseGetItemObjectHandle
• MediaGetItemObjectHandle
These APIs are defined in public\automedia\sdk\inc\automediacoreex.h.
Applications can issue commands directly to the device handle using MTP IOCTLs. All of the
standard, extended, and proprietary MTP IOCTLs are supported. Unlike iPod devices, there is no
passthrough state when calling directly to an MTP device. An application could cause
performance or other issues if using passthrough while the MTP device is being heavily used for
other functions, such as indexing.
Device Lab
Microsoft has created a device lab to help facilitate compatibility between Windows Embedded
Automotive 7 and a growing number of media devices, including devices under development by
automakers. The Device Lab tests approximately 400 phones and 150 media players each year
to ensure that the Windows Embedded Automotive platform works with the latest devices. Each
release of the Automotive platform includes test reports and feature compatibility statements
for each supported device.
Staff members from the Device Lab select devices for testing from markets in North America,
Europe, and Asia based on several elements, including:
 Popularity/sales figures
 Mobile operator distribution and supported technologies
 OEM/customer request
 Compatibility complaints from end users
The Device Lab staff considers devices to be compatible devices if
there is a test report listed for the device on the Automotive results
website on or before the release date of each new version of the
Automotive platform. A compatible device should function as
reported on the results website.